[EMAIL PROTECTED] schrieb:
Hi All,

Lenya is a platform.  Our community is:
Users - Editors and Administrators using the GUI.  They almost never
post to the MLs; they are typically supported by an administrator at
their organization.  We rarely see posts like "How do I edit a page?"

Developers - Application developers adding functionality to
Publications.  We expect their questions on the user ML; they usually
post to the dev ML.

Platform Developers - Committers and others contributing to the Lenya
platform.  We expect the dev ML to handle these discussions, but
questions from the second group interfere.

I propose a new ML for discussing Lenya platform development.  While
"dev" is traditional for a project's development team,

it's not actually, but rather the name "dev" is misleading, because people associate it with "developers". In my opnion it should be renamed to [EMAIL PROTECTED] because this list should not be reserved for the development team of lenya but rather be about development, no matter if someone is part of the development team or not

The same is true for "users", which I think should be renamed to [EMAIL PROTECTED]
the name
confuses our community.  An ML named "platform" or "base" would avoid
the confusion.  ("core" might seem to exclude modules, translations,
and other important platform work. "commits" has a specific use.)

Thoughts?

I don't think the current traffic is enough reason to introduce another mailing list, but I rather think
one should rename the mailing lists as suggested above

users -> usage
dev -> development

and add a clear description to

http://lenya.apache.org/community/ml.html

which would make it clearer (than without description)

Cheers

Michael
solprovider

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to