Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-dev] Bugzilla components

During the call two weeks ago we agreed on the proposed Bugzilla
component names. Wayne brought up a point on bug 328418 though that
short names can cause confusion if they match names of other (Eclipse)
projects such as B3, EGit etc.

The simplest way to avoid that would be to use longer and more
descriptive names such as "B3 Connector", "EGit Connector", "Java
Bridge" etc.

Personally, I like short names but avoiding confusion seems more
important and we usually refer to the components by their full name
anyways.

Any other thoughts on this?

Steffen


On Fri, Oct 8, 2010 at 4:22 PM, Steffen Pingel
<steffen.pingel@xxxxxxxxxxx> wrote:
> I have posted to this bug where we tracked a related discussion:
> 215853: standardize on bug tags and improve components
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=215853
> My sense is that on an Eclipse project management level having each
> sub-project manage its own product provides more independence between
> projects but on the down side adds additional hierarchy and management
> overhead.
> I guess the alternative would be to stick with a single "Mylyn" product with
> a Bugzilla component for each sub-project and then use tags such as
> [framework] or [hudson] to differentiate the sub-project components.
> I think JGit and EGit are a different case since unlike the Mylyn projects
> the framework project (JGit) is separate from the tools project (EGit).
> Steffen
>
> On Fri, Oct 8, 2010 at 2:16 PM, Mik Kersten <mik@xxxxxxxxxxx> wrote:
>>
>> The proposal looks good to me in general.  I have some specific comments
>> on the components, but those can wait until we’re finalizing the details on
>> a Bugzilla bug.
>>
>>
>>
>> High level, I’m wondering whether the key framework projects should be
>> their own products, rather than being components of things like “Mylyn
>> Versions”.  Specifically, at the outset, it seems that at least EGit and
>> JGit should remain independent products in Bugzilla, as per our
>> differentiation in branding between Framework Projects (eg, Mylyn Versions)
>> and Tools Projects (eg, JGit) which, unlike the framework projects, don’t
>> need to be prefixed by “Mylyn” for their branding.
>>
>>
>>
>> Mik
>>
>>
>>
>> --
>>
>> Dr. Mik Kersten
>>
>> Tasktop CEO, Mylyn Lead, http://twitter.com/mik_kersten
>>
>> Assistant: zoe.jong@xxxxxxxxxxx, +1-778-588-6896, Skype: zoe.e.jong
>>
>>
>>
>> From: mylyn-dev-bounces@xxxxxxxxxxx [mailto:mylyn-dev-bounces@xxxxxxxxxxx]
>> On Behalf Of Steffen Pingel
>> Sent: October-07-10 3:19 PM
>> To: Mylyn developer discussions
>> Cc: Wayne Beaton
>> Subject: [mylyn-dev] Bugzilla components
>>
>>
>>
>> To follow up on the discussion on the call today, here is my proposal for
>> restructuring the Bugzilla components and product to reflect the new Mylyn
>> top-level project structure as outlined in
>> http://wiki.eclipse.org/Mylyn/Restructuring .
>>
>> I propose that each sub-project gets its own product in Bugzilla. This
>> allows each project to define its own components and versions and evolve and
>> plan separately from other sub-projects. It should also work well in terms
>> of using the automatic IP log to track contributions.
>>
>> The Mylyn product would provide an inbox for users who are unsure where to
>> file a specific bug and a place to track administrative tasks.
>>
>>
>>
>> I suggest that we create the following products and components :
>>
>> Mylyn
>> * Inbox, Releng, Website
>>
>> Mylyn Builds
>>
>> * B3, Framework, Hudson
>>
>> Mylyn Commons
>> * Identity, Monitor, Repositories, Notifications, UI
>>
>> Mylyn Context
>> * Java, C/C++, Framework, PDE, Resources
>>
>> Mylyn Docs
>> * WikiText, HtmlText
>>
>> Mylyn Incubator
>> * Usage Monitor, UI Experiments, Web Templates, WikiText Sandbox
>>
>> Mylyn Reviews
>> * Framework, Gerrit, R4E, SCM, Tasks
>>
>> Mylyn Tasks
>> * Bugzilla, Framework, OSLC, Trac
>>
>> Mylyn Versions
>> * CVS, Framework, EGit, OSLC
>>
>> --
>> Steffen Pingel
>> Committer, http://eclipse.org/mylyn
>> Senior Developer, http://tasktop.com
>>
>> _______________________________________________
>> mylyn-dev mailing list
>> mylyn-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/mylyn-dev
>>
>
>
>
> --
> Steffen Pingel
> Committer, http://eclipse.org/mylyn
> Senior Developer, http://tasktop.com
>



-- 
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com


Back to the top