On Mon, 2011-03-28 at 23:33 +0200, KP Kirchdoerfer wrote: > Am Montag, 28. März 2011, um 22:48:56 schrieb Martin Hejl: > > Hi again, > > > > I've been wondering - what's the "accepted" approach to updating the > > wiki? Should everybody with write access (I seem to have write access) > > just go ahead, or should there be some discussion about proposed changes > > first? I know, changes in the Wiki can be backed out again relatively > > easily, but just like in CVS (or git, or whatever), that causes extra > > work, that might be avoided by simply talking about changes one wants to > > make. > > > > For now, what I have in mind is to make some minor changes to the > > OpenVPN chapter (since it obviously needs work) - but I don't want to > > alienate those who did all of the work so far, by making some changes > > and "breaking the rules" in the process. > > > > So, I figured I'd ask first... > > > > Hi Martin; > > Write access is restricted to registered LEAF developers only (and for > obvious > reasons you do have write permissions). > > For discussion about wiki content, esp. if you are concerned about new > content, we use the "talk option" in the wiki itself. > > For rules contributing to in the wiki see: > https://sourceforge.net/apps/mediawiki/leaf/index.php?title=Wiki_Contributor_Guidelines > > And yes a backout is every time possible, and it may some work (for David > esp, > who did most of the work on the wiki and had the patience to deal me writing > to the wiki), but every improvement is welcome. > > kp
Hi Martin, Thanks for asking but please go ahead! Many of the existing pages are unmodified copies of Bering-uClibc 3.x content and need correcting and expanding. One good thing about the Wiki is that it is easy to make minor corrections, and to see what has been changed. kp has covered most of the "rules". In my view, correcting or expanding existing pages is always OK. Adding new pages needs more thought, so please "discuss" those here or on a Wiki Discussion page first. It is also possible to raise a Trac ticket for Component = Documentation, useful if a major topic needs to be added. davidMbrooke ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
