Yes, of course!

Tasks must be coding problems to complete in a set of open-source repositories. We have eight repositories now and will add more in the future. You can source tasks by identifying merged commits into these repos, and making the following: - A well-defined task description (what should the AI do?) - A golden solution (can be sourced by the implementation in the merge commit) - A test patch (can be sourced from the merge commit, this is a testing suite that verifies whether the AI's solution is correct).

If you can make a task that is hard enough for our AI, you will get paid a fixed amount. That's it!

Once you are approved onto the site, there will be a more detailed tech spec + payment info + a tutorial.

▲

causal 3 hours ago | parent [-]

So this has to be a meaningful PR for the open source repository? You can't just invent arbitrary coding challenges?

This seems like trying to get free code contributions with a weird sort of gambling mechanic attached.

▲

carterschonwald an hour ago | parent | next [-]

Ive seen more than one flakey startup do this to fluff adoption metrics and perceived activity. It was frustrating

▲

hackmaxim 3 hours ago | parent | prev [-]

Nothing is free, of course, since we transparently pay per task (and as previously stated, the pay is very generous). There are certainly guidelines for what kinds of tasks you can submit to our platform, but beyond that, you can make any verifiable coding task in any of our qualifying open-source repositories.

We also definitely do not require you to write new code into the repo. As I said, you can adapt existing merged commits into coding tasks.

	▲	nl 19 minutes ago \| parent [-]
		How do we know in advance if something it going to be hard enough? For example I have a bunch of closed PRs on my Vibe-Prolog project that took multiple attempts to get right: https://github.com/nlothian/Vibe-Prolog/pulls?q=is%3Apr+is%3... As a specific example: https://github.com/nlothian/Vibe-Prolog/pull/214 which implements https://github.com/nlothian/Vibe-Prolog/issues/204 I'd be very interested if it is eligible!