the submission user flow needs a lot of rethinking. it should be super easy for OSS projects - as simple as connecting your github account and choosing the repo you wish to submit.
Unless you are a large scale company, luckily there isn't much responsibility on your part. Really the danger vectors I identified are more geared to entities with massive resources and also have the power to dictate public discourse.
But as we get more efficient models and hardware, there might be dangers the small scale researcher could let loose. Cant wait!
In all honesty, the first step is to educate yourself on the actual mechanisms behind today's models, and realize they are not super intelligent Gods and selling them like it will only hurt the public and industry. Aim for specially tailored models that have an off switch and do not directly "talk" to critical hardware. Don't copy ai generated code wholesale, since downstream these could be exploited by a hacker. Don't make hacking AIs like thats just asking for pain.
The biggest one is think about the downstream effects your final product could have on both the positive and the negative. Today everyone focuses on the positive while ignoring the possible dooms. Dont be blinded by the possible future, see what could go wrong and plan for it so it doesnt become a problem.
Have you seriously considered this, or is it a joke? I tried my hand at farming a little bit, and it's not easy at all. Lots of hard back breaking work, but also interesting opportunities for automation at scale. The small family farmers and ranchers I knew had incredible work ethics, seemed happy, but had basically no work life balance. It's a whole lifestyle...
