- I'm a UX Developer.
- Employed for a year and a half at my current position.
- I didn't sign any sort of contact/non-compete when I started my employment.
- My employer said I could include any projects in my portfolio when I leave as long as I'm open and honest about what my role was in the project.
- My employer said they don't care if I work on projects/moonlight during my free time.
- The projects in question started as personal open source projects that I developed during my weekends/free time.
- The company did not ask or require me to start or maintain the open source projects.
- All projects are/have always been licensed under the MIT License
During my employment, I've been building a front-end framework and a few simple npm packages to be used asa boilerplate for my personal projects along with work projects since the company didn't have a boilerplate/framework until they adopted mine. I've been developing these projects in my free time as open source projects and I've been hosting the repositories on my GitHub account. My employer has noticed the framework and wants to implement it as our companies official boilerplate. They've asked me to move the development of the framework and packages to the companies organizational GitHub account. I've moved the projects and I have been using the new repositories but I'm curious as to how it looks from an outside perspective.
- Is it unprofessional or inappropriate to maintain open source projects linked to a company after I leave the company?
- Do I maintain private versions of my projects on my account (the original repositories) so I can continue development on the off-chance that I leave my current employer?
- For future employment/project opportunities is it better to contribute and manage several open source projects associated with a current/previous employer or is it better to have a list of open source projects linked directly to my account?