I'm thinking about open sourcing my project but there are multiple hurdles to this.<p>1. I have aws services including serverless, cognito, dynamodb, amplify on the project as the initial intention was not to open source.<p>2. The open source parts run on container services and kubernetes and the whole server side might be expensive for indie's to run just for the benefits of creating a conflict free schedule on google calendar<p>3. If I open source it, do I have to rewrite all the aws services into open source alternatives?<p>What do you guys think?<p>What are benefits vs risk?<p>I think there will be an increase level of trust if I open source but AWS services adds a whole lot of complexity for anyone to self host.<p>Plus V2 of the project (work in progress) which is a hybrid between clockwise and doodle would also be open source if I open source v1.
Why do you want to open source it?<p>Almost no projects get contributors, if that's what you're looking for.<p>No, don't rewrite to use open source alternatives. Write what you need.<p>I've written open source code which depends on proprietary packages. It's not a problem.<p>Without knowing why you want to open source it, it's hard to be more definite.
If it wasn't designed to be open-source from the outset you could be too late. If it's hard to strip all the AWS mechanics away, then don't do it. All my code is modular anyway, and I open source specific single-duty modules on Github.