Hi,

I agree on all you said.

> code drop is the next big thing, I would say. I already contacted Ole
> and Jerome regarding this. We generally want a complete import of the
> history, so we need to figure out how this goes.

[email protected] is the place to ask

> After that, we already had quite some contributors who signed the eZ
> Systems CLA. Derick is in charge of contacting those to send an Apache
> iCLA, so that we get clean IP for the project.

Thats a very good idea :-)

> I would very much like to import our old issue tracker data into Jira,
> if possible. Though, we will need to anonymize them somehow, since we
> cannot migrate user data due to privacy reasons. Do you think this would
> be possible? Whom should I contact in this direction, is Infra the right
> place to ask for this?

Also, its infra list. I know that was possible from bugzilla to jira,
so i assume that ther could be a chance with lets say CSV or
something. Infra knows

> Finally, we need to get our web site up and running. Kore already made a
> new design. Since the website was always generated static HTML, we
> should not have much issues.

Very well :-)
Infra usually prefers if static generated content is checked into SVN
in a specific location. The reason is to restore everything quickly in
case of a shutdown without knowing all the tools.

How are the pages generated?


> I think these are basically the next steps. Anything I forgot?

No, I agree with you.

Do you ask infra yourself? I think it should be OK

Cheers
Christian

> Cheers,
> Toby
> - --
> Tobias Schlitt         [email protected]       GPG Key: 0xC462BC14
> a passion for php                     http://schlitt.info/opensource
> eZ Components are Zeta Components now!          http://bit.ly/9S7zbn
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkwaHGYACgkQ5bO3TcRivBRO3gCfd75wXbPkbB7b824ANz6xPS6V
> gV8AoLa/GHE9WRTdgA3ghyLD11EqcG4l
> =YINi
> -----END PGP SIGNATURE-----
>

Reply via email to