Hi Jörn,
Jörn Nettingsmeier schrieb:
Thorsten Scherler wrote:
On Thu, 2009-02-12 at 18:05 +0100, Andreas Hartmann wrote:
Vik Tara schrieb:
I'll check out and take a look - some of my team would also like to lend
a hand.
Cool, TIA!
Thanks for the offer Vik, we really appreciate your offer. However the
zone server can only be operated by lenya committers since the access is
not public.
goes to show that we really need to make it easier for non-committers to
collaborate :( this situation sucks. we really cannot afford to lose
people who are willing to do such work.
how about vik and his team check out the code, do the migration on their
machine and create a new publication that could then be added by a
committer (me, for example)?
sure, we would lose the history information, but i don't think that's
crucial for a publication. (for code, it's priceless, of course).
the docu publication works well with the current 2.0.x branch. What
needs to be updated are the scripts that run the nightly builds for the
tests and demo, basically the setup of the SVN commands etc.
another matter: as you know, i've been pulling daily off-site backups of
the publication. i don't think it's wise that no other committer has
access to those (people do get run over by buses, after all), so i would
welcome lenya committers to send me their public keys so that they will
be able to look at and possibly restore backups from
[email protected]:lenya-docu-backup if the need
arises.
Thanks for this offer – I'll send you my key.
i briefly thought about making them available via a http server, but
that would involve some bot magic and extra security measures since i'm
pulling the user information as well, and that could be hairy.
I think the keys would be sufficient, after all it's "just" a backup for
emergency situations when even the ASF infrastructure backup fails.
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
