3 ms·

What’s the long term strategy for this code base? Does the author expect community code contribution or just bug reports or maybe just test contributions?

• fg137 4mo ago
  In 6 months, seeing no adoption, move the repo to maintenance mode. Archive in 12 months.
• Yokohiii 4mo ago
  He will be probably super happy for starring the project.
• 0x000xca0xfe 4mo ago
  The agents did all the work but _somebody_ has to test it for real on their own data to find the edge cases overlooked by AI. That's what users are for nowadays.
• schacon 4mo ago
  I'm happy to take contributions if you want to throw some tokens at it. Bug reports would be amazing, since I haven't tested it for real very much (enough to know you can do basics). I want to get it to the point where we can replace fork/exec'ing to an unknown Git binary or having said binary be an external dependency for GitButler. The networking stuff (push/fetch) is currently an external dep for both GitButler and Jujutsu (and pretty much every other Git-based tool in the world). I'm pretty sure I can get the project good enough at these networking ops (including all the hairy credential stuff) to be able to not need those fork/exec calls.
  • witx 4mo ago
    I won't touch relicensed code even if you payed me. This is morally, if not legally, wrong.