Considering how cumbersome it is to establish a contract with ICANN, I see the only solution as pre-paying a contractor to look for and fix a set number of issues from target repositories. While it is unorthodox, it is what is possible within the constraints we have to work with. Regards, -- Mark W. Datysgeld from Governance Primer [www.markwd.website] In partnership with AR-TARC and the Brazilian Association of Software Companies (ABES) On August 9, 2019 10:02:24 PM GMT-03:00, John Levine <john.levine@standcore.com> wrote:
In article <B71902F5-E139-40C5-BC8D-9DAA6507FCA9@techobscura.com> you write:
Hi Mark
3. Offer developers a small amount of money, say $500 to motivate them to change their code. If we spent $1m on that I would regard it as a good investment. Marksv>>> We don't know how to do this in the ICANN system due to contractual complexity.
That was raised and the alternatives I suggested were 1) to pay someone to submit patches to as many projects as possible along with any reasonable ‘patch processing fee’ or 2) pay someone to run a compliance bounty programme. Both of those are things we can contract out.
I proposed a bounty program and ICANN said no.
See https://eaibounty.standcore.com/
R's, John
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.