Re: [Pyblosxom-devel] pyblosxom maintenance

[Wari W. <wa...@ho...>]

Sounds good. Don't believe that pyblosxom is over 9 yrs old now, from a
simple python script, and watched it grow to a full blown module. :)
Pyblosxom would not have been such a project without Will's plugin
implementation (which I'm still amazed at it's flexibility). I'm still
using a very old version for stuff at work as it fills my needs.

Moving everything to github is just a good idea all round, and yes, a
vote goes to a pyblosxom 'organization' in github. Also, gh-pages would
work well too.

I could check out the contribs, time willing, and see what works and
what does not.

On 19/06/2012 19:44, 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.
>
> 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.
>
> 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 think that's it.
>
> How does that plan sound?
>
> /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
>


-- 
Foo bar