Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open-Source Bounty System #46

Closed
Kaptard opened this issue Sep 27, 2017 · 2 comments
Closed

Open-Source Bounty System #46

Kaptard opened this issue Sep 27, 2017 · 2 comments
Assignees

Comments

@Kaptard
Copy link
Member

Kaptard commented Sep 27, 2017

Feature Description

Adds a system that allows attaching bounties (in the shape of ingame assets) to Github issues. List of bounties will be on separate page on development hub. New listings may also get automatically posted on Discord and mention anyone who joins the specific role.

Which problem will your feature solve?

This feature will likely bring a lot of life, or at least attention, to our open source approach.

What scenario will your feature be used in?

Will be used by players who need ingame currency/items in a short time frame.
Also useful for developers that were interested anyway and needed that bit of extra convincing to get more involved into the respective issues.

Documentation

Due to the scope of this project, the documentation will be kept to an abstract minimum

Scraping
Issues with bounties will be scraped through Github's API. Issues will be filtered by the Bounty label and then by user (whether or not they're in the nexus-devs org). The title should include the bounty like Some Issue [Bounty: 30p] where everything between the last : and last ] will be taken as bounty.

User implementation
The resulting data will then be displayed on their own page on the nexus-stats website (simple sortable list) and updated through our nexus-bot on discord.

@Kaptard
Copy link
Member Author

Kaptard commented Feb 12, 2018

accidently closed by accidental test commit :^)

@Kaptard Kaptard reopened this Feb 12, 2018
@Kaptard
Copy link
Member Author

Kaptard commented Jun 28, 2018

I'll close this issue for now as it is way too far from being implemented. Also, there's other solutions already doing this that we could work on to integrate.

@Kaptard Kaptard closed this as completed Jun 28, 2018
Kaptard added a commit that referenced this issue Sep 24, 2018
- adds something
- but doesn't really do anything

this also fixes #46 for some reason


Former-commit-id: d99d215
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant