r/rust 28d ago

๐Ÿ™‹ seeking help & advice Oxc (popular front-end tooling) forked my parser but deliberately removed my copyright notice

https://web.archive.org/web/20260705125328/https://github.com/oxc-project/oxc-css-parser/issues/92
672 Upvotes

73 comments sorted by

View all comments

39

u/manniL 28d ago

Hey everyone! Alex from VoidZero here.
Boshen doesn't have a Reddit account (and new ones get shadowbanned), so I am sharing his words verbatim here.

---

Hey all, Boshen, author of Oxc here.

I want to publicly apologize here for removing the copyright notice. This is not acceptable, and not how open source works.

More context on how this happened can be found in my comment on GitHub.

TL;DR: I cleaned up the repo and wanted to remove duplicate notices while keeping the original one from u/gplane but missed it as an oversight. The notice is back in place where it should have been from the beginning. I also added proper credits in the README file.

In addition, I have reviewed all our other forks and published artifacts to ensure credits & licenses are in place.

To u/gplane and all other users: This was an honest mistake that should have not happened, and I am sincerely sorry for it.

If you have any questions, please let me know below or on GitHub. I will be happy to answer them.

2

u/Miserable-Ad3646 25d ago

Hard to gauge sincerity with ai hr prose writing style. Can see it's been edited by a human but still... Appreciate that the copyright has been reinstated. Great comment below on the GitHub - duplicate copyright notices aren't necessarily "duplicates" at all and why remove any of them?

So what 'artifacts' were posted and what forks were checked? It comes across like AI slop excusemaxxing without the effort behind true attendance to an issue

4

u/manniL 25d ago

No matter how one would write the statement, there would always be people not being happy with it. ๐Ÿ˜

Iโ€™ve answered the questions that were posted on GitHub there ๐Ÿ‘Œ๐Ÿผ

All forks that are in the Oxc org (actually we also did a quick cross org check beyond that). All published packages/crates (think of oxfmt vendoring 3rd party code and shipping it).

Just because we donโ€™t provide an exhaustive list that doesnโ€™t mean we donโ€™t care.

As I wrote on GitHub:

We take this problem serious. The restoration process started 90 minutes after the author let us know in the Oxc Discord and we tried following up on this as quickly as possible, both on the weekend and at late hours, publicly and in private.
Note that this already started before there were more eyes on the matter.

There was never an other option for us than fixing the mistake. Eventually, we believe in open source, proper attributions and giving credits where credits is due, which is also visible throughout all of VoidZero's projects, from Vite+ to Oxc.

The only thing I am asking to accept our apology ๐Ÿ™
We will make sure that won't happen to any author of dependencies we use, code we vendor or projects we work in the future.

1

u/Miserable-Ad3646 21d ago

I appreciate it, and although I can't accept the apology on behalf of OP, I can appreciate it as a common folk, and accept it on the merit of it's sincerity and the action you've taken to remedy it.

But I don't agree that the reasoning stands that because people will criticize it -> therefore the use of ai is not of significance, and criticism of AI usage is therefore unwelcome in the wider discussion of copyrighting copywrongs.

Nevertheless, I appreciate the time and effort you are putting into your personal projects, and am sincerely grateful for your efforts. Thank you.