Thread: gborg abandoned projects
Howdy folks,
We're still moving forward on plans to shut down gborg, and things are
progressing slowly but surely. At this point I need to bring up the list of
abandoned projects. Some of these projects I got no response from when
trying to contact them, some I got bounces, so thier project owners may not
be aware of whats going on. I plan to send a copy of this list of projects
to both announce and general, to give any users a chance to claim a project
as one they actually use. However, I suspect even then some projects will
get no takers, so we need to decide what to do with those projects. We have
a couple of options as I see them:
1) Let the projects go the way of the dino's. If we have a copy of the server,
we'd have the ability to retrieve the code should a need come up, but
otherwise we'd be removing stuff no one seems to care about.
2) Push all the projects to pgfoundry. This would allow easy access to the
code should someone want it, and also would provide some type of historical
record in case someone is researching a topic within the pg sphere.
Anyone have a strong preference? Also does the specifics of the projects in
question matter? If so I can produce a list for everyone.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
Robert,
In the past I have removed "dead" projects and for those projects
that had something, usually very little, I have kept copies of the CVS
repository and any released files they had. I would think doing this
for any unclaimed projects would be best to reduce the required effort
for moving projects. We could make this list of resources available
someplace if we wanted for posterity purposes.
Chris Ryan
--- Robert Treat <xzilla@users.sourceforge.net> wrote:
> Howdy folks,
>
> We're still moving forward on plans to shut down gborg, and things
> are
> progressing slowly but surely. At this point I need to bring up the
> list of
> abandoned projects. Some of these projects I got no response from
> when
> trying to contact them, some I got bounces, so thier project owners
> may not
> be aware of whats going on. I plan to send a copy of this list of
> projects
> to both announce and general, to give any users a chance to claim a
> project
> as one they actually use. However, I suspect even then some projects
> will
> get no takers, so we need to decide what to do with those projects.
> We have
> a couple of options as I see them:
>
> 1) Let the projects go the way of the dino's. If we have a copy of
> the server,
> we'd have the ability to retrieve the code should a need come up, but
>
> otherwise we'd be removing stuff no one seems to care about.
>
> 2) Push all the projects to pgfoundry. This would allow easy access
> to the
> code should someone want it, and also would provide some type of
> historical
> record in case someone is researching a topic within the pg sphere.
>
> Anyone have a strong preference? Also does the specifics of the
> projects in
> question matter? If so I can produce a list for everyone.
>
> --
> Robert Treat
> Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that
> your
> message can get through to the mailing list cleanly
>
____________________________________________________________________________________
Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool.
http://autos.yahoo.com/carfinder/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Saturday, August 25, 2007 13:32:05 -0400 Robert Treat <xzilla@users.sourceforge.net> wrote: > 1) Let the projects go the way of the dino's. If we have a copy of the > server, we'd have the ability to retrieve the code should a need come up, > but otherwise we'd be removing stuff no one seems to care about. The 'critical part' of any of the projects, IMHO, is the CVS repository, and that is ~638M right now ... so, as long as we save *that*, we at least retain the 'work', we just lose the trouble tickets and mailing lists, which can be recreated ... - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFG0G0P4QvfyHIvDvMRAul2AJ4z+A7SrrH3UgbcFti7ptHP1/PdSgCcDl5Y kMEIPCnjftsarPJIDHm6hQM= =WxoV -----END PGP SIGNATURE-----
On Sat, Aug 25, 2007 at 01:32:05PM -0400, Robert Treat wrote: > 1) Let the projects go the way of the dino's. If we have a copy of the server, > we'd have the ability to retrieve the code should a need come up, but > otherwise we'd be removing stuff no one seems to care about. Like others said, as long as we keep the code repository, it should be ok. (And I say this as someone who just hates to see old URLs go bad.) A -- Andrew Sullivan | ajs@crankycanuck.ca In the future this spectacle of the middle classes shocking the avant- garde will probably become the textbook definition of Postmodernism. --Brad Holland
All, Here's my vote: 1) Projects with no files and no CVS (or just 1-2 files in CVS with a total of < 1K) should simply be deleted. These are non-projects. 2) Projects *with* files should go into some kind of legacy repository, maybe a single project on pgFoundry called "legacy Gborg code." -- Josh Berkus PostgreSQL @ Sun San Francisco
On Sun, Aug 26, 2007 at 11:39:04AM -0700, Josh Berkus wrote: > 1) Projects with no files and no CVS (or just 1-2 files in CVS with a total of > < 1K) should simply be deleted. These are non-projects. I'm really uncomfortable with that. _No_ files is one thing, but "just small files" is another matter. I think the rule should be simply, "If there's something in CVS, save it." A -- Andrew Sullivan | ajs@crankycanuck.ca The whole tendency of modern prose is away from concreteness. --George Orwell
Andrew, > I'm really uncomfortable with that. _No_ files is one thing, but > "just small files" is another matter. I think the rule should be > simply, "If there's something in CVS, save it." Even if it's just a header file and 50 lines of code which doesn't build? -- Josh Berkus PostgreSQL @ Sun San Francisco
On Mon, Aug 27, 2007 at 10:43:35AM -0700, Josh Berkus wrote: > > Even if it's just a header file and 50 lines of code which doesn't build? Yes. Some of the best stuff I've ever done has come from me looking at something broken. It's actually easier to move the CVS wholesale than to look at everything and make choices. A -- Andrew Sullivan | ajs@crankycanuck.ca The plural of anecdote is not data. --Roger Brinner
Andrew, > Yes. Some of the best stuff I've ever done has come from me looking > at something broken. It's actually easier to move the CVS wholesale > than to look at everything and make choices. +1 on "easier". Consensus on simply deleting projects with no CVS and no recent (last 6months) mailing list traffic? -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Monday, August 27, 2007 11:47:29 -0700 Josh Berkus <josh@agliodbs.com> wrote: > Andrew, > >> Yes. Some of the best stuff I've ever done has come from me looking >> at something broken. It's actually easier to move the CVS wholesale >> than to look at everything and make choices. > > +1 on "easier". > > Consensus on simply deleting projects with no CVS and no recent (last > 6months) mailing list traffic? I'm okay with that ... - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFG00kZ4QvfyHIvDvMRArqBAJ9Sucslr8JmwnpBcEen1UOhLypajACgjPZU QXZt+xQ2nX0LUdt33Qx9Fvg= =Nvvz -----END PGP SIGNATURE-----