|Re: [eclipse.org-committers] How to deal with stackoverflow contributions|
> Stackoverflow has a license > https://stackoverflow.blog/2009/06/25/attribution-required/ This covers their back, but not ours. Imagine a junior dev taking some company code and pasting it to StackOverflow without being aware of this implicit license grant! Since he doens't own the rights himself he also cannot grant anything to SO. So better be careful. Otoh if the source is so trivial that it doesn't even create originary IP (threshold of originarity), then there is no IP on the code at all and you are free to use it. There is a big grey area between those ends. LieGrue, strub > Am 07.06.2018 um 19:38 schrieb Christian Pontesegger <christian.pontesegger@xxxxxx>: > > Hi, > > I would like to ask how we should deal @ eclipse with code saples taken from stackoverflow. Nowaday it is quite common to find code snippets on stackoverflow and reuse them for own implementations. While this might be common practice, I would like to know how such contributions should be dealt with. > > Stackoverflow has a license > https://stackoverflow.blog/2009/06/25/attribution-required/ > > that at least requires attribution. Say we would re-use a code snippet like this one: > https://stackoverflow.com/questions/30031748/how-to-get-image-from-plugin-internal-resources?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa > > What would be the correct way to use it within a commit? Attribution in the source code next to the snippet? Would we need to file a CQ? > > > thanks for your answers > Christian > > _______________________________________________ > eclipse.org-committers mailing list > eclipse.org-committers@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/eclipse.org-committers > > IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
Description: Message signed with OpenPGP
Back to the top