[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[modeling-pmc] Re: Infrastructure Changes
|
Hi Nick,
I agree with the one releng module and the eventual migration to a single
builder for all. The hope is for you and Max (not sure who does releng on
GMT/MDDi) to start collaborating on this, and within the context of the
"buildmaster summit" for Modeling.
And, I agree about maintaining the web content where it is.
I'm rgronback on Skype and Yahoo, gronback@xxxxxxx on MSN, 235880828 on ICQ.
Thanks!
- Rich
On 7/19/06 10:39 PM, "Nick Boldt" <codeslave@xxxxxxxxxx> wrote:
>
> Has anyone thought about how to structure the releng stuff?
>
> Should it be one releng module per project - lots of duplicated code, but
> committers control their own stuff, as they do with their plugins and
> features?
> Or one releng module for the whole Modeling project - fewer hands on the
> code, better centralized content?
>
> Me, I'd prefer one releng module, eg.,
> /cvsroot/modeling/org.eclipse.modeling.releng, under which we'd put
> everyone's releng code in one place, including a common/ folder for shared
> scripts and resources and a template/ folder (for use when creating new
> subprojects - this could eventually evolve into a JET template or perhaps a
> wizard). To make it editable by project committers, we'd just have to
> either have everyone share in a modeling-releng group, or create groups
> like modeling-releng-uml2, modeling-releng-gmf, ... modeling-releng-common,
> etc. to keep things safe.
>
> Re: web content, eg:
>
> /cvsroot/modeling
> /emf, /gmf, /uml2, /emft, etc.
>
> I don't think we should move the website folders into /cvsroot/modeling -
> they should stay in /cvsroot/org.eclipse/www. Two reasons for this:
>
> 1) consistency with other projects, including webtools and tptp, who
> despite their many subprojects still live in /cvsroot/org.eclipse/www; and
> 2) separation of web content from source content - one cvs repository for
> each type of content
>
> Now that you can viewcvs on the web cvsroot too
> (http://dev.eclipse.org/viewcvs/index.cgi/www/?cvsroot=Eclipse_Website),
> there's no benefit (aside from keeping it all in one cvs root) to having
> the web content in /cvsroot/modeling vs. in /cvsroot/org.eclipse/www. Plus,
> I'm not sure Denis would agree to having web content in another cvs
> repository. See reason #1. ;-)
>
> I'm available anytime to chat about these issues. Once we're all in
> agreement, I'd like to see most of the source content for the various
> projects copied over as soon as possible into the new cvsroot, so that we
> can start migrating the releng stuff into one cohesive builder in a sandbox
> environment outside the ongoing development. Once it's ready, we would of
> course copy the source over again, run some builds, and flush the old
> source out of technology and tools (like we did when XSD moved from tech to
> tools).
>
> For the non-IBMers involved here, what IM tools do you folks use? I'm
> partial to Skype (username: nickboldt) since it does both text and VoIP
> chat but if there's another IM client you recommend - AIM, ICQ, Jabber,
> MSN, Yahoo... - let me know and I'll sign up.
>
> Cheers,
>
> --
> Nick Boldt :: Software Developer, IBM Toronto Lab
> Eclipse Modeling Framework :: http://eclipse.org/emf
> 905/413/4308 (t/l 969) :: codeslave@xxxxxxxxxx :: Skype
>
>
>
>
>
> Wednesday, July 19, 2006 10:14 PM
> To: PMC members mailing list <modeling-pmc@xxxxxxxxxxx>
> cc: Max Feldman <Max.Feldman@xxxxxxxxxxx>, Nick Boldt/Toronto/IBM@IBMCA
> From: Richard Gronback <richard.gronback@xxxxxxxxxxx>
> Subject: Infrastructure Changes
>
>
> Hi All,
>
> As discussed on our last call, a number of infrastructure items need to be
> discussed/agreed to before submitting the requests to the webmaster.
>
> I've included those that are not yet proposed/approved/provisioned just for
> a more complete picture, while they will not be part of the initial
> request.
> When they are provisioned, I imagine they will look similar to what is
> below:
>
> Newsgroups:
>
> eclipse.tools.emf -> eclipse.modeling.emf
> eclipse.tools.uml2 -> eclipse.modeling.mdt.uml2 (need new e.m.mdt)
> eclipse.technology.gmf -> eclipse.modeling.gmf
> eclipse.technology.emft -> eclipse.modeling.emf (with additional
> *.emf.ocl, *.emf.validation, *.emf.query, *.emf.transaction, etc.?)
> eclipse.technology.gmt -> eclipse.modeling.gmt
> eclipse.technology.gmt.amw -> eclipse.modeling.gmt.amw
> eclipse.technology.mddi -> eclipse.modeling.mddi
>
> Bugzilla:
>
> Need new 'Modeling' classification with following 'Product' migrations:
> Tools/EMF -> Modeling/EMF
> Tools/UML2 -> Modeling/MDT (UML2 is first component)
> Technology/GMF -> Modeling/GMF
> Technology/GMT -> Modeling/GMT
> Technology/MDDi -> Modeling/MDDi
>
> CVS:
>
> /cvsroot
> /modeling
> /emf
> /org.eclipse.emf
> /..
> /mdt (not yet provisioned)
> /org.eclipse.uml2
> /org.eclipse.emf.ocl (future org.eclipse.ocl?)
> /..
> /gmf
> /org.eclipse.gmf
> /gmt
> /org.eclipse.gmt
> /..
> /mddi
> /org.eclipse.mddi
> /m2m (not yet provisioned)
> /org.eclipse.qvt
> /..
> /m2t (not yet provisioned)
> /org.eclipse.jet
> /org.eclipse.xpand ?
> /..
>
> Download site:
>
> /technology/gmf -> /modeling/gmf
> /tools/emf -> /modeling/emf
> /tools/uml2 -> /modeling/mdt/uml2
> /technology/gmt -> /modeling/gmt
> /technology/mddi -> /modeling/mddi
> /technology/emft -> /modeling/emf/..
>
> Mailing lists:
> No changes required.
>
> Thanks,
> Rich
> --
> Richard C. Gronback
> Borland Software Corporation
> richard.gronback@xxxxxxxxxxx
> +1 860 227 9215
>
>
--
Richard C. Gronback
Borland Software Corporation
richard.gronback@xxxxxxxxxxx
+1 860 227 9215
