Hi Pharo Developers, I am looking to better understand the decision-making and planning process for the Pharo core image. I have a few architectural ideas and new feature concepts, and want to ensure I align with the community's vision or determine if I should build them independently. Could anyone share insights on the following: 1. The Core Decision Process: How are major changes to core classes, refactorings, or large feature additions typically proposed, debated, and approved? Is there a formal RFC/PIP (Pharo Improvement Proposal) process, or does this primarily happen via GitHub issue triage? 2. Prioritization & Roadmap: How does the Consortium or core team decide what gets integrated into the next major Pharo release versus what gets left to external ecosystems? 3. Contribution Best Practices: What is the recommended path for an individual contributor to pitch a significant design change? Should I present prototypes on this mailing list first, open a GitHub issue, or discuss it on Discord? Ultimately, my goal is to figure out whether my ideas belong as core contributions or if they are better suited as separate, independent libraries managed via Metacello. For greater context, I’m working on a Smalltalk environment where the current global system is broken up into separate projects: a Smalltalk OS or platform, a programming environment, and various apps. Thank you for your time and guidance! Warmest regards, Alfonso Guerra
