PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
Create an issue tracker for new leagues or open up Discord to the public.
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 5.4k
- Forks
- 2.4k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 26
Description
Check for duplicates
- I've checked for duplicate issues by using the search function of the issue tracker
Is your feature request related to a problem?
I started looking at implementing some of the new patch changes when I saw random PRs being opened for the same thing already. Seems like there is a discord where people are organizing. This makes it hard for a newcomer to come and contribute as I don't know what's being worked on, or not.
Describe the solution you'd like
So I understand that it may be a lot of work to open up an issue for each new PR before that PR is being worked on, (although I would recommend it), but atleast for new leagues there should be an issue to track a master list of things to do before the new patch, or make 1 of the channels on the discord public so people can drive-by contribute.
Describe alternatives you've considered
Master issue tracker, either on Github or website or Discord.
Opening up public discord.
Requiring an issue to be written before work on a PR begins.
Creating a list of contributable issues for each new League, (although this kind of exists, it's not for bringing in new stuff from the patch, but for old issues or bugs).
Additional context
No response
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 by reviewing issue #3283 and its three comments, then compare the proposed options: a GitHub master issue, a website or Discord tracker, a public Discord channel, or requiring issues before pull requests. Done means the project has a decided, documented contribution-tracking approach for new leagues; no implementation files or tests are identified in the issue.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100