Ticket #3072 (closed task: fixed)

Opened 2 years ago

Last modified 2 years ago

web2.dav should be moved out to a separate project

Reported by: dreid Owned by: wsanchez
Priority: highest Milestone: Web2-Gold-Master
Component: web2.dav Keywords:
Cc: Branch:
Author: Launchpad Bug:

Description

This will allow web2 trunk to make changes which break compatibility with web2.dav. The idea is that it will let us speed up web2 development without having to refactor/rewrite all of the internally dependent dav code.

Presumably web2.dav should move to  http://calendarserver.org.

Once web2 is folded back into twisted.web (i.e. done) we can reevaluate adding dav back in.

Attachments

eradicate_dav.diff Download (295.8 KB) - added by dreid 2 years ago.
A patch that eradicates DAV from trunk.

Change History

Changed 2 years ago by glyph

This sounds like a great idea. I feel like Twisted's development style has gummed up the works for the DAV project as well, and I've felt a little bad about not being able to speed up reviews and help with integrating patches and such. I'm looking forward to streamlining processes for both projects, and the eventual re-integration of everything :).

Having a separate project on  http://calendarserver.org will also provide some higher profile for Twisted, since the actual calendar server page doesn't currently mention Twisted, but presumably a "DAV support for Twisted" page would.

One thing that might be good to consider while doing this is having some web plugin mechanism so that web2.dav (or whatever its new name will be) can be easily deployed as a plugin via the twistd command line. Maybe that's just a twistd plugin for dav, maybe it's something more.

Changed 2 years ago by wsanchez

  • priority changed from normal to highest
  • status changed from new to assigned

Here's what I propose:

  1. Merge the long-outstanding ACL branch (which is used by Calendar Server at calendarserver.org, web2.dav's most active user is using) down to trunk.
  2. Delete web2.dav from trunk.
  3. Create a branch for DAV, and add web2.dav there.

This enables web2 to continue development on trunk without being constrained by web2.dav. It becomes the web2.dav developers' responsibility to reconcile any problems by merging forward periodically. It also enables web2.dav to evolve a bit faster without affecting anything on trunk.

Some time after web2 is considered stable, web2.dav should be able to merge forward, become stable itself, then go back to review for a pull-down to trunk.

I would think it likely that a web2 release would happen without DAV before we do such a pull-down.

That advantage to this over pulling it out to another project is that we don't have to change the namespace out of twisted only to switch it back later, which is significant work on both web2.dav and its clients.

I talked to glyph about this yesterday, and he thought this would be a workable plan.

Changed 2 years ago by wsanchez

  • milestone set to Web2-Gold-Master

Changed 2 years ago by dreid

(In [22825]) Merging forward

Refs #3072

Changed 2 years ago by dreid

A patch that eradicates DAV from trunk.

Changed 2 years ago by wsanchez

FWIW, attache patch is all removals except the last file (twisted/web2/tap.py).

Changed 2 years ago by dreid

  • status changed from assigned to closed
  • resolution set to fixed

(In [22836]) Delete twisted.web2.dav and all references to it except in the autogenerated zsh completion files.

Author: dreid Reviewer: exarkun

Refs #3078 Fixes #3072

Changed 2 years ago by radix

(In [22867]) Delete twisted.web2.dav and all references to it except in the autogenerated zsh completion files.

Author: dreid Reviewer: exarkun

Refs #3078 Fixes #3072

Note: See TracTickets for help on using tickets.