[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-ui-dev] Super easy, nice to have bugs for a Hackathon
|
Agreed, I think we should use bugday for bugs we specifically approve for potential new contributors. Anything that comes in that 1) is a request for something and 2) is in an area not under active development gets helpwanted (because we'd consider a patch but no one will look at it on their own) so helpwanted includes some more complicated features in Platform/UI.
Paul Webster
Eclipse Platform UI Component Lead
IBM Rational Canada
Lars Vogel ---03/27/2014 06:19:21 AM---I suggest to use "bugday" as keyword to mark: 1.) Easy to solve bugs
![]()
| ![]()
Lars Vogel <lars.vogel@xxxxxxxxx> |
![]()
| ![]()
"Eclipse Platform UI component developers list." <platform-ui-dev@xxxxxxxxxxx>, |
![]()
| ![]()
03/27/2014 06:19 AM |
![]()
| ![]()
Re: [platform-ui-dev] Super easy, nice to have bugs for a Hackathon |
I suggest to use "bugday" as keyword to mark:
1.) Easy to solve bugs
2.) Which we want to have in the IDE
"helpwanted" would also fit but it looks to me that this have been used extensively in the past and it looks to me that the number of "invalid" bugs marked with this keyword is relatively high which the number marked with bugday are relatively small.
A small number of bugs is a good thing, as a potential new contributor can find something to fix relatively fast.
Is it OK for the platform.ui team to use "bugday" for small and important bugs which are easy to solve?
Best regards, Lars
2014-03-26 19:17 GMT+01:00 Lars Vogel <lars.vogel@xxxxxxxxx>:
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev

