Locking GitHub Conversations

#1

Post by jodal » Mon, Jun 09, 2014, 8:48 PM UTC

Re: Locking GitHub Conversations

#2

Post by vhost- » Mon, Jun 09, 2014, 8:56 PM UTC

I wonder how much this is going to be abused. There are a lot of angry BDFLs out there and I can see this being used to silence people.

Re: Locking GitHub Conversations

#3

Post by jipiboily » Mon, Jun 09, 2014, 8:56 PM UTC

Finally, no more :+1:s when it's all that is being said by everyone, without much discussions...yay to less noise!

Re: Locking GitHub Conversations

#4

Post by TimWolla » Mon, Jun 09, 2014, 9:04 PM UTC

jipiboily wrote: post #3

Finally, no more :+1:s when it's all that is being said by everyone, without much discussions...yay to less noise!

I must admit that I like those :+1:s, it shows which issues should be prioritized.

Re: Locking GitHub Conversations

#5

Post by teeray » Mon, Jun 09, 2014, 9:09 PM UTC

TimWolla wrote: post #4

jipiboily wrote: post #3

Finally, no more :+1:s when it's all that is being said by everyone, without much discussions...yay to less noise!

I must admit that I like those :+1:s, it shows which issues should be prioritized.

Yeah, but it's symptomatic of needing voting for issue priority. Comments aren't the place for indicating you'd like something to be fixed.

Re: Locking GitHub Conversations

#6

Post by DigitalSea » Mon, Jun 09, 2014, 9:13 PM UTC

Finally.

Now all we need is the ability to vote up an issue and we're set. Seems comments have been used as a voting mechanism on Github since its inception and this new feature could put a stop to that. I hope not.

Re: Locking GitHub Conversations

#7

Post by yeukhon » Mon, Jun 09, 2014, 9:14 PM UTC

vhost- wrote: post #2

I wonder how much this is going to be abused. There are a lot of angry BDFLs out there and I can see this being used to silence people.

I don't think locking a thread is going to do harm.

If I don't want you to participate in my issue tracking, I can choose to ignore you, or now I can choose to lock the issue. You either continue to request attention from me, or won't come back to my software.

This can happen before locking is brought to us by Github, but this feature can help reduce noises. There are people who follow the repo and actually get spams from following repos they like to keep an eye on.

You have your choice to write about someone's angry ignorance on your blog or hackernews and people just won't care. They can even hide the repo or delete the repo once and for all.

Is this a good way to deal with people publicly? Yes to some, no to many. It's a choice. You either opt-in or opt-out.

Re: Locking GitHub Conversations

#8

Post by steveklabnik » Mon, Jun 09, 2014, 9:15 PM UTC

DigitalSea wrote: post #6

Finally. Now all we need is the ability to vote up an issue and we're set. Seems comments have been used as a voting mechanism on Github since its inception and this new feature could put a stop to that. I hope not.

This was there long ago, and was removed.

Re: Locking GitHub Conversations

#9

Post by sloanesturz » Mon, Jun 09, 2014, 9:17 PM UTC

Hopefully this feature will help to mitigate political PR's like this one so that project leaders can get back to writing code and won't have to deal with their repos being overloaded by non-contributor talking heads. 742 comments over a simple terminology change? Yeesh.

https://news.ycombinator.com/item?id=7801646

Re: Locking GitHub Conversations

#10

Post by RKoutnik » Mon, Jun 09, 2014, 9:17 PM UTC

EDIT: Looks like this has been fixed already. Speedy update by GitHub, nice work folks.

This is very easy to bypass. I was able to 'chime in' on one of the massive threads this feature intends to stop by referencing it in an issue on one of my repositories:

https://github.com/joyent/libuv/pull/1015#issuecomment-45544...

Obviously this is a tad more complicated than before (and makes it much harder to go on multi-paragraph rants) but the trolls can still troll.