Integrate labels into rewards.rchain.coop

[ghost]

opened on behalf of @dckc

Benefit to RChain Coop and Community

Guides could easily review budgets on their issues.

Proposed Budget

$300 based on an estimate of 2 story points ($125 ea per #273) plus some training time.

Measure of Completion

• rewards.rchain.coop sync integrates labels
• guides are trained to use them

---

Legal

Task Submitter shall not submit Tasks that will involve RHOC being transacted in any manner that (i) jeopardizes RHOC’s status as a software access token or other relevant and applicable description of the RHOC as an “asset”—not a security— or (2) violates, in any manner, applicable U.S. Securities laws.

[jimscarver]

Aadi and I started making this table for review of labeled issues https://rhobot.glitch.me/
As is the table can be copy pasted into a google sheet for cooperation amoung the reviewers of the label.
Here is the query I use

query:  {
  repository(owner: "rchain", name: "bounties") {
    issues(first: 100, labels: ["Governance"], states: [OPEN], orderBy: {field: UPDATED_AT, direction: DESC}) {
      nodes {
        number
        title
        author {login}
        updatedAt
        labels(first: 10) {
          nodes {
            name
          }
        }
      }
    }
  }
}

[jimscarver]

@dckc We can extend https://rhobot.glitch.me/ to provide information from the mysql bounty database given credentials. Links into the bounty system for voting might also be good. Do you think this is a worthwhile activity or are there other plans?

[dckc]

It's probably worthwhile, especially if it happens before I find time for my idea: I intend to enhance the issue download stuff in rewards.rchain.coop to grab labels.

No credentials are needed to access any of the data in rewards.rchain.coop; it's all public. I think you can GET any data you like in CSV format... maybe JSON or XML too.

[lapin7]

Yeah, that's very powerful. Is all data from August 2017 onwards in the App?

[jimscarver]

@dckc We will want to access the bounty data real time but can use a snapshot for development.
Can you suggest how we might make a link to vote on an issue?
We plan to try setting up a graphql interface to mysql so that very little programming will be required to use it and so that it might be reconfigured to run on rchain easily.

[dckc]

Can you suggest how we might make a link to vote on an issue?

Err... navigate to it and bookmark the URL in your browser as usual. Is there some trick to this that I'm missing?

e.g. all votes on 668 in CSV, a vote related to 668 in HTML, vote exported in XML

Is all data from August 2017 onwards in the App?

Sorting the rewards by date shows that it's not, right? Again, is there a trick to this that I'm missing?

It's not clear to me how much you tried to find the answer yourself before putting the ball in my court. How to Ask Questions The Smart Way is largely common sense, but evidently it bears repeating:

When you ask your question, display the fact that you have [tried various ways to find the answer] first; this will help establish that you're not being a lazy sponge and wasting people's time.

[lapin7]

Here's a Budgets and Bounties spreadsheet to play with.

It has all data from August 2017 to April 2018

It's the base for a nice financial report.

[dckc]

data dump: http://rewards.rchain.coop/db-bak/201804.sql.gz

[dckc]

code to sync labels is committed and deployed:

• https://github.com/dckc/rchain-dbr d3af715

The Right Thing would have been a new issue_label table to relate labels to issues; but I took a short-cut by just adding labels to the issue table.

Still to do: train guides.

[aviationhacker]

Just an update from Jim & myself, we've cloned the open issues table/site we built (https://rchain-bounty.glitch.me), and are now updating it with a GraphQL element and a MySQL element, looking to connect the two to basically add more functions in the future. The original site (https://rhobot.glitch.me) has been left as is, as we understand some people are using it to help them with other tasks.

At this point, if anyone is pretty good with GraphQL and feels like coaching us a little, we could definitely use the help!

[jimscarver]

Anyone who knows some javascript or is willing to learn GraphQL and not too afraid of typing commands should join our collaborative learning work studies Thursday 2pm EST, Mon, Tue, Thu 4pm EST in https://zoom.us/j/6853551826

I expect the rhobot project will fork from this issue once the label review app is complete.

[dckc]

I looked into glitch a little... pretty cool!

I know javascript and GraphQL, but I'm not available at those times. I'm available Saturdays at 9am (#403).

[dckc]

@lapin7 thanks for the suggestion. How does it look?

• 088f643 include labels in reward, budget views

[dckc]

I have talked with several guides about this: @lapin7 , @TrenchFloat , @pmoorman , @jimscarver .

Optimistically, I'm going to say that's a critical mass and they'll train the rest.

[jimscarver]

Prototyping support for the review process is continuing @dckc Is there someplace else to report that oe should this issue be reopened?
We added creation date and column sorting per member request to http://rhobot.glitch.me
Cookies to remember choices, more cross links to rewards and cosmetic improvement are in the pipe.

[dckc]

I wonder how to integrate rhobot.glitch.me into rewards.rchain.coop

But I suppose it's good to keep the discussion here for a bit...

[jimscarver]

The answer is you don't integrate rhobot.glitch.me into rewards.rchain.coop. rhobot is a user driven self-sovereign interface independent of the rewards.rchain.coop interface. It integrates via APIs. We can integrate our own front ends using mysql but it would be nice if APIs for each function were available, preferably with GraphQL

Todaty Allanc, JIm, Gary and Aadi Reordered columns, added ALL to label dropdown
Added get issue by number and css in https://rhobot.glitch.me/

[dckc]

The answer is you don't integrate rhobot.glitch.me into rewards.rchain.coop.

Ok... then since this issue is about rewards.rchain.coop, that work is out of scope of this issue. Let's use #609 to track it.

[dckc]

@jimscarver @aviationhacker given the scope clarification above, your budget votes on this issue look a bit high. Please review.

[aviationhacker]

I've just had a look at my budget for this issue, but I can't see one that I've placed? Was it removed? If so, it saves me changing it :)

[dckc]

I guess I'm confusing you with @entropee .

[pmoorman]

@dckc not sure if this is the right place (but it's better than nothing):

small feature request for the rewards app: Could we add the label "discussion" to the labels that would exclude an issue from the Overdue list?

Discussion issues often don't require a vote. #775 and #831 are examples of that nature (and sit in our marketing overdue list)

[dckc]

good idea

[dckc]

I made the Discussion tweak 2018-09-26 in 121343ca