Hi all, I have been following the progress on Bering-uClibc4 with some interest. Kudos to Andrew and the team for what has been achieved so far! It seems that we are close to having a stable v4 platform. For me a 2.6 Kernel, Shorewall 4.x and excellent IPv6 support are all important, and the extra size is not a big problem.
We will need some new user (and developer?) documentation for Bering-uClibc4, at least to reflect the differences from v3 and preferably to improve on what we have already. I would like to volunteer to help with this. At the moment our master documentation source is maintained in DocBook format and converted to HTML for on-line viewing. Personally I like DocBook and the ability to convert to HTML, ASCII, PDF etc. from one master source, but not everyone is familiar with the DocBook markup syntax. Many other projects have switched across to Wikis for their documentation - for example see http://www.mythtv.org/wiki - so maybe we should consider that? SourceForge can provide MediaWiki as one of their "Hosted Apps". Team members might be more inclined to contribute or correct documents if the process is easier, and MediaWiki markup is widely used and not hard to learn. Then again, maybe we should stick with DocBook? What about the structure of the documentation? Today we have an Installation Guide, a User Guide and a Developer Guide. I think that the Developer Guide should definitely be separate but to me the boundary between the Installation and User Guides is less clear - should they be combined? What other improvements should we aim for? davidMbrooke ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ leaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-devel
