> On Thursday 29 July 2010 20:24:09 Brandon Philips wrote:
> > Lets look at the mission statement of the openSUSE: namespace[1]:
> >
> > "And the openSUSE community's openSUSE: namespace to collaboratively
> > write on documentation for their projects and teams."
>
> http://en.opensuse.org/Help:Namespace
> "openSUSE - Presentation and working pages of our teams, tools and projects.
> Everything for the contributors to our project."
That is a more helpful definition. Maybe the namespace should be
contrib: then? Or perhaps move all of the user facing documentation to
docs:?
> > Possible alternatives:
> >
> > 0. No namespace at all, the openSUSE community exists at openSUSE.org!
> > We have an entire domain to call our own! Why do we need a namespace?
>
> Breaks separation of content on part that is used to present openSUSE to
> casual visitors (majority), part used for troubleshooting which is minority,
> and part for contributors which is even smaller.
As a contributor the namespaces are not helping me and are confusing.
How has Wikipedia managed to create a huge and useful repository without
namespaces?
> We absolutely don't want to push information on 1001 problem, collected in
> last 15 years of SUSE, in eyes of people that clicked on some web link to see
> what is openSUSE.
If this was the original problem it would seem it is being solved in a
poor way. There are lots of ugly pages in the wiki that are out of date
and confusing but shoving everything into a namespace plasters over the
issue; sweeping it under the rug.
Solutions:
- Lots of hard work fixing and pruning pages, staging the new wiki at a
diferent URL
- Introducing a wiki just for users e.g. welcome.opensuse.org or
docs.opensuse.org
> > 1. devel: ? Oh, but these teams are not necessarily developers
>
> Developer as in?
> Software developer, business developer, community developer, film developer
> (chemical), etc :)
> Creating artwork is development.
> Writing documentation is development.
> Creating communication infrastructure is development.
> Developing marketing strategy is ... (right development).
Certainly, I agree with all of these definitions of developers. But,
things in the openSUSE namespace include governance and community
building information like openSUSE:Board, openSUSE:Ambassadors_events,
etc
e.g. devel:Board wouldn't reflect the work they do for openSUSE: they
facilitate, communicate and assist in resolving issues.
> > 3. community: ? Maybe, but community:Java packaging cookbook looks
> > strange
>
> Not strange at all, but it is redundant as well. Of course it is
> community, not Martians :)
Community: at least adds the hint that these community oriented pages
and not part of the openSUSE consumer documentation.
> > 4. project: ? This is my second choice as nearly all of the links on
> > http://en.opensuse.org/Portal:Project are to the openSUSE:
> > namespace...
>
> That is default, but as soon as you choose name for the wiki it will
> become that name, in our case "openSUSE".
I don't follow this.
> > 1-4 have their problems but at least they are not redundant.
>
> We had redundancy before. This one will not change much.
Agreed. At the very least we can figure out a name which might make it
clearer what the mission of this namespace is. Although, preferably just
get rid of it all together.
> > Lets discuss what problem this openSUSE: namespace is trying to
> > solve and how we can make sane looking URLs on our new wiki. And
> > lets do it fast so we can avoid breaking URLs again.
>
> Too late for not breaking anything :)
True, I have REDIRECTED many pages already.
> There is already a lot of internal links that should be changed in
> case that we want something different as a project namespace.
Add two levels of redirection? It isn't too late. This new wiki is only
a few weeks old. The total damage is small today.
Thanks for you input.
Cheers,
Brandon
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-wiki+help@opensuse.org
No comments:
Post a Comment