i do not think this is reasonable. every piece of code should have (at least one) owner. the idea that you can produce code and then "relinquish" it to someone else was tried in the software industry many times (i believe it was the dominant model in the 70's), and was rejected. anyone who "owns" a piece of the core functionality, regardless if it's implemented as "core" or as "extension", is by definition part of the "core development team".bantu wrote: The development team will package code into extensions as it sees fit. Control over said code is relinquished (or not) as the development team sees fit.
no argument here: first of all, bad code should be deleted, and replaced by good code, not "ripped out".bantu wrote:Ripping out features into extensions is a good idea in my opinion, but a different story. The code properties of legacy code (spaghetti code, non-explicit dependencies, lack of tests, etc.) make doing so rather difficult. I personally would suggest to rather spend time on making the extension system itself more robust in the near future.
i did not suggest to invest heavily in dismembering phpbb right now - my comment was not so much about "what should we do tomorrow morning", but rather "what is the shape of the long-term destination/direction we are moving towards".
i also agree that tending to the extension system itself is high priority, but IMO, the surest way to do so is to try and make sure new development happens, as much as possible, in the form of "extension".
this will help the developers identify any deficiency of the extension system, and augment it - something that's much less likely to happen when they are happily adding more code and more functionality to the central monolith.