[zeta] Re: Rewritten History: Zeta on Github

yes, sounds good!

On Mon, May 21, 2012 at 9:25 AM, Nicolas Pastorino <nfrp[@]ez.no> wrote:

> Hi,
>
> On Sunday, May 20, 2012 at 08:39 , Benjamin Eberlei wrote:
>
>
>
> On Wed, Apr 25, 2012 at 1:39 AM, Benjamin Eberlei <kontakt[@]beberlei.de>wrote:
>
> Hello everyone,
>
> i have just completed the migration of the Apache SVN to Github
> organization: Code is still pushed at the moment, these are the done tasks:
>
> https://github.com/zetacomponents
>
> * Each component is split into its own repository
> * Author Information has been updated on frequent committers i have the
> email of.
> * composer.json was added to every project. No dependencies were defined
> on other components (even though could be done through DEPS) - because the
> Base version was never specified and such the information is incomplete
> anyways. Releases in the future should go and specificy the dependencies of
> packages more explicitly.
> * All tags have been generated from the commit messages.
> * MVCTools Migration didnt work, I have to try this again.
> * Document has some problem with GC and is very large repo, i have to
> cleanup or remigrate so i didnt push to github yet.
>
> However code is not yet free for all, we have some problems to tackle:
>
> * Do we need to adjust the headers? If yes, we should do this now using a
> mass-edit.
> * Unit-tests have still to be fixed, we need a generic approach for all
> components for that.
> * I plan to fix the Archive component as an example.
> * All packages have to be put on packagist.org so can be used with
> Composer
>
>
> 1. Ok, so it seems we retired successfully from Apache Foundation and we
> can keep the name, but we have to state explicitly that we retired from
> Apache on the website.
>
> 2. I still have some mass updating to do, which i will do tonight or
> tomorrow. Add testing glue-code as shown here,
> https://github.com/zetacomponents/Archive/commit/541b1faca6d63c441bead83fe8ca5d9e174afe53
>
> 3. We should render a new version of the docs into gh-pages. Can you do
> that Kore? Also zetacomponents.org should point there (or to the github
> repo). I can help you set that up with github (if not only poke you to do
> it ;))
>
> 4. Github Teams can be opened now, code is "free for all" :-) I am not
> sure about the proceeding here, but i guess the old team will claim
> components they can/want to still maintain and then everything still left
> is either being actively deprecated or a new maintainer is searched for. I
> will open a new thread for this.
>
> 5. I will register each package on Packagist, so it can be installed
> through Composer asap.
>
> 6. I will post a rough guide on how to fix the tests for a component.
>
> 7. I will post a guide on the ML how to add a component to Travis CI after
> testing works for a component.
>
> Well done !
>
> It seems I can include more definitive information in the blog post to the
> eZ Publish Community (name, repo URL, packagist support).
> Let me know if you guys think this is not ok.
>
> Cheers,
> --
> Nicolas
>
>
>
>
> greetings,
> Benjamin
>
>
>
>
Received on Mon May 21 2012 - 08:26:15 BST