Bug Bounty?

[clevername27]

Some folks expressed interest in a bug bounty system earlier this year. I am again repeating my offer to host this system, and to make the first donation.

That being said, I'm wondering what the most effective configuration would be? I think @Christoph-Hart has a full schedule of fixes, updates and refactoring that would keep him busy for the next ten years. I would also imagine, like most large software projects, there are things that need fixing — but don't make sense to fix because the system encompassing it is going to be refactored/replaced in the future.

Maybe it would make sense for him to request what community test something or such, instead of us reporting issues on own volition? Many things that seem like bugs may not be, so a directed approach might reduce the signal/noise ratio for him.

Thoughts?

EDIT: I'm realising that it may seem I'm implying HISE has lots of bugs.Quite the opposite. In two years, I've never had a compiled HISE plugin fail in a DAW.

[d.healey]

@clevername27 said in Bug Bounty?:

my offer to host this system

How would it work?

[clevername27]

@d-healey Do you mean the hosting, or the programme itself?

[d.healey]

@clevername27 Both. Are you going to be the escrow?

[clevername27]

@d-healey Excellent question. I am offering to provide web infrastructure. My $0.02 is for a third-party escrow model; otherwise, there are liability and tax implications.

[d.healey]

I'd rather go with something like bountysource, I'm sure there will be an alternative out there to it but I haven't looked.

[clevername27]

@d-healey Exactly. I'm referring to a layer between the two, if that's useful.

[d.healey]

@clevername27 What would such a layer provide that isn't provided by the bountysource type site?

[clevername27]

@d-healey I realise this isn't the answer you're looking for — it would depend on what was needed, and if the service provided it.