public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luke-Jr <luke-jr@gentoo.org>
To: Kurt Lieber <klieber@gentoo.org>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] What sort of infrastructure programs/features do we want?
Date: Fri, 19 Sep 2003 23:54:14 +0000	[thread overview]
Message-ID: <200309192354.23061.luke-jr@gentoo.org> (raw)
In-Reply-To: <20030919152406.GJ16273@mail.lieber.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 19 September 2003 03:24 pm, Kurt Lieber wrote:
> * shared calendaring
I setup a very simple thing for this by making a cvs-group-writable 
'gentoo.ics' calendar in my home dir on peregrine... Don't know how many 
people are using it. Unfortunately, it's very easy to lose data this way (and 
with KDE, at least, you need to enter a password to open it for read-write a 
few times before it finally works). I was unable to find a protocol designed 
for a shared (writing) calendar in my searching, but perhaps someone else 
knows of one?

> * shared addressbooks
Possibly included in this idea might be a way to get things like 'peregrine', 
'*.g.o', and perhaps other aliases to resolve on dev (users too?) systems. 
Otherwise, maybe this should be added as another idea...

> * web mail
Would this be webmail for @g.o emails or webmail for users also?

> * workflow management/project management
Not sure what is meant by this... any place I can get details?

> * wiki (internal and/or external)
I don't know what this could be used for, but I'm sure if one existed someone 
would find a use for it. :)

> * php support for developer ~/ directories
That would be nice, especially if we get a BT tracker.

>
> and the list goes on.

* BitTorrent tracker :)

> * Your participation in all of this is crucial.  I realize we don't all
>   have the time to research options, write up proposals, etc.  Fine.  But
>   at least take the time to comment and vote on the other proposals that
>   get put forth.  I don't know what sort of infrastructure we want.  I know
>   what I want, but you all need to tell me (using the process above) what
>   you want.  Then, we can figure out what the best solution is for the
>   entire team.
Unfortunately, I don't have much time these days. To look into extensive 
details for much of any of these (except BT tracker, perhaps) would probably 
at least cut my dev time in half, let alone writing up a document for them. 
If someone else has time to make a GLEP for the stuff, please do. Otherwise, 
I'll probably write one in a few weeks/months when I get more time (winter 
break?).
- -- 
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/a5csZl/BHdU+lYMRAhn+AJ9TPnsgEdgz2JMYDylKVNg3tjtP9QCePVtB
LJEhq7xIPzYIIfFlQL0Rgbo=
=ozSV
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-09-19 23:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 15:24 [gentoo-dev] What sort of infrastructure programs/features do we want? Kurt Lieber
2003-09-19 23:54 ` Luke-Jr [this message]
2003-09-20  0:19   ` Kurt Lieber
2003-09-20  0:25     ` Mike Frysinger
2003-09-20  4:34       ` C. Brewer
2003-09-20  7:46         ` Mike Frysinger
2003-09-20  0:34     ` Luke-Jr
2003-09-20  3:30 ` Chris Gianelloni
2003-09-20  8:46 ` Paul de Vrieze
2003-09-20 10:16   ` Luke-Jr
2003-09-20 10:22     ` Paul de Vrieze

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=200309192354.23061.luke-jr@gentoo.org \
    --to=luke-jr@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=klieber@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