On Thu, 2010-10-14 at 20:44 +0100, davidMbrooke wrote: > On Thu, 2010-10-14 at 20:54 +0200, KP Kirchdoerfer wrote: > > Am Donnerstag, 14. Oktober 2010, 20:29:27 schrieb davidMbrooke: > > > > > >From my reading of the Trac guidance notes the "Version" is where a > > > problem was *found* and the "Milestone" is where it might be *fixed* (at > > > the latest). Would therefore be good to include 4.01 & 4.1 as > > > Milestones. > > > > Understand. Have to confess, I didn't read the docs carefully, instead had > > a > > look how other projects handle it. > > I believe it should be the other way round - it would be good to include > > the > > milestones as versions, cause I do not expect moving to new _versions_ that > > soon, though I expect that we'll have a lot of work with the milestones. > > In either way, I've learned that the versions and milestones have to be in > > sync. > > > Thanks. I am happy as long as they match. > > > > > Suggest we also add "Documentation" as a Component. > > > > I thought about that one myself, but had in mind that the documentation > > will > > be in the wiki, and that you proposed to discuss documenation issues in the > > wiki's comments section. > > (BTW: I've prepared a few chapters from the old docs to add to the wiki, > > but > > still waiting for a more or less final structure. Mostly to see how > > subchapters > > and other nice things can be done :)) > > > So now I feel guilty for not working more on the Wiki documentation :-) > > 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. > 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? -- 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
