> Yes, will be taken care of. I am volunteering to register the domain and
> manage access. I think we have an enthusiastic volunteer for web master ...
> not me. There is a loose team of 3-4 of us who have already been
> coordinating among ourselves so redundancy should not be a major problem.
> In this posting:
> http://mail.python.org/pipermail/baypiggies/2006-April/thread.html >
> Deirdre mention restricted sftp access for some accounts. I would like to
> get root access for management purposes.
Good. Ok, I'll review the thread there just to get myself up to speed, and
will send you the root access (it's not really root) details to you.
Deirdre, if you haven't done the domain name transfer thing yet, could you pass
the domain to Dennis rather than me? He's been active with Baypiggies, and I
trust him with it.
> I sense that whoever is providing hosting might want to stop providing
> hosting. Also, the CMS tools might change with a new webmaster. Both of
> these possibilities suggest a server move is in the future. I hope that
> addressing what needs to be known is part of the "server details" you are
> writing up.
We do have the option of running other services on python-hosting. For
example, they appear to allow Zope, TuroGears, or Django installs. (Has anyone
heard of this crazy Django thing? *wink*) I guess I'm trying to say: moving
is always possible, but let's see if we can accomodate the CMS at
Baypiggies mailing list
[hidden email] http://mail.python.org/mailman/listinfo/baypiggies