Change Details

I'll explain this later in more detail (I'm doing a demo) but we really miss a high level architecture overview for potential technical contributors. They simply get lost in all our diversity of options, languages, components, etc.

We really miss a high level architecture overview of MediaWiki core and basic extensions. Reasons to have one: * MediaWiki and relatives form a very complex family. https://www.mediawiki.org/wiki/Developers/Maintainers lists 210 components only for core, and there is no subdivision to be seen. Without a shared high level map it is a lot more complex to have shared high level discussions and plans. * New potential contributors need an overview to understand the basics of MediaWiki and find the area where they want to work on. Such diagram would be really helpful to identify an area as a starting point. After many conversations with many newcomers with different skill levels, we know that most of them get simply lost / overwhelmed in their first contact. * Defining areas is a premise required to discuss whether we want to have architects / owners / maintainers for a specific area that would worh with the #ArchCom or be part of it.

I'll explain this later in more detail (I'm doing a demo) but we really miss a high level architecture overview for potential technical contributorsWe really miss a high level architecture overview of MediaWiki core and basic extensions. Reasons to have one: * MediaWiki and relatives form a very complex family. https://www.mediawiki.org/wiki/Developers/Maintainers lists 210 components only for core, and there is no subdivision to be seen. They simply get lost in all our diversity of options,Without a shared high level map it is a lot more complex to have shared high level discussions and plans. * New potential contributors need an overview to understand the basics of MediaWiki and find the area where they want to work on. languages,Such diagram would be really helpful to identify an area as a starting point. componentsAfter many conversations with many newcomers with different skill levels, etcwe know that most of them get simply lost / overwhelmed in their first contact. * Defining areas is a premise required to discuss whether we want to have architects / owners / maintainers for a specific area that would worh with the #ArchCom or be part of it.