Request to lock Announcements after new announcement has been posted

[PureKrome]

Hi Team,

Problem:

with things ramping up and more announcements coming forth there's starting to be more noise around each announement, which IMO defeats the purpose of each actual announcement.

TLDR: there's starting to be too much noise from this GH Repo which defeats the purpose of this repo.

Example: The mega discussions about #24 and #28

Suggested Solution

• Discussion Issue: Create an issue about the announcement in the exact repo. This is where any discussion will occur.
• Announcement Issue: Create an announcement issue in this repo and link to the discussion issue.
  Authorised people create a new Issue (which is the actual announcement) in this repo provide a reference to the discussion issue, then lock this issue ASAP.

Example: New command: dnu sources (lets assume this is part of the /aspnet/dnx repo).

• Jump over to https://github.com/aspnet/dnx/issues and create a new issue. eg. [Announcement] New command: dnu sources. Body => Discuss the announcement here. Copy the issue URL for reference.
• Jump back to https://github.com/aspnet/Announcements/issues.
• Create a new issue in this Announcement repo: New command: dnu sources
• Add a reference to the original issue created in /aspnet/dnx/issues
• Lock this issue.

So now, we have the announcement issue which has lots of subscribers and we get notified - yay! 🎉

If anyone wants to chat/discuss this announcement, they have a link to it .. which they click and voila! off they go .. chat chat chat.

... and I (and many others) don't get hit by that conversation.

[guardrex]

👎 One dev's "noise" is another dev's valuable Q&A with the team on the Announcement. This is the ideal place for some discussions, at least because they don't all fit neatly into another repo.

There is an "Unsubscribe" button right there. If you don't want additional comments from each Announcement you read, then click the button. Is it really that difficult?

[haneytron]

If it was meant to be the discussion thread, it would be called [Discussions], not [Announcements]

[guardrex]

How about this: One Announcements repo locked and one Announcements repo unlocked. All the team has to do is create the issue in each. Anyone can subscribe to one or the other on the basis of wanting to read folks' reactions/Q&A or not.

[Encosia]

Yes, please. I'm very interested in the announcements, but not at all in the bikeshedding that often follows.

[imranbaloch]

+1

[tinganho]

Please don't lock the thread. Any unclarities about an announcement can be sorted out in the following comments. Also referencing another thread will lead to less engagement.

[felipepessoto]

+1

Every time a new announcement is posted I need to open GitHub and unsubscribe the post.

[keichinger]

@guardrex

There is an "Unsubscribe" button right there. If you don't want additional comments from each Announcement you read, then click the button. Is it really that difficult?

The thing about the unsubscribe button is that it's simply not working. You're still getting E-Mails and the GitHub Feed is still spammed/cluttered.

I've approached the Dev team with the very same idea when the repo has been created and the first mega discussions took place and the guy I was talking to on JabbR didn't seem to understand the problem people like you and I are having. Waking up in the morning just to have 70+ unnecessary E-Mails in my inbox and having a GitHub activity feed that basically became unusable is awesome and definitely defeats the purpose of this repository.

I think a few people are exploiting this repository for their Q&As. I can understand that it's easy and neat for them to do it right here, but let's be honest that a dedicated issue would still work (like it did in the past with any other changes).

In the end if nothing changes then I simply might have to unsubscribe from the whole repository and check it manually every now and then...

So +1 for your suggestion.

[tinganho]

You're still getting E-Mails

This seem to be not correct? In my experience you are only getting email if you got mentioned or you replied to a thread. I don't think you receive any emails if you unsubscribe.

[keichinger]

I've got plenty of E-Mails in my inbox from unsubscribed and unreplied threads.

[m0sa]

+1 I agree with the proposed solution.
The abuse of announcements for (most of the time trivial) Q&A and bikeshedding has to stop!

[HellBrick]

+1. I'd rather be notified about the announcements themselves and opt in monitoring discussions I'm interested in, than have to opt out of every single announcement.

[tugberkugurlu]

👎, don't lock them. If anyone sees the discussions as noise:

• unsubscribe from the whole repo
• unsubscribe from the noisy issue.
• Set up a rule on your e-mail provider to discard e-mails (auto delete, get it into somewhere other than inbox, etc.) which was sent to Announcements@noreply.github.com and whose subject starts with Re: [Announcements].

If the discussion goes out of scope, the issues are being locked already (#24). If the discussion is relevant, I wanna see it here, not anywhre else.

[tugberkugurlu]

Also 👍 to @tinganho's less engagement point.

[topia]

👍 Please refrain this repository has many watchers (868 for now). I don't want to see any long discussion, but I still need corrections. I believe it's main purpose to follow this repository.
For unclear things, we can resolve it on another place, and add some corrections by collaborator on here.