Re: [Mailman-Developers] Mailman "true virtual hosting" and Google SoC


"Heikki Lampén" <heikki.lampen@gmail.com> writes:
It will happen some time, it's just a question of when.
Exactly.
I've been busy with other things, but I'm planning to finish the vhost stuff some time in June (if nobody has beat me to it until then).
"Finish" would mean that we can go into production here with an unofficial 2.1-vhost branch based on 2.1 (we probably want this sooner than an official 2.2 release can be reasonably be expected to happen).
This planning of mine includes getting the vhost branch ported to 2.2 while developing the 2.1 version. The idea is that we can just use the official Mailman code by the Mailman team after the 2.2 release.
Practical issues:
- I need to get the copyright assignment form stuff done.
- Either I have to learn and cope with svk or someone with sufficient karma would need to trust me enough to provide me with svn write access.
Then I'd probably best create an svk/svn branch each off 2.1 and 2.2, then start on the 2.1-vhost branch and maintain 2.2-vhost to keep in sync with my main project of 2.1-vhost.
OK, and first I'd want to wait until 2006-05-23 to make sure there is no SoC project concurrently working on the vhost issue.
Gruß,
Uli

"Heikki Lampén" <heikki.lampen@gmail.com> writes:
It will happen some time, it's just a question of when.
Exactly.
I've been busy with other things, but I'm planning to finish the vhost stuff some time in June (if nobody has beat me to it until then).
"Finish" would mean that we can go into production here with an unofficial 2.1-vhost branch based on 2.1 (we probably want this sooner than an official 2.2 release can be reasonably be expected to happen).
This planning of mine includes getting the vhost branch ported to 2.2 while developing the 2.1 version. The idea is that we can just use the official Mailman code by the Mailman team after the 2.2 release.
Practical issues:
- I need to get the copyright assignment form stuff done.
- Either I have to learn and cope with svk or someone with sufficient karma would need to trust me enough to provide me with svn write access.
Then I'd probably best create an svk/svn branch each off 2.1 and 2.2, then start on the 2.1-vhost branch and maintain 2.2-vhost to keep in sync with my main project of 2.1-vhost.
OK, and first I'd want to wait until 2006-05-23 to make sure there is no SoC project concurrently working on the vhost issue.
Gruß,
Uli
participants (2)
-
Hans Ulrich Niedermann
-
Heikki Lampén