search

ubiquity / ubiquibot

Putting the 'A' in 'DAO'
https://github.com/marketplace/ubiquibot
MIT License
17 stars 60 forks source link

September 2023 Strategic Priorities #751

Open 0x4007 opened 1 year ago

0x4007 commented 1 year ago

Strategic Priorities

Drafting some concerns. I'll tag recommended assignee per initiative.

  1. Reduce dependence on team salaries and more on to our new system. We need to:
    1. Set high incentives across all types (bounties, comment incentives etc) @pavlovcik
      • This will require experimentation but I expect between 4-8x our current rates.
    2. Enhance pull request review velocity @rndquu
      1. Enable pull request review incentives
      2. Develop a design that incentivizes high review accuracy
        • e.g. delayed payout unless no pull request revert for one month
      3. Set up tests so that pull requests are less burdensome to review.
      4. Auto eject bounty hunters when pull request review is too tedious.
  2. Onboard partners https://github.com/ubiquity/business-development/issues/64
    1. We will need to allocate a dedicated support engineer for a good partner experience. @0xcodercrane
gitcoindev commented 10 months ago

My two cents as a bounty hunter. The proposals look great. Would be good for the internal team to do Ubiquity devpool grooming once a quarter. By that I mean to go through all bounties, close the obsolete issues, ask about abandoned PRs and add a comment or label which bounties can be taken only by the internal team.

Maybe ChatGPT could do an initial scan to give an overview about stalled issues. Sometimes bounty hunters write that they will come back to a half-baked solution but they never do and issues keep idling forever.They also re-start work several times without comments, or state that they got sick or their PC main board blown out and they have to wait 4 weeks for delivery but they rarely return and finish.

Also frequently PRs are closed due to inactivity as people move on, but a lot of work was made and it is a pity to loose it. In such cases a comment could be added: development was done in PR XYZ but it was abandoned. Feel free to start from scratch or base on already existing code. Or any other suggestion for the bounty hunter about availability.

Currently out of 120 devpool issues just a part is really available and it is time consuming to find out which ones to pick.

0x4007 commented 10 months ago

@gitcoindev thanks a lot for your feedback. I wish we could get more feedback from contributors so that we can prioritize what we should focus on improving.

add a comment or label which bounties can be taken only by the internal team.

I do have a solution in mind for this, where we can have XP points (a leveling system) and XP gating based on labels (e.g. Priority: High requires 100 XP)