Re: [Pyblosxom-devel] pyblosxom maintenance

[Akai <ope...@gm...>]

Thanks :-)
You guys have my email, although it looks like everyone is busy/on 
vacation about now.

Will - If we move the site to GH-pages, could you point the old site to 
the new one, or do you plan to take down the domain completely?
also -
is there a way to just backup the issue tracker?  that way we could 
start fresh without all the legacy mess, but still refer back to it if 
we find ourselves needing to fix something and nothing in the new 
tracker or wanting to migrate more issues and you wouldn't have to host 
it [and it wouldn't confuse users]




On 6/21/2012 4:03 PM, will kahn-greene wrote:
> Here's the current status:
>
> On 06/19/2012 08:23 AM, Akai wrote:
>> I'm on sourceforge under foxdeveloper and github under AkaiKitsune.
>>
>> and using GH pages makes a lot of sense, at least to cut on hosting costs.
>>
>> On 6/19/2012 2:44 PM, will kahn-greene wrote:
>>> Hi!
>>>
>>> Janis, Akai and Sean expressed interest in continuing Pyblosxom in
>>> some capacity. Given that, I'd like to hand it off to them.
>>>
>>>
>>> Here's where things are at:
>>>
>>> 1. pyblosxom has a repository on github under my account. My vote is
>>> that I move that to a newly created pyblosxom organization.
> Done! I created a pyblosxom organization. In it are me and Akai.
>
> If anyone else wants to be part of the pyblosxom organization on github,
> tell Akai your github account name and he can add you.
>
>
>>> 2. pyblosxom has a repository on gitorious. My vote is I do what
>>> Asheesh suggested a while back, delete all the files, and check in a
>>> README that says, "Thanks for playing!" and points to the new repository.
> Done! I nixed all the files in the pyblosxom repository and pointed it
> at the new one on github.
>
>
>>> 3. pyblosxom has a pyblosxom-web repository on gitorious. My vote is I
>>> move that under the pyblosxom organization on github and then nuke the
>>> one on gitorious. This has all the files needed for rendering the
>>> website.
>>>
>>> 4. pyblosxom has a pyblosxom-contrib repository on gitorious that is
>>> almost entirely bitrotten plugins. They all need work before being
>>> pulled into Pyblosxom core. Some of them shouldn't be pulled in at
>>> all. I think my vote is that someone should go through them and see
>>> what's up and pull over the ones that are interesting to them. Then we
>>> ditch the repository.
>>>
>>> 5. pyblosxom.bluesock.org is on my server. It's just static HTML
>>> pages, so we could move it to gh-pages. I'm up for whatever you want
>>> to do.
>>>
>>> 6. pyblosxom has a Roundup issue tracker with a few interesting bugs
>>> and a lot of crap in it. My vote is that someone looks through it and
>>> moves the interesting things to the github issues tracker, then I
>>> close it down.
>>>
>>> 7. There are two mailing lists hosted on sourceforge. I can pass off
>>> administration of those to someone with a SF account.
> I'll do number 7 later today.
>
> I don't think you need me to do the rest of the stuff in this list. I'll
> wait to nix pyblosxom.bluesock.org and the roundup issue tracker until I
> get the ok from someone. They can hang out on my server, but going
> forward I won't be updating either.
>
> I'm around on irc and email if there are any questions about moving
> things over. I'll send an update after I transfer the mailing lists.
>
> Hope that helps!
>
> /will
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel