On Thu, Dec 12, 2013 at 11:30:02AM +0100, Michal Hrusecky wrote:
Michal Hrusecky - 15:56 11.12.13 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 - 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) + people are more familiar with wiki than with asciidoc * asciidoc could support multiple formats for easier printing/offline/mobile browsing, although I don't think this is important, just a cherry on top
But I would say that this is definitely a good idea to discuss :-)
So, let's make cons & pros list, or wiki vs github list. Wiki is good for collaborative documentation, but for something like RFC, we probably want something less changeable, but that could be arranged in the wiki as well probably...
Wiki: Pros: * people know how to write there * we have it already Cons: * we would have to setup some rights system and test it * hard merging and discussion of changes * not easy to prepare full OSEP, review it and merge it
Github: Pros: * easy way to merge and review changes * easy way to submit new OSEP * rights management for free * we can accept only full proposals Cons: * not everybody knows asciidoc * yet another place for documentation although little promotion could cover that
What did I missed?
Wiki: Pros: * people know how to write there * we have it already + * easy way to review changes ever heard about page history? + * easy way to submit new OSEP wiki is designed for making submissions easy to anyone
Cons: * we would have to setup some rights system and test it why? anyway wikimedia does support that since beggining [1] * hard merging and discussion of changes have you ever hear about Talk pages? but discussions should happen on ML by default * not easy to prepare full OSEP, review it and merge it cm'n, wiki is designed for this use case - or do you really expect dozens of pull requests for documentation?
The easiest approach is 1.) $OWNER write OSEP proposal and put it into wiki with proper Category 2.) Then sent it as an attachement to ML 3.) Changes are merged by $OWNER back to wiki 4.) Once agreed, OSEP is accepted 5.) profit! I really do not see any particular advantage of git in this specific case. And btw all OSEPs can be watched, so people can be warned on edit. Please KISS! [1] http://en.wikipedia.org/wiki/Wikipedia:Blocking_policy Regards Michal Vyskocil -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org