Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] [epp-dev] Mylyn in C/C++ EPP?

Hi,

Thanks for the info! Out of curiosity, do you use the context (task-focused interface) or do you use just the Tasks list (or other things)?

Thank you,
Marc-Andre
________________________________________
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Austin Morgan [admorgan@xxxxxxxxxxxxxxxxxxx]
Sent: Monday, 19 October 2015 2:50 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] [epp-dev]  Mylyn in C/C++ EPP?

I do use Mylyn a lot with CDT. Actually I have convinced many of the
teams I work with about the benefits it offers. I do knot know if it
"needs" to be included in the default EPP, but it helps with a lot of
workflows.

Austin Morgan

On Mon, Oct 19, 2015 at 06:26:57PM +0000, Doug Schaefer wrote:
> Well, that wasn’t the original intent of the packages. The idea was to provide a collection of features that a specific segment of the community would be interested in. What we’re saying is that the C++ segment of our community may not be interested in Mylyn.
>
> And as I’ve argued for other proposals, I don’t think throwing features into the packages is a good way to help those features become discoverable. It would be interesting to survey package users whether they even noticed Mylyn’s features were available to them or even whether they know what the Task List view was for, even if they noticed it was there. You need to have proper marketing of the features if you want users to know about them.
>
> Packages exist because we didn’t have a good installer. I think we have a little ways to go but I can see a time where we’ll even wonder whether we want the packages any more because everyone is using the installer instead. In that case your argument about a common baseline would be valid because the installer could have a baseline. And we can argue then whether Mylyn should be in it.
>
> Doug.
>
> From: <epp-dev-bounces@xxxxxxxxxxx<mailto:epp-dev-bounces@xxxxxxxxxxx>> on behalf of Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx<mailto:konstantin.komissarchik@xxxxxxxxxx>>
> Reply-To: Eclipse Packaging Project <epp-dev@xxxxxxxxxxx<mailto:epp-dev@xxxxxxxxxxx>>
> Date: Monday, October 19, 2015 at 1:59 PM
> To: Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx<mailto:marc-andre.laperle@xxxxxxxxxxxx>>, Eclipse Packaging Project <epp-dev@xxxxxxxxxxx<mailto:epp-dev@xxxxxxxxxxx>>, "CDT General developers list." <cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>>
> Subject: Re: [epp-dev] [cdt-dev] Mylyn in C/C++ EPP?
>
>
> Don’t forget the builds/hudson/jenkings integration. In my opinion, these type of decisions should not be made at a per-package level. I would urge package owners to not deviate unnecessarily from a common baseline.
>
>
>
> - Konstantin
>
>
>
>
>
> From: Marc-André Laperle
> Sent: Monday, October 19, 2015 10:48 AM
> To: Eclipse Packaging Project;CDT General developers list.
> Subject: Re: [epp-dev] [cdt-dev] Mylyn in C/C++ EPP?
>
>
> We could just keep the "Mylyn Task List" feature. I'm not sure Bugzilla is really needed as there are so many other popular bug trackers and there is an "Install Connectors" UI to find them.
>
> Marc-Andre
>
> From: epp-dev-bounces@xxxxxxxxxxx<mailto:epp-dev-bounces@xxxxxxxxxxx> [epp-dev-bounces@xxxxxxxxxxx<mailto:epp-dev-bounces@xxxxxxxxxxx>] on behalf of Konstantin Komissarchik [konstantin.komissarchik@xxxxxxxxxx<mailto:konstantin.komissarchik@xxxxxxxxxx>]
> Sent: Monday, 19 October 2015 1:37 PM
> To: Doug Schaefer; CDT General developers list.; epp-dev@xxxxxxxxxxx<mailto:epp-dev@xxxxxxxxxxx>
> Subject: Re: [epp-dev] [cdt-dev] Mylyn in C/C++ EPP?
>
> I would urge caution. Mylyn isn’t just context-constraining UI, it’s also integration with the bug tracking systems, which is a feature commonly expected of an IDE. Discoverability of features is a serious problem that Eclipse ecosystem continues to struggle. While insiders would know to install Mylyn if they want this, a developer new to Eclipse would simply conclude that Eclipse lacks integration with bug tracking systems. This isn’t a hypothetical scenario. We’ve seen it unfold with other features and it hurts our competitive position.
>
>
>
> - Konstantin
>
>
>
>
>
> From: Doug Schaefer
> Sent: Monday, October 19, 2015 10:25 AM
> To: CDT General developers list.;epp-dev@xxxxxxxxxxx<mailto:epp-dev@xxxxxxxxxxx>
> Subject: Re: [epp-dev] [cdt-dev] Mylyn in C/C++ EPP?
>
>
> Yeah, it’s a bit sad in a way. The Mylyn gang kindly built the CDT extension for it which encouraged us to add it in to the C++ package. But I have to admit I never use it. I hope others do.
>
> At any rate, it might fit into that category of things that should be in the Marketplace and people can add it on later if they want it.
>
> Doug.
>
> From: <cdt-dev-bounces@xxxxxxxxxxx<mailto:cdt-dev-bounces@xxxxxxxxxxx>> on behalf of Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx<mailto:marc-andre.laperle@xxxxxxxxxxxx>>
> Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>>
> Date: Monday, October 19, 2015 at 1:20 PM
> To: "epp-dev@xxxxxxxxxxx<mailto:epp-dev@xxxxxxxxxxx>" <epp-dev@xxxxxxxxxxx<mailto:epp-dev@xxxxxxxxxxx>>
> Cc: "cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>" <cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>>
> Subject: [cdt-dev] Mylyn in C/C++ EPP?
>
> Hello,
>
> I'm wondering if people use Mylyn in the context of the C/C++ EPP. I'm thinking perhaps it could be removed from the EPP if it's not really used. It would clear up some things in the UI and make the package a bit lighter (start-up time and size).
>
> Let me know what you think!
>
> Marc-Andre
>
>
>
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.


> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top