Pushing the code into the open is the easy part; if the technical cofounder was on board with open sourcing it that would be very easy for them. The hard parts are things like:
Does the code contain anything you don’t have the rights to share?
Does the code contain any passwords, tokens, or other secrets? (It shouldn’t, but this is common.)
Is the code a mess that they’re worried would reflect poorly on them as a developer? (Very likely; I deal with this by just pushing things publicly anyway, but I also have a good enough traditional resume that I’m not reliant on my github resume.)
Pushing the code into the open is the easy part; if the technical cofounder was on board with open sourcing it that would be very easy for them. The hard parts are things like:
Does the code contain anything you don’t have the rights to share?
Does the code contain any passwords, tokens, or other secrets? (It shouldn’t, but this is common.)
Is the code a mess that they’re worried would reflect poorly on them as a developer? (Very likely; I deal with this by just pushing things publicly anyway, but I also have a good enough traditional resume that I’m not reliant on my github resume.)