Hi Ron The GPL FAQ states:
"If the program dynamically links plug-ins, and they make function calls to each other and share data structures, we believe they form a single program, which must be treated as an extension of both the main program and the plug-ins." Of course this has never legally been proven and is stated as the intent of the license. Even if you have managed to write a plugin or component that doesn't use any code from the core and doesn't 'include' any files from the core then you are covered by AGPL. If the Theme didn't require any changes to the Status Net core it is less clear as it is retrieved by the client and not explicitly part of the source. However it's probably unimportant as the CSS is easily accessible to everyone any way. The odd case in my mind is the config file. Config.php is strictly a source file and included within the running code and so it is by the letter of AGPL part of the source. I hope no one ever tries to enforce this. Martin 2009/11/23 Ron Shanks <[email protected]> > All, > > We've planned a launch of new website based on laconica 0.8.0. > We understand that laconica is released under AGPL v3.0 > > We need your help to better understand the license restrictions for > the modified and new code. > > Specifically: > - We've created a new site theme for laconica, which'll be used by our > site. > - We've created a new plugin for laconica, similar to FBconnect, > autoscroll etc. > - We've created an independent piece of software, plugged in to one > of the pages in laconica. This required introduction of a new method > in one of the laconica's php class to put appropriate reference to the > new piece of code. The software accesses laconica database to fetch > information about posted notices and performs some operation on the > same to display the results to the user. > > We need help to understand: > - Do we need to release the source code for the newly created theme? > - Do we need to release the source code for the new plugin? > - Do we need to release the source code fro the new component developed? > > We already plan to release the modified laconica classes, which were > modified to make the framework better suited to site's need. > > Any help in this regard is greatly appreciated... > > Thanks > ~Ron > _______________________________________________ > StatusNet-dev mailing list > [email protected] > http://lists.status.net/mailman/listinfo/statusnet-dev >
_______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
