[seam-dev] Modules have been moved

[Pete Muir]

On 14 Dec 2009, at 22:57, Mark Struberg wrote:

> git per se has no security at all. Git uses the security of the underlying transfer/storage layers.
> 
> Btw: you should rethink your modules/modularity because git treats a repo always as a whole.

I don't think this is entirely necessary ;-) All that happens is that a sandbox is a clone of the tree which different people control.

> Means no spatial checkouts, a tag is always over the whole repo, etc.
> 
> There is a mechanism called git submodule [1] but that is a bit clumsy still. 
> 
> Git is _really_ fine, but certainly needs a bit of a different mindset than SVN!
> 
> LieGrue,
> strub
> 
> [1] http://www.kernel.org/pub/software/scm/git-core/docs/git-submodule.html
> 
> --- Shane Bryzak <sbryzak at redhat.com> schrieb am Mo, 14.12.2009:
> 
>> Von: Shane Bryzak <sbryzak at redhat.com>
>> Betreff: Re: [seam-dev] Modules have been moved
>> An: "Pete Muir" <pmuir at redhat.com>
>> CC: seam-dev at lists.jboss.org
>> Datum: Montag, 14. Dezember 2009, 23:24
>> On 15/12/09 04:59, Pete Muir wrote:
>>> I was waiting to see if there was a chance jboss.org
>> would provide Git soon. There isn't.
>>> 
>>> We can therefore do the migration to github.
>>> 
>>> Only outstanding issue is connecting commits into JIRA
>> - is this something people use a lot?
>>>     
>> 
>> It seems that github has commit postbacks which we can
>> possibly use to 
>> connect issues together.  The other thing I'm not
>> clear about is 
>> repository security - it was our intention to give module
>> committers 
>> access to their own module (and nothing else).  I
>> can't see anything on 
>> github that gives us the fine grained security control that
>> SVN 
>> currently does.  Of course maybe I just don't know
>> enough about git yet 
>> and security works in a totally different way...
>>> On 11 Dec 2009, at 17:04, Dan Allen wrote:
>>> 
>>>     
>>>> On Fri, Dec 11, 2009 at 11:53 AM, Shane
>> Bryzak<sbryzak at redhat.com> 
>> wrote:
>>>> The plan is to probably move to github, although
>> we are going to do some (prudent) evaluation first.
>>>> 
>>>> We'll of course wait for Pete to return on Monday
>> because we can't decide anything without him, and likely he
>> makes the final call anyway. But I still vote that we just
>> go for it. We have gotten tons of feedback about github and
>> while there have been great arguments for Mercurial, I think
>> we can all agree that both are better than SVN and github is
>> well run. If worse comes to worse, we can make another move,
>> but all signs just point to doing it.
>>>> 
>>>> So let's hang until Monday, see what Pete says,
>> but if need be, we can do a vote on the list and just bite
>> the bullet.
>>>> 
>>>> -Dan
>>>> 
>>>> -- 
>>>> Dan Allen
>>>> Senior Software Engineer, Red Hat | Author of Seam
>> in Action
>>>> Registered Linux User #231597
>>>> 
>>>> http://mojavelinux.com
>>>> http://mojavelinux.com/seaminaction
>>>> http://www.google.com/profiles/dan.j.allen
>>>> _______________________________________________
>>>> seam-dev mailing list
>>>> seam-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>>       
>>>     
>> 
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>> 
> 
> __________________________________________________
> Do You Yahoo!?
> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. 
> http://mail.yahoo.com