Do *something* about Gitter
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11
- Forks
- 4
- Avg merge
- 1h 49m
- Merged PRs (30d)
- 2
Description
Over on the Scala Contributors forum, the point came up that spammers are occasionally infesting Gitter channels. I don't see an immediate crisis -- there have definitely been some roaming bots, but nothing terribly immediate -- but in principle we shouldn't have completely unmonitored and unmaintained channels out there.
So I'd say that we should either:
- Update ourselves to be able to maintain those channels (at the least, some of us newer members of the Steering Committee, and/or other responsible volunteers, should be given appropriate admin powers), or
- Acknowledge that the channels are truly dead, and archive them.
I'm not particularly attached to which direction we choose (and I'm willing to check in there occasionally, if I'm given the power to do something about it), but the current state of affairs isn't great.
(None of this is unique to us -- the same is true for a variety of Scala channels -- but the ones under "typelevel" are our responsibility.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Scala Contributors forum discussion and inspect the Gitter channels under "typelevel" to determine whether they are still needed and whether responsible volunteers can obtain admin powers. Done means choosing either a maintainable ownership plan or archiving the channels, then carrying out that decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100