Re: Get Involved and related wiki areas
Ted Leung <twl-6zGkXsw2EZWGJGYlWa3Ukdi2O/[email protected]>
| Newsgroups | gmane.org.osaf.general |
|---|---|
| Message-ID | <[email protected]> |
Hi Sheila, At a high level your proposal looks fine to me. See inline for some questions on the details: On Jun 14, 2007, at 10:06 AM, Sheila Mooney wrote: > So I have been tasked with driving the effort to organize the Get > Involved wiki areas. Of course when I started to look at this, > there are a bunch of related links like For Developers, the FAQs > etc that we should look at too. As a first step I wanted to do an > inventory of the current links and what pages they go to. Here is > the current hierarchy.... > > + We have a desktop landing page with links to.... > + Get Involved page > + For Developers page > + Product FAQ > > + We have a Cosmo landing page with links to.... > + Get Involved page > + For Developers page > + Product FAQ > > For each of the landing pages, these links point to different pages > which are customized specifically for the particular product or > project. > > + The Product, Teams, Projects all have links on the left nav to > Get Involved, For Developers and the Product FAQ. but they are not > currently active. These pages are more general so we don't have the > context of pointing to a particular FAQ or Get Involved page. > > Mimi and I chatted and we came up with the following proposal for > Preview. > > Proposal: > > + Create single main pages for Get Involved, For Developers and the > FAQ. This means we can link to this single page from the main > landing page as well as all the wiki pages. We are looking at a > single centralized landing page for Preview anyhow and won't have > the 2 main pages that we do now. > + Obviously there is different information specific to the end-user > related info and the server specific information so we would > structure these pages with sections or a table of contents so users > can easily get at the information they need. Alternatively, we > could keep the main page brief and create links to secondary pages > for product specific info. > + In keeping with this structure we would generalize the "log a > bug" and "report a problem" information as well. > > Mimi and I did a brainstorm of what type of information would go in > each page.... > > - Get Involved > - IRC > - Lists > - Feedback > - Log a bug > - Roles - ways to contribute > - Projects I'm not sure what would go here - is this just a list of the various OSAF projects? > - Help us page I think that we need an overhaul of our approach to "Help us" -- I was expecting to tackle that -- is that in line with your thinking here? > - Governance > > - FAQ > - One FAQ with sections > - End user chandler desktop/hub/casual collaborator > - Server What about Developer FAQ questions? Does that go here or under For Developers > > - For Developers > - One page with sections > - Server > - Web front end > - Desktop I think that we could start with one page here, but that we will end up needing a page each instead of a section each. But this is probably a good start. Ted _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "General" mailing list http://lists.osafoundation.org/mailman/listinfo/general