I would like to participate too.
Do you think its necessary to prepare some topics in advance for the meeting?
I dont know how long it will be or how much time the team will have for questions afterwards but i think there are lot of people in the community that have things they would like to ask, so maybe it would be useful to have that information here already to avoid repeating information or questions and you could use this information too to better organize the meeting.
A bit of context on why I’m joining: I’m a developer on a small team that’s been testing and working on Corteza for around six months as paying users.
We see real potential in the platform and would like to keep investing in it, but we’re also at a point where we need to be honest about a few things before we commit to it long-term.
The community meetup feels like a good opportunity to ask those questions in the open and learn from however the team and other community members answer.
I’d like to flag the topics I’m hoping to raise so the Planet Crust folks can come prepared and bring whoever is best placed to answer (it would be especially helpful to have someone from engineering and/or product, not just community-facing). The areas I’d most like to discuss:
• Strategic direction — what the next 12–24 months look like for Corteza, and how the @human project relates to it (separate product, successor, or something in between)
• Roadmap visibility — whether public roadmaps are likely to come back, and what level of detail customers/community can expect going forward
• Active development — what’s been shipped recently and what’s planned for the coming months
• Deployment & environment management — recommended patterns for moving namespaces and modules between dev/staging/production without the ID-conflict pain that currently breaks references on import
• Workflow limitations — when custom code is recommended over workflows, and what limitations teams typically hit at scale
• Extensibility & integration — the supported way to extend Corteza, API stability for long-term integrations, and how heavily-customised customers typically operate (mainline vs forks)
• Documentation — plans for closing the gap between docs and current behaviour, especially around page block development, functionalities, and deployment topology
• Community engagement — how community contributions and PRs are being handled going forward
A couple of logistical questions while I’m here:
How long is the meetup scheduled to run? I’d like to plan my questions appropriately and not hog airtime if it’s shorter than expected.
Will there be someone from engineering or product on the call who can speak to the technical and roadmap questions specifically?
For anyone interested but unable to attend, I’m planning to post a written summary of what was discussed in the days after the meetup so the answers are accessible to the wider community.
If anyone reading this has related questions they’d like raised, drop them in this thread and I’ll do my best to fit them in.
@nmccarthy — could you confirm those last two (duration + who’ll be on the call) before Thursday?
