On Thursday, August 25, 2016 at 1:11:04 PM UTC-5, Larry Garfield wrote: > > It's not that FIG needs to own the code per se; strictly speaking there is > no legal entity called FIG, so it cannot own copyright on anything. >
Then you're assigning copyright to an entity that have standing or process for determining who can represent it where and how? Sounds like that's a bigger problem to solve first. > However, bear in mind that under copyright law you own any non-trivial > work you produce immediately upon doing so, and no one else has any legal > right to copy it, much less use it, without your explicit consent (modulo > fair use). > Adding a license - any license - governs the terms of contribution, usage, etc, which the MIT (or BSD or Apache) covers as is. The "entity" only has to own the copyright if there's a need to relicense it or transfer ownership later and you don't want to contact all the contributors. Are you planning to transfer ownership? * I ran a GPL->BSD relicense a few years back after forking a project: http://web2project.net/2011/01/web2project-license-change/ and worked through all the details with extensive legal and technical advise. keith -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/760607af-4fef-427f-afd7-6d17bd1d9e85%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
