Boosters Team/Projects/Integrate all Infrastructure under one Umbrella

From openSUSE

Purpose

Screen Design: openSUSE-Bento

Currently the openSUSE web infrastructure is not perfectly integrated.

The tools grew over time and now the openSUSE project owns nearly twenty sub projects which are mostly independant from each other. This Boosters project will improve the situation here to make the infrastructure more integrated, easier accessible and help people to find stuff they search for.

This topic was discussed on the openSUSE Conference 2009 in Nuremburg, Klaas gave a talk about it.

These is a list of existing infrastructure sub projects:

• forums.opensuse.org
• download.opensuse.org
• users.opensuse.org
• features.opensuse.org
• software.opensuse.org
• build.opensuse.org
• shop.opensuse.org
• news.opensuse.org
• lizards.opensuse.org
• openSUSE Wiki
• zonker.opensuse.org
• build.opensuse.org
• factory.opensuse.org (to be created)
• help.opensuse.org
• my.opensuse.org (portal, to be created)
• more...

We should also aim at integrating projects that are hosted outside the official servers:

• opensuse-community.org
• planet.opensu.se

And it should be possible to add some additional sites afterwards (via request in openfate with considerable amount of votes)

User Qualification Classes

All openSUSE infrastructure sub projects can be categorized in user qualification classes, which reflect basically what guru level users might want to have to make good use of a specific sub project. [Note: the name user qualification class could probably be improved, please go ahead!]

The following three user groups were suggested:

1. Linux Newbies - people starting with Linux and want to learn how to achieve basic things
2. Linux Users - people getting around with Linux very well. They are interested and would be willing to contribute bug hunting and features or help out other users.
3. Linux Geeks - long time Linux people, mostly computer professionals being deep into topics like packaging or development.

Other naming schemes could be "Users", "Potential Contributors", "Contributors", or "New Users", "Power Users", "Contributors".

Other possible scheme can be distinguish users according to the actions they most likely want to do:

• Users
  People searching for information, help, or wanting to report bugs. So these people will be interested in manuals and user tutorials, forums, ...
• Developers
  People actually contributing to the code of openSUSE. They are interested in buildservice, their bugs & features, developers documentation, developers tutorials, ...
• Community
  People helping with promoting openSUSE and people interested in everything around openSUSE. They'll need easy access to the planet openSUSE, news, calendar with upcoming events, tubes.openSUSE, ...

Project Requirements

The Boosters project is considered successful if

• all sub projects use the same design template
• all sub projects offer a direct way to sub projects of the same user qualification class
• all sub projects offer a way to all other sub projects
• which sub project can be accessed directly and which indirectly will be configurable for registered users
• the sub projects are accessible from the landing page http://www.opensuse.org
• The user qualification classes are clearly reflected on the landing page and guide users where they have to go.

Related Links

• Design Concept: Written concept (no text desert!)
• Concept Graphics: Wireframes, Organisation Plans, Mockups