[RFC | Poll] **Issue Backlog Challenge**

Collective
1

Poll Issue Backlog Challenge

Our repository currently has 91 unresolved issues, creating a significant maintenance burden. These issues fall into several categories: potentially outdated tickets, straightforward bug fixes, feature requests, and items that may not be actionable.

To address this backlog efficiently while managing limited maintainer resources, I propose implementing a community bounty program with the following parameters:

  • Duration: 3 months
  • Incentive: $20 gift card per resolved issue (More like a range from 10 to 100$ seems appropriate in most cases)
  • Goal: Reduce backlog and engage community contributors
Using some of the open collective money of pyRevit labs to make a bounty program to solve issues and feature requests?
  • Hell yeah!
  • Noooo!
0 voters

Feel free to comment, argue, discuss below.
Poll ends in two weeks.

2 Likes
3

Fantastic idea for putting funds to good use. Will issues be triaged & flagged as “eligible for bounty” - or how will that eligibility be established. Would like to make sure theres no bad-faith actors trying to create & resolve a bunch of new (or existing) “low hanging fruit” issues just for the sake of getting the bounty.

1 Like
4

That’s a good point.
I will take some inspiration from ifc.js, and the ways they handled issues at first. Pretty lean, it could look like this:

  • labels to flag issues bounty friendly by GitHub main contributors
  • @mention in the comments to engage into the resolution (1 person on 1 issue at time)
  • validation by admins
  • @mention when resolved
  • validation by admins and payment at the end of the 3 months period
1 Like
5

I’d love to help, However, my knowledge doesn’t go beyond python and Revit API. I’ll find the ones that are possible for me to handle.

2 Likes
6

$20 is ok for small issues, but I think for anything more significant, the bounty should be $50 or $100, since it will probably take a skilled person a few hours to solve.

I would also love to help, but last time I looked at the issues, there were none that I could understand and solve. I understand how to automate things using the Revit API, but the inner workings of pyRevit are still a mystery to me, so there’s not much I can do currently.

1 Like
7

100% agree.
The not so fun part will be to put a price tag on issues :grin:

10

I’d like to help. But my technical knowledge is currently limited to Python.
I think the issues should be cleaned up first, because some of them have already been resolved through merged PRs but are still open, others have more info requested since long time ago :slight_smile:

11

@Mohamed.Asli if you are comfortable helping to clean up, I will add you as a maintainer role so that you can edit issues more broadly

1 Like
12

Do you want me to add you as a maintainer on the repo so that you can edit issues and close them as well @tayOthman

13

Hello @Jean-Marc ,

Sure, please add me and be patient with me :wink: hopefully I won’t screw up things.

14

I tell myself that many times during the week. This week, I tackled a change on the installer, never touched it before. And I am still hoping there is no side effects to what I’ve been doing.

1 Like
15

so far so good! We fix things by breaking things, so we get more issues reported. we call it infinite loop.

2 Likes