So we need to come up with a policy for the community creating new namespaces on the wiki.
Namespaces are like User:, Talk:, and Archive:. Archive: is a good example of a custom namespace that doesn't come built with MediaWiki that we decided we needed.
Mike McGrath wants to create a Zodbot: namespace so we can have a '.felp' command with Zodbot that'll pass a wiki link back to a user. The first step for us is making that namespace...
Here's my thinking -- 1. Namespace and reasoning gets proposed to fedora-wiki (like I did up there). Perhaps we need something like [Namespace] at the beginning of the subject line. 2. It gets discussed. 3. It gets voted on by FDSCo or other notable people or on the mailing list. (This starts the part that I'm not sure about.) 4. A ticket gets filed with Infrastructure to create the new namespace. Infrastructure will be instructed that certain people must link to the mailing list thread archive that shows that the prooposal was approved by the Docs project within that ticket. 5. Profit!
What do you all think?
On Wed, Dec 10, 2008 at 08:18:52AM +0800, Yuan Yijun wrote:
What makes a namespace?
A namespace, as defined by the Docs project, is something that doesn't fit in the main namespace (the lack of a namespace, per se).
The main namespace contains documentation and helpful things for end users and developers, which is mostly what's there now.
On Tue, Dec 09, 2008 at 04:13:39PM -0600, Ian Weller wrote:
So we need to come up with a policy for the community creating new namespaces on the wiki.
Namespaces are like User:, Talk:, and Archive:. Archive: is a good example of a custom namespace that doesn't come built with MediaWiki that we decided we needed.
Mike McGrath wants to create a Zodbot: namespace so we can have a '.felp' command with Zodbot that'll pass a wiki link back to a user. The first step for us is making that namespace...
I don't get what the Zodbot: namespace does?
Here's my thinking --
- Namespace and reasoning gets proposed to fedora-wiki (like I did up
there). Perhaps we need something like [Namespace] at the beginning of the subject line. 2. It gets discussed. 3. It gets voted on by FDSCo or other notable people or on the mailing list. (This starts the part that I'm not sure about.)
We probably can do it via consensus on the list, no voting required. If it gets contentious, then ... well, I suppose having Docs leadership rule at that point works as well as anything.
- A ticket gets filed with Infrastructure to create the new namespace.
Infrastructure will be instructed that certain people must link to the mailing list thread archive that shows that the prooposal was approved by the Docs project within that ticket. 5. Profit!
What do you all think?
Lightweight should work here, since not many people are requesting new namespaces. We mainly need to explain to people why their idea doesn't really need a namespace, and here is what to do instead -- I figure that covers most requests we'll have until people truly understand the value/reason for a separate name space.
- Karsten
-
Ian Weller -
Karsten Wade -
Yuan Yijun