savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers] Requesting help on Savannah?


From: Hugo Gayosso
Subject: Re: [Savannah-hackers] Requesting help on Savannah?
Date: 06 Jun 2004 00:47:22 -0400
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3

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

Richard Stallman <address@hidden> writes:

> It isn't decided yet.  Probably we will hire short-term contractors
> for some of them, look for volunteers for some, and some we won't do
> unless a volunteer takes the initiative.


There are a couple of pieces missing from the puzzle:

1) Who makes technical decisions about Savannah, and what is the
   process to make them?

   In other words, who is the "Savannah Architect"?

   That person (or group of persons) should:

   - decide when, how and what features to implement/enable.

   - coordinate the work of all the people you mentioned
     (i.e. volunteers, contractors, staff, etc.) in regards to
     Savannah.  Ok, this mixes architecture with management, but for
     this case I think it is no big deal.

   - work with FSF sysadmin staff to fit Savannah into FSF IT
     infrastructure's guidelines.


2) Will Savannah run 'savane', GForge, or ?
   This is important (among other reasons) to be able to choose the
   skill set for the volunteers and contractors.

   Actually, I would expect this answer from the Architect(s).



> As far as I know, Savannah is already nearly 'back to normal'; that
> list consists of additional work we would like to do to improve
> matters.

I definitely disagree, Savannah is not nearly 'back to normal', there
are still important issues to be resolved, besides the one I described
above, Elfyn described others in his email.


Greetings,
- -- 
Hugo Gayosso
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAwqHaMNObVRBZveYRAruAAJ4qtR0/5bTA6V5qk7Ap7Y86b40wNgCfU8Bt
LdPnITtRVt1UEC2l8ACW3iQ=
=Dvuj
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]