From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] [Fwd: gentoo.org reorg (GDN/GUN)]
Date: 19 Sep 2002 11:03:08 -0600 [thread overview]
Message-ID: <1032454989.26838.81.camel@inventor.gentoo.org> (raw)
-----Forwarded Message-----
From: antonio.meireles@epandemic.com
Subject: [gentoo-core] gentoo.org reorg (GDN/GUN)
Date: 17 Sep 2002 17:33:09 +0100
for public review / comments / whatever
________________________________________________________________________
version 0.0.1 (14/September/2002 [18h00 GMT-0] )
Objectives/Goals:
* have gentoo.org to function as a central hub to all our
(growing) community
* from an end-user perspective
* from a developer perspective
* from a multilingual/multinational perpective
* from an OEM/ISV/VC perpective
* from a non (yet) gentoo-user perpective comming from *NIX
land
* from a non (yet) gentoo-user perspective comming fron Win*/Mac
...
* from a (mainstream/IT) press perspective
* [insert here] from an yet not thougth perspective
Current issues/problems
* the current web site is confuse, graphically not very
atractive and lacks clear focus, doesn 't even have a search
function
* the current web site targets (almost) only english speaking
users
* there isn 't a clear separation between what is information
targeted at developers and what is information targeted at
end-users
* information regarding the same issues is disperse around
several places: Mailing lists, foruns, instalation docs,
bugzilla, etc, makind it hard to find for inexperienced users
* when one reach gentoo.org (non gentoo user/developer) there
isn 't a clear message about Gentoo nature, and what make him
different/better on the front-page
* the information/structure available is too english-centric
wich takes to the proliferation of national/regional gentooo
sites, which makes us loose cohesion and weakes the community
as a whole
* [insert here] other issues/problems
Watching how others handle the situation ... Four case studies
* Zope community
* www.zope.com
* www.zope.org
* Microsoft
* www.microsoft.com
* support.microsoft.com
* msdn.microsoft.com
* ActiveState
* www..activestate.com
* aspn.activestate.com/ASPN/
* Red Hat
* www.redhat.com
* www.redhat.com/apps/support/
Proposals/Remedies
split the current gentoo.org in diferent areas with clear different
focus
* www.gentoo.org
* here will be all the general stuff
* what is Gentoo (whith an high altitude FAQ)
* Advocacy Docs
* Social Contract
* Important News
* Propaganda Stuff (screenshots, users rave comments,
etc)
* Press Reviews
* Download Links
* [insert here] other relevant topics
* gdn.gentoo.org
* Gentoo Developer Network (here will be loccated all the
information relevant to developers - a cross of ASPN with
MSDN
* Developer Docs
* Bugzilla (developer side)
* Developers Only Knowledge Base
* Developers Only FAQ
* ARCH specific Documentation
* specific developer forums/wikis (see zope.org)
* developer Mailing Lists
* Hardware Compatibilty Guide
* i18n
* IRC logs from #gentoo-dev and #gentoo-qa
* roadmaps, etc
* [insert here] other relevant topics
* gun.gentoo.org
* Gentoo Users Network (here will be located all the
information relevant to end-users - a cross of
support.microsoft.com and www.zope.org)
* End-User HowTos
* End-User ARCH specific Documentation
* End-User Oriented Knowledge Base
* End-User Oriented FAQ collection (on the style of the
LDP)
* the three above items should be fully searchable
aand indexable)
* End-User Foruns and Wikis
* End-User Focused Polls (usabilty, features, etc)
* End-User Mailing Lists
* Hardware Compatibilty Guide (both by ARCH and by type
of HW (sound, networking, etc)
* shared with GDN, should have relevant info
extracted from bugzilla, forums, wikis, etc
regarding Hardware issues
* Bugzilla (end user side)
* [insert here] other relevant topics
* GDN could be mainly english based (as, like it or not, the English
is the lingua franca in this world)
* Both www.gentoo.org and GUN should/must support
internationalization of content rigth from the start ...
* GDN would only be accessible to registered Developers (with
perhaps different access levels)
* GUN would be acessible read-only to all, but to take really
advantage users should register ...
* [insert here] other relevant notes
All the best to all,
António Meireles
--
--
Daniel Robbins
Chief Architect, Gentoo Linux
http://www.gentoo.org
next reply other threads:[~2002-09-19 17:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 17:03 Daniel Robbins [this message]
2002-09-19 18:32 ` [gentoo-dev] [Fwd: gentoo.org reorg (GDN/GUN)] Fred Van Andel
2002-09-19 19:04 ` [gentoo-dev] " Mark Gordon
2002-09-19 19:30 ` [gentoo-dev] " Steven Stillaway
2002-09-19 20:07 ` Peter Ruskin
2002-09-19 23:36 ` William Kenworthy
2002-09-19 23:40 ` Matthew Walker
2002-09-19 22:06 ` Evan Read
2002-09-19 23:14 ` humpback
2002-09-20 8:42 ` Paul de Vrieze
2002-09-20 1:29 ` [gentoo-dev] " Mecho Puh
[not found] <106232945@toto.iv>
2002-09-19 22:20 ` [gentoo-dev] " Jeffrey D. Kowing
[not found] <83821536@toto.iv>
2002-09-19 22:28 ` Jeffrey D. Kowing
2002-09-24 11:12 ` Thomas M. Beaudry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1032454989.26838.81.camel@inventor.gentoo.org \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox