Re: pyblosxom maintenance

Sounds like a plan!


On 6/19/2012 2:44 PM, will kahn-greene wrote:
> 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.



------------------------------------------------------------------------------
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/