9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: uriel@cat-v.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] complaints about new web site
Date: Sat, 28 Jan 2006 19:41:37 +0100	[thread overview]
Message-ID: <36e9307daa1b7ee8b9f5453b394c01ed@cat-v.org> (raw)
In-Reply-To: <20060128141832.88F171E8C29@holo.morphisms.net>

>> 1.) We create two places to look for software (sources and web)
>> 
>> 2.) It may be stuff _new_ people commonly want - I don't want GCC on
>> Plan 9.  And those people probably don't really want GCC either.
> 
> No one really wants gcc.  But TeX was the original "additional software"
> and it remains useful and worth being easy to find.  So is Python.
I agree that there are various important packages that should be
listed in a convenient place, I'm working in a new version of the
'Software for Plan 9' wiki page that will(I hope) replace the
"Additional software" page.  First step is to get everyone with
various code bits in random pages over the net to move them to sources
so I can delete the external links.


> Everything on the additional software page is links to sources,
> so there's really only one place to find the archives.  There's also
> only one real place to look for software, and that's the web page,
> unless you like reading large unsorted lists of software packages.
> (What Uriel has built is not an index.  It is a table of contents.
> A real index would actually help a lot.)
The "Contrib Index"[1] is far from perfect, but I think it's still
quite useful.  Any ideas about how to improve it without involving too
much manual work which would ensure its fast obsolescence?


Allowing to tag packages with some kind of category might be good,
probably by having a list of common directory names(eg., 'scripts',
'ports', 'games, 'drivers', etc.,), only problem is to get everyone
with sources accounts to take the time and care to organize their
packages according to those conventions.

Thanks

uriel

[1] Thanks to everyone that moved their code to sources
http://plan9.bell-labs.com/wiki/plan9/Contrib_index/



      reply	other threads:[~2006-01-28 18:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-27 17:21 Russ Cox
2006-01-27 17:38 ` erik quanstrom
2006-01-27 18:42 ` Sascha Retzki
2006-01-27 19:04   ` Russ Cox
2006-01-28  8:52     ` Sascha Retzki
2006-01-28 14:18       ` Russ Cox
2006-01-28 18:41         ` uriel [this message]

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=36e9307daa1b7ee8b9f5453b394c01ed@cat-v.org \
    --to=uriel@cat-v.org \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).