Kiwi TCMS is donating € 10000 (ten thousand euro) to our community to enable more hands working together and give an opportunity for people to get exposed to open source contributions. You will help us complete pending tasks faster while learning something new and receive a bonus for your efforts! This blog post outlines the rules of our open source bounty program.
Who is eligible to participate
Everyone who meets the following criteria is eligible to participate:
- Has an account on https://opencollective.com - needed to follow program updates and request payments
- Has a bank account - needed for actual money transfer, more info below!
If you are beginner in Python, Django or some other technology that we use please consider available documentation, your local user group, developers forum and StackOverflow to get help. Do not turn GitHub issues into a "getting started in programming" discussion.
- Program will be split into multiple rounds as we work to clearly define what needs to be done and adjust priorities
- News and updates will be posted at https://opencollective.com/kiwitcms/updates/
- You are expected to mostly work alone on issues
- Technical discussion will be happening via GitHub pull requests and/or GitHub issues under https://github.com/kiwitcms/Kiwi unless indicated otherwise
- Translation related discussion will be happening via Crowdin under https://crowdin.com/project/kiwitcms/discussions when needed
- Do not contact individual team members privately, we are going to ignore such messages
FIFO order for code review
- Contributions will be reviewed and merged in a rolling first-in-first-out order, that is we review 1 PR and while waiting for updates continue on the next in the queue
- In case of collisions, multiple contributions that try to resolve the same problem, our team will review the first one, then the second one, etc. The pull request which is first to pass DoD and code review will be merged and the conflicting ones closed
- Please comment on issues and work together with other community members to split the work and avoid collisions as much as possible
Our team will try to clearly describe each task and what constitutes a successfully completed task, e.g. definition of done (DoD). If this isn't the case please ask questions and seek clarification about such tasks.
- Only Issues under the bounty-program milestone AND labelled with a specific monetary amount are eligible for payout!
- Unlabelled issues need further refinement before they can be accepted for bounties!
Once DoD has been met and the contribution is merged you may claim the assigned bounty. You must perform the following steps:
- Submit an expense to the Kiwi TCMS Collective
- All expenses submitted to the Kiwi TCMS Collective must follow the invoicing rules of our Fiscal Host. Here is an invoice template (Google Doc) you can use. Fill-in the blue parts and leave the black parts
- Invoice & expense description contains the number of issue(s) and PR(s) for which bounty is claimed
Identity cross validation:
Once an expense has been submitted add a comment with your GitHub/Crowdin username to it + open a new issue in GitHub /new discussion in Crowdin with link to the expense submission. This will help us cross-validate that we are talking to the same person between platforms.
Note on bank transfers
A message from our Fiscal Host:
We currently prefer to do payouts using bank transfers. We used to support PayPal but fees were way too high for the collectives.
About bank transfer, we do EU transfers as well as non EU (which takes more time obviously).
We noticed that several collectives are now using Revolut bank accounts which is the easiest and cheapest way (it’s free) to receive money anywhere in the world.
It looks like the fastest & cheapest way to get paid is via Revolut account if you have one, followed by standard bank transfer and PayPal account is last!
Bounties: translation related tasks
- Chinese Simplified - #1459, #1460 #1461, #1462, #1463
- Hindi - #1464, #1465 #1466, #1467, #1468
- Indonesian - #1469, #1470 #1471, #1472, #1473
- Bengali - #1474, #1475 #1476, #1477, #1478
- German - #1505, #1506, #1507, #1508, #1509
- Japanese - #1489, #1490 #1491, #1492, #1493
- Swahili - #1494, #1495 #1497, #1498, #1499
- Vietnamese - #1484, #1485 #1486, #1487, #1488
- Korean - #1479, #1480 #1481, #1482, #1483
Bounties: test automation plugins
- Django test runner reporting plugin - #693
- py.test reporting plugin - #1511
- JUnit plugin: annotation & improvement for test case mapping - #1512
- TestNG plugin - #692
Bounties: assorted technical issues
- pylint - #1192
- Migration from Travis CI to GitHub workflows - #1550, #1551, #1552, #1553, #1554
Call for sponsors
We are also calling upon teams and organizations who use Kiwi TCMS in their testing workflows. Please consider making a one-time donation or becoming a regular sponsor via our Collective. You can contribute as low as € 1! The entire budget will be distributed to the community!
Vote for Kiwi TCMS
Our website has been nominated in the 2020 .eu Web Awards and we've promised to do everything in our power to greet future FOSDEM visitors with an open source billboard advertising at BRU airport. We need your help to do that!
- Go to https://webawards.eurid.eu/?q=kiwitcms.eu;
- Point your mouse to the photo of our website and click the Thumbs Up 👍 button;
- No email or registration required!
Happy bounty hunting!