Closed dwwmmn closed 4 months ago
Hi @taconi , unfortunately now I work for an employer who restricts contributions to open source. I have to get approval before making even simple contributions to open-source projects because they need to be checked by legal for "company intellectual property". The policy is dumb and nobody here likes it, but I would like to keep my job.
Were this for a more important change such as a bug fix, I would go through the process of filing the paperwork and meeting with one of our lawyers but as it's a simple theme, out-of-date, anyone can download it, it's been nearly six years and nobody seems to have missed it, etc. I don't see a reason to do that.
I'll publicly archive the repository instead of deleting; if someone else would like to fork and make the required changes I wouldn't be opposed.
Hello, could you update the PR to resolve the conflicts?
Another issue is that your
repo.json
does not have theWebsite
andLicense
fields, could you add this metadata?Could you add your
repo.json
to theplugins/
folder and update channel.json link to use this link? E.g.https://raw.githubusercontent.com/micro-editor/plugin-channel/master/plugins/editorconfig-micro.json
. Use the plugin name as the file name.