[Twisted-Python] The Argument I Lost
![](https://secure.gravatar.com/avatar/d6328babd9f9a98ecc905e1ccac2495e.jpg?s=120&d=mm&r=g)
I was confused by the recent discussion of the recent tmlabs.* hierarchy, so there was a long discussion on IRC tonight about how exactly the various splits are going to proceed. We almost reached a consensus about how things should work, except foom (James Knight) managed to win the argument about how it should work eventually. However, I'm more irritating than he is, so we're still doing things my way. To recap, James's way, which is similar to what was discussed on the list before, is: Keep everything in the same repository, but provide different top-level directories for Twisted and the new split-off packages, e.g. svn://.../trunk/Twisted/twisted/internet/..., svn://.../trunk/TwistedNews/twisted/news/... (previously we were going to keep everything in different repositories, but we agreed that this was unnecessary and came with several unpleasant restrictions) Move code in new subdirectories to the tmlabs.* hierarchy for marketing purposes because it provides a cleaner separation between core and applications. However, I feel that there are lots of other hierarchy reorganizations that are potentially a good idea, and this is another step. Set up buildbot to run application packages against both last-released core and most-current core. My way is: For now... The repository mostly stays how it is. Buildbot keeps running against trunk, but against a series of application packages instead of twisted.test. Package names do not change. Eventually, one or all of these may need to change. However, all that will be happening to split out packages is: Modules in protocols/, test/, and tap/ move to an appropriate top-level package, with backward-compatibility wrapper. The release script will be changed to generate separate tarballs for various top-level packages. We will create a topfiles/ directory or somesuch to contain READMEs, setup.py's, etc., for each subproject. Barring any strong objections, this smaller, simpler plan is now how the releases should proceed. We do still intend to do new websites and download areas for each subproject (sorry maintainers, you're not getting out of writing HTML!), just not new repositories. Hopefully this will be a bit easier on users as we will get decoupled release cycles, but aside from protocols moving, it should require no code changes to remove all import-related deprecation warnings. The main point in this change in plan is to avoid doing too many things at once, to make sure that the whole split finishes before someone implements some crazy new features. Therefore, issues such as how to version APIs, re-organize modules, or re-name packages will be addressed *after* the appropriate changes for this split have been prepared, but feel free to discuss them beforehand. I will be replying to James's setversion proposal soon.
![](https://secure.gravatar.com/avatar/d7875f8cfd8ba9262bfff2bf6f6f9b35.jpg?s=120&d=mm&r=g)
On Sat, 2004-04-24 at 02:41, Glyph Lefkowitz wrote:
Barring any strong objections, this smaller, simpler plan is now how the releases should proceed.
Here's how I think the remaining unmentioned pieces should work: 1. Issue tracker will be the same for all projects unless it's a big enough project (e.g. web). 2. Docs are included in per-project directories. 3. Mailing list is the same for all projects (unless it's big enough, again e.g. web). -- Itamar Shtull-Trauring http://itamarst.org Looking for a job -- http://itamarst.org/resume.html
![](https://secure.gravatar.com/avatar/15fa47f2847592672210af8a25cd1f34.jpg?s=120&d=mm&r=g)
On Apr 24, 2004, at 10:23 AM, Itamar Shtull-Trauring wrote:
1. Issue tracker will be the same for all projects unless it's a big enough project (e.g. web).
It would be *really* nice if the issue tracker sanely supported multiple projects in one tracker. Such that each can have separate bug listings, but that you could transfer/reassign bugs between them and good things like that. The "tag" system it has can kinda do that, but noone ever fills it out because it's a textfield instead of a required-entry popup menu, which it really probably should be. James
![](https://secure.gravatar.com/avatar/d7875f8cfd8ba9262bfff2bf6f6f9b35.jpg?s=120&d=mm&r=g)
On Sat, 2004-04-24 at 11:56, James Y Knight wrote:
It would be *really* nice if the issue tracker sanely supported multiple projects in one tracker.
Roundup supports user-extensible schemas, so it should be pretty easy to add this. -- Itamar Shtull-Trauring http://itamarst.org Looking for a job -- http://itamarst.org/resume.html
![](https://secure.gravatar.com/avatar/3bef09da3292c944649ffc28673df870.jpg?s=120&d=mm&r=g)
On Sat, Apr 24, 2004, Itamar Shtull-Trauring wrote:
This will still be a pain for anyone doing cross-project work *cough*docs*cough*. I'm tempted to say that projects that are large enough to get their own bug tracker ought to consider getting their own docs editor, release manager etc. -Mary
![](https://secure.gravatar.com/avatar/d7875f8cfd8ba9262bfff2bf6f6f9b35.jpg?s=120&d=mm&r=g)
Another question - what should the main site for Twisted core be? http://projects.twistedmatrix.com/twisted/ or www.twistedmatrix.com? (If the former we will provide backwards-compatability for the important URLs, of course).
![](https://secure.gravatar.com/avatar/d7875f8cfd8ba9262bfff2bf6f6f9b35.jpg?s=120&d=mm&r=g)
On Sat, 2004-04-24 at 02:41, Glyph Lefkowitz wrote:
Barring any strong objections, this smaller, simpler plan is now how the releases should proceed.
Here's how I think the remaining unmentioned pieces should work: 1. Issue tracker will be the same for all projects unless it's a big enough project (e.g. web). 2. Docs are included in per-project directories. 3. Mailing list is the same for all projects (unless it's big enough, again e.g. web). -- Itamar Shtull-Trauring http://itamarst.org Looking for a job -- http://itamarst.org/resume.html
![](https://secure.gravatar.com/avatar/15fa47f2847592672210af8a25cd1f34.jpg?s=120&d=mm&r=g)
On Apr 24, 2004, at 10:23 AM, Itamar Shtull-Trauring wrote:
1. Issue tracker will be the same for all projects unless it's a big enough project (e.g. web).
It would be *really* nice if the issue tracker sanely supported multiple projects in one tracker. Such that each can have separate bug listings, but that you could transfer/reassign bugs between them and good things like that. The "tag" system it has can kinda do that, but noone ever fills it out because it's a textfield instead of a required-entry popup menu, which it really probably should be. James
![](https://secure.gravatar.com/avatar/d7875f8cfd8ba9262bfff2bf6f6f9b35.jpg?s=120&d=mm&r=g)
On Sat, 2004-04-24 at 11:56, James Y Knight wrote:
It would be *really* nice if the issue tracker sanely supported multiple projects in one tracker.
Roundup supports user-extensible schemas, so it should be pretty easy to add this. -- Itamar Shtull-Trauring http://itamarst.org Looking for a job -- http://itamarst.org/resume.html
![](https://secure.gravatar.com/avatar/3bef09da3292c944649ffc28673df870.jpg?s=120&d=mm&r=g)
On Sat, Apr 24, 2004, Itamar Shtull-Trauring wrote:
This will still be a pain for anyone doing cross-project work *cough*docs*cough*. I'm tempted to say that projects that are large enough to get their own bug tracker ought to consider getting their own docs editor, release manager etc. -Mary
![](https://secure.gravatar.com/avatar/d7875f8cfd8ba9262bfff2bf6f6f9b35.jpg?s=120&d=mm&r=g)
Another question - what should the main site for Twisted core be? http://projects.twistedmatrix.com/twisted/ or www.twistedmatrix.com? (If the former we will provide backwards-compatability for the important URLs, of course).
participants (4)
-
Glyph Lefkowitz
-
Itamar Shtull-Trauring
-
James Y Knight
-
Mary Gardiner