Re: issue tracking -- let's fix this!
Sebastian Spaeth <[email protected]> Fri, 01 Oct 2010 08:33:46 +0200
| Newsgroups | gmane.comp.web.pyblosxom.devel |
|---|---|
| Message-ID | <[email protected]> |
On 2010-09-30, will kahn-greene wrote: > We've switched from svn to git. That solved a bunch of problems. Yay! Yay! > We've moved the website from Sourceforge to Bluesock (my server) and > that's solved some problems and has the potential to solve more > problems. Yay! Even more yay! > 1. issue tracking I have used roundup which is written in python and used by python.org. It seems decent and has an email interface, so you can log issues just by sending an email. (a cron script polling a mailbox, so you could run a spamfilter before) It is pretty ok, I think. No spam filter built into it though. As for distributed git-based stuff, here is a list http://www.cs.unb.ca/~bremner/blog/posts/git-issue-trackers/ Of these, these 2 seem most interesting to me: http://bugseverywhere.org/be/show/HomePage http://syncwith.us/sd/ Otherwise, there are hosted things such as: http://lighthouseapp.com/ which provide free issue tracking, but that one requires an account with them. > Should we roll our own system using the PyBlosxom core? Hehe, a bugtracking plugin for pyblosxom? Sounds like a cool idea. Especiall http://bugseverywhere.org/be/show/HomePage (bugs in git alongside the source code) which is written in python could proabably be adapted to have a pyblosxom interface, their current webfrontent is using web.py and some templates. it seems. have never used it though. Sebastian ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev