The conversation

Lessons learnedExperience excerpt · English

Hi everyone, this is Daniel from the Pickle team

Hi everyone, this is Daniel from the Pickle team. Glass is a new open source project from us that we plan to build on and improve. We built several original features for it like live summaries, real-time STT Transcript and one-click "Ask" from summary that we're very excited about. However in initially building it we included code from a GPL-licensed project that we incorrectly attributed as Apache. This was incorrect and sloppy work on our end. We made a quick fix and are working right now to do a proper fix that addresses the issues fully and cleanly. We are sorry to the original author of the project, Soham (CheatingDaddy), and thank him for pointing this out. We are also sorry to the open source community for messing up here. Thanks everyone for caring about this.

Original discussionMy open source project was relicensed by a YC company [license updated]506 source comments · at import
8

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 8

Direct replies available in this import. Original-language excerpts.

SE

The correct approach is to license your code as GPL v3 with Soham as the author. It's a simple fix.

Full original
CS

> This was incorrect and sloppy work on our end. We made a quick fix and are working right now to do a proper fix that addresses the issues fully and cleanly. There is no fix. Your work is derived and should be/will be licensed as GPL. You do not want to accidentally succeed and then find you have nothing. You are being a smart-ass here.

Full original
OE

Hiding the entire history of this incident[1] behind a force push[2] to make it seem as if credit was given and proper license was chosen from the start really displays a lack of integrity, and tells me it’s definitely malicious (which should be quite clear from zero mention of the original project to begin with, but this act reinforces that) rather an inadvertent screwup. [1] https://github.com/pickle-com/glass/commits/5c462179acface88... [2] https://github.com/pickle-com/glass/commit/4c51d5133c4987fa1...

Full original
AN

Calling it sloppy work is too charitable. It's one thing for others to give you a benefit of the doubt, it's absolutely crazy that you yourself are doing it. It's clear if the other guy did not speak up, you would not have "corrected" the incorrect attribution. Your entire repo uses the work from someone else, and you did not even credit the person who built it until he called you out for the deception.

Full original
NE

> This was incorrect and sloppy work on our end Cut the grandoise talk. You stole someone's work and now you just shrug it off as "incorrectly attributed as Apache". That's not a mistake, that's a deliberate action plan. The force push others have mentioned is the proof. Atleast be honest in your apology. I hope YC takes serious action and eliminates you guys from their cohort if you're still in one. This reflects very poorly on them otherwise.

Full original
SA

If you had any semblance of respect for the work of others and what is right you would sincerely apologize and shut the project down instead of rolling with it.

Full original
CR

Hard to say that your work isn't derived from a GPL project if you quite openly are reimplementing a GPL project you used at the core of your own project.

Full original
EQ

> This was incorrect and sloppy work […] You meant: this was illegal and unethical work. You might be lucky with the original author not suing you. I'm not sure your backers will be equally kind. I certainly wouldn't, depending on what exactly you told your investors we may be looking at straight up securities fraud here.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.