Menu
▾
▴
pyblosxom-devel
|
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: 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 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: 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: 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: 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-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: 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: 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: 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 |
Thanks for helping keep SourceForge clean.
X