Menu
▾
▴
pyblosxom-devel — Development Mailing List for pyblosxom
You can subscribe to this list here.
| 2003 |
Jan
(24) |
Feb
(226) |
Mar
(150) |
Apr
(103) |
May
(101) |
Jun
(83) |
Jul
(80) |
Aug
(27) |
Sep
(48) |
Oct
(2) |
Nov
(17) |
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(11) |
Feb
(67) |
Mar
(53) |
Apr
(60) |
May
(79) |
Jun
(17) |
Jul
(6) |
Aug
(13) |
Sep
(14) |
Oct
(6) |
Nov
(13) |
Dec
(161) |
| 2005 |
Jan
(37) |
Feb
(31) |
Mar
(82) |
Apr
(119) |
May
(30) |
Jun
(5) |
Jul
(3) |
Aug
(9) |
Sep
(7) |
Oct
(14) |
Nov
(1) |
Dec
(10) |
| 2006 |
Jan
(32) |
Feb
(18) |
Mar
(12) |
Apr
(14) |
May
(10) |
Jun
(5) |
Jul
(1) |
Aug
(17) |
Sep
(21) |
Oct
(6) |
Nov
(27) |
Dec
(16) |
| 2007 |
Jan
(4) |
Feb
(6) |
Mar
(18) |
Apr
(1) |
May
(33) |
Jun
(6) |
Jul
(16) |
Aug
(12) |
Sep
(12) |
Oct
(9) |
Nov
(17) |
Dec
(31) |
| 2008 |
Jan
|
Feb
(4) |
Mar
(9) |
Apr
(29) |
May
(11) |
Jun
(7) |
Jul
(21) |
Aug
|
Sep
(3) |
Oct
(22) |
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
(5) |
Mar
(4) |
Apr
(8) |
May
(8) |
Jun
(9) |
Jul
(6) |
Aug
(2) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
|
| 2010 |
Jan
(16) |
Feb
(6) |
Mar
|
Apr
|
May
(27) |
Jun
(5) |
Jul
(2) |
Aug
(9) |
Sep
(1) |
Oct
(35) |
Nov
(5) |
Dec
|
| 2011 |
Jan
(18) |
Feb
(3) |
Mar
(18) |
Apr
(18) |
May
|
Jun
(4) |
Jul
|
Aug
(5) |
Sep
|
Oct
(3) |
Nov
(13) |
Dec
(9) |
| 2012 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
(1) |
Jun
(38) |
Jul
(5) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(9) |
| 2013 |
Jan
(3) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(6) |
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Sebastian S. <Seb...@SS...> - 2011-03-13 08:43:50
|
On Sat, 12 Mar 2011 23:04:55 -0500, will kahn-greene <wi...@bl...> wrote: > I'm really psyched to see things happening in the issue tracker. I've > been doing A/V work and haven't had time to do PyBlosxom work. However, > I met another PyBlosxom user here and he's interested in doing 1.5 work > on Monday. Thus, I'm planning to do a bunch of PyBlosxom work then. > > One of the things I'm going to tackle on Monday is the web-site. It > sucks. It should be way better. At a bare minimum, it shouldn't be so > horribly wrong about everything. One thing I was searching for lately, is the IRC channel of pyblosxom. This might be good info eg on the Mailling list page. Something like: If you prefer more direct communication, there are often some people hanging out on the IRC channel #pyb...@ch.... However, sometimes no one is listening or reading the channel for hours, so if you come over to say hello, be patient. would already help. Thanks :) Sebastian |
|
From: will kahn-g. <wi...@bl...> - 2011-03-13 04:05:14
|
I'm really psyched to see things happening in the issue tracker. I've been doing A/V work and haven't had time to do PyBlosxom work. However, I met another PyBlosxom user here and he's interested in doing 1.5 work on Monday. Thus, I'm planning to do a bunch of PyBlosxom work then. One of the things I'm going to tackle on Monday is the web-site. It sucks. It should be way better. At a bare minimum, it shouldn't be so horribly wrong about everything. Anyhow, I really apologize for not keeping up with things. Keep up the awesome work! /will |
|
From: will kahn-g. <wi...@bl...> - 2011-03-08 20:18:48
|
Hi! Sean and I talked about sprints on IRC yesterday and decided that instead of doing a single minor sprint, we'd do a 7-day sprint! Thus, I hereby welcome you all to Sprint Week for PyBlosxom 1.5! The Sprint Week will start on Thursday, March 10th and end a week later on Thursday, March 17th. The goal of the sprint is to finish everything off so we can do a PyBlosxom 1.5 release. This will make us all much happier. I encourage you all to participate, even if it's doing one thing on the list. If you need any help, send an email to the pyblosxom-devel list. 9 times out of 10, you'll need help because I didn't document something appropriately. Here's a non-exhaustive list of things that I'd like us to work on over the sprint week: 1. There are a list of issues marked with the 1.5 milestone. Working on these definitely gets us closer to a 1.5 release. Working on flavour packs, updating the plugin registry, and updating the documentation don't require and coding skills. 2. Also in the 1.5 milestone are a bunch of issues that were ported over from SourceForge bug tracker. You can recognize these because they all have ID: xxxxx at the end of the issue title. These need to be triaged. It's possible that some of these aren't issues anymore. 3. Going through the bug tracker for bugs that should be in the 1.5 milestone, but aren't. 4. Getting the most recent PyBlosxom from git and running the unit tests. If you bump into failures, write up an issue for each one. If you're able to fix the failures, sending patches is fantastic! 5. Fixing any other issues you have with PyBlosxom or the plugins or even writing new plugins. 6. Writing up issues for problems with the web-site, infrastructure, or other things. This doesn't require coding skills. I'm at PyCon 2011 from Thursday through Wednesday during much of this sprint. I'll be checking email and I'll be on IRC when I can be. I'll also plan to spend some quality time with PyBlosxom towards the end of the conference. I encourage you to participate. If there's anything that makes participating difficult, let me know and I'll work on reducing barriers to entry and blocks as much as I can. I'd love to get this release out the door, but I can't do it alone (unless we all want to wait another 6 months). Let the sprint begin! /will |
|
From: will kahn-g. <wi...@bl...> - 2011-02-24 23:54:43
|
PyBlosxom has an issue tracker at: http://pyblosxom.bluesock.org/bugs/ In the sidebar on the left towards the top is a link titled "Milestone 1.5". The url for that is: http://pyblosxom.bluesock.org/bugs/issue?status=-1,1,2,3,4,5,6,7&@sort=-activity&@search_text=&@columns=id,activity,title,creator,assignedto,status&@dispname=Milestone%201.5&@group=priority&milestone=1&@filter=status,milestone&@pagesize=50&@startwith=0 That's the current list of things we want to look into and/or do for 1.5. There are probably other things that aren't yet in the issue tracker. Capturing those would be really helpful! I've assigned issues I'm currently working on to myself (willg). Anything else is fair game. /will On 02/24/2011 06:48 PM, seanh wrote: > I's like to do this over IRC from the UK. I won't be available for the > whole period of March 9th-17th, but I should be free for some of it. > > I think working towards getting 1.5 out seems the most important > thing. Is there a list of what needs to be done for it? I'd be up for > picking tasks out of such a list and working on them. > > Besides getting 1.5 out and more experimentally, the jinja renderer > idea interests me and might be fun to work on. > > On 24 February 2011 16:12, will kahn-greene <wi...@bl...> wrote: >> I'm going to PyCon 2011 in Atlanta which I think is in two weeks. If >> anyone else is going, I'd love to do a sprint on any of the following >> things: >> >> 1. unit tests >> >> 2. documentation >> >> 3. fixing up the web-site >> >> 4. plugins >> >> 5. flavour packs >> >> 6. anything else that other people are interested in working on >> >> 7. anything that helps us get pyblosxom 1.5 out >> >> >> We could do the sprint in such a way that we're coordinating the sprint >> on irc so then people who are there and people who aren't there can all >> participate. >> >> If there are people interested, I'd like to assemble a small list of >> things that we'd like to work on so we're more likely to get things >> accomplished. >> >> Anyone interested? If so, what would you like to work on? >> >> /will >> >> ------------------------------------------------------------------------------ >> Free Software Download: Index, Search & Analyze Logs and other IT data in >> Real-Time with Splunk. Collect, index and harness all the fast moving IT data >> generated by your applications, servers and devices whether physical, virtual >> or in the cloud. Deliver compliance at lower cost and gain new business >> insights. http://p.sf.net/sfu/splunk-dev2dev >> _______________________________________________ >> Pyblosxom-devel mailing list >> Pyb...@li... >> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel >> > > ------------------------------------------------------------------------------ > Free Software Download: Index, Search & Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT data > generated by your applications, servers and devices whether physical, virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > Pyblosxom-devel mailing list > Pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel > |
|
From: seanh <sn...@gm...> - 2011-02-24 23:49:04
|
I's like to do this over IRC from the UK. I won't be available for the whole period of March 9th-17th, but I should be free for some of it. I think working towards getting 1.5 out seems the most important thing. Is there a list of what needs to be done for it? I'd be up for picking tasks out of such a list and working on them. Besides getting 1.5 out and more experimentally, the jinja renderer idea interests me and might be fun to work on. On 24 February 2011 16:12, will kahn-greene <wi...@bl...> wrote: > I'm going to PyCon 2011 in Atlanta which I think is in two weeks. If > anyone else is going, I'd love to do a sprint on any of the following > things: > > 1. unit tests > > 2. documentation > > 3. fixing up the web-site > > 4. plugins > > 5. flavour packs > > 6. anything else that other people are interested in working on > > 7. anything that helps us get pyblosxom 1.5 out > > > We could do the sprint in such a way that we're coordinating the sprint > on irc so then people who are there and people who aren't there can all > participate. > > If there are people interested, I'd like to assemble a small list of > things that we'd like to work on so we're more likely to get things > accomplished. > > Anyone interested? If so, what would you like to work on? > > /will > > ------------------------------------------------------------------------------ > Free Software Download: Index, Search & Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT data > generated by your applications, servers and devices whether physical, virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > Pyblosxom-devel mailing list > Pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel > |
|
From: will kahn-g. <wi...@bl...> - 2011-02-24 16:12:48
|
I'm going to PyCon 2011 in Atlanta which I think is in two weeks. If anyone else is going, I'd love to do a sprint on any of the following things: 1. unit tests 2. documentation 3. fixing up the web-site 4. plugins 5. flavour packs 6. anything else that other people are interested in working on 7. anything that helps us get pyblosxom 1.5 out We could do the sprint in such a way that we're coordinating the sprint on irc so then people who are there and people who aren't there can all participate. If there are people interested, I'd like to assemble a small list of things that we'd like to work on so we're more likely to get things accomplished. Anyone interested? If so, what would you like to work on? /will |
|
From: will kahn-g. <wi...@bl...> - 2011-01-26 10:56:20
|
Between the bugs we migrated over from SourceForge and new bugs that are being created, there's a fair amount of work for PyBlosxom. I've marked some of it as needing to be done in the 1.5 cycle. Half of those bugs, though, probably just need to be triaged. Anyhow, I need some help. At work, I'm in the middle of a very aggressive/ambitious development cycle that ends March 1st. I really want to make sure PyBlosxom continues to move forward rather than languishing in the eves of my free time. If anyone has an hour they can spare this week, I encourage you to pick a bug from the issue list and triage it. Triaging involves finding a bug marked "unread" or "chatting", reading through it, and answering the following questions: 1. is the bug reproducible with what's in git master? 2. if the bug is reproducible, is there a theory for what's going on and what might need to be fixed? Add a comment to the issue with your answers. And that's it! You don't have to fiddle with flags or issue metadata--just add a comment. Answering those two questions turns a bug from an unknown into something that we can do something with. The issue tracker is at: http://pyblosxom.bluesock.org/bugs/ The 1.5 milestone is at: http://pyblosxom.bluesock.org/bugs/issue?status=-1,1,2,3,4,5,6,7&@sort=-activity&@search_text=&@columns=id,activity,title,creator,assignedto,status&@dispname=Milestone%201.5&@group=priority&milestone=1&@filter=status,milestone&@pagesize=50&@startwith=0 There's a "Milestone 1.5" link in the sidebar of the issues page if that link is too ornery. Thank you! Your help will make it more likely we get an rc3 with a lot of bug fixes out in the near term rather than in June. /will |
|
From: Dieter P. <di...@pl...> - 2011-01-13 09:48:20
|
On Wed, 12 Jan 2011 16:16:40 +0200 Marius Gedminas <ma...@ge...> wrote: > On Wed, Jan 12, 2011 at 01:23:24PM +0100, Sebastian Spaeth wrote: > > That having said, I would be happy to see new things going on and > > perhaps help with some jinja2 work in the future. > > I would be interested in PyBlosxom using a more powerful templating > engine for its flavours. (Mako is my favourite at the moment.) > > I mostly miss lack of conditionals. > > Marius Gedminas There is a ticket about a new templating engine on roundup. add all your requirements there. (and preferably, start coding :) Dieter |
|
From: Marius G. <ma...@ge...> - 2011-01-12 14:16:48
|
On Wed, Jan 12, 2011 at 01:23:24PM +0100, Sebastian Spaeth wrote:
> That having said, I would be happy to see new things going on and
> perhaps help with some jinja2 work in the future.
I would be interested in PyBlosxom using a more powerful templating
engine for its flavours. (Mako is my favourite at the moment.)
I mostly miss lack of conditionals.
Marius Gedminas
--
There are only two things wrong with C++: The initial concept and the
implementation.
-- Bertrand Meyer
|
|
From: Sebastian S. <Seb...@SS...> - 2011-01-12 12:54:01
|
On Sat, 08 Jan 2011 12:18:34 -0500, will kahn-greene <wi...@bl...> wrote: > I haven't heard anything from anyone except for Tim. I (manually) > copied the bugs over from SF and closed two of them. Other than that, > no one has added any new bugs or continued this thread. > > Is this not the system you were hoping for? Have the fires of PyBlosxom > development cooled so much due to my ridiculous amount of bottlenecking > and business? Thanks for this. I haven't written back, as I was very happy with the plans (and you doing the hard work :-)). My pyblosxom setup is currently just working right(tm), so I am not very eager to open new construction sites at the moment :-). (Plus family and offlineimap taking most of my "free" time) That having said, I would be happy to see new things going on and perhaps help with some jinja2 work in the future. Sebastian |
|
From: Dieter P. <di...@pl...> - 2011-01-09 10:12:27
|
On Sat, Jan 08, 2011 at 12:18:34PM -0500, will kahn-greene wrote: > I haven't heard anything from anyone except for Tim. I (manually) > copied the bugs over from SF and closed two of them. Other than that, > no one has added any new bugs or continued this thread. a bit of patience man, I actually entered about 14 bugs yesterday (and that was before I even saw your "noone did anything" mail) On Sun, 9 Jan 2011 11:29:59 +0200 Marius Gedminas <ma...@ge...> wrote: > Also, I don't see any compelling benefits of upgrading, other than the > ability to test latest code and contribute plugin fixes back... And > I'm not convinced that people are interested in my fixes and > enhancements -- my emails on that topic back in 2009 never received > any response, and my last attempted plugin contribution was answered > by "why do people even care about this?". > > So that perhaps explains my lack of enthusiasm. I care about your work (you know this, cause I mailed you about it). So much, that I actually took patches out of your bzr tree, committed them into git (keeping you as author) and got them merged in the main tree. If you want your stuff merged, switching to git and using proper commit messages is a good first step. then submit merge requests. I actually found the "barrier to entry" pretty low compared to other projects who are more strict. (like, the magicword.py plugin contains some trailing whitespace, which is a big no-go in my book, but I didn't want to modify the plugin, and still it got merged - functionality-wise it works fine, btw) > Hey, I've seen worse-run open-source projects. I myself run some of > them, with patches languishing in my inbox for _years_ when I was > suffering from burnout. +1, I've seen much worse. Luckily, with a vcs like git it's not too bad to lag a bit behind, because folks can easily pull from each other. > I'm happy to see new activity with the website, documentation (Sphinx > rules), Git repositories, bug trackers. +1 Dieter |
|
From: Marius G. <ma...@ge...> - 2011-01-09 09:30:08
|
On Sat, Jan 08, 2011 at 12:18:34PM -0500, will kahn-greene wrote:
> I haven't heard anything from anyone except for Tim. I (manually)
> copied the bugs over from SF and closed two of them. Other than that,
> no one has added any new bugs or continued this thread.
Yes, well, you know how it is.
My blog is running on 1.4.something as packaged in Ubuntu, with lots of
tweaks in the plugins to make it work with my configuration. Given the
amount of breakage I've had to manually fix, I'm reluctant to upgrade
without first writing a test suite for my blog. And I'm unsure how to
start with that -- WebTest? Twill? Selenium?
Also, I don't see any compelling benefits of upgrading, other than the
ability to test latest code and contribute plugin fixes back... And I'm
not convinced that people are interested in my fixes and enhancements --
my emails on that topic back in 2009 never received any response, and my
last attempted plugin contribution was answered by "why do people even
care about this?".
So that perhaps explains my lack of enthusiasm.
> Is this not the system you were hoping for? Have the fires of PyBlosxom
> development cooled so much due to my ridiculous amount of bottlenecking
> and business?
Hey, I've seen worse-run open-source projects. I myself run some of
them, with patches languishing in my inbox for _years_ when I was
suffering from burnout.
I'm happy to see new activity with the website, documentation (Sphinx
rules), Git repositories, bug trackers.
Marius Gedminas
--
Life was simple before World War II. After that, we had systems.
-- Grace Murray Hopper, 1987
|
|
From: Dieter P. <di...@pl...> - 2011-01-08 21:00:16
|
thanks Will! *starts filing entries* I've noticed two things: * I can only specify my timezone as offset against UTC. no sense of daylight saving, it seems (I should probably complain to the roundup guys, not here) * I can modify any existing ticket (i.e. ones reported by other users) see history of http://pyblosxom.bluesock.org/bugs/issue17 Dieter |
|
From: will kahn-g. <wi...@bl...> - 2011-01-08 17:18:46
|
I haven't heard anything from anyone except for Tim. I (manually) copied the bugs over from SF and closed two of them. Other than that, no one has added any new bugs or continued this thread. Is this not the system you were hoping for? Have the fires of PyBlosxom development cooled so much due to my ridiculous amount of bottlenecking and business? On 01/06/2011 08:27 AM, will kahn-greene wrote: > I'm really sorry this took so long, but it's just been pretty crazy in > Will land. > > I went back to the conversation we had about issue tracking in October > and collected the following requirements: > > * web-based interface > * maximize ease of use > * use something pre-existing rather than writing our own > * use something that is widely used rather than something that isn't > widely used > * minimizes spam > * roadmap showing all the bugs in a given milestone so we know where > things are at > * activity so we know what's happening (or not happening) > > I had these additional requirements, but was ok with dropping them > depending on how compelling a given solution was: > > * use something we host and have full control over (I'm loathe to have a > SF-like experience again) > * use something written in php or python (those are languages I can deal > with easily and can extend) > * no Trac > * email interface > > > I've been doing some bug reporting for OpenHatch which uses Roundup. > After talking with Asheesh, I decided that Roundup meets a lot of these > requirements. I know there were a few people who dislike Roundup. I > suspect some of that is either theme related or interface related. More > on that in a smidge. > > Anyhow, I spent the last week or so working my way through Roundup, > installing it on my server, and with lots of help from Asheesh and the > OpenHatch crew, got milestones working. > > The result is at: > > http://pyblosxom.bluesock.org/bugs/ > > There are probably still some issues and the theme could be better > (which can also be said of the entire PyBlosxom site). > > Things I need help with: > > 1. I need someone to go through the bugtracker on SF and move bugs over > to the new bug tracker. > > 2. If there are problems with the new bug tracker, I need people to > write up bugs for them. I created an "infrastructure" keyword for any > issues regarding the PyBlosxom web-site, bug tracker, git repository, ... > > 3. If you've written an email to the devel list about a problem you're > having that you know hasn't been fixed yet, write it up as an issue. > Feel free to just copy and paste your email into the issue description. > > 4. If you're into theming, I'd love to get a better theme for the whole > PyBlosxom site including Roundup. Let me know if that's something > you're interested in. > > > In the meantime, I'm going to write up issues for the things I think > still need to be fixed for 1.5. > > After all that work, I think we'll be in a much better place. Amongst > other things, it'll be a lot clearer to all of us where we're at. > > One thing you'll notice is that there's no link to the issue tracker on > the PyBlosxom web-site. I'll rectify that today or tomorrow. I wanted > to make sure the issue tracker was working for all of us before I made > the whole thing public. > > I really appreciate that discussion on issue trackers a while back. > Thank you all for your input--it helped get us to where we're at now. > > /will |
|
From: will kahn-g. <wi...@bl...> - 2011-01-07 15:27:38
|
I just merged in a bunch of fixes from Dieterbe. Plus there have been a bunch of changes since rc2 as well, mostly in documentation. I was thinking of doing an rc3 release in the next week. Before I do that, what else do people want to fix? If I don't hear anything, I'll just do an rc3 release next week. Changes between rc2 and master: 1a1a51d add magicword plugin 6c4502d Bugfix: only render comment-story if comment-form will be rendered too. 4385ac8 Check whether absolute_path is set, not whether its length is non-zero 6abb6af No need to mention the `commandline` callback twice in the same list a7f1c5e print commandline errors to stderr, not stdout 7a42deb When errors happen on commandline, exit 1 instead of 0 6988482 Minor overhaul of comments chapter. 1cafccb Reworked including files. 385a9ba Tweaked language at top of INSTALL file. ede9570 Fixing old-style names to new-style names. 0a35f19 Added a warning about naming plugins the same as system packages. 1815cd1 Fixed titles in html and rss flavours. 7b8574c Updated load_plugins and plugin_dirs documentation. 9e33341 Minor tweak to quell a docs build warning. a7eadb7 Fixed documentation for plugin_dirs and load_plugins. d8a76f0 Fixes handling of wrong exception in tags plugin. a63b2ed Fixed formatting of CHANGELOG 1.5 item 21. 6ad2266 Reworked INSTALL to have a separate installation for hacking. f495517 Fixing the virtualenv activate line. 83f494b Reworked the INSTALL document. 5100808 Removed _escaped and _urlencoded value creation from comments. 8d93b38 Adding download_url to setup.py metadata. 4814f4b Added RELEASE process. d92f572 Fixed License classifier to work with PyPI. Many thanks to Dieterbe for his work--both fixing things and finding fixes that exist out there that should get merged into the core! /will |
|
From: will kahn-g. <wi...@bl...> - 2011-01-06 14:59:38
|
That's awesome! I didn't even know SF could export data. Can you send the xml file to me in email? Then I'll import it into Roundup? On 01/06/2011 09:56 AM, Tim Gray wrote: > On Jan 06, 2011 at 08:27 AM -0500, will kahn-greene wrote: >> 1. I need someone to go through the bugtracker on SF and move bugs over >> to the new bug tracker. > > I was going to take a stab at this, but it looks as if there is a way to do > an import that would save some time. I've got XML files of the bugs and > features issues from SF. Roundup has a script, import_sf.py, that looks as > if it will prepare those files for Roundup import. However, you need > Roundup installed to run it and I'm assuming you want to run it from the > system that your Roundup tracker is actually hosted on... > > Now, I don't know if it actually works at all. But I'm definitely not going > to get it going from this end. > > Tim |
|
From: Tim G. <tg...@pr...> - 2011-01-06 14:56:29
|
On Jan 06, 2011 at 08:27 AM -0500, will kahn-greene wrote: > 1. I need someone to go through the bugtracker on SF and move bugs over > to the new bug tracker. I was going to take a stab at this, but it looks as if there is a way to do an import that would save some time. I've got XML files of the bugs and features issues from SF. Roundup has a script, import_sf.py, that looks as if it will prepare those files for Roundup import. However, you need Roundup installed to run it and I'm assuming you want to run it from the system that your Roundup tracker is actually hosted on... Now, I don't know if it actually works at all. But I'm definitely not going to get it going from this end. Tim |
|
From: will kahn-g. <wi...@bl...> - 2011-01-06 13:28:09
|
I'm really sorry this took so long, but it's just been pretty crazy in Will land. I went back to the conversation we had about issue tracking in October and collected the following requirements: * web-based interface * maximize ease of use * use something pre-existing rather than writing our own * use something that is widely used rather than something that isn't widely used * minimizes spam * roadmap showing all the bugs in a given milestone so we know where things are at * activity so we know what's happening (or not happening) I had these additional requirements, but was ok with dropping them depending on how compelling a given solution was: * use something we host and have full control over (I'm loathe to have a SF-like experience again) * use something written in php or python (those are languages I can deal with easily and can extend) * no Trac * email interface I've been doing some bug reporting for OpenHatch which uses Roundup. After talking with Asheesh, I decided that Roundup meets a lot of these requirements. I know there were a few people who dislike Roundup. I suspect some of that is either theme related or interface related. More on that in a smidge. Anyhow, I spent the last week or so working my way through Roundup, installing it on my server, and with lots of help from Asheesh and the OpenHatch crew, got milestones working. The result is at: http://pyblosxom.bluesock.org/bugs/ There are probably still some issues and the theme could be better (which can also be said of the entire PyBlosxom site). Things I need help with: 1. I need someone to go through the bugtracker on SF and move bugs over to the new bug tracker. 2. If there are problems with the new bug tracker, I need people to write up bugs for them. I created an "infrastructure" keyword for any issues regarding the PyBlosxom web-site, bug tracker, git repository, ... 3. If you've written an email to the devel list about a problem you're having that you know hasn't been fixed yet, write it up as an issue. Feel free to just copy and paste your email into the issue description. 4. If you're into theming, I'd love to get a better theme for the whole PyBlosxom site including Roundup. Let me know if that's something you're interested in. In the meantime, I'm going to write up issues for the things I think still need to be fixed for 1.5. After all that work, I think we'll be in a much better place. Amongst other things, it'll be a lot clearer to all of us where we're at. One thing you'll notice is that there's no link to the issue tracker on the PyBlosxom web-site. I'll rectify that today or tomorrow. I wanted to make sure the issue tracker was working for all of us before I made the whole thing public. I really appreciate that discussion on issue trackers a while back. Thank you all for your input--it helped get us to where we're at now. /will |
|
From: Marius G. <ma...@ge...> - 2011-01-02 03:47:10
|
On Sat, Jan 01, 2011 at 09:20:24PM -0500, Will Kahn-Greene wrote: > On Sun, 2 Jan 2011, Marius Gedminas wrote: > >Can PyBlosxom support date-based URLs? > > Out of the box, PyBlosxom supports date-based archives. It should > be easy to write a plugin that does date-based urls like what > WordPress does. > > I'm not sure if that answers your question or not. It does, thanks. Specifically: - the core doesn't support it - it's possible to implement with a plugin - the plugin should be easy - nobody has written such a plugin Marius Gedminas -- Q: How many IBM CPU's does it take to execute a job? A: Four; three to hold it down, and one to rip its head off. |
|
From: Will Kahn-G. <wi...@bl...> - 2011-01-02 02:27:20
|
On Sun, 2 Jan 2011, Marius Gedminas wrote: > On Sat, Jan 01, 2011 at 12:01:51PM -0500, will kahn-greene wrote: >> I think date-based urls are also good for uniqueness. I may write >> several blog posts about my status on a certain project and all those >> posts will have the same tags and category, but they'll be at different >> date-based urls. > > Can PyBlosxom support date-based URLs? Out of the box, PyBlosxom supports date-based archives. It should be easy to write a plugin that does date-based urls like what WordPress does. I'm not sure if that answers your question or not. |
|
From: Marius G. <ma...@ge...> - 2011-01-02 00:24:37
|
On Sat, Jan 01, 2011 at 12:01:51PM -0500, will kahn-greene wrote: > I think date-based urls are also good for uniqueness. I may write > several blog posts about my status on a certain project and all those > posts will have the same tags and category, but they'll be at different > date-based urls. Can PyBlosxom support date-based URLs? Marius Gedminas -- 9. Okay, then, what do you think about "syntactic noise" in config files? !@#@!#(#%^!%$@#';,!@# -- http://alumnit.ca/wiki/index.php?page=RetchMail |
|
From: will kahn-g. <wi...@bl...> - 2011-01-01 17:02:07
|
I disagree that the content of a post has no relation to a date--it has every relation to a date because that's the day the person wrote it in the context of what he/she was doing and all the other things in his/her life. I treat my blog like an online journal and often refer to my date-based archives to figure out when I was doing things. I do this with other peoples' blogs, too. I find it really annoying when people don't provide date-based archives especially when they're referring to prior posts without linking to them. I think date-based urls are also good for uniqueness. I may write several blog posts about my status on a certain project and all those posts will have the same tags and category, but they'll be at different date-based urls. On 01/01/2011 08:05 AM, Dieter Plaetinck wrote: > On Sat, 1 Jan 2011 14:13:11 +0200 > Marius Gedminas <ma...@ge...> wrote: > >> Happy New Year, everyone! >> >> I've written a plugin to render a Blogger-like dynamic archive tree in >> the sidebar of my blog (http://mg.pov.lt/blog/). >> >> If anyone's interested, the code is at http://bit.ly/dQIF76 [1] >> >> [1] >> http://bazaar.launchpad.net/~mgedmin/%2Bjunk/blog/annotate/head%3A/plugins/tree.py >> is the ungainly and ugly full URL, *sigh* Bazaar *sigh* >> >> Marius Gedminas > > Something i've always pondered: > why do people care so much about dates on blogs? > i mean, many blog systems have url's like /<date>/entry.html > and PB also separates content by date (by default) on the front page, > and then those time-based selectors. > > when i search for content on a blog, i always try to search by category > or tag (or even type author name + subject in google), because the > content of a post usually has no particular relation to a date. > > Dieter |
|
From: Dieter P. <di...@pl...> - 2011-01-01 13:05:49
|
On Sat, 1 Jan 2011 14:13:11 +0200 Marius Gedminas <ma...@ge...> wrote: > Happy New Year, everyone! > > I've written a plugin to render a Blogger-like dynamic archive tree in > the sidebar of my blog (http://mg.pov.lt/blog/). > > If anyone's interested, the code is at http://bit.ly/dQIF76 [1] > > [1] > http://bazaar.launchpad.net/~mgedmin/%2Bjunk/blog/annotate/head%3A/plugins/tree.py > is the ungainly and ugly full URL, *sigh* Bazaar *sigh* > > Marius Gedminas Something i've always pondered: why do people care so much about dates on blogs? i mean, many blog systems have url's like /<date>/entry.html and PB also separates content by date (by default) on the front page, and then those time-based selectors. when i search for content on a blog, i always try to search by category or tag (or even type author name + subject in google), because the content of a post usually has no particular relation to a date. Dieter |
|
From: Marius G. <ma...@ge...> - 2011-01-01 12:32:25
|
Happy New Year, everyone! I've written a plugin to render a Blogger-like dynamic archive tree in the sidebar of my blog (http://mg.pov.lt/blog/). If anyone's interested, the code is at http://bit.ly/dQIF76 [1] [1] http://bazaar.launchpad.net/~mgedmin/%2Bjunk/blog/annotate/head%3A/plugins/tree.py is the ungainly and ugly full URL, *sigh* Bazaar *sigh* Marius Gedminas -- If something has not yet gone wrong then it would ultimately have been beneficial for it to go wrong. |
|
From: Glennie V. <gl...@gl...> - 2010-11-26 16:13:05
|
Hello, I'm in the process of (re)writing a moinmoin wiki syntax parser plugin for pybloxsom pyblosxom, as the existing one doesn't work with the current version. A working version of my code can downloaded from http://www.glennie.fr/dynamicdata/miscs/moinmoin.py. The rendering result can be viewed at http://pyblosxom.glennie.fr/. The raw entry file can be viewed at http://www.glennie.fr/dynamicdata/miscs/AdminWindowsLinux.txt and moinmoin format is at http://www.glennie.fr/AdministrationWindowsApartirDeLinux?action=rawAdminWindowsLinux.txt The raw moinmoin file is correctly rendrered under pyblosxom with just the entry title and "#parser moinmoin" added to it. The output can be used with any moinmoin theme with a little modification of and existing pyblosxom flavour. As the moinmoin uses some meta info starting with '#', in order to be used, the following patch should be applied to pyblosxom: ------------------- --- pyblosxom.py.ori 2010-11-26 11:39:25.000000000 +0100 +++ pyblosxom.py 2010-11-26 11:58:18.000000000 +0100 @@ -989,6 +989,7 @@ # call the preformat function args = {'parser': entry_data.get('parser', config.get('parser', 'plain')), 'story': lines, + 'filename': filename, 'request': request} entry_data["body"] = tools.run_callback( 'preformat', ----- As you can see, this is an one liner patch adding 'filename' to the args dict before calling before calling preformat hooks. Can you apply this patch to next release? Thanks -- http://www.glennie.fr The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. |
13 messages has been excluded from this view by a project administrator.
