[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-dev] Advertising 1 "trivial" bug a week
|
Hi Mickael,
while the idea seems good I must confess that I personally found these
"trivial" bugs the most frustrating one.
- initial setup-cost are very high (what repository? what dependencies
required, how to test)
- the task is not very attractive and boring
- the impact is so low, that in most cases one has to ask several times
to get reviews
- often the bug is not that trivial as first assumed as the reporter
does not know the complexity
If the bug is really that trivial, why does not a commiters with a
already configured IDE that knows where to look at simply takes these
5-10 minutes to fix this? I know we all have much to do, but others have
also, so that's not really a point.
Instead we wait for other people to take much more effort (it often
takes > half an hour do setup/download the required IDE, target files
and git-sources, find the right maven calls and so on), to fix things
the commiters of the project itself don't bother or find them to boring.
In my opinion, if we really like to attract new commiters they should
not simply give something considered trivial. Instead we should find
bugs that:
1) are likely isolated but still interesting to solve e.g. a certain
amount of debugging might be required and a certain degree of freedom of
the solution is possible
2) The exact steps to setup, run and reproduce the problem should be clear
3) There should be at least one commiter that feels responsible to guide
the beginner, review the code and help with setup/submission of the
patch for this specific bug
I know that this would make it even more hard to find suitable bugs and
maybe a little bit off for a simple campaign, but as noted I think
otherwise we more frustrate than attract new contributors...
Am 02.09.20 um 08:06 schrieb Mickael Istria:
Hi all,
I'd like to start a campaign with the @EclipseJavaIDE twitter account to
bring in new contributors. The idea will be that every week, a tweet
would be posted with an encouraging message and a link to a *very
simple* bug to fix for newcomers.
An example of such bugs would be
https://bugs.eclipse.org/bugs/show_bug.cgi?id=566404 (changing some labels).
The difficulty is identifying which bugs are really simple. The
"helpwanted" and "bugday" bugs are realistically not all easy enough and
triaging that is more effort than what I'm willing to spend for the
twitter campaign.
So do you have some examples of other trivial bugs we could use for this
campaign. 6~8 bugs would be enough for a start.
Thanks in advance
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
