Menu
▾
▴
pyblosxom-devel
|
From: will kahn-g. <wi...@bl...> - 2012-06-19 11:44:31
|
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 |
|
From: Akai <ope...@gm...> - 2012-06-19 12:11:19
|
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. |
|
From: Akai <ope...@gm...> - 2012-06-19 12:23:16
|
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. > > 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 |
|
From: Sean W. <spw...@sd...> - 2012-06-19 16:09:08
|
Your plan sounds good to me. I am about to leave the country for a month so I won't be able to help at this point. I'll check-in in a month's time to see what needs doing. Sean |
|
From: Akai <ope...@gm...> - 2012-06-19 16:25:39
|
Will - Let me know what you need help with. -Akai On 6/19/2012 7:08 PM, Sean Whitton wrote: > Your plan sounds good to me. > > I am about to leave the country for a month so I won't be able to help > at this point. I'll check-in in a month's time to see what needs > doing. > > Sean |
|
From: will kahn-g. <wi...@bl...> - 2012-06-21 13:04:07
|
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 |
|
From: Akai <ope...@gm...> - 2012-06-21 21:00:35
|
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 |
|
From: Akai <ope...@gm...> - 2012-06-21 21:05:06
|
Will - Is there a reason we don't have the pyblosxom-web repo on github? -Akai |
|
From: will kahn-g. <wi...@bl...> - 2012-06-21 21:13:05
|
None that I'm aware of. On 06/21/2012 05:04 PM, Akai wrote: > Will - > > Is there a reason we don't have the pyblosxom-web repo on github? > > -Akai |
|
From: will kahn-g. <wi...@bl...> - 2012-06-21 21:16:56
|
On 06/21/2012 05:00 PM, Akai wrote: > > 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? I can redirect all traffic to the new site. That's fine. > 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] I think there are like 100 users total. I don't think "confusing users" is really a problem you're going to have once the search engines figure out that things have moved. I don't think there's much useful acrhival data in the roundup tracker. I think it's best to look through it, move over whatever you think is useful, and otherwise ditch it. The useful commentary is in the git commit comments. The bug data is pretty meh. I'm not sure how I feel about backing it up and making it available. It's non-trivial work to separate out the user data from the issue data and I don't think it's responsible to be providing the user data in a public form. So I think if you can get along without it, that's the best option. If you really can't, then I'll add "figure out how to back up the roundup tracker keeping peoples' privacy in mind" to my todo list. /will |
|
From: Akai <ope...@gm...> - 2012-06-21 21:30:31
|
so backing up is a bust.. I guess if people know to go to github we could just leave it up for a bit.. if its ok with you of course. I note we already have three pull requests. Am I supposed to be clearing things with someone? Should I just start addressing things? |
|
From: Akai <ope...@gm...> - 2012-06-21 23:08:06
|
Do we need anything do a new release? I imagine we need something to make a new version of the PIP package. On 6/22/2012 12:16 AM, will kahn-greene wrote: > On 06/21/2012 05:00 PM, Akai wrote: >> 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? > I can redirect all traffic to the new site. That's fine. > > >> 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] > I think there are like 100 users total. I don't think "confusing users" > is really a problem you're going to have once the search engines figure > out that things have moved. > > I don't think there's much useful acrhival data in the roundup tracker. > I think it's best to look through it, move over whatever you think is > useful, and otherwise ditch it. The useful commentary is in the git > commit comments. The bug data is pretty meh. > > I'm not sure how I feel about backing it up and making it available. > It's non-trivial work to separate out the user data from the issue data > and I don't think it's responsible to be providing the user data in a > public form. So I think if you can get along without it, that's the best > option. If you really can't, then I'll add "figure out how to back up > the roundup tracker keeping peoples' privacy in mind" to my todo list. > > /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 |
|
From: Akai <ope...@gm...> - 2012-07-01 21:56:08
|
Whats been going on: The migration to GitHub is mostly complete, all the files are hosted in the right place and the old site redirects to the new one - but there is the occasional pesky link that doesn't point to the right place. I think I got the vast majority of them today. Other than just keeping the site up and the project existing, I've been doing some thinking as to what could make PyBlosxom better (besides getting to the bug reports and pull requests, which I AM addressing). It seems pretty apparent to me that our plugins are both one of the best parts of PyBlosxom as well as our Achilles heel. They can be difficult to choose from, configure and include, and they easily get out of date and buggy. If we had a central way of managing plugins which could handle the worst of the heavy lifting if the user desired (finding the right plugin, the right version and making sure it has all the dependencies and configurations needed to run [like a package manager]) PyBlosxom could be a lot more viable when compared to some of the other blog engines mentioned earlier. It would have the added benefit of making the documentation more accessible because it could display the relevant parts during the install process. Obviously, such an endeavor would require some design thinking for a management interface as well as going though all the existing plugins to test them, make sure they are fully documented and then integrating them into such an interface - But that pretty much has to be done anyway to at least some degree and I think it would pay off in usability, even if we only included a fraction of the plugins we have accumulated into the interface. /Akai |
|
From: will kahn-g. <wi...@bl...> - 2012-06-21 23:28:36
|
The release process I used is documented here: http://pyblosxom.bluesock.org/1.5/dev_release.html For that, you need a PyPI account and permisions to push new versions. If you have a PyPI account, I can add you. /will On 06/21/2012 07:07 PM, Akai wrote: > Do we need anything do a new release? > I imagine we need something to make a new version of the PIP package. > > On 6/22/2012 12:16 AM, will kahn-greene wrote: >> On 06/21/2012 05:00 PM, Akai wrote: >>> 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? >> I can redirect all traffic to the new site. That's fine. >> >> >>> 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] >> I think there are like 100 users total. I don't think "confusing users" >> is really a problem you're going to have once the search engines figure >> out that things have moved. >> >> I don't think there's much useful acrhival data in the roundup tracker. >> I think it's best to look through it, move over whatever you think is >> useful, and otherwise ditch it. The useful commentary is in the git >> commit comments. The bug data is pretty meh. >> >> I'm not sure how I feel about backing it up and making it available. >> It's non-trivial work to separate out the user data from the issue data >> and I don't think it's responsible to be providing the user data in a >> public form. So I think if you can get along without it, that's the best >> option. If you really can't, then I'll add "figure out how to back up >> the roundup tracker keeping peoples' privacy in mind" to my todo list. >> >> /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 > > > > ------------------------------------------------------------------------------ > 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 > |
|
From: Akai <ope...@gm...> - 2012-06-21 23:49:55
|
my username is AkaiKitsune On 6/22/2012 2:28 AM, will kahn-greene wrote: > The release process I used is documented here: > > http://pyblosxom.bluesock.org/1.5/dev_release.html > > For that, you need a PyPI account and permisions to push new versions. > If you have a PyPI account, I can add you. > > /will > > > On 06/21/2012 07:07 PM, Akai wrote: >> Do we need anything do a new release? >> I imagine we need something to make a new version of the PIP package. >> >> On 6/22/2012 12:16 AM, will kahn-greene wrote: >>> On 06/21/2012 05:00 PM, Akai wrote: >>>> 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? >>> I can redirect all traffic to the new site. That's fine. >>> >>> >>>> 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] >>> I think there are like 100 users total. I don't think "confusing users" >>> is really a problem you're going to have once the search engines figure >>> out that things have moved. >>> >>> I don't think there's much useful acrhival data in the roundup tracker. >>> I think it's best to look through it, move over whatever you think is >>> useful, and otherwise ditch it. The useful commentary is in the git >>> commit comments. The bug data is pretty meh. >>> >>> I'm not sure how I feel about backing it up and making it available. >>> It's non-trivial work to separate out the user data from the issue data >>> and I don't think it's responsible to be providing the user data in a >>> public form. So I think if you can get along without it, that's the best >>> option. If you really can't, then I'll add "figure out how to back up >>> the roundup tracker keeping peoples' privacy in mind" to my todo list. >>> >>> /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 >> >> >> ------------------------------------------------------------------------------ >> 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 >> > ------------------------------------------------------------------------------ > 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 |
|
From: will kahn-g. <wi...@bl...> - 2012-06-22 00:08:49
|
Added. On 06/21/2012 07:49 PM, Akai wrote: > my username is AkaiKitsune > > On 6/22/2012 2:28 AM, will kahn-greene wrote: >> The release process I used is documented here: >> >> http://pyblosxom.bluesock.org/1.5/dev_release.html >> >> For that, you need a PyPI account and permisions to push new versions. >> If you have a PyPI account, I can add you. >> >> /will >> >> >> On 06/21/2012 07:07 PM, Akai wrote: >>> Do we need anything do a new release? >>> I imagine we need something to make a new version of the PIP package. >>> >>> On 6/22/2012 12:16 AM, will kahn-greene wrote: >>>> On 06/21/2012 05:00 PM, Akai wrote: >>>>> 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? >>>> I can redirect all traffic to the new site. That's fine. >>>> >>>> >>>>> 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] >>>> I think there are like 100 users total. I don't think "confusing users" >>>> is really a problem you're going to have once the search engines figure >>>> out that things have moved. >>>> >>>> I don't think there's much useful acrhival data in the roundup tracker. >>>> I think it's best to look through it, move over whatever you think is >>>> useful, and otherwise ditch it. The useful commentary is in the git >>>> commit comments. The bug data is pretty meh. >>>> >>>> I'm not sure how I feel about backing it up and making it available. >>>> It's non-trivial work to separate out the user data from the issue data >>>> and I don't think it's responsible to be providing the user data in a >>>> public form. So I think if you can get along without it, that's the best >>>> option. If you really can't, then I'll add "figure out how to back up >>>> the roundup tracker keeping peoples' privacy in mind" to my todo list. >>>> >>>> /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 >>> >>> >>> ------------------------------------------------------------------------------ >>> 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 >>> >> ------------------------------------------------------------------------------ >> 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 > > > > ------------------------------------------------------------------------------ > 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 > |
|
From: Wari W. <wa...@ho...> - 2012-06-20 12:15:30
|
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 |
Thanks for helping keep SourceForge clean.
X