You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(53) |
Feb
(81) |
Mar
(47) |
Apr
(29) |
May
(32) |
Jun
(24) |
Jul
(41) |
Aug
(86) |
Sep
(40) |
Oct
(28) |
Nov
(11) |
Dec
(23) |
2004 |
Jan
(32) |
Feb
(54) |
Mar
(30) |
Apr
(28) |
May
(113) |
Jun
(17) |
Jul
(5) |
Aug
(111) |
Sep
(103) |
Oct
(18) |
Nov
(5) |
Dec
(38) |
2005 |
Jan
(31) |
Feb
(26) |
Mar
(69) |
Apr
(36) |
May
(45) |
Jun
(35) |
Jul
(11) |
Aug
(25) |
Sep
(9) |
Oct
(27) |
Nov
(4) |
Dec
(11) |
2006 |
Jan
(33) |
Feb
(11) |
Mar
(7) |
Apr
(10) |
May
(11) |
Jun
(2) |
Jul
(9) |
Aug
(7) |
Sep
(22) |
Oct
(40) |
Nov
(34) |
Dec
(5) |
2007 |
Jan
(21) |
Feb
(23) |
Mar
(28) |
Apr
(1) |
May
(15) |
Jun
(45) |
Jul
(71) |
Aug
(45) |
Sep
(52) |
Oct
(31) |
Nov
(20) |
Dec
(6) |
2008 |
Jan
(17) |
Feb
(25) |
Mar
(7) |
Apr
(5) |
May
(9) |
Jun
(3) |
Jul
(2) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
(2) |
Apr
(3) |
May
(1) |
Jun
(1) |
Jul
(15) |
Aug
(9) |
Sep
(10) |
Oct
(1) |
Nov
|
Dec
|
2010 |
Jan
(42) |
Feb
(28) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
(7) |
Sep
(19) |
Oct
(14) |
Nov
(27) |
Dec
(14) |
2011 |
Jan
(8) |
Feb
(9) |
Mar
(9) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(18) |
Sep
|
Oct
|
Nov
|
Dec
(6) |
2012 |
Jan
(5) |
Feb
(2) |
Mar
(2) |
Apr
|
May
|
Jun
(13) |
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
(4) |
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(9) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
2016 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Akai <ope...@gm...> - 2016-02-20 20:51:10
|
Hey guys! So its becoming more and more obvious that my work/life balance isn't going to improve any time soon. What I hoped would be a small disruption has become daily 10-15hr workdays and not leaving me time to work on things I care about, Pyblosxom among them. If any of you have vision and interest in stepping up and doing more with Pyblosom, I'm happy to do at least as much as I'm doing now. Either way, I'm not abandoning the project. Just been too busy to do it justice. I'm happy to be a "maintainer" in that I'm here to answer questions, debug/make patches, maintain the site, etc.., but I'm not anywhere near what you guys deserve in the way of active improvement. Yours, Akai |
From: Dieter P. <di...@pl...> - 2013-10-13 23:18:56
|
cool website. also i like the more git-focused approach to the plugins and themes repo. On Sun, 13 Oct 2013 21:51:49 +0300 Akai <ope...@gm...> wrote: > Hi everyone - > > The new site is deployed! > Besides modernizing the look a little, the new site's goal is to make it > easier to find things, make changes, and keep track of the existing content. > The new design also makes it easier to make visible micro-updates (such > as tweets) for things that aren't HUGE issues, but should be visible. > > The old site is great and I'd like the new one to be at least as good, > if not amazingly better - so let me know if you catch any issues or > think any changes should be made (or feel free to do a github pull > request to that page. Its all static HTML as of right now, except for > the plugins/flavours) > > I have many more changes to make, which will hopefully improve PyBlosxom > as well. > > The site is available at our normal URL http://pyblosxom.github.io/ > > Yours, > > -Akai > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk > _______________________________________________ > pyblosxom-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users |
From: Akai <ope...@gm...> - 2013-10-13 23:00:50
|
Thanks! I'm hoping to have as much as I can (plugins and flavours) in the git repo as soon as I can rework them for maximal compatibility with the latest pyblosxom) On 10/14/2013 1:36 AM, Dieter Plaetinck wrote: > cool website. > also i like the more git-focused approach to the plugins and themes repo. > > > > On Sun, 13 Oct 2013 21:51:49 +0300 > Akai <ope...@gm...> wrote: > >> Hi everyone - >> >> The new site is deployed! >> Besides modernizing the look a little, the new site's goal is to make it >> easier to find things, make changes, and keep track of the existing content. >> The new design also makes it easier to make visible micro-updates (such >> as tweets) for things that aren't HUGE issues, but should be visible. >> >> The old site is great and I'd like the new one to be at least as good, >> if not amazingly better - so let me know if you catch any issues or >> think any changes should be made (or feel free to do a github pull >> request to that page. Its all static HTML as of right now, except for >> the plugins/flavours) >> >> I have many more changes to make, which will hopefully improve PyBlosxom >> as well. >> >> The site is available at our normal URL http://pyblosxom.github.io/ >> >> Yours, >> >> -Akai >> >> >> ------------------------------------------------------------------------------ >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >> the latest Intel processors and coprocessors. See abstracts and register > >> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk >> _______________________________________________ >> pyblosxom-users mailing list >> pyb...@li... >> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users |
From: Akai <ope...@gm...> - 2013-10-13 18:51:56
|
Hi everyone - The new site is deployed! Besides modernizing the look a little, the new site's goal is to make it easier to find things, make changes, and keep track of the existing content. The new design also makes it easier to make visible micro-updates (such as tweets) for things that aren't HUGE issues, but should be visible. The old site is great and I'd like the new one to be at least as good, if not amazingly better - so let me know if you catch any issues or think any changes should be made (or feel free to do a github pull request to that page. Its all static HTML as of right now, except for the plugins/flavours) I have many more changes to make, which will hopefully improve PyBlosxom as well. The site is available at our normal URL http://pyblosxom.github.io/ Yours, -Akai |
From: Hauke F. <hauke@Espresso.Rhein-Neckar.DE> - 2013-07-31 10:22:22
|
On Wed, 31 Jul 2013 04:37:46 +0300, Akai wrote: > Version 1.5.3 has been released! Thanks! I updated the pkgsrc www/py-blosxom package. Cheerio, hauke -- Hauke Fath <hauke@Espresso.Rhein-Neckar.DE> Ernst-Ludwig-Straße 15 64625 Bensheim Germany |
From: Akai <ope...@gm...> - 2013-07-31 01:37:51
|
Hi Everyone - Version 1.5.3 has been released! You can get it the normal way: via the download page here: http://pyblosxom.github.io/download/ or via pip: pip install pyblosxom Feel free to comment on anything. It's been a while since our last release - Let me know what you like, what you hate and if anything broke. I'm moving from here to adding in the Jinja2 plugin and getting more themes and plugins together to hopefully improve the ease of getting started Have a great day! |
From: Janis K. <ja...@fi...> - 2013-07-19 19:06:53
|
Akai wrote: > Hi, > > How many of you are using the latest version from git? > I think it might be time to make a point release, and then move to > adding new features such as the integration of the theme repos, Jinja2, > etc.. > > -Akai > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Pyblosxom-devel mailing list > Pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel > > > I haven't upgraded yet.. It's been very busy since we moved. I'll see if I can grab the lastest release today <grin> Ok, just downloaded pyblosxom-1.5.2.tar.gz :) Thanks Akai, appreciate your time in this. Take care, Janis |
From: Akai <ope...@gm...> - 2013-07-18 23:56:25
|
Anything worth pulling into the core, or just personal modifications? On 7/19/2013 2:37 AM, will kahn-greene wrote: > I'm actually using my fork. It's like the official master tip, but has a > correct version and possibly some other things. > > /will > > > On 07/18/2013 05:46 PM, Akai wrote: >> Hi, >> >> How many of you are using the latest version from git? >> I think it might be time to make a point release, and then move to >> adding new features such as the integration of the theme repos, Jinja2, >> etc.. >> >> -Akai > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > pyblosxom-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users |
From: will kahn-g. <wi...@bl...> - 2013-07-18 23:54:31
|
I'm actually using my fork. It's like the official master tip, but has a correct version and possibly some other things. /will On 07/18/2013 05:46 PM, Akai wrote: > Hi, > > How many of you are using the latest version from git? > I think it might be time to make a point release, and then move to > adding new features such as the integration of the theme repos, Jinja2, > etc.. > > -Akai |
From: Akai <ope...@gm...> - 2013-07-18 21:46:28
|
Hi, How many of you are using the latest version from git? I think it might be time to make a point release, and then move to adding new features such as the integration of the theme repos, Jinja2, etc.. -Akai |
From: Akai <ope...@gm...> - 2013-07-03 22:42:12
|
Pyblosxom is still alive :-) Feel free to join in! On 7/2/2013 11:14 PM, Dieter Plaetinck wrote: > still alive. just not super active development, but i guess it just works for most people (me included) > > On Tue, 2 Jul 2013 21:29:50 +0200 > Daan Bellefroid <da...@id...> wrote: > >> Hello all Is pyblosxom still alive or should I look for an alternative ;)) Regards Daan >> >> ---Too brief? -> Sent from my iPhone >> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > pyblosxom-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users |
From: Dieter P. <di...@pl...> - 2013-07-02 20:38:23
|
still alive. just not super active development, but i guess it just works for most people (me included) On Tue, 2 Jul 2013 21:29:50 +0200 Daan Bellefroid <da...@id...> wrote: > Hello all Is pyblosxom still alive or should I look for an alternative ;)) Regards Daan > > ---Too brief? -> Sent from my iPhone > |
From: Daan B. <da...@id...> - 2013-07-02 19:52:26
|
Hello all Is pyblosxom still alive or should I look for an alternative ;)) Regards Daan ---Too brief? -> Sent from my iPhone |
From: Akai <ope...@gm...> - 2013-06-26 01:43:55
|
Hi, It's been a pretty tumultuous year both for me and PyBlosxom. I've spent a lot of this time getting used to the codebase, which was frankly somewhat intimidating to someone new to the project, which I was when I first joined a year ago. On the Pyblosxom front, Although we haven't had a super-large amount of updates, We did get some bugs squashed and began a new repo for external plugins, which I hope will eventually lead to plugins being more updated and accessible Markus Koschany (https://launchpad.net/~apoleon) has been working on the Debian repo to finally get our package there updated for the next release. (If you are on this list, Thank you!) We made the move over to GitHub will all our stuff and the documentation has been updated to reflect it I'm happy to note it looks like we got a few new installs and a few new faces appeared on IRC We also now have a shiny new repo for themes - I've uploaded an updated version of MainlyGreen to get started with, which has been updated for the latest PyBlosxom and optimized for pagnate and the comments plugin. If anyone would like to submit cool themes, tested and converted or not, I'd be happy to test and update them. |
From: Asheesh L. <as...@as...> - 2012-12-04 02:51:55
|
On Tue, 4 Dec 2012, Akai Kistune wrote: > Because its not just other git repos, its all over the place. Also - > While I'm not sure how the git submodule process would work, in any > case, publishing to the repo should be akin to a "release" of your > plugin, while the versions in people's personal repos would be the > development versions. > I hope that it will always be possible to pull a working version of a > 3rd party plugin from the repo. I'd just like to say, as a user of pyblosxom: In my opinion this is *amazing*. Sincerely, Asheesh. |
From: <wa...@ho...> - 2012-12-04 02:27:12
|
Well, if its actually hosted in other git repos, why not link to it as a git submodule within the plugins.git project? At least the pointers are there, and the original maintainers can update as they please. > Hi! > > By request, I've created a plugin repo > (https://github.com/pyblosxom/plugins.git) for 3rd party plugins and I > hope to make another for flavours as soon as I have the time. > > The idea is to make it easier for people to contribute to existing 3rd > party plugins and to build up a library of updated plugins (which was > difficult when they were hosted on other people's githubs/servers) > > Feel free to tell me why this is a great/horrible idea and/or to add and > update plugins. > I plan on adding the existing plugins as soon as I test them for > compatibility with the latest version of Pyblosxom. > > The core plugins will (with the exception of the "sample" plugin) stay > out of the 3rd party repo. > > -akai > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > pyblosxom-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users > > |
From: Akai K. <ope...@gm...> - 2012-12-04 02:12:36
|
Because its not just other git repos, its all over the place. Also - While I'm not sure how the git submodule process would work, in any case, publishing to the repo should be akin to a "release" of your plugin, while the versions in people's personal repos would be the development versions. I hope that it will always be possible to pull a working version of a 3rd party plugin from the repo. On 12/04/2012 03:54 AM, wa...@ho... wrote: > Well, if its actually hosted in other git repos, why not link to it as a > git submodule within the plugins.git project? At least the pointers are > there, and the original maintainers can update as they please. > >> Hi! >> >> By request, I've created a plugin repo >> (https://github.com/pyblosxom/plugins.git) for 3rd party plugins and I >> hope to make another for flavours as soon as I have the time. >> >> The idea is to make it easier for people to contribute to existing 3rd >> party plugins and to build up a library of updated plugins (which was >> difficult when they were hosted on other people's githubs/servers) >> >> Feel free to tell me why this is a great/horrible idea and/or to add and >> update plugins. >> I plan on adding the existing plugins as soon as I test them for >> compatibility with the latest version of Pyblosxom. >> >> The core plugins will (with the exception of the "sample" plugin) stay >> out of the 3rd party repo. >> >> -akai >> >> ------------------------------------------------------------------------------ >> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial >> Remotely access PCs and mobile devices and provide instant support >> Improve your efficiency, and focus on delivering more value-add services >> Discover what IT Professionals Know. Rescue delivers >> http://p.sf.net/sfu/logmein_12329d2d >> _______________________________________________ >> pyblosxom-users mailing list >> pyb...@li... >> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users >> >> > > > |
From: Akai K. <ope...@gm...> - 2012-12-04 01:04:41
|
Hi! By request, I've created a plugin repo (https://github.com/pyblosxom/plugins.git) for 3rd party plugins and I hope to make another for flavours as soon as I have the time. The idea is to make it easier for people to contribute to existing 3rd party plugins and to build up a library of updated plugins (which was difficult when they were hosted on other people's githubs/servers) Feel free to tell me why this is a great/horrible idea and/or to add and update plugins. I plan on adding the existing plugins as soon as I test them for compatibility with the latest version of Pyblosxom. The core plugins will (with the exception of the "sample" plugin) stay out of the 3rd party repo. -akai |
From: Akai <ope...@gm...> - 2012-10-23 22:19:56
|
Tyler, Welcome :-) Since Will answered the first question, I'll get the 2nd: You can take a look at how to make a flavour by looking at the flavour registry here - http://pyblosxom.github.com/registry/flavours/ (many of them not exactly updated to the latest PyBlosxom, but some have sidebars so you can see how they did it.) and checking out the flavour documentation at http://pyblosxom.github.com/1.5/flavours_and_templates.html -Akai > Hello all, > I am new to pyblosxom, but hope to use it for at least 2 of my blogs > once I get everything configured to my liking. One thing I feel like I > can't live without is tagging. I followed the documentation and got > tags(ex. weather) to show up on the bottom of my post, but when I > clicked on them I was taken to a blank page url//blog/tag/weather. Any > clue what I have to do to make it show up? I am using static rendering > and version 1.5.2. > > I also want to have a sidebar. I figure this can be done with a div or a > table. Any guidance on where to put the div/table? > > Thanks in advance! > - Tyler > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > > > > _______________________________________________ > pyblosxom-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users > |
From: will kahn-g. <wi...@bl...> - 2012-10-23 17:58:29
|
Earlier this month, I switched my blog over from CGI rendering to static rendering. In the process of doing that, I fixed the tags and paginate plugins to work with static rendering and fixed some other minor issues. You'll need to use pyblosxom from git master tip for that On 10/23/2012 01:31 PM, Tyler Rusk wrote: > Hello all, > I am new to pyblosxom, but hope to use it for at least 2 of my blogs > once I get everything configured to my liking. One thing I feel like I > can't live without is tagging. I followed the documentation and got > tags(ex. weather) to show up on the bottom of my post, but when I > clicked on them I was taken to a blank page url//blog/tag/weather. Any > clue what I have to do to make it show up? I am using static rendering > and version 1.5.2. > > I also want to have a sidebar. I figure this can be done with a div or a > table. Any guidance on where to put the div/table? > > Thanks in advance! > - Tyler |
From: Tyler R. <td...@gm...> - 2012-10-23 17:32:02
|
Hello all, I am new to pyblosxom, but hope to use it for at least 2 of my blogs once I get everything configured to my liking. One thing I feel like I can't live without is tagging. I followed the documentation and got tags(ex. weather) to show up on the bottom of my post, but when I clicked on them I was taken to a blank page url//blog/tag/weather. Any clue what I have to do to make it show up? I am using static rendering and version 1.5.2. I also want to have a sidebar. I figure this can be done with a div or a table. Any guidance on where to put the div/table? Thanks in advance! - Tyler |
From: Akai <ope...@gm...> - 2012-06-23 18:24:10
|
Hi everyone! I've stepped up as maintainer of pyblosxom and I'd like to know a little bit about what both I and we as a team can do to make the project better. I know there are a lot of blog engines out there so I'd like an idea of what attracts you to using pyblosxom specifically, so I can make sure to keep the best parts of what led you here, while continually making things better. I'd also like to know what versions you guys are using (and how many people are using the latest version off GIT) so I can get a general idea of how often changes should be made into an actual release. Also, since Will is retiring the site, we have moved to github (the site part will be up soon). As such, bugs and issues should be submitted here: https://github.com/pyblosxom/pyblosxom Thanks! -Akai |
From: Fernando T. G. <ft...@gm...> - 2012-06-16 16:37:42
|
Thanks for your work. On Fri, Jun 15, 2012 at 5:11 PM, will kahn-greene <wi...@bl...>wrote: > In the last week, we've had an interesting conversation about > alternatives to Pyblosxom on pyblosxom-devel. It's worth talking more > about those. You can see the archives at > http://sourceforge.net/mailarchive/forum.php?forum_name=pyblosxom-devel . > > However, no one mentioned wanting to pick up maintenance of Pyblosxom > and no one expressed interest in continuing the project. Given that, I > think I'm going to do some work to move the site to github pages, nix > the roundup tracker, put the project in indefinite sleep mode, update > the docs in regards to all these things, and write a "farewell" blog post. > > It'd be really super if people who migrated their blogs over to > Pyblosxom alternatives sent an email to the > pyblosxom-users/pyblosxom-devel lists about their experiences switching. > That'll help others migrate, too. > > Thank you all for the many years of Pyblosxom-hood! I wish all well! > > /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-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users > -- Fernando Tricas |
From: Janis K. <ja...@fi...> - 2012-06-16 07:16:08
|
Hi Will, I'm truly sorry to see you leave the project, and I'm even more sad that no one has picked up on the maintenance of the project. I do understand that other projects may pull you away from this one. It happens to us all the time.. I have thought about switching to other blogging server software projects and have checked out the ones mentioned thus far.. Nah, not for me <grin> I'll stick with PyBloxsom. It does EXACTLY what I want, so thank you for all the time you took to make this work so well. I guess if someone creates some problem somewhere with the code, I'll have to deal with it... and maybe fix it :) Take care, Janis will kahn-greene wrote: > In the last week, we've had an interesting conversation about > alternatives to Pyblosxom on pyblosxom-devel. It's worth talking more > about those. You can see the archives at > http://sourceforge.net/mailarchive/forum.php?forum_name=pyblosxom-devel . > > However, no one mentioned wanting to pick up maintenance of Pyblosxom > and no one expressed interest in continuing the project. Given that, I > think I'm going to do some work to move the site to github pages, nix > the roundup tracker, put the project in indefinite sleep mode, update > the docs in regards to all these things, and write a "farewell" blog post. > > It'd be really super if people who migrated their blogs over to > Pyblosxom alternatives sent an email to the > pyblosxom-users/pyblosxom-devel lists about their experiences switching. > That'll help others migrate, too. > > Thank you all for the many years of Pyblosxom-hood! I wish all well! > > /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-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users > > > |
From: Joseph R. <jos...@re...> - 2012-06-15 16:22:03
|
On 06/15/2012 11:11 AM, will kahn-greene wrote: > It'd be really super if people who migrated their blogs over to > Pyblosxom alternatives sent an email to the > pyblosxom-users/pyblosxom-devel lists about their experiences switching. > That'll help others migrate, too. I know you're pointing out devel, but since it's not being developed anymore, most devels are users, and users are impacted, I would think the conversation would happen here. I'm pretty happy with my pyblosxom install now and don't imagine making a switch before braver souls precede me. However, I looked into it a bit into the static generators and found pelican and myn to be closes to my liking. In fact, pelican supports RSS imports, which could make the process easier. Comments will be the big deal. I imagine that as part of my conversion script (from my HTML into whichever system I use) I will pull in the existing pyblosxom comments as part of the content and present them as "archival comments." It looks like the static people are also pretty much stuck with Disqus which has its ups and downs. |