I'll respond to a few of these with my understanding. On 3/13/07, Ricardo Nabinger Sanchez <[EMAIL PROTECTED]> wrote: > On Mon, 12 Mar 2007 14:14:30 -0700 > mpb <[EMAIL PROTECTED]> wrote: > > * Potential users > > * Beginning users > > * Advanced users > > * Gobo devel team > > I'd merge Advanced users + Gobo devel team, unless there's a special reason > for this separation. :)
I think there is room for a separation, and I would want to know what I was targeting if I was writing a page. Advanced users (as defined by mpb earlier) don't care how to commit patches to the scripts cvs. Devs don't need to know about PrepareProgram -t (because they already do). Remember, "advanced users" just means people who are comfortable with Gobo, and can write a few Recipes or submit a bug report. > But this would be done at the wiki or the wiki would provide extensive > documentation of these procedures? Ie, details about how to report clearly a > bug, how to create recipes and how/where to submit, and how to adapt Gobo to > their need? Sounds like the wiki will just provide information on *how* to do these things. e.g. "If you encounter a bug, please go to bugs.gobolinux.org and fill out a report. Don't forget to include which version of Scripts you have." etc. From mpb's reply to Carlo: "The Wiki doesn't have to do these functions, it merely has to tell advancesd users where and how to do them." > I wouldn't have found Roadmaps under Community. :) > > Doesn't it worth a Development category, which may further include info about > the previous releases (what they had packaged in), and what's being > considered for the new ones (alongside the roadmap itself, which usually > provides a not-much-detailed big-picture of the coming releases)? There should definitely be a roadmap targeted at potential and new users, to help them get excited about what's coming, and realize that Gobo is headed on a good path with active development. If the devs find it useful to have a separate roadmap, one of them will make one :). The reason it's in community is because that's the category that new and potential users will be hanging around in. > > Step 7) Implement maintenence tracking techniques > > ... > > This page [[Last Reviewed March 2007]] at Scripts version 2.6.2 by mpb. > > > > This will allow tracking (via back-links) of when pages were last > > reviewed, and will allow older pages to be reviewed and updated first. > > Is there an automated way to do that or will require explicit information by > who is updating it? The person updating it must manually put in the date they made an update (unless Nick can work some template black magic :) ). However, this is only supposed to apply to a major check/update by an experienced member of the WikiTeam, so it seems having a manual tag is the only way to distinguish it from a random edit anyway. The process of viewing a list of all the "last updated Mar '07" pages is automatic once the tags are in place. _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
