On 12/12/2013 07:55 AM, Michal Hrusecky wrote:
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?
Makes me wonder why we do not have a million wiki pages that require everyone to wear pink hats. Do we really have such a big trust problem as you are displaying here? If that is the case we have other issues to discuss that would, IMHO, take precedence over everything else. The wiki is open, enables easy collaboration and has a history, thus it is still easy to see who made the changes. And the person that added the pink hats requirement can be asked why that would be a potentially good idea. Later, Robert
-- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org