[bisq-network/projects] Make compensation requests programattically parsable (#32)
m52go
notifications at github.com
Wed Jun 17 15:00:14 UTC 2020
With the new compensation request issue template now merged, all contributors should now use the new format that came about as a result of this project.
Here I'll run through each of the objectives that has been completed so far.
> Finalize compensation request format (Markdown table, YAML, etc)
The new format, in a nutshell, simplifies all line-items for **contributions and roles** into a single table.
- There is no longer a separate section for roles performed.
- Each contribution should specify the team it belongs to.
- As soon as `[WIP]` is removed from the issue title, the issue will be linted by a bot to make sure it can be evaluated later for budgeting purposes.
- If a request is valid, it's labeled as `parsed:valid` and no further action is necessary from the contributor.
- If it's invalid, it's labeled as `parsed:invalid`, and the bot will make a comment indicating the error. Then the contributor should correct the request until it's marked as `parsed:valid`.
**The [updated issue template](https://github.com/bisq-network/compensation/issues/new) should include all details a contributor would need to compose a valid compensation request.**
> Clarify planned results
Currently the bot will post an issuance breakdown by team after DAO voting when the request is marked as accepted or rejected by the compensation maintainer. This will help achieve the near-term goal of determining total issuance by team. For now, results will be posted in a spreadsheet that will be made public.
The next step is to add context to the raw totals by aggregating line-item titles to give more context to team issuance numbers.
> Create and test linting bot
> Create and test parsing bot
@jmacxx took care of all of this. Thank you! It's been a pleasure working with you.
> Edit wiki documentation and compensation request template to reflect changes
See [tentative documentation in the wiki](https://bisq.wiki/Compensation#Ensure_your_request_is_valid). That article will be reworked so that "Making a compensation request" is a standalone article, but the linked section covers the basics. Aside from the new format (detailed in the issue template) and the linting (errors are posted in the issue), there isn't anything additional users need to know or do.
I'll make announcements on Keybase and in https://github.com/orgs/bisq-network/teams/dao to draw attention to this new format and encourage contributors to test it in this cycle.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/projects/issues/32#issuecomment-645428550
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200617/095e65a1/attachment.html>
More information about the bisq-github
mailing list