On Sat, 2010-10-16 at 12:35 +0100, davidMbrooke wrote: > On Thu, 2010-10-14 at 14:22 -0700, Mike Noyes wrote: > > On Thu, 2010-10-14 at 20:44 +0100, davidMbrooke wrote: > > > > > > Do we have aligned permissions across Trac and Mediawiki? In other words > > > can anyone able to create a Trac ticket also edit the Wiki pages? I note > > > that Trac ticket #1 (should) relates to Documentation... > > > > David, > > No. The SF hosted apps are separate entities that share some common data > > provided from our SF project data. Management, etc. of each SF hosted > > app is unique. > > Thanks for the clarification Mike. That's what I suspected, so probably > any SourceForge user can create a Trac ticket for LEAF?
David, We have control over access. Most/all SF hosted apps allow limiting edit/write access to project users. > I don't have a > problem with that (in fact we want any Beta tester or LEAF user to be > able to report problems) so we should add Documentation as a Category in > Trac. > In fact I see that someone (kp?) has already done that; thanks. KP, Thank you for attending to this task. > > > I suggest we initially edit this page to sketch out the User Guide > > > structure before we create separate Chapter / Sub-Chapter pages: > > > https://sourceforge.net/apps/mediawiki/leaf/index.php?title=Bering-uClibc_4.x_-_User_Guide > > > > > > > Defining structure is desirable. However, I propose we don't spend a > > great deal of time building consensus on structure. The nice thing about > > wiki's is their ability to accommodate change. Scripts for converting > > html and docbook into wikitax are available. With some very basic ideas > > we can convert and present a considerable amount of content to users in > > a short time-frame. We can then tweak structure to meet consensus view, > > while updating content. > > > > Does this proposed method sound reasonable? > > IMHO yes, within reason. I agree we should not delay creating documents > but one big drawback with a Wiki is lack of structure. The last thing we > want is a lot of incomplete and unmaintained Wiki pages and both kp and > I are keen to keep the documentation structure fairly "clean". David, Agreed. Attending to orphan pages in wikis is a major ongoing maintenance task. Limiting their appearance is desirable. > I had good success importing the existing DocBook content into the > Developer Guide chapters in the Wiki using a conversion script and I am > happy to convert more of the User Guide if required (though it will > require more re-work because of the changes from 3.x to 4.x). > > Right now my focus is on debugging 4.x so that I can use it in > "production". I am now close (I hope!) and then I plan to devote much > more time to documentation, since that is easier than fixing code :-) Good to hear. I'll attempt to set some time aside for exporting our old phpWebSite content from html to wikitax. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
