On 12/11/2013 03:10 PM, Michal Vyskocil wrote:
I appreciate such move from unstructured mess of various email threads and discussions to something much easier to deal with and to follow!
Thanks.
Because the OSEPs are maintained as text files in a versioned repository, their revision history is the historical record of each proposal footnoteref:[note_repo, https://www.github.com/TBD].
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?
Yes, I think you're right. As long as proper access permissions work in the wiki and if nobody says anything against this idea in the following days, I'm changing that into the OSEP (I'll have a look first just to check how permissions work there and if they're good enough for our needs).
OSEP Types ----------
There are two kinds of OSEP:
- An _Informational OSEP_ describes an issue, or provides general guidelines or information to the openSUSE developers, but does not propose a new feature. Informational OSEPs do not necessarily represent a community consensus or recommendation, so users and implementers are free to ignore Informational OSEPs or follow their advice.
What is the reason to spent a time on creating and discussing a proposal, which will ends in informational state? Do you have any example, where the process is worth effort, but the result is not that important?
Think something like: http://www.gentoo.org/proj/en/glep/glep-0057.html It's mainly a series of definitions so that other GLEPs can use those concepts.
Once a draft is written in the style described below, it should be presented to the _opensuse-factory_ mailing list.
it MUST be presented on opensuse-$FOO mailinglist - having mandatory OSEP not beeing discussed in a public is a no-go.
Completely correct. I think I originally wrote there "it should be presented to the opensuse-factory or opensuse-project mailing lists", then changed it to just opensuse-factory to have just one entry point for OSEPs, but in any case, you're right it MUST say MUST. I won't send again the fixed OSEP-0001 in order not to spam the list (at least, not for a few days so that we can collect more fixes), but consider your changes included. Greetings, -- Antonio Larrosa -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org