[whispersystems] Add "help-wanted" label

[art1fa]

Hey!

What do you think of adding a "help-wanted" label for smaller and
"easy-to-fix" issues for which the core developers currently do not have
the time to look into?
I am speaking of for example the scroll-to-bottom issue (#2856), the iOS
9.1 emoji (#4279) etc.

This might be an additional incentive for non-OWS devs to contribute and
submit PRs that have a good chance to be merged if the contributing
conventions are met.

art1fa
(@agrajaghh @2-4601)

[Shankar Kulumani]

I thought there was an "easy" label for this?

Post by art1fa
Hey!
What do you think of adding a "help-wanted" label for smaller and
"easy-to-fix" issues for which the core developers currently do not have
the time to look into?
I am speaking of for example the scroll-to-bottom issue (#2856), the iOS
9.1 emoji (#4279) etc.
This might be an additional incentive for non-OWS devs to contribute and
submit PRs that have a good chance to be merged if the contributing
conventions are met.
art1fa

[orta therox]

There’s an Easy Contribution <https://github.com/WhisperSystems/Signal-iOS/issues?q=is:open+is:issue+label:%22Easy+Contribution%22> label, but as an iOS developer who could spend their OSS time on Signal, I see 25 un-merged PRs, and the majority for this year with no comments. This says to me any time I put into Signal is effectively wasted.
--
[A.] Orta Therox

w/ Artsy <http://artsy.net/>CocoaPods <http://cocoapods.org/> / CocoaDocs <http://cocoadocs.org/> / GIFs.app <https://itunes.apple.com/us/app/gifs/id961850017?l=en&mt=12>
@orta <http://twitter.com/orta> / orta.github.com <http://orta.github.com/>
I thought there was an "easy" label for this?
Hey!
What do you think of adding a "help-wanted" label for smaller and
"easy-to-fix" issues for which the core developers currently do not have
the time to look into?
I am speaking of for example the scroll-to-bottom issue (#2856), the iOS
9.1 emoji (#4279) etc.
This might be an additional incentive for non-OWS devs to contribute and
submit PRs that have a good chance to be merged if the contributing
conventions are met.
art1fa

[art1fa]

I know there is an "easy" label, but I think it was not meant to
actually ask for contributions.


art1fa

There’s an Easy Contribution
<https://github.com/WhisperSystems/Signal-iOS/issues?q=is:open+is:issue+label:%22Easy+Contribution%22> label,
but as an iOS developer who could spend their OSS time on Signal, I see
25 un-merged PRs, and the majority for this year with no comments. This
says to me any time I put into Signal is effectively wasted.
--
[A.] Orta Therox

w/ Artsy <http://artsy.net/>
CocoaPods <http://cocoapods.org> / CocoaDocs
<http://cocoadocs.org> / GIFs.app
<https://itunes.apple.com/us/app/gifs/id961850017?l=en&mt=12>
@orta <http://twitter.com/orta> / orta.github.com
<http://orta.github.com>
I thought there was an "easy" label for this?
Hey!
What do you think of adding a "help-wanted" label for smaller and
"easy-to-fix" issues for which the core developers currently do not have
the time to look into?
I am speaking of for example the scroll-to-bottom issue (#2856), the iOS
9.1 emoji (#4279) etc.
This might be an additional incentive for non-OWS devs to
contribute and
submit PRs that have a good chance to be merged if the contributing
conventions are met.
art1fa

[Mark Somerville]

There’s an [1]Easy Contribution label, but as an iOS developer who
could spend their OSS time on Signal, I see 25 un-merged PRs, and the
majority for this year with no comments. This says to me any time I put
into Signal is effectively wasted.

Yes, although I'm not an iOS developer, this is concerning news to me.

What process (or anything other) changes can contributors make to ensure
this sort of backlog doesn't happen so easily?

[blake]

I think the problem is there is no current lead dev for signal on iOS. They've been trying to hire one for a while.

Post by Mark Somerville

There’s an [1]Easy Contribution label, but as an iOS developer who
could spend their OSS time on Signal, I see 25 un-merged PRs, and the
majority for this year with no comments. This says to me any time I

put

into Signal is effectively wasted.

Yes, although I'm not an iOS developer, this is concerning news to me.
What process (or anything other) changes can contributors make to ensure
this sort of backlog doesn't happen so easily?