Advertising 1 "trivial" bug a week

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Advertising 1 "trivial" bug a week

Mickael Istria-5
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 developer, for Red Hat Developers

_______________________________________________
platform-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
Reply | Threaded
Open this post in threaded view
|

Re: Advertising 1 "trivial" bug a week

Christoph Läubrich
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
> [hidden email]
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
>
_______________________________________________
platform-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
Reply | Threaded
Open this post in threaded view
|

Re: Advertising 1 "trivial" bug a week

Mickael Istria-5
In reply to this post by Mickael Istria-5
Hi all,

Thanks Christoph for your answer. I agree with many points. However I'm not sure those should be reasons for not trying it. Maybe it will work, maybe not, but I don't think it can hurt (in worst case, we get people not interested or not able to setup dev environment, but this case is just exactly what happens every day).
After some discussion with some other interested participants -from Red Hat I admit- to the @EclipseJavaIDE account, we decided that although it's likely to be a failure, the cost of this initiative is very small and the risk of making things worse (ie losing contributors) seems null, and the chances of success are small but non-null. Overall, the balance of it all has convinced us it's worth trying.
So I'll soon identify 2 more easy fixes and will tweet about those opportunities to get started contributing once a week starting from next week.
We'll then see whether it does bring some value or not ;)

Cheers,

_______________________________________________
platform-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
Reply | Threaded
Open this post in threaded view
|

Re: Advertising 1 "trivial" bug a week

Paul Pazderski
Hey Mickael,

I can give you some more or less trivial bugs to consider:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=563977
 - the actual change to do is very ease, adding as option gives a bit
extra work to make it not to trivial

https://bugs.eclipse.org/bugs/show_bug.cgi?id=560977
 - even more trivial than the first one

https://bugs.eclipse.org/bugs/show_bug.cgi?id=46103
 - I took a quick look and it should be rather trivial but a bit work
with the preference stuff involved

https://bugs.eclipse.org/bugs/show_bug.cgi?id=491853
 - should be easy, but I have not looked closer into

Another bug, more in the spirit of Christoph:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=551260
 - Should be well isolated but not fully trivial and might not have much
degree of freedom to fix. Debugging Eclipse startup is a bit trickier
but I added the necessary details to get it going.



Am 16.09.2020 um 16:52 schrieb Mickael Istria:

> Hi all,
>
> Thanks Christoph for your answer. I agree with many points. However I'm
> not sure those should be reasons for not trying it. Maybe it will work,
> maybe not, but I don't think it can hurt (in worst case, we get people
> not interested or not able to setup dev environment, but this case is
> just exactly what happens every day).
> After some discussion with some other interested participants -from Red
> Hat I admit- to the @EclipseJavaIDE account, we decided that although
> it's likely to be a failure, the cost of this initiative is very small
> and the risk of making things worse (ie losing contributors) seems null,
> and the chances of success are small but non-null. Overall, the balance
> of it all has convinced us it's worth trying.
> So I'll soon identify 2 more easy fixes and will tweet about those
> opportunities to get started contributing once a week starting from next
> week.
> We'll then see whether it does bring some value or not ;)
>
> Cheers,
>
>
> _______________________________________________
> platform-dev mailing list
> [hidden email]
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
>

_______________________________________________
platform-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Advertising 1 "trivial" bug a week

Mickael Istria-5
Thanks.
I've picked 3 bugs from Paul's list and scheduled tweetdeck to tweet about 1 of them on every Thursday at 3.30pm , for the next 3 weeks.
Let's debrief about it in 3.5 weeks ;)

_______________________________________________
platform-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
Reply | Threaded
Open this post in threaded view
|

Re: Advertising 1 "trivial" bug a week

Mickael Istria-5
In reply to this post by Mickael Istria-5
So it's already time for the conclusions:

3 tweets were sent with equivalent wording and different bugs; they received a roughly similar amount of reactions (between 25 and 40 likes/RTs).
Only the 1st one attracted a new contributor who got a patch merged. However, both other bugs got totally ignored, no reaction took place on Bugzilla.

My guess is that the next issues are less trivial and require some pre-existing understanding of some Eclipse Plugin development. I believe that the technical bar to fix the issues is already too high for the @EclipseJavaIDE twitter audience.

Negative side: Eclipse SDK doesn't have many really trivial issues in the pipe; or at least not in an easily identifiable way. Finding 3 "affordable" issues required some triaging effort from several contributors, and the result is not so positive for at least 2 of them. The "bugday" and "helpwanted" keywords don't help here.
If we want to continue such a campaign, I believe we need more trivial fixes. But this experiment has highlighted that the backlog doesn't contain enough easy fixes and that finding one is taking a lot of time and energy to some contributors. The approach of digging for an easy enough fix is too expensive IMO. So regularly spending this time in finding 1 easy bug and planning such tweets on a regular basis is IMO not profitable/sustainable; and should be discarded for the moment.
Positive side: However, we also had a "demonstration by example" (with the very poor reliability of such demonstrations ;) that going social on simplest bugs can attract new contributors. That's quite important to know that.

My proposal to carry on on this topic is that instead of planning tweets and crawling the backlog for a trivial fix (which may not exist), we instead switch to a "push" model, where some experienced contributor who identifies a trivial fix should immediately share a Bugzilla link with @EclipseJavaIDE owners so they then plan an #easyFix tweet for it and hopefully attract a new contributor like it happened with this campaign.

What do you think?



_______________________________________________
platform-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
Reply | Threaded
Open this post in threaded view
|

Re: Advertising 1 "trivial" bug a week

Aleksandar Kurtakov


On Tue, Oct 13, 2020 at 2:24 PM Mickael Istria <[hidden email]> wrote:
So it's already time for the conclusions:

3 tweets were sent with equivalent wording and different bugs; they received a roughly similar amount of reactions (between 25 and 40 likes/RTs).
Only the 1st one attracted a new contributor who got a patch merged. However, both other bugs got totally ignored, no reaction took place on Bugzilla.

My guess is that the next issues are less trivial and require some pre-existing understanding of some Eclipse Plugin development. I believe that the technical bar to fix the issues is already too high for the @EclipseJavaIDE twitter audience.

Negative side: Eclipse SDK doesn't have many really trivial issues in the pipe; or at least not in an easily identifiable way. Finding 3 "affordable" issues required some triaging effort from several contributors, and the result is not so positive for at least 2 of them. The "bugday" and "helpwanted" keywords don't help here.
If we want to continue such a campaign, I believe we need more trivial fixes. But this experiment has highlighted that the backlog doesn't contain enough easy fixes and that finding one is taking a lot of time and energy to some contributors. The approach of digging for an easy enough fix is too expensive IMO. So regularly spending this time in finding 1 easy bug and planning such tweets on a regular basis is IMO not profitable/sustainable; and should be discarded for the moment.
Positive side: However, we also had a "demonstration by example" (with the very poor reliability of such demonstrations ;) that going social on simplest bugs can attract new contributors. That's quite important to know that.

My proposal to carry on on this topic is that instead of planning tweets and crawling the backlog for a trivial fix (which may not exist), we instead switch to a "push" model, where some experienced contributor who identifies a trivial fix should immediately share a Bugzilla link with @EclipseJavaIDE owners so they then plan an #easyFix tweet for it and hopefully attract a new contributor like it happened with this campaign.

Did we manage to get more interest from the person that fixed the first issue? IMHO this is important when we evaluate the importance of the program.


What do you think?


_______________________________________________
platform-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev


--
Alexander Kurtakov
Red Hat Eclipse Team

_______________________________________________
platform-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
Reply | Threaded
Open this post in threaded view
|

Re: Advertising 1 "trivial" bug a week

Paul Pazderski
In reply to this post by Mickael Istria-5
We got a good change from a new contributor (at least his first action
in Bugzilla) for the advertised "Persist Word Wrap" bug.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=491853


_______________________________________________
platform-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Advertising 1 "trivial" bug a week

Mickael Istria-5


On Tue, Oct 20, 2020 at 10:54 PM Paul Pazderski <[hidden email]> wrote:
We got a good change from a new contributor (at least his first action
in Bugzilla) for the advertised "Persist Word Wrap" bug.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=491853

Thanks Paul for notifying!
--
Mickael Istria
Eclipse IDE developer, for Red Hat Developers

_______________________________________________
platform-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev