thoughtbot / thoughtbot/administrate
Experimenting with discussions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
I've enabled GitHub's Discussions feature to try and see if it'll be helpful. We'll try it out for a few months and see how it goes.
It's always been great to see people chip into various issues and PRs over the years, but I'm keen to try and see if we can encourage more community discussions. It's important that everyone who uses the project has a (hopefully easy) opportunity to chip in with features and direction, and some of these are not appropriate for opening or commenting on an issue and potentially discussions will help with that.
I've left things at the defaults for now, but we'll see what's working and adjust from there.
I'll see you over in the discussions!
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
No files, tests, or entry points are mentioned. The issue announces an experiment with GitHub Discussions rather than defining a code change or a measurable completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100