Re: [eclipse.org-feep-stakeholders] Should FEEP bugs be triaged?

[Mikaël Barbero <mikael@xxxxxxxxxxx>]

For FEEP 2016's round, the AC has created these meta-issues to discuss about potential bugs they wanted to propose to EMO, and to classify them. So, despite most of them are on the AC project, they are really only about creating a theme for a group of bugs (e.g., https://bugs.eclipse.org/bugs/show_bug.cgi?id=482409). 

I will however go through the list and see if some of them do not fit into this category and should be moved to other projects.

Thanks.

Le 22 nov. 2016 à 09:56, Mickael Istria <mistria@xxxxxxxxxx> a écrit :

On 11/22/2016 09:35 AM, Mikaël Barbero wrote:

Done. I've removed [FEEP] prefix from all bug titles and added the recently created "feep" keyword. The search is now:

Thanks,
Another question: all bugs are currently assigned to Architecture Council "project", which isn't very representative of the state of the issue. How is this useful? Shouldn't such enhancement requests be assigned to the actual project they're targetting? It would allow project stakeholders to be aware of the opportunity to get funding for those issues, and at some point, the project teams have to be involved anyway. Moreover, there are some bugs that might be taken by the community without funding...

Cheers,

--
Mickael Istria
Eclipse developer for Red Hat Developers
My blog - My Tweets

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