Re: [Twisted-Python] Issues 0.1 alpha release
On Thu, Jun 26, 2003 at 02:20:51PM +1000, Richard Jones wrote: Content-Description: signed data
On Wednesday 25 June 2003 12:17 pm, Jonathan Lange wrote:
Issues, a issue tracking system built on Twisted technology, has been released for the first time today!
Could I ask why you've developed this from scratch rather than use Roundup's core?
Sure. The answer is that I didn't know about it. No one has told me about Roundup, and it didn't stand out in any of my previous investigations into bug trackers (some of which were more than cursory). I guess I'll have to investigate Roundup further. Oops, jml
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, June 27, 2003, at 08:05 AM, Jonathan
No one has told me about Roundup, and it didn't stand out in any of my previous investigations into bug trackers (some of which were more than cursory).
I guess I'll have to investigate Roundup further.
I posted about developing a twisted frontend to Roundup a while ago, I guess you a) weren't subscribed then or b) missed it :) I've been told that developing a front-end will be a doddle - similar to Roundup's current HTTPServer (roundup-server) frontend. That'll get you going right now. I believe the backend will need a little more attention to make it play nicely with the async nature of twisted (speaking from my basic knowledge of twisted here). That should be pretty easy to do too - the backend has fairly simple requirements. Anthony Baxter's looking into an Oracle backend, which would rock :) Richard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (Darwin) iD8DBQE++uumrGisBEHG6TARArNvAJ0epYWpRwIal4JPuToKz8Ebxe7GzgCdFX+n trhCqm90o3xW0nZp9kctc70= =8ZV/ -----END PGP SIGNATURE-----
Richard Jones wrote I believe the backend will need a little more attention to make it play nicely with the async nature of twisted (speaking from my basic knowledge of twisted here). That should be pretty easy to do too - the backend has fairly simple requirements. Anthony Baxter's looking into an Oracle backend, which would rock :)
I'm still working on the design issues - trying to de-serialise the hyperdb code... -- Anthony Baxter <anthony@interlink.com.au> It's never too late to have a happy childhood.
On Thu, Jun 26, 2003 at 10:48:31PM +1000, Richard Jones wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Friday, June 27, 2003, at 08:05 AM, Jonathan
No one has told me about Roundup, and it didn't stand out in any of my previous investigations into bug trackers (some of which were more than cursory).
I guess I'll have to investigate Roundup further.
I posted about developing a twisted frontend to Roundup a while ago, I guess you a) weren't subscribed then or b) missed it :)
Probably b), being a heartless b., I tend to skip through the "I'm using twisted and I don't understand" posts (you know, the one's that would go to twisted-user if there was such a thing). Invariably I miss a few important ones. Here comes the pseudo-intelligent, almost-thought-out response to compliments yesterday's "oops" post. I've had a brief look at Roundup and I agree that a Twisted frontend to it would rock. However, Issues seems to have distinctly different design goals. I wasn't joking when I said Issues was all about simplicity (at least, in these first few releases). We've (the Issues dev team) been thinking about how to do the simplest possible bugtrack, mostly without reference to existing implementations (although we've looked at a lot of design docs). The basic "workflow" is modelled on something between a two-player conversation and a singles tennis match. The ball is in court A, court B, or the game is over. That's it. However, Roundup is way more featureful than that. It has a guiding principle of generality, which is far removed from Issues guiding principle of simplicity. Which of course doesn't rule out the idea of me making Issues some sort of Roundup plugin. It's certainly worth considering. Roundup looks like it rocks, and it obviously kicks some design ass. However, Issues (so far) is a mini experiment in how simple an issue-tracking workflow can get. cheers, jml
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, June 27, 2003, at 11:28 PM, Jonathan Lange wrote:
The basic "workflow" is modelled on something between a two-player conversation and a singles tennis match. The ball is in court A, court B, or the game is over. That's it.
However, Roundup is way more featureful than that. It has a guiding principle of generality, which is far removed from Issues guiding principle of simplicity. Which of course doesn't rule out the idea of me making Issues some sort of Roundup plugin. It's certainly worth considering.
That's not necessarily true. The Roundup default tracker schema (see the online demo or the "instant gratification" python demo.py when you download the source) aims for simplicity. One of the implementation goals is flexibility of schema and workflow, which is what you get when you delve under the covers to make the tracker work just the way you wish it to. The ball game workflow you describe above (if I follow it correctly) could trivially be implemented in Roundup with the simple addition of some reactor code (which may be what you're referring to by the term "plugin" :)
Roundup looks like it rocks, and it obviously kicks some design ass. However, Issues (so far) is a mini experiment in how simple an issue-tracking workflow can get.
Fair enough. I'd just hate to see effort wasted on developing Yet Another Tracker just to fit the Twisted framework - when I believe that it'd be such a simple job getting Roundup running in that framework. Roundup's development has been going for two years now (and it seemed like it'd be such a quick-n-simple job when I started - there always seems to be some new feature that's really cool and just has to be implemented ;) One of these days, I might find some spare time to actually do the job myself, but don't hold your breath :) Richard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (Darwin) iD8DBQE+++ZFrGisBEHG6TARAmDkAJ9HxgopsemztL84e4PWNdCHw335MACfS/eG GImWfhu5/NoeeyBFdUvc9o0= =3MT2 -----END PGP SIGNATURE-----
Probably b), being a heartless b., I tend to skip through the "I'm using twisted and I don't understand" posts (you know, the one's that would go to twisted-user if there was such a thing). Invariably I miss a few important ones.
I proposed a few weeks ago to create a web forum such as forums.gentoo.org, but every body here said that the mailing is doing its job quite well :-(
participants (4)
-
Anthony Baxter -
Jonathan Lange -
Philippe Lafoucrière -
Richard Jones