and this readme also : <a href="https://github.com/gatein/gatein-portal/blob/master/README.txt">https://github.com/gatein/gatein-portal/blob/master/README.txt</a><br><br><div class="gmail_quote">On Mon, Mar 19, 2012 at 1:08 PM, Thomas Heute <span dir="ltr"><<a href="mailto:theute@redhat.com">theute@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
This page will also have to be updated:<br>
<a href="http://www.jboss.org/gatein/contributing" target="_blank">http://www.jboss.org/gatein/contributing</a><br>
<div class="HOEnZb"><div class="h5"><br>
On 03/19/2012 12:40 PM, Thomas Heute wrote:<br>
> Thanks on the migration !<br>
><br>
> Was it tweeted already ? :)<br>
><br>
> On 03/19/2012 11:49 AM, Boleslaw Dawidowicz wrote:<br>
>> I think this translates to: Fell free to fork, clone, commit and issue<br>
>> pull requests! :)<br>
>><br>
>> Here is the basic doc about how we should proceed with Git for trunk:<br>
>><br>
>> <a href="https://community.jboss.org/wiki/GateInPortalGitContributionGuide" target="_blank">https://community.jboss.org/wiki/GateInPortalGitContributionGuide</a><br>
>><br>
>> We are still missing some stuff like mailing list for pull requests<br>
>> (working on it…) and we will probably need to adjust the whole process<br>
>> over time as we learn about limitations. Fell free to comment and add<br>
>> suggestions.<br>
>><br>
>> As a side note - at the moment only 4 persons have permissions to push<br>
>> into gatein-portal repo - me, Julien, Thomas and Trong. This is mainly<br>
>> for the start and ideally over time we add more people as a<br>
>> gatekeepers when we feel safer of not nuking up the repo by accident…<br>
>><br>
>> We will try to follow with migration of other components shortly.<br>
>> Schedule to be defined.<br>
>><br>
>> I would like to thank Julien for leading this part of the migration,<br>
>> investing his time and sharing expertise to drive it.<br>
>><br>
>> Bolek<br>
>><br>
>> On Mar 18, 2012, at 10:46 PM, Julien Viet wrote:<br>
>><br>
>>> I've updated the repository with a new migration which is better<br>
>>> because empty commits are removed (mostly svn:ignore commits) and<br>
>>> more important the .gitignore file is added through the whole history<br>
>>> (which means doing a checkout of an earlier version will have the<br>
>>> .gitignore).<br>
>>><br>
>>> it means that any fork of the previous version are not valid anymore<br>
>>> and should be refreshed as history had to be rewritten (specially for<br>
>>> putting .gitignore everywhere).<br>
>>><br>
>>> Beside that, I've been able to capture the steps for migrating the<br>
>>> repository and will provide them soon, they are fairly easy to use<br>
>>> and actually I've been using them to make a prototype of portlet<br>
>>> container migration here : <a href="https://github.com/vietj/pc-preview" target="_blank">https://github.com/vietj/pc-preview</a> .<br>
>>><br>
>>><br>
>>><br>
>>> On Mar 16, 2012, at 2:18 PM, Nick Scavelli wrote:<br>
>>><br>
>>>> "cloning now"...can't wait until it's official ! Thanks Julien !<br>
>>>><br>
>>>> On 03/16/2012 04:46 AM, Julien Viet wrote:<br>
>>>>> I created the repository as "candidate for release" :<br>
>>>>> <a href="https://github.com/gatein/gatein-portal" target="_blank">https://github.com/gatein/gatein-portal</a><br>
>>>>><br>
>>>>> it will be officially the gatein portal repository monday.<br>
>>>>><br>
>>>>> at the moment you can clone it (via git clone) but you should avoid<br>
>>>>> to "fork" it the "github way" (if we need to recreate it for some<br>
>>>>> reason, your fork will be lost).<br>
>>>>><br>
>>>>> please have a look, clone it, play with it, build it, etc...<br>
>>>>><br>
>>>>> thanks for your feedback.<br>
>>>>><br>
>>>>> On Mar 15, 2012, at 3:12 PM, Boleslaw Dawidowicz wrote:<br>
>>>>><br>
>>>>>> I cut off write access to:<br>
>>>>>><br>
>>>>>> <a href="https://svn.jboss.org/repos/gatein/portal/trunk" target="_blank">https://svn.jboss.org/repos/gatein/portal/trunk</a><br>
>>>>>><br>
>>>>>> Julien will be starting migration process to github. This should<br>
>>>>>> hopefully take us around 2 days to test everything properly. We<br>
>>>>>> aim to be able to continue with access to the new repo on github<br>
>>>>>> around Monday morning.<br>
>>>>>><br>
>>>>>> I will try to provide basic documentation covering source code<br>
>>>>>> contribution to the project by then.<br>
>>>>>><br>
>>>>>> Please tell me if you have any serious reasons to re-enable svn<br>
>>>>>> access to gatein/portal/trunk.<br>
>>>>>><br>
>>>>>> Bolek<br>
>>>>>><br>
>>>>>> On Mar 15, 2012, at 9:51 AM, Julien Viet wrote:<br>
>>>>>><br>
>>>>>>> portal vn team is fine.<br>
>>>>>>><br>
>>>>>>> On Mar 15, 2012, at 9:46 AM, Boleslaw Dawidowicz wrote:<br>
>>>>>>><br>
>>>>>>>> Does anyone have any pending work for portal/trunk? If now i<br>
>>>>>>>> would like to turn it into readOnly mode today. Please let me know.<br>
>>>>>>>><br>
>>>>>>>> Bolek<br>
>>>>>>>><br>
>>>>>>>> On Mar 14, 2012, at 6:48 PM, Ken Finnigan wrote:<br>
>>>>>>>><br>
>>>>>>>>> Would need to add:<br>
>>>>>>>>><br>
>>>>>>>>> .settings<br>
>>>>>>>>> .project<br>
>>>>>>>>> .classpath<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> On Wed, Mar 14, 2012 at 1:37 PM, Julien Viet<br>
>>>>>>>>> <<a href="mailto:julien@julienviet.com">julien@julienviet.com</a><mailto:<a href="mailto:julien@julienviet.com">julien@julienviet.com</a>>> wrote:<br>
>>>>>>>>><br>
>>>>>>>>> For eclipse users : anything you want to add in .gitignore<br>
>>>>>>>>> for Eclipse ?<br>
>>>>>>>>><br>
>>>>>>>>> On Mar 13, 2012, at 11:30 PM, Julien Viet wrote:<br>
>>>>>>>>><br>
>>>>>>>>> > Hi,<br>
>>>>>>>>> ><br>
>>>>>>>>> > we are going to migrate the GateIn Portal repository to<br>
>>>>>>>>> GIT soon (hopefully by next week) and here is the process<br>
>>>>>>>>> we should follow:<br>
>>>>>>>>> ><br>
>>>>>>>>> > 1/ provide an initial repository (by me) as preview to<br>
>>>>>>>>> play with it and check things are OK (identities, tags).<br>
>>>>>>>>> > 2/ stop SVN commits by the end of this week (which means<br>
>>>>>>>>> that people having pending commits will have to flush them<br>
>>>>>>>>> before the end of this week).<br>
>>>>>>>>> > 3/ the new repository should be available in GitHub early<br>
>>>>>>>>> next week, ready to be used in the GateIn organization in a<br>
>>>>>>>>> repository named "gatein-portal".<br>
>>>>>>>>> ><br>
>>>>>>>>> > We want to use GIT in order to keep a trunk as stable as<br>
>>>>>>>>> possible and the main motivation is to never have<br>
>>>>>>>>> "unfinished" work in the master of the repository:<br>
>>>>>>>>> > - a long feature does not have to be entirely finished of<br>
>>>>>>>>> course to go in master but it should reach a certain<br>
>>>>>>>>> milestone in its implementation.<br>
>>>>>>>>> > - a small feature should be finished and then merged in<br>
>>>>>>>>> the master.<br>
>>>>>>>>> > - bug fixes can go directly in the master as they are<br>
>>>>>>>>> independant.<br>
>>>>>>>>> ><br>
>>>>>>>>> > Git provides a huge benefit over SVN : it allows to<br>
>>>>>>>>> schedule when commits are merged in the master without<br>
>>>>>>>>> blocking other people to work. We will use this<br>
>>>>>>>>> > feature to "implement" the behavior explained before.<br>
>>>>>>>>> ><br>
>>>>>>>>> > After the 3.2 release, we want to increase our release<br>
>>>>>>>>> rate with GateIn 3.3, 3.4, etc.. We think we should be able<br>
>>>>>>>>> to make up to 4 releases a year (as opposed to<br>
>>>>>>>>> > a single release in almost 2 years which means an x8<br>
>>>>>>>>> factor). We also think that using correctly Git will help<br>
>>>>>>>>> us to do that (also with a proper management of<br>
>>>>>>>>> > the roadmap and dependencies between features of course).<br>
>>>>>>>>> The idea is to focus on a few selected features in the<br>
>>>>>>>>> master at a time for the next release and<br>
>>>>>>>>> > keep the other in other branches (TBD).<br>
>>>>>>>>> ><br>
>>>>>>>>> > We will clarify how people can work with this repository<br>
>>>>>>>>> soon, but in short at the beginning only a few persons will<br>
>>>>>>>>> interact directly with the repository. We will<br>
>>>>>>>>> > use the "pull request" mechanism of Git to notify when a<br>
>>>>>>>>> merge should be done (to be clarified by Bolek soon). Also<br>
>>>>>>>>> here the idea is that we will schedule<br>
>>>>>>>>> > pull request at the appropriate time.<br>
>>>>>>>>> ><br>
>>>>>>>>> > So this is valid at the moment for the portal project,<br>
>>>>>>>>> other project will be migrated later (during March/April),<br>
>>>>>>>>> at the moment we focus on the portal because it's<br>
>>>>>>>>> > the place where the main activity is done at the moment.<br>
>>>>>>>>> Other project will have likely similar rules but it will be<br>
>>>>>>>>> less strict since it's usually used by less people<br>
>>>>>>>>> > than the portal.<br>
>>>>>>>>> ><br>
>>>>>>>>> > So tonight I'm providing a repository preview<br>
>>>>>>>>> <a href="https://github.com/vietj/gatein-portal-preview" target="_blank">https://github.com/vietj/gatein-portal-preview</a> for the<br>
>>>>>>>>> portal that contains the SVN history and the released tags<br>
>>>>>>>>> ><br>
>>>>>>>>> > - it does not contain branch information (since we don't<br>
>>>>>>>>> use them for the community versions).<br>
>>>>>>>>> > - you should check the repository (like using a tag and<br>
>>>>>>>>> building it).<br>
>>>>>>>>> > - you must check your identity was correctly migrated<br>
>>>>>>>>> (based on the information you provided) : if it is not tell<br>
>>>>>>>>> me what is your Git identity.<br>
>>>>>>>>> > - the .gitignore file was not added yet, I will add it<br>
>>>>>>>>> later (likely like this one<br>
>>>>>>>>> <a href="https://github.com/juzu/juzu/blob/master/.gitignore" target="_blank">https://github.com/juzu/juzu/blob/master/.gitignore</a>) : if<br>
>>>>>>>>> you have specific desire tell me<br>
>>>>>>>>> > - the maven release plugin is not yet updated to use Git<br>
>>>>>>>>> and it will be done later (and actually it should be<br>
>>>>>>>>> updated to release things more correctly).<br>
>>>>>>>>> ><br>
>>>>>>>>> > if you feel something is missing or have question, don't<br>
>>>>>>>>> hesitate to raise the concern.<br>
>>>>>>>>> ><br>
>>>>>>>>> > cheers<br>
>>>>>>>>> ><br>
>>>>>>>>> > Julien<br>
>>>>>>>>> ><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> _______________________________________________<br>
>>>>>>>>> gatein-dev mailing list<br>
>>>>>>>>> <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><mailto:<a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a>><br>
>>>>>>>>> <a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> _______________________________________________<br>
>>>>>>>>> gatein-dev mailing list<br>
>>>>>>>>> <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><mailto:<a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a>><br>
>>>>>>>>> <a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
>>>>><br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> gatein-dev mailing list<br>
>>>>> <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
>>>>> <a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> gatein-dev mailing list<br>
>> <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
> _______________________________________________<br>
> gatein-dev mailing list<br>
> <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
<br>
_______________________________________________<br>
gatein-dev mailing list<br>
<a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><b><span style="font-weight:normal;background-color:rgb(255,255,255)"><span style="font-family:'lucida grande',arial,helvetica,sans-serif;color:rgb(128,128,128);font-size:small">Patrice Lamarque</span><br>
<span style="font-family:'lucida grande',arial,helvetica,sans-serif;color:rgb(128,128,128);font-size:x-small">eXo - VP Products </span><br><font color="#ff6600" face="'lucida grande', arial, helvetica, sans-serif" size="1"><br>
</font></span></b><br>