Why's that Greg? If we provide a SourceForge instance to Fedora you can
customize it to meet your needs, you'll
have site admin access (i.e. complete control over the site) hardware
and network will be managed by the team that looks
after SourceForge.net 24x7, access to the SourceForge mirrors around the
world and you'll get the visibility and community
support from the largest open source nexus on the planet :-)
Would be useful if there were a list of requirements for hosting Fedora
then all of the candidates could respond with what
they can and can't do for Fedora.
Col
Greg DeKoenigsberg wrote:
I think Savannah is the right choice, myself.
--g
-------------------------------------------------------------
Greg DeKoenigsberg || Fedora Project || fedoraproject.org
Be an Ambassador || http://fedoraproject.org/wiki/Ambassadors
-------------------------------------------------------------
On Tue, 18 Apr 2006, Bill Nottingham wrote:
So, someone today wanted to move a Fedora-related bit of source
to externally available CVS. This was easily enough done; just
import it onto cvs.fedora:/cvs/devel, add an ACL, etc.
He then asked 'now, what if I want to release tarballs?'. Oops.
So, this leads to: what do we want to do for project hosting?
- CVS/<scm-of-choice>?
- mailing lists?
- bug tracking?
- web space?
How do we tie it together? Do we take the savannah software?
Something else? Roll our own? (shudder)
This is going to become even more of a need when we decomission
i18n.redhat.com and move all of that source...
Bill
_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-advisory-board
_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-advisory-board
