Henne Vogelsang - 13:25 12.12.13 wrote:
Hey,
On 11.12.2013 15:56, Michal Hrusecky wrote:
Michal Vyskocil - 15:10 11.12.13 wrote:
So do you want to maintain OSEPs in some github repo? Would not that be overkill compared to wiki, which provides the same set of features you want?
hmmm, interesting idea, never thought about wiki as I know Gentoo does it this way. Maybe somebody else would have some idea about the reasoning behind. Thinking about using wiki, my first few thoughts:
- we would need to create a new namespace and limit access and check how access rights in wiki works - means some work, but once set up, could work
I don't see why you would need a new namespace. You can simply have a decent site template with categorization in openSUSE: and a Portal to tie it all together.
hmm, to make it findable and reachable and not that messy?
- harder/trickier submission of new OSEPs and changes * preparing somewhere, asking for a page/access, copy the result over vs pull request (which we can even link in mailing list discussion)
Hm why would you need access rights at all? I could just start openSUSE:My_proposal-0001 in the category Draft_OSEPs, show it to the "key people" and if they like it, propose it to the mailing list. Once it's discussed, you can reference the discussion and change the category to Accpeted_OSEPs etc. etc. No need for access rights....
To ensure nobody randomly messes up with it without prior agreement on mailing list and to make sure all changes are agreed upon and discussion leading to it is documented. What would prevent me from putting document saying that everybody needs to wear pink hat's into that category? It wouldn't pass the review probably, but apart from that? -- Michal HRUSECKY SUSE LINUX, s.r.o. openSUSE Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org