On Sun, 2006-01-08 at 13:31 -0600, Lance Albertson wrote: > > Indeed it's GDP area but to expose project goals, status and low level > > docs isn't even related with GDP. We can't maintain the high level of > > docs like GDP does and it's not even your goal. I think the public wiki > > idea will improve the communication between devs and users, add goals > > and show the status of projects. IMO GDP can't do much in this area > > simply because they don't have much to do about this and they have of > > course high level of docs to maintain. > > I had thought about creating some kind of a site like this, but not > necessarily in a wiki form. I don't like the idea of letting users add > random docs. There's too much room for error and how do you deal with > accountability? There has to be a developer who either will take the > time to maintain it or accept responsibility for any errors it may have. > I like the idea of having an area for herds to keep track of their > internal thing, but I fear it will just end up replacing what the GDP > (and our www site) does. Its too easy for them to just start adding docs > there instead of on www because its 'too hard' to deal with guidexml. > Like i said GDP maintain High Level Docs i think no one want's to replace that. Herds docs will not replace GDP. Even if that's for somehow happen it could be easy backported to GDP maintaining an High Level doc. A few months back Diego "Flameeyes" started writing maintainer docs for some applications, X team started their own docs about modular X, amd64 team does have their docs and it doesn't have anything to do with GDP or will replace them. An example for this is the AMD64 FAQ that is part of GDP and all writen by AMD64 team. > If the issue here is guidexml, lets figure out the problem. We need to > define what exactly is the problem before we decide on an > implementation. Is the problem that there's no central place for herds > to put updates/goals/etc? Is the problem that there's no easy way for > users to submit new docs for people to use? Is the problem that guidexml > hampers development time with regard to creating docs and you wish to > have a better/easier way to create such docs? > Indeed guidexml isn't a fast method to write information but we should keep it for high level docs of course. > Simply saying 'we need a public wiki' is great an all, but I'd rather > ask 'What problem(s) does the wiki solve' before we even get farther. > There might be better ways to solving the problem other than putting up > a wiki. > I think the wiki will have users cooperate directly into herds, herds can expose all types of information there (like status and future goals) and it could be useful for feature requests, ideas, interaction between everyone and it's a simple method for doing all this stuff. -- Luis Medinas <[EMAIL PROTECTED]> http://dev.gentoo.org/~metalgod Gentoo Linux Developer: AMD64,Printing,Media-Optical,Sound
-- gentoo-dev@gentoo.org mailing list
