I think that is why before the move of lists to UW uportal-dev required approval to join which included reading a page about the intent of the list. Renaming may be the way to go but we need to make sure we know what we're getting into with changing documentation and such.

-Eric

Cris J Holdorph wrote:
I wonder if we should consider some list renaming.

People consistently post to uportal-dev with questions that are about them "developing" their portal. Look at the list name, think about what those people are doing, it's really not a stretch. "uportal-user" sounds like it might be for people to learn how to login, move portlets around, etc. "uportal-dev" sounds more reasonable when I need to ask a question about how to write a new portlet for my portal.

I wonder if we should have names that help make the distinction between "development of the core framework services" and "development and configuration of portals using uPortal" better.

For example, what if "uportal-dev" was renamed "uportal-framework" and "uportal-user" was named "uportal-admin". I don't really like the name "uportal-admin" but you get the idea. It just feels like the names we currently have will continue to cause us trouble, because they do not match well with the intent of the content to be posted to them, at least from a new-user-to-the-community perspective.

---- Cris J H

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to