I would like to be able to migrate the geodata committee's mailing
lists, their archives and the website off of CN and onto the new
infrastructure as soon as possible. The list archives have spam in
them, the website is so dreary and there's a lot of new things to put
in it. I would be happy to act as a guinea pig for the migration
process and to put in some work doing administrivia, whatever.
I have some questions about how all this is going to work out:
* Can we get a dump of the current list archives from CollabNet in
mbox format and import into whatever is replacing it (I assume
mailman?)
* Is there some arrangement with CollabNet staff to do this and to
shift the DNS over promptly when asked? Though i suppose we can use
an alternative domain - Gary also has osgeo.net registered - and
wait to move the whole zone over, not bother CN with piecemeal requests
Re the mailing list server setup I had imagined it would be more
straightforward to have all the mailing lists under one lists.osgeo.org
domain, the redundancy of the current foo@foo.osgeo.org scheme grates
on me a bit - maybe others disagree - it's a much more complex setup for
mailman to run multiple domains, isn't it?
* I would like to keep the geodata committee presence at geodata.osgeo.org
as it has been ... will that hold a drupal instance
and is there some way of providing a generic set of templates /
views that many different instances of committee / project sites
can re-use? Or is there something like this already in the plan?
I just recieved a test dump of a mailing list from cn this morning and am working on what has to be done to
convert ezmlm to mailman. The dump is an tar gzip file of the ezmlm directory associated with a specific mailing list. Thankfully ezmlm uses mbox (only needs a little massaging to get into proper mbox format) to create mailman archives. the subscribers now, that is a different story but, i think i'm pretty close to having the subscriber list figured out....only real issue is i don't think i'll be able to migrate info such as passwords or differentiating a user who was getting daily digests.
And i definitly have a preferance in not setting up virtual domains with mailman.
The DNS migration is being looked at right now.
Jo Walsh wrote:
dear all,
I would like to be able to migrate the geodata committee's mailing
lists, their archives and the website off of CN and onto the new
infrastructure as soon as possible. The list archives have spam in
them, the website is so dreary and there's a lot of new things to put
in it. I would be happy to act as a guinea pig for the migration
process and to put in some work doing administrivia, whatever.
I have some questions about how all this is going to work out:
* Can we get a dump of the current list archives from CollabNet in
mbox format and import into whatever is replacing it (I assume
mailman?)
* Is there some arrangement with CollabNet staff to do this and to
shift the DNS over promptly when asked? Though i suppose we can use
an alternative domain - Gary also has osgeo.net registered - and
wait to move the whole zone over, not bother CN with piecemeal requests
Re the mailing list server setup I had imagined it would be more
straightforward to have all the mailing lists under one lists.osgeo.org domain, the redundancy of the current foo@foo.osgeo.org scheme grates
on me a bit - maybe others disagree - it's a much more complex setup for
mailman to run multiple domains, isn't it?
* I would like to keep the geodata committee presence at geodata.osgeo.org
as it has been ... will that hold a drupal instance
and is there some way of providing a generic set of templates /
views that many different instances of committee / project sites can re-use? Or is there something like this already in the plan?
On Wed, Dec 13, 2006 at 02:44:07PM -0500, shawn barnes wrote:
story but, i think i'm pretty close to having the subscriber list
figured out....only real issue is i don't think i'll be able to migrate
info such as passwords or differentiating a user who was getting daily
digests.
List admins can also help tweak if needed, and i bet list members
won't mind having to adjust their settings, after all it is in a good
cause.
And i definitly have a preferance in not setting up virtual domains with
mailman.
Does anyone else have a strong opinion about list domains and are
their objections to having everything under lists.osgeo.org ? That way
CN could delegate the domain now and we could start using it, oh
almost right away, right?
Does anyone have thoughts about list archive search utilities /
better alternatives to pipermail? This isn't a priority, i suppose but
would be a real nice-to-have.
KK et al, you're on this list right? Do you think it will be easy to
make multiple drupal instances as little different as possible sharing
templates themes etc? I mean, there is no big rush, but i definitely
want to mess around with this in spare time between xmas and new year.
Hi jo walsh,
Yeah it can be possible to handle multiple drupal instance with little difference.
As soon HyperJohnGraham create a virtualhost for this on telascience server, i will copy current drupal instance there and make some policy to share themes and modules.
Waiting for comments from HyperJohnGraham .
On Wed, Dec 13, 2006 at 02:44:07PM -0500, shawn barnes wrote:
story but, i think i’m pretty close to having the subscriber list
figured out…only real issue is i don’t think i’ll be able to migrate
info such as passwords or differentiating a user who was getting daily
digests.
List admins can also help tweak if needed, and i bet list members
won’t mind having to adjust their settings, after all it is in a good
cause.
And i definitly have a preferance in not setting up virtual domains with
mailman.
Does anyone else have a strong opinion about list domains and are
their objections to having everything under lists.osgeo.org ? That way
CN could delegate the domain now and we could start using it, oh
almost right away, right?
Does anyone have thoughts about list archive search utilities /
better alternatives to pipermail? This isn’t a priority, i suppose but
would be a real nice-to-have.
KK et al, you’re on this list right? Do you think it will be easy to
make multiple drupal instances as little different as possible sharing
templates themes etc? I mean, there is no big rush, but i definitely
want to mess around with this in spare time between xmas and new year.
dear kk,
On Fri, Dec 15, 2006 at 07:53:19PM +0530, Kanhaiya kale ( ??? ??? ) wrote:
As soon HyperJohnGraham create a virtualhost for this on telascience
server, i will copy current drupal instance there and make some policy to
share themes and modules.
Okay, I'd imagined this all happening on the new machine. If that is
not too far away it could be better to wait? OTOH i would be up for
testing out the setup at telascience and working something up there if
it is going to be a while. Thanks, and a good policy on reuse of
druapl components, styling etc would be much apprec.
dear kk,
On Fri, Dec 15, 2006 at 07:53:19PM +0530, Kanhaiya kale ( ??? ??? ) wrote:
As soon HyperJohnGraham create a virtualhost for this on telascience
server, i will copy current drupal instance there and make some policy to
share themes and modules.
Okay, I’d imagined this all happening on the new machine. If that is
not too far away it could be better to wait?
I dont know that is happening on new machine or not.
We can wait for this.
OTOH i would be up for
testing out the setup at telascience and working something up there if
it is going to be a while.
As soon as setup is over, we will start to work on this.
Thanks, and a good policy on reuse of
druapl components, styling etc would be much apprec.
I can add a vhost to the telascience server ... what do you want ??
John
Kanhaiya kale ( कન્હૈযা ਕਾளெ ) wrote:
Hi jo walsh,
Yeah it can be possible to handle multiple drupal instance with little difference.
As soon HyperJohnGraham create a virtualhost for this on telascience server, i will copy current drupal instance there and make some policy to share themes and modules.
Waiting for comments from HyperJohnGraham .
Best Regards,
On 12/14/06, *Jo Walsh* <jo@frot.org <mailto:jo@frot.org>> wrote:
dear Shawn, this all sounds great, thanks.
On Wed, Dec 13, 2006 at 02:44:07PM -0500, shawn barnes wrote:
> story but, i think i'm pretty close to having the subscriber list
> figured out....only real issue is i don't think i'll be able to
migrate
> info such as passwords or differentiating a user who
was getting daily
> digests.
List admins can also help tweak if needed, and i bet list members
won't mind having to adjust their settings, after all it is in a good
cause.
> And i definitly have a preferance in not setting up virtual
domains with
> mailman.
Does anyone else have a strong opinion about list domains and are
their objections to having everything under lists.osgeo.org
<http://lists.osgeo.org> ? That way
CN could delegate the domain now and we could start using it, oh
almost right away, right?
Does anyone have thoughts about list archive search utilities /
better alternatives to pipermail? This isn't a priority, i suppose but
would be a real nice-to-have.
KK et al, you're on this list right? Do you think it will be easy to
make multiple drupal instances as little different as possible sharing
templates themes etc? I mean, there is no big rush, but i definitely
want to mess around with this in spare time between xmas and new year.
Hi John Graham,
Just like osgeodev.telascience.org, i want another virtualhost for another drupal instance.
and also access to that location like ssh,mysql db access etc.
I can add a vhost to the telascience server … what do you want ??
John
Kanhaiya kale ( कન્હૈযা ਕਾளெ ) wrote:
Hi jo walsh,
Yeah it can be possible to handle multiple drupal instance with
little difference.
As soon HyperJohnGraham create a virtualhost for this on telascience
server, i will copy current drupal instance there and make some policy
to share themes and modules.
Waiting for comments from HyperJohnGraham .
On Wed, Dec 13, 2006 at 02:44:07PM -0500, shawn barnes wrote:
story but, i think i’m pretty close to having the subscriber list
figured out…only real issue is i don’t think i’ll be able to
migrate
info such as passwords or differentiating a user who
was getting daily
digests.
List admins can also help tweak if needed, and i bet list members
won’t mind having to adjust their settings, after all it is in a good
cause.
And i definitly have a preferance in not setting up virtual
domains with
mailman.
Does anyone else have a strong opinion about list domains and are
their objections to having everything under lists.osgeo.org
<http://lists.osgeo.org> ? That way
CN could delegate the domain now and we could start using it, oh
almost right away, right?
Does anyone have thoughts about list archive search utilities /
better alternatives to pipermail? This isn’t a priority, i suppose but
would be a real nice-to-have.
KK et al, you’re on this list right? Do you think it will be easy to
make multiple drupal instances as little different as possible sharing
templates themes etc? I mean, there is no big rush, but i definitely
want to mess around with this in spare time between xmas and new year.
On 15-Dec-06, at 6:23 AM, Kanhaiya kale ( कન્હૈযা ਕਾளெ ) wrote:
Hi jo walsh,
Yeah it can be possible to handle multiple drupal instance with little difference.
As soon HyperJohnGraham create a virtualhost for this on telascience server, i will copy current drupal instance there and make some policy to share themes and modules.
If we've had this discussion already, please remind me.. but it seems we need to agree on our approach for handling subdomains/vhosts on our new install.
This affects both mailing lists and drupal sites equally as much. Because our historic infrastructure automatically creates subdomains for every project, we have a legacy of many many subdomains that are marginally useful.
I think we've already discussed mailing lists, but I hope we can move to a format like:
project@lists.osgeo.org and project-dev@lists.osgeo.org
Instead of the historic discuss@project.osgeo.org and dev@project.osgeo.org.
Similarly on the www/drupal side, we have http://project.osgeo.org, even for projects that have a marginal web presence. I believe it is safe to say that maintaining this level of vhost management is more painful than simply adding node-based drupal urls like: http://osgeo.org/project
That way there is no vhost set up required and CMS managers can do dirty work without bothering sysadmins. Of course, we have some legacy usage of http://project.osgeo.org - but can we do some rewrites to handle this in the meantime?
I am innately opposed to having multiple drupal instances unless we really really need to. I don't assume I'm correct in my logic, but I think this is a good time to aim for simplicity. So I ask, at what point do we want/need to keep content all in the same drupal instance? Can we aim to reduce our need to use subdomains? When is it beneficial to use them instead? Can we 'theme' different parts of a drupal site, i.e. by group? (e.g. so http://osgeo.org/project1/* has different theme than http://osgeo.org/project2/* )?
Other thoughts? Am I being too complicated or too simplistic?
Does anyone have thoughts about list archive search utilities /
better alternatives to pipermail? This isn't a priority, i suppose but
would be a real nice-to-have.
For the grass.itc.it site, I have set up Mailman with
- htdig + google search engine
- bogofilter as spamfilter for the open lists (web server
feedback list, bugtracker etc)
- some handcrafted procmail rules to filter standard rubbish
- fix for signed mails to not make them finish as shrubbed attachment
