6 ms·
> I found out the process to open source my own work and get it published to the AWS Samples GitHub repo. I went through the open source process for every piece
by gurchik 3y ago
> I found out the process to open source my own work and get it published to the AWS Samples GitHub repo. I went through the open source process for every piece of code I wrote after removing the proprietary customer specific parts.
I'm not a lawyer, so I'm under the belief that in general this is quite difficult. Once you're paid to create project X, it's ethically or legally difficult to simplify it into an X' for another purpose. It will depend on the company and the contracts you signed, right?
- scarface_74 3y agoYes, all AWS contracts in ProServe had a clause that any IP that the ProServe team created belong to both the company and AWS. Of course we had to strip out any proprietary information and then put it through the approval process to get it open sourced. It’s the same at my current company. Anything we create that doesn’t divulge proprietary company information belongs to us and the customer. If you come to AWS’s own Professional Services division , what are you going to do? Say you’re going to another consulting division that’s better? I worked on mostly frameworks around AWS that are reusable across implementations and then put any custom business logic as a layer on top of it.