Thread: Updating Freshmeat & Sourceforge?
All, Johnathan Fuerth used to update our Freshmeat & SF.net profiles every time our project did a release. However, I haven't heard from him in a year, and I don't think he's involved with PostgreSQL anymore. Can someone else take over this duty? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
Josh Berkus wrote: > All, > > Johnathan Fuerth used to update our Freshmeat & SF.net profiles every > time our project did a release. However, I haven't heard from him in a > year, and I don't think he's involved with PostgreSQL anymore. > > Can someone else take over this duty? I suggest we just point them to our URLs. We have enough to do and have years of this not being done promptly. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
Bruce, > I suggest we just point them to our URLs. We have enough to do and have > years of this not being done promptly. Freshmeat/Sourceforge are self-service. There is no "them" to point. Also, they've been maintained until whenever Jonathan got bored, sometime this year. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
Josh Berkus wrote: > Bruce, > > > I suggest we just point them to our URLs. We have enough to do and have > > years of this not being done promptly. > > Freshmeat/Sourceforge are self-service. There is no "them" to point. > > Also, they've been maintained until whenever Jonathan got bored, > sometime this year. That doesn't match my memory, but I won't destroy your fantasy. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
On 09/09/2011 06:04 PM, Bruce Momjian wrote: > > Josh Berkus wrote: >> Bruce, >> >>> I suggest we just point them to our URLs. We have enough to do and have >>> years of this not being done promptly. >> >> Freshmeat/Sourceforge are self-service. There is no "them" to point. >> >> Also, they've been maintained until whenever Jonathan got bored, >> sometime this year. > > That doesn't match my memory, but I won't destroy your fantasy. > Well, without stomping on toes, over the last two years or so it has been relatively maintained. I won't say on the spot but better than it was previous to that. It seems to me that the solution is to make updating Freecode (freshmeat doesn't exist anymore) and sourceforge should be part of the committers job as part of the release process. I mean, someone has to update the front page of the website, they should also update those two sites as well or at least have someone step up during packaging to do so. Sincerely, Joshua D. Drake -- Command Prompt, Inc. - http://www.commandprompt.com/ PostgreSQL Support, Training, Professional Services and Development The PostgreSQL Conference - http://www.postgresqlconference.org/ @cmdpromptinc - @postgresconf - 509-416-6579
> It seems to me that the solution is to make updating Freecode (freshmeat > doesn't exist anymore) and sourceforge should be part of the committers > job as part of the release process. That seems unreasonable. The release team has enough to do, and if Freecode gets updated a couple of days later, it's not really a problem. I think continuing to do it through separate advocacy volunteers makes sense. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com