[seam-dev] Git Migration of Seam2

[John D. Ament]

+1 to github.com/seam2
Having it as a separate organization will keep things like permissions
better.  Even if you just have one repo.


On Wed, Nov 28, 2012 at 6:30 PM, Stuart Douglas
<stuart.w.douglas at gmail.com>wrote:

>
>
> Shane Bryzak wrote:
> > I don't see a problem with having it located at github.com/seam, this is
> > the most obvious/intuitive place to locate the code.  How about we use
> > https://github.com/seam/legacy ?
>
> I think github/seam/seam2 makes more sense, or even just a whole new seam2
> organization.
>
> I don't think legacy give any info as to what the repo actually contains.
>
> Stuart
>
> >
> > On 11/29/2012 08:39 AM, Marek Novotny wrote:
> >> Hi Seam devs,
> >>
> >>     I am looking for target of migrated Seam 2 repository from SVN to
> GIT
> >> on github.com. Just to inform you, we already have prepared migrated
> >> sources, but need to do final steps.
> >>
> >> I don't think that current https://github.com/seam is good for that as
> >> it is more likely about Seam 3.
> >>
> >> I don't have any experience with creating a new organization on
> >> github.com. Even I feel it would be the best way, your
> >> voice/opinions/help to find a proper github.com target is important.
> >>
> >>     So please give me some attention with that question ;-).
> >>
> >> Cheers,
> >>
> >
> > _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20121128/3157ea97/attachment.html