On Mon, Sep 15, 2014 at 3:34 AM, Matthias Andree <mat...@gm...> wrote:
>> grarpamp:
>> tickets that I
>> think got destroyed when the ticket system got destroyed/moved, or maybe
>> on this list, or something like that, I don't remember.
> thank you for the reminder. I downloaded the ticket data from BerliOS
> but have not yet found a way to recreate Sourceforge tickets from them
> authentically, the instructions that were given on sf.net in May were a
> bit vague and not at all turnkey solutions, quite on the contrary.
"
BerliOS is shutting down end of this month, and their mailing list
export is broken, so I may not be able to obtain subscriber rosters in a
timely manner.
I will move downloads to sourceforge.net, but I have not yet decided if
I want to move the mailing lists there because their list archive
interface is awkward to use and inconcise.
"
Yes, SF has a horribly unuseful archive interface. They seem to
use mailman as management frontend, but skip the good pipermail
archiver in deference to their own junk. So when I just now went
looking for pipermail's gzipped mbox text archives of fetchmail lists
to import into mutt to search and begin to use... well, we can't.
I meant to suggest back then finding a home for the lists that
ran mailman+pipermail gzip mboxes. Once found, all the past
archives you hold could be loaded into it. They could also be
put up as a tarball, optionally updated quarterly or some such
if no mm+pm host can be found. Even rsync would work.
Github, or a local bugzilla, trac or request tracker would probably
be better than SF for ticketing. Export and import would be nice.
Sourceforge seems to be stuck in the 'first generation' while
better options have sprung up around them.
|
