LBRYCommunity/lbry-desktop

Fork 0

Help wanted on these issues #4067

New issue

Open

opened 2020-04-24 19:46:50 +02:00 by kauffj · 8 comments

kauffj commented

2020-04-24 19:46:50 +02:00

(Migrated from github.com)

Looking for issues to work?

Make sure you read this first.
Check issues tagged help wanted. These issues were typically explicitly looked at the LBRY team, are friendly to work on and desirable features, but are explicitly not a priority for us.
Check issues tagged Tom's Wishlist. These issues are typically workable and are highly desired, but not always new contributor friendly. You should only work on one of these if not assigned and should comment if you're going to work on them.

This issue is designed as a signpost for people exploring the help wanted tag.

Looking for issues to work? 1. Make sure you [read this first](https://github.com/lbryio/lbry-desktop/blob/master/CONTRIBUTING.md). 1. Check issues tagged [help wanted](https://github.com/lbryio/lbry-desktop/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22). These issues were typically explicitly looked at the LBRY team, are friendly to work on and desirable features, but are explicitly _not_ a priority for us. 1. Check issues tagged [Tom's Wishlist](https://github.com/lbryio/lbry-desktop/issues?q=is%3Aopen+is%3Aissue+label%3A%22Tom%27s+Wishlist%22). These issues are typically workable and are highly desired, but not always new contributor friendly. You should only work on one of these if not assigned and should comment if you're going to work on them. _This issue is designed as a signpost for people exploring the `help wanted` tag._

👍 1

kauffj commented

2020-04-24 19:50:18 +02:00

(Migrated from github.com)

@HarshKhandeparkar @jeffslofish just made this, thought you guys might want to know about @tzarebczan 's Wishlist tag.

harshkhandeparkar commented

2020-04-24 19:52:49 +02:00

(Migrated from github.com)

I was just going through the list when I got this notif 😃.

On Fri, 24 Apr, 2020, 11:20 PM Jeremy Kauffman, notifications@github.com
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
https://github.com/lbryio/lbry-desktop/issues/4067#issuecomment-619158345,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIJI5HYMP53L2VVRHQLWFK3ROHGOTANCNFSM4MQJFW2Q
.

I was just going through the list when I got this notif 😃. On Fri, 24 Apr, 2020, 11:20 PM Jeremy Kauffman, <notifications@github.com> 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 > <https://github.com/lbryio/lbry-desktop/issues/4067#issuecomment-619158345>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIJI5HYMP53L2VVRHQLWFK3ROHGOTANCNFSM4MQJFW2Q> > . >

bitcoinbrisbane commented

2020-04-29 11:35:46 +02:00

(Migrated from github.com)

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?

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?

harshkhandeparkar commented

2020-04-29 11:58:54 +02:00

(Migrated from github.com)

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, notifications@github.com
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
https://github.com/lbryio/lbry-desktop/issues/4067#issuecomment-621093853,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIJI5H6OLKP3UPNLHHV5L7DRO7YIFANCNFSM4MQJFW2Q
.

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, <notifications@github.com> 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 > <https://github.com/lbryio/lbry-desktop/issues/4067#issuecomment-621093853>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIJI5H6OLKP3UPNLHHV5L7DRO7YIFANCNFSM4MQJFW2Q> > . >

harshkhandeparkar commented

2020-04-29 12:00:13 +02:00

(Migrated from github.com)

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, mjkgoa@gmail.com 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, notifications@github.com
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
https://github.com/lbryio/lbry-desktop/issues/4067#issuecomment-621093853,
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, <mjkgoa@gmail.com> 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, <notifications@github.com> > 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 >> <https://github.com/lbryio/lbry-desktop/issues/4067#issuecomment-621093853>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AIJI5H6OLKP3UPNLHHV5L7DRO7YIFANCNFSM4MQJFW2Q> >> . >> >

👍 1

bitcoinbrisbane commented

2020-04-29 12:09:39 +02:00

(Migrated from github.com)

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.

> 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)](https://github.com/lbryio/lbry-desktop/issues/4067#issuecomment-621093853)>, 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.

mohamed0group commented

2020-08-22 06:50:10 +02:00

(Migrated from github.com)