On 10/8/08, Andreas Hartmann <[EMAIL PROTECTED]> wrote: > Thorsten Scherler schrieb: > > Extending a publication is for me dev stuff, meaning that should be > > discussed on this list. > > IMO it would belong on the user list. It should only be posted to the dev > list if it contains a suggestion how to improve Lenya to better suit this > particular use case. > -- Andreas
This illustrates my point. Two of our best contributors do not agree what belongs on the dev ML. How can we expect people unfamiliar with the project to understand the purpose of the current MLs? Someone editing HTML, CSS, XSL, etc. labels themselves a developer. Others need help with writing Generators and InputModules = developers. None of this work will be integrated into the Lenya project, yet these people post questions to the dev ML. Almost every new "user" of the Lenya platform is a "developer". Explaining that questions are being posted to the wrong ML has not helped; the next new user makes the same mistake. It is obvious to every newcomer that the dev ML is for developing with Lenya, rather than our expectation that the dev ML is for developing the Lenya.platform. I assume we want a ML dedicated to developing the Lenya platform. We know "dev" causes confusion. Any name that can be confused with application development is bad. A new name should exclude application development. Poor choices include: "application", "code", "dev", "development", "programming". ATM, the MLs are not very active so the project does not need separate "users" and "application developers" MLs. Will application developers post to the "user" ML if the other ML is obviously not appropriate for their questions? We could name the other list to obviously include both users and application developers: [EMAIL PROTECTED] - For questions about using or developing with Lenya. [EMAIL PROTECTED] - Discussions about contributions to the Lenya platform. I would like the confusion about the dev ML to end. Do we want an ML just for developing the platform? If no, end this discussion and we will continue to handle both application development and platform development on the dev ML (and wonder why we have a User ML.). If yes, choose ML names with purposes obvious to people unfamiliar with OSS traditions. solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
