Closing issues or create a pending label

[codeekage]

In the spirit of labeling good-first-issues 😃 in the repos, most issues in the CommComm repo has been open for a while with no activity.

Please @nodejs/community-committee members, review issues, make contributions or discussion to either add pending or labels that fit the issue or close them to assist people coming into the ecosystem to know their way around. 👍

[Tiriel]

This is indeed a real issue, there are lots of open issues with no activity (ironically, including this one).

I don't know whether a pending label would be of use though. In an ideal world, an open issue means there is still work to be done, and not-actionable /finished issues should be closed. We need to be more reactive on this.

cc @nodejs/community-committee
Without response or input on the label idea in 72hours, I'll close this issue.

[WaleedAshraf]

Instead of marking an issue as pending, it'd be good to close it and reopen when/if needed. I think pending label will cause more issue-staling.

[Bamieh]

most of the opened issues date back from march, which is not a long period at all. the remaining 10-15 issues are opened because they still need attention and resolution (but not an immediate one). I do not see this as a problem in this repo, 40 issues and 25 of them date maximum a few months ago is more than a acceptable IMO.

[Tiriel]

It's true that the question is more to know if the issue is actionable or not and not its date of opening. But we could indeed do a bit more on the cleaning side to avoid stale issues IMHO.

[bnb]

For what it's worth, I do try to go through our backlog once every month or two to close older issues/ask if progress has been made. This isn't a responsibility of the CommComm chair, but something I've personally found is helpful for maintaining an ongoing and constructive discussion long-term. Here's an example of that.

Having more people help with this kind of work across all the CommComm repos would definitely be appreciated 🙌

[codeekage]

I have gone through the @nodejs/community-committee repo and here is a list of issues I think that should be closed or revisited.

• Open Meeting: Individual Membership Subgroup Meeting - Monday, July 16th #353
• Node.js Foundation Community Committee Meeting 2018-06-28 #341
• Individual Membership Subgroup Meeting - June 25th, 2018 #337
• Q&A with Tracy Hinds (CommComm Director Elect) #331
• CommComm Restructuring Efforts Meeting 2018-05-28 (date to be changed) #309
• Reviving Evangelism Working and Other Inactive Working Groups  #275
• COMMUNITY [GLOBALIZATION, DIVERSITY] #268
• Automate Meeting Participant History Document #267
• Restructuring efforts transition phase proposal #299
• Updating CONTRIBUTING.md with new/relevant context #313

That’s all for now. I will be closing them in 72 hours of inactivity. 😄 :praying:

[hackygolucky]

Can we see this as a PR to the Collaborator Guide?. Particularly

1. the process we've documented here
2. making sure we comment on every issue before it is closed having followed this process so that contributors understand why it was closed and that it can easily be reopened.

[TimothyGu]

@codeekage Maybe you could go ahead and close them now? Many 72 hours have passed :)