| Re: [eclipse.org-architecture-council] FEEP Proposals |
|
Prefixing tagging feels like the right approach to me. Perhaps I'm
being pedantic, but I don't see the value in having an umbrella bug
that will never be marked fixed. The query to find all open FEEP bugs is this: http://eclip.se/5H I've added a link from the Architecture Council landing page [1] in the wiki. I'd like to reiterate that the intent is to present the EMO with a list of priorities to feed into the decision making process. It would be great if we can factor these priorities into discrete tasks that are well-defined to make the bidding process easier. The process for bidding and awarding contracts is out of scope. While I have your attention... I need some mentors [2]. There are some very interesting projects in our pipeline that need your input. Wayne [1] https://wiki.eclipse.org/Architecture_Council [2] http://eclip.se/3Y On 12/10/15 03:41 AM, Marcel Bruch
wrote:
All seem to agree that every proposal will be tracked in a separate bug. Whatever the discussion of tags, prefixes, umbrella bugs etc. will be, I just created two bugs to get the discussion started how to leverage FEEP: Bug 479541: [FEEP] New Project Website for Java Tooling Bug 479536: [FEEP] Improve Tooling Support for NullPointerAnalysis Thank you. Marcel P.S.: I’ll adjust my proposal bugs to fit into whatever search-and-filter technique you finally agree on. https://bugs.eclipse.org/bugs/show_bug.cgi?id=479536 https://bugs.eclipse.org/bugs/show_bug.cgi?id=479541Am 10.10.2015 um 08:29 schrieb Daniel Megert <daniel_megert@xxxxxxxxxx>: Sorry my bad.. My use case was to share *my* tags with others. This allowed me to share a list which could not be modified by others and did not pollute the bug with my plans. This seems to restrictive for our FEEP case, so let's go with the umbrella bug. Dani From: Denis Roy <denis.roy@xxxxxxxxxxx> To: eclipse.org-architecture-council@xxxxxxxxxxx Date: 09.10.2015 20:36 Subject: Re: [eclipse.org-architecture-council] 8-Oct AC Meeting Notes Sent by: eclipse.org-architecture-council-bounces@xxxxxxxxxxx On 09/10/15 02:22 PM, Daniel Megert wrote: Denis, are you 100% sure? I made a query and shared it. And others were able to see it, Did this change in the recent Bugzilla version? You can create a query using tags and share it ... but the results of the query will be entirely different from one user to the other. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=453171 where a team used tags but got unexpected results. This is always how I've known Tags to work. Denis Dani From: Denis Roy <denis.roy@xxxxxxxxxxx> To: eclipse.org-architecture-council@xxxxxxxxxxx Date: 09.10.2015 19:02 Subject: Re: [eclipse.org-architecture-council] 8-Oct AC Meeting Notes Sent by: eclipse.org-architecture-council-bounces@xxxxxxxxxxx On 09/10/15 11:40 AM, Daniel Megert wrote: I assume an example on using tags? You can set any tags on a bug into the 'Tags' field. Then you create a search query that matches that tag. After that you save the query under a name and share it via 'Saved Searches' preference page. As Wayne has mentioned, the Bugzilla "Tags" field is not shared and is only used for personal tags.. https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#tag Denis HTH Dani From: Wayne Beaton <wayne@xxxxxxxxxxx> To: eclipse.org-architecture-council@xxxxxxxxxxx Date: 09.10.2015 17:30 Subject: Re: [eclipse.org-architecture-council] 8-Oct AC Meeting Notes Sent by: eclipse.org-architecture-council-bounces@xxxxxxxxxxx Sorry to be daft. Can point me at an example? Wayne On 09/10/15 11:08 AM, Daniel Megert wrote: He meant bugzilla tags. They can be shared like any other query. The summary field is usually used by components with well-defined tokens, and like Lars, I'd prefer not to add other "tags". Dani From: Wayne Beaton <wayne@xxxxxxxxxxx> To: eclipse.org-architecture-council@xxxxxxxxxxx Date: 09.10.2015 16:45 Subject: Re: [eclipse.org-architecture-council] 8-Oct AC Meeting Notes Sent by: eclipse.org-architecture-council-bounces@xxxxxxxxxxx I'm a little confused about what you mean. Do you mean Bugzilla Tags or prefix tagging a subject line (e.g. "[FEEP] Do something interesting stuff"). I had intended the latter (I've good success with using these for queries). I've never used Bugzilla Tags, but my understanding is that they are connected to the individual (i.e. they're not shared). Wayne On 08/10/15 05:45 PM, Lars Vogel wrote: Wayne, could he use instead of a new prefix a tag? Easier to filter for tags IMHO and we are in platform.ui are using prefixes already to classify our bugs. Best regards, Lars On Thu, Oct 8, 2015 at 6:38 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote: I went to create the umbrella bug and it occurred to me that it might be just as easy to prefix the subject line with "[FEEP]". Are there any objections to just doing this rather than open an umbrella bug that will never actually get closed as "FIXED" ? Wayne On 08/10/15 12:05 PM, Oberhuber, Martin wrote: Hi all, Notes of today’s meeting are now online: https://wiki.eclipse.org/Architecture_Council/Meetings/October_8_2015 Great discussion about how to come up with a good list of priorities for the development funding program. There was a number of interesting possibilities mentioned for “funding-worthy” work items. Wayne’s going to create an Umbrella bug for discussion proposals and hooking dependent bugs for discussion under it. Thanks, Martin -- Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6 _______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal. -- Wayne Beaton @waynebeaton The Eclipse Foundation _______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal. -- Eclipse Platform UI and e4 project co-lead CEO vogella GmbH Haindaalwisch 17a, 22395 Hamburg Amtsgericht Hamburg: HRB 127058 Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel USt-IdNr.: DE284122352 Fax (032) 221739404, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com _______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal. -- Wayne Beaton @waynebeaton The Eclipse Foundation [attachment "attjhvru.png" deleted by Daniel Megert/Zurich/IBM] [attachment "ECE Friends 130x100_0.png" deleted by Daniel Megert/Zurich/IBM] _______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal. _______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal. -- Wayne Beaton @waynebeaton The Eclipse Foundation _______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal. _______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal. --
Wayne Beaton @waynebeaton The Eclipse Foundation 
|