[bisq-network/projects] Make compensation requests programattically parsable (#32)

[m52go]

@cbeams we might have something worth testing. @jmacxx has created bots that evaluate compensation requests using [this template](https://gist.githubusercontent.com/m52go/1a585470aff9decb1016cbb4f59164e2/raw/09c421cd71f954ac073a22cd0d091f2549e62a77/proposed-cr-template.md). 

Please check to see if it looks acceptable to you.

It should largely conform to the ideas you and I discussed earlier, with one difference:
- the "roles performed" section is removed, as discussed, and role items are included in the main contributions table, but line-items for roles include an asterisk in the team name column to designate them as role items (see template linked above for an example)

For what it's worth, I also drafted bullet points for documentation that would need to be added according to the proposed template and bots:

- compensation requests are parsed programmatically for budgeting, so please make sure your compensation request adheres to the template as closely as possible. there are comments in the template for guidance, and you can always check past requests for reference. 
- a linter will check your request once you've removed `[WIP]` from your issue title and will notify you of any errors.
- all contributions should specify values in usd. only the top-line number in the summary section should be denominated in bsq.
- role reports and related compensation should _both_ be included in the "contributions delivered" table. role items should include an asterisk in the team column (so a regular growth contribution would specify the team as "growth", and a growth team _role_ would specify the team as "growth*").
- multiple smaller contributions can be added into the "contributions delivered" column with just the link field filled in and a total specified below (see example in compensation request template).
- the "contributions in progress" section is ignored by the parser.

If this format is ok, I think it would make sense to proceed with testing...perhaps provision an API key to let @jmacxx test the bots with real requests. Maybe team leads could make their requests using the new format 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-629230268
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200515/3a6cc33e/attachment.html>