Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [modeling-pmc] Re: [Bug 165777] Modeling Project "sub-component"newsgroups not standard [was: Modeling Project "component" newsgroups not standard]

Title: Re: [modeling-pmc] Re: [Bug 165777] Modeling Project "sub-component"newsgroups not standard [was: Modeling Project "component" newsgroups not standard]
OK, thanks Kenn.

I guess we can summarize this discussion as:

  • Modeling projects were intentionally organized into components in order to achieve a unified/coordinated delivery of similar capabilities within a single project.  Projects are discouraged from creating subcomponents.
  • The Modeling PMC has agreed that component-level newsgroups should be created when sufficient interest/traffic exists for the component within the project newsgroup.
  • The Project/Component Lead is responsible for identifying the need for a component-level newsgroup and requesting from the Foundation, keeping in mind the Foundation’s preference for fewer newsgroups overall.
  • The following newsgroups are hereby requested:
    • eclipse.modeling.mdt
    • eclipse.modeling.mdt.ocl
    • eclipse.modeling.mdt.uml2
    • eclipse.modeling.mdt.uml2tools
    • eclipse.modeling.mdt.xsd (really, with 0 posts in the past month and given Ed’s comment?)
    • eclipse.modeling.mdt.eodm (similarly? - seems to be averaging ~4 posts per week)
    • eclipse.modeling.gmt
    • eclipse.modeling.gmt.amw
    • eclipse.modeling.gmt.modisco
  • The following closures/migrations are requested:
    • eclipse.modeling.mdt.uml2.uml -> eclipse.modeling.mdt.uml2
    • eclipse.modeling.mdt.uml2.tools -> eclipse.modeling.mdt.uml2tools
    • eclipse.modeling.mdt.uml2.ocl -> eclipse.modeling.mdt.ocl

Thanks,
Rich

On 12/6/06 12:09 PM, "Kenneth Hussey" <khussey@xxxxxxxxxx> wrote:


Rich,

I don't necessarily advocate creation of the groups at time of component creation/provisioning... I advocate their creation when the project lead "knows when it is time" which COULD be at creation/provisioning time but could also be based on traffic levels at a later time; in any case, it should be left to the discretion of the project lead, IMO. In the case of the MDT components, we already have separate groups, so I see it as less of an impact on the community if we keep it that way...

Cheers,

Kenn Hussey

Senior Software Developer
Rational Software, IBM Software Group

770 Palladium Drive
Kanata, Ontario, K2V 1C8

T: (613) 599-3980  F: (613) 599-3912



Richard Gronback <richard.gronback@xxxxxxxxxxx> 12/06/2006 11:44 AM

To

Kenneth Hussey/Ottawa/IBM@IBMCA

cc

Ed Merks/Toronto/IBM@IBMCA, Jean Bezivin <Jean.Bezivin@xxxxxxxxxxxxxx>, Sébastien Demathieu <sebastien.demathieu@xxxxxxxxxxxxxxx>

Subject

Re: [Bug 165777] Modeling Project "sub-component" newsgroups not standard [was: Modeling Project "component" newsgroups not standard]




I expect we should first come to an agreement (as a PMC) on what the approach should be (therefore, adding Sebastien).  It seems Jean and I are OK with the approach of growing component-level newsgroups organically, while you advocate the creation of these newsgroups upon component creation/provisioning.

Ed, Sebastien... Thoughts?

Thanks,
Rich


On 12/6/06 11:12 AM, "Kenneth Hussey" <khussey@xxxxxxxxxx> wrote:


Rich,

Bjorn seems to want agreement from the "PMC" (which I assume must mean leadership since Jean and I are on the PMC but don't seem to count). I propose that Jean and I decide what makes sense for our projects and the PMC leadership backs us on that decision. I have already stated my needs in my latest comment in Bugzilla, so if you and Ed could add comments saying you're in ageement, we can start making the required changes.

Thanks,

Kenn Hussey

Senior Software Developer
Rational Software, IBM Software Group

770 Palladium Drive
Kanata, Ontario, K2V 1C8

T: (613) 599-3980  F: (613) 599-3912



Richard Gronback <richard.gronback@xxxxxxxxxxx>
12/06/2006 10:37 AM
To
Jean Bezivin <Jean.Bezivin@xxxxxxxxxxxxxx>
cc
Kenneth Hussey/Ottawa/IBM@IBMCA, Ed Merks/Toronto/IBM@IBMCA
Subject
Re: [Bug 165777] Modeling Project "sub-component" newsgroups not standard [was: Modeling Project "component" newsgroups not standard]




It seems the EMO is interested in the opposite approach; that is, have a
general newsgroup per project, and when it is evident a certain topic
(component) has enough interest, give it its own newsgroup.  This seems
sensible to me, although does raise the problem of requiring explicit
[topic] markers in subject lines in the main newsgroup.  The good news is
that the history will always be available if/when a new component-level
newsgroup is created (the old one won't be closed, as it's representing the
project itself).

I'd say the Project Lead is most likely to know when it's time, and
recommend to the Foundation.  I'm not sure it requires PMC intervention,
although we can certainly work with the EMO when required (like now).

Other thoughts?

Best,
Rich


On 12/6/06 10:26 AM, "Jean Bezivin" <Jean.Bezivin@xxxxxxxxxxxxxx> wrote:

> Rich:
>
> How do you see a justification by traffic for some component.
> Does that mean that if there is not enough traffic the associated
> newsgroup should be closed?
>
> For me the PMC should take the responsibility
> to assign a newsgroup to a given "component"
> when it see fit.
>
> Jean
>
>
>
> On 12/6/06, Jean Bezivin <Jean.Bezivin@xxxxxxxxxxxxxx> wrote:
>> May be we can discuss first on this thread
>> and relat our conclusions to the next PMC call.
>>
>> Jean
>>
>> On 12/6/06, Richard Gronback <richard.gronback@xxxxxxxxxxx> wrote:
>>> Hi,
>>>
>>> Should we cover this on the next PMC call (scheduled for the 19th), or have
>>> a quick call to discuss sooner?  As I see it, and as I discussed with Bjorn,
>>> we're OK to have the 4 segment newsgroups to represent components, but
>>> Bjorn/Denis/EMO would like to see them first justified by traffic.
>>>
>>> Or, we can just discuss it on this thread, I guess.
>>>
>>> Thanks,
>>> Rich
>>>
>>>
>>> On 12/6/06 9:57 AM, "Kenneth Hussey" <khussey@xxxxxxxxxx> wrote:
>>>
>>>
>>> Rich,
>>>
>>> Yes, makes sense. The fact that these components have distinct release
>>> versions further supports their existence as separate components (with
>>> separate newsgroups) - see my latest comment in the bug.
>>>
>>> Cheers,
>>>
>>> Kenn Hussey
>>>
>>> Senior Software Developer
>>> Rational Software, IBM Software Group
>>>
>>> 770 Palladium Drive
>>> Kanata, Ontario, K2V 1C8
>>>
>>> T: (613) 599-3980  F: (613) 599-3912
>>>
>>>
>>>
>>> Richard Gronback <richard.gronback@xxxxxxxxxxx> 12/05/2006 05:36 PM
>>>
>>> To
>>>
>>> Kenneth Hussey/Ottawa/IBM@IBMCA, Ed Merks/Toronto/IBM@IBMCA
>>>
>>> cc
>>> Subject
>>>
>>> FW: [Bug 165777] Modeling Project "sub-component" newsgroups not standard
>>> [was: Modeling Project "component" newsgroups not standard]
>>>
>>>
>>>
>>>
>>> Just to be clear, the reference to "single release for all the MDT
>>> components" means coordinated (as in, with Europa) to me.
>>>
>>> Best,
>>> Rich
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Richard C. Gronback
>>> Borland Software Corporation
>>> richard.gronback@xxxxxxxxxxx
>>> +1 860 227 9215
>>>
>>
>>
>> --
>> See you in June 2007 in Zurich for the TOOLS conference:
>> http://tools.ethz.ch/
<http://tools.ethz.ch/> __________________________________
>> Jean Bézivin - ATLAS Group (INRIA & LINA) - University of Nantes - 2,
>> rue de la Houssinière
>> 44322 Nantes cedex 3 - France
>> tel. +33 2 51 12 58 13 - fax. +33 2 51 12 58 12 - cell.+33 6 14 32 22 36
>> - e.mail: Jean.Bezivin@xxxxxxxxxxxxxx
>> http://www.sciences.univ-nantes.fr/lina/atl/
<http://www.sciences.univ-nantes.fr/lina/atl/> - Skype: jbezivin
>> ---------------------------------------
>>
>




--
Richard C. Gronback
Borland Software Corporation
richard.gronback@xxxxxxxxxxx
+1 860 227 9215

Back to the top