On Thu, Dec 31, 2009 at 1:15 PM, Magnus Hagander <magnus@hagander.net> wrote:
> I definitely agree. Which is why I say that if we're moving off
> gforge, we're moving to Somebody Elses Problem, not to another
> platform maintained by *us*.
"Somebody Elses Problem" is going to be ours if we consider the whole
community and not only the sysadmins/web teams. PostgreSQL is defined
by/appreciated for its whole ecosystem, not only the core code.
As a community member I think it's a great thing to have a code
repository that we manage as a community:
- when we approve a project, we sometimes discuss the license with the
project creator;
- we also sometimes decide to give a dead project to another community member;
- we are sure the code repository won't go to trash because managed by
some random company having problems or making the wrong decision for
us;
- it's a good opportunity to have a lot of PostgreSQL projects
gathered in one place.
As a developer having a project on pgFoundry, I don't really like the
idea of moving elsewhere:
- I'm going to lose my trackers/forums history;
- I'll have to chose another place with CVS/Subversion repositories (I
don't really want to use bazaar or git) and hope it won't be closed in
the next few years.
I'm pretty sure I'm not the only one in this case and I'm also pretty
sure there's a lot of projects that won't be moved and will be lost
(either immediately or after a few years).
I don't really see pgFoundry maintenance as something requiring a lot
of time. Am I wrong?
--
Guillaume
