Hi Reid, So far I have only updated: http://www.yoper.com/wiki/index.php?title=Developers:Local_Yoper_Build_Environment http://www.yoper.com/wiki/index.php?title=Proposal_for_Package_List_Formalization
I have created an updated RPM build guide I am still working on here: http://www.yoper.com/wiki/index.php?title=Developers:RPM_Howto_2.9x%283.0-Beta%29# So If you would like to wikify them go ahead :) Hopefully they aren't too rough. For the Main Page, Install guides should probably be in user support and perhaps there should be a Projects page, listing all the different projects happening at the moment, like YIS, E17 etc. I would perhaps change the Development Guides heading to a link to the Developer guide page, where we can list out all the dev guides and have better descriptions of what each is about. And change the order of them so Newbies can start with the first and by the time they reach the last guide they are Pro's. Just my two cents for the Main Page :) Kaneri Warren aka lordtweety On 11/14/06, Miller, Reid A. <[EMAIL PROTECTED]> wrote:
Kaneri and others, I would like to see the front-page navigation to the development sections slimmed down a bit. Visit http://www.yoper.com/wiki/index.php?title=Main_Page <http://www.yoper.com/wiki/index.php?title=Main_Page> and compare the left-hand green box (which is support) to the right-hand blue box (which is development). I would like to see the development box shorted by about 40%. This may require some restructuring of the development area... which I think is much needed in addition to Kaneri's effort to update the guides. If someone from the development team, more knowledgeable than myself on development issues, can think up a development guide structure schema I will be glad to put my wiki syntax knowledge to work and rearrange the guides. If even it's this kind of text file, This is main |-- Sub category |-- Sub category This is title #2 |-- Sub category Or a written description or whatever... I can try to structure it properly. Because for me, a linux-familiar user looking to get his feet wet in development, that section is confusing and difficult for me to approach. Simply because of the structure. Also I will follow Kaneri's edits up and proof/wikify them. That'll be my contribution to this effort :) --Reid Miller (oreo_masta) _____ From: Kaneri Warren [mailto:[EMAIL PROTECTED] Sent: Fri 11/10/2006 10:32 PM To: yoper-dev Subject: [yoper-dev] Documentation Hi Everyone, Over the next couple of weeks I am going to try and update all the packaging and build server guides in the Yoper Wiki. So if anyone has any particular requests or ideas feel free to send them to me at lordwteety at gmail dot com or post them to the list. I'll try to incorporate them or I'll let you know why I haven't. Also if you see something isn't quite right let me know, I'm not the most experienced packager out there :D So it might not be perfect. I am aiming it at people who aren't already packagers but might want to do some packaging. The idea is to make it easy to setup and start so more people are willing to help out. As well as to fill in any gaps our understanding of what is happening. Cheers, Kaneri Warren aka lordtweety _______________________________________________ yoper-dev mailing list [email protected] https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev <https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev> _______________________________________________ yoper-dev mailing list [email protected] https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
_______________________________________________ yoper-dev mailing list [email protected] https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
