-
Notifications
You must be signed in to change notification settings - Fork 412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help wanted on these issues #4067
Comments
@harshkhandeparkar @jeffslofish just made this, thought you guys might want to know about @tzarebczan 's Wishlist tag. |
I was just going through the list when I got this notif 😃.
…On Fri, 24 Apr, 2020, 11:20 PM Jeremy Kauffman, ***@***.***> wrote:
@harshkhandeparkar <https://github.com/HarshKhandeparkar> @jeffslofish
<https://github.com/jeffslofish> just made this, thought you guys might
want to know about @tzarebczan <https://github.com/tzarebczan> 's
Wishlist tag.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4067 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIJI5HYMP53L2VVRHQLWFK3ROHGOTANCNFSM4MQJFW2Q>
.
|
For the last few weeks I've been playing around with the desktop app and the daemon and looking for issues to pick off. Although the branching naming conversion uses fix/feature/feat nomenclature, as a newbie, its hard for an outsider to understand if issues are actively being worked on, and thus my coding could be wasted. Perhaps if lbry could assign users when they're actively working on an issue and / or use the issue number as the branch name as we did at ConsenSys and other roles? |
Hi. You don't really need to follow any *branch* naming convention. Just
giving the branch a descriptive name is enough.
Also if you want to know if someone is working, just drop a comment. Also,
if you want to claim an issue, just leave a comment.
If someone had claimed an issue and haven't replied in a long time, it can
be assumed that they abandoned it. Or you can just ask one of the
reviewers/maintainers to reassign it.
…On Wed, 29 Apr, 2020, 3:06 PM Lucas Cullen, ***@***.***> wrote:
For the last few weeks I've been playing around with the desktop app and
the daemon and looking for issues to pick off.
Although the branching naming conversion uses fix/feature/feat
nomenclature, as a newbie, its hard for an outsider to understand if issues
are actively being worked on, and thus my coding could be wasted.
Perhaps if lbry could assign users when they're actively working on an
issue and / or use the issue number as the branch name as we did at
ConsenSys and other roles?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4067 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIJI5H6OLKP3UPNLHHV5L7DRO7YIFANCNFSM4MQJFW2Q>
.
|
Also, I don't believe that outsiders with no contribution can be assigned
to an issue using the issue assign feature.
Although, we could create a label for that...
…On Wed, 29 Apr, 2020, 3:28 PM M K, ***@***.***> wrote:
Hi. You don't really need to follow any *branch* naming convention. Just
giving the branch a descriptive name is enough.
Also if you want to know if someone is working, just drop a comment. Also,
if you want to claim an issue, just leave a comment.
If someone had claimed an issue and haven't replied in a long time, it can
be assumed that they abandoned it. Or you can just ask one of the
reviewers/maintainers to reassign it.
On Wed, 29 Apr, 2020, 3:06 PM Lucas Cullen, ***@***.***>
wrote:
> For the last few weeks I've been playing around with the desktop app and
> the daemon and looking for issues to pick off.
>
> Although the branching naming conversion uses fix/feature/feat
> nomenclature, as a newbie, its hard for an outsider to understand if issues
> are actively being worked on, and thus my coding could be wasted.
>
> Perhaps if lbry could assign users when they're actively working on an
> issue and / or use the issue number as the branch name as we did at
> ConsenSys and other roles?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#4067 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AIJI5H6OLKP3UPNLHHV5L7DRO7YIFANCNFSM4MQJFW2Q>
> .
>
|
Sure. That being said, I was looking at issue #3800 and noticed branch https://github.com/lbryio/lbry-desktop/tree/feat-channelAbandon. Im not sure if someone is actively working on this fix. All good, just an observation / suggestion. |
Looking for issues to work?
This issue is designed as a signpost for people exploring the
help wanted
tag.The text was updated successfully, but these errors were encountered: