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.

[Eilon]

Hi folks,

We realize that this repo can cause a fair amount of emails/notifications to sometimes flood peoples' inboxes when they wake up. Sorry about that!

We need to balance the value of people seeing important announcements and helpful discussions about those announcements with the cost of seeing other chatter that is not necessarily directly related to the announcements themselves.

One proposal is as follows:

1. The ASP.NET and EF teams continue to post announcements in this repo, but will lock every issue.
2. Every issue in this repo will link to an unlocked issue in a feature-specific repository, presumably named something like "Announcement Discussion: New feature XYZ"
3. As the discussion yields new information (such as a limitation, bug, or other interesting commentary), the ASP.NET and EF team will post updates in the Announcements repo on the issue.

The hope is that this enables rapid dialog between those who wish to participate in that dialog, and enable others to monitor just the key announcements and updates to those announcements.

[csharpfritz]

Eilon +1

This strategy keeps those discussions with a vested interest in specific
feature areas in those areas. The key element here is the link in the
announcement post to the discussion element.

To note: if the discussion announcement is in a repo you are already
following, then there is no additional step you need to take, you will get
both emails and the 70+ replies.
On Jul 26, 2015 1:03 PM, "Eilon Lipton" notifications@github.com wrote:

Hi folks,

We realize that this repo can cause a fair amount of emails/notifications
to sometimes flood peoples' inboxes when they wake up. Sorry about that!

We need to balance the value of people seeing important announcements and
helpful discussions about those announcements with the cost of seeing
other chatter that is not necessarily directly related to the announcements
themselves.

One proposal is as follows:

1. The ASP.NET and EF teams continue to post announcements in this repo,
   but will lock every issue.
2. Every issue in this repo will link to an unlocked issue in a
   feature-specific repository, presumably named something like "Announcement
   Discussion: New feature XYZ"
3. As the discussion yields new information (such as a limitation, bug, or
   other interesting commentary), the ASP.NET and EF team will post updates
   in the Announcements repo on the issue.

The hope is that this enables rapid dialog between those who wish to
participate in that dialog, and enable others to monitor just the key
announcements and updates to those announcements.

—
Reply to this email directly or view it on GitHub
#47 (comment)
.

[scionwest]

+1 for this. I think this is a good compromise. Allowing the discussion to take place, and keeping everyones inboxes at zero ;)

[guardrex]

👎

As the discussion yields new information (such as a limitation, bug, or other interesting commentary), the ASP.NET and EF team will post updates in the Announcements repo on the issue.

Will probably create more overhead for the teams and make it harder to track down Announcement discussion nits and bits than if you had just had Announcements (Locked) and Announcements (Unlocked) repos. A post in each would have done it. If you only want Announcements, you subscribe to Locked. If you want the full deal, you subscribe to Unlocked. IMHO this would be much simpler and easier to maintain than the proposal.

[PureKrome]

Sanity prevails 👏 👏

[jimmyp]

+1

On Mon, 27 Jul 2015 at 09:17 Pure Krome notifications@github.com wrote:

Sanity prevails [image: 👏] [image: 👏]

—
Reply to this email directly or view it on GitHub
#47 (comment)
.

[kevinrood]

I agree with @guardrex and favor the locked and unlocked repo approach. I am interested in all the announcements here - and the discussions around them. I would not want to go to separate repos to subscribe to specific issues for more discussion. I also realize others just want the announcements.

[scionwest]

You could use a website w/ an RSS feed for people to subscribe to. Post the announcements there for those who don't want to participate in discussions, while leaving this repo open for conversations. Just a thought. I realize posting an announcement in two places is a bit of a pain. Not sure there's a one-size fits all solution to this.

[dmccaffery]

Not to beat this to death, but perhaps a simple disclaimer asking folks to refrain from arguing the merits of the announcement each time a new one is created would suffice. It's easy enough to lock the issue on a case by case basis if one gets out of hand. I've only seen a few that go haywire. I suppose my thoughts are that arguments are par for the course in an open-source community. The one that caused all of this ruckus to begin with resulted in a reversal on the decision, so the 'bikeshedding' had a useful effect. Even if some people didn't think it was important, enough people did.

For the most part, I do believe that the community has been mature and reasonable; a few fly-away threads is the medicine one must take in exchange for up-to-the-minute information about an open-source project.

At any rate, I think everyone has been great, and I am very excited for .NET Core. :)

On Jul 27, 2015, at 9:30 AM, Johnathon Sullinger <notifications@github.commailto:notifications@github.com> wrote:

You could use a website w/ an RSS feed for people to subscribe to. Post the announcements there for those who don't want to participate in discussions, while leaving this repo open for conversations. Just a thought. I realize posting an announcement in two places is a bit of a pain. Not sure there's a one-size fits all solution to this.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/47#issuecomment-125264952.

[Garciat]

+1

[ianbattersby]

@Eilon +1

[victorhurdugaci]

The first announcement that follows the new pattern: #51

[haneytron]

@victorhurdugaci thank you and the whole team. This is so much better.

[Eilon]

@victorhurdugaci nope, the first one was #49 😄

[dotnetchris]

@victorhurdugaci can you make If you have any comments, concerns, or questions, post them on this thread. entire sentence be a hyperlink instead of just "this", (unless it's intentionally non-obvious to limit discussion)