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