So, you still think you want to contribute, eh?

If a prospective technical contributor doesn’t seem to be a very good match, I, Jon, am unlikely to spend a lot of time attempting to integrate that person because I’ve seen many such people who have good intentions who have inadvertently ended up harming Plucky just a little bit each by sucking away my time. While such people have good hearts and want to help, there is a big gap between wanting to help, being able to help, and actually helping.

Because I think my time is best spent actually improving Plucky, I must attempt to weed out well-wishers who aren’t truly dedicated to (and competent to contribute to) the Plucky/Andoff cause.

If the Plucky team were bigger, ironically, it would be easier to take on more people. But being tiny, it’s hard, and I need to wait for a really good prospects.

Having said that, if you feel you are one of those who really would help Plucky in the long haul, I’ll give you a couples challenges to prove it:

  1. Improve https://blockers.xbuilders.org/ . To gain access to the repository, you’ll need to send Jon your ssh public key.

  2. Implement HRS3 schedules in Kotlin.

If you are sure you want to continue, choose one of the above, do it, and then get back to me.

If you are uncertain, please do not insist that you’d be a good contributor because while I might really like you and love to chat with you, I really must get back to Plucky work right this very moment. Trust me when I say that I shan’t be offended in the least if you don’t complete either challenge. They are intended to turn away most people.