You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
|---|
|
From: Anastasios H. <ah...@gm...> - 2004-12-14 13:26:42
|
PostgreSQL 8.0 which will come with native Windows support - along other improvements - is expected to be released either Dec 20th or Jan 5th. January is more likely due to christmas. Anastasios |
|
From: Anastasios H. <ah...@gm...> - 2004-12-13 10:24:16
|
FSF Europe replied to my mail on Friday. Summarized: The FLA meets our legal needs. Please read this posting for detailed information and suggestions on how to address the legal issues. Some decisions are needed in order to proceed. > -----Forwarded Message----- > > From: Anastasios Hatzis <ah...@gm...> > > To: fl...@fs... > > Subject: FLA for two OSS projects > > Date: Fri, 10 Dec 2004 08:56:29 +0100 > > > > > > A) PROJECTS LICENSING [...] > > B) LEGAL CONSIDERATIONS > > In particular I mean following: > > > > 1) We don't accept stolen code or other infringement of copyright, > > authorship right - neither a contributor should steal from a 3rd-party > > (e.g. from his employer or a commercial product) to commit it to our > > projects, nor a 3rd-party developer should steal code/documentation from > > our projects non-compliant to our licenses. This would require an > > agreement of all contributors that they don't infringe 3rd-party rights > > by contributing to our projects. > > a) I don't think that this would protect us from charges on court, but > > AFAIK it's the only practical thing we can do. > > b) We don't have the resources to enforce the licenses of our projects > > against license violations by 3rd-parties. And we don't have a legal > > entity entitled to proceed such an approach. This issue is less > > important than 1a) and the license assignment below, but it would be > > nice to have an option here. > > The FLA particularly has provisions to address the issues above. The FLA would allow the FSFE to enforce the license and work together with others, for example, FSF US or FSF India. Nevertheless, this could require presence of project admins at court. > > 2) I want all contributors to assign copyright and whatever is needed to > > us or some legal entity to publish their contributions under LGPL or > > FDL. This should protect our projects and users of our free software if > > a contributor changes his mind and thinks we were not allowed to publish > > their contributions under LGPL/FDL. > > a) This assignment should be done with probative force, maybe therefor > > it is required in form of undersigned hard-copies. This should work for us: Critical parts that are FreeGee-specific and distributed with FreeGee packages, e.g. codes, basic documentation, require contributors to sign hard-copy of the FLA. Only these contributions can be accepted and will be published as part of FreeGee under LGPL. Exceptions are the 3rd-party modules, for example, Python, PostgreSQL, Apache, including their codes and documentation. Contributions to 3rd-party modules are done in the original projects, where other licenses and processes may apply. In case of the FLA the contributer needs to print out two copies of the FLA. He downloads prepaired templates where product description in §3 is already filled out, completes them, signs them and mails them to the FSFE. The FSFE will send back one of the copies after it was signed by FSFE. One of our admins will be informed of any successful process. The admin will create user accounts (e.g. for SVN), grants rights for the authorized contributor to commit code or documents. Which of his contributions are accepted is then decided on individual base, e.g. code quality. If the FLA process fails the admin have to deny, respective remove, *all* contributions of this contributor. These regulations may effect requirements to the tools we use, like SVN repository. Additionally to the FLA also this suggestions has been made: > If you want to protect yourselves further, you might want to publish > the policy that people do not work on code where they have seen the > code of a proprietary counterpart and make accepting contributions > depending on acceping that policy. > > If the policy is stated publicly and people acknowledge it either by > publicly readable or signed email, that ought to be good enough to > show in any future court case that you made people aware of potential > problems and tried to avoid them. > What do you think about the policy? Non-critical parts that are not distributed with FreeGee packages, e.g. Website content, doesn't require FLA signing. Depending on the contribution the contributor just attach the GFDL to his document or accepts implicitely Website's terms of use which should state GFDL application. Examples given: writing a support enquiry or bug issues in the tracker database, posting in mailing lists, editing a Web page article, or uploading images to the Web site. In addition, the Website's terms of use should link to SF.net's terms of use. GNU Lesser Public License (LGPL): http://www.gnu.org/licenses/lgpl.html GNU Free Documentation License (GDFL): http://www.gnu.org/licenses/fdl.html > > b) The ability to re-license the project under other licences according > > to the idea of free software (maybe any OSI approved OSS license?), to > > meet future technical or legal changes. > > c) I think the (re-)license agreements would require a single entity > > which could be copyright holder and re-licenser of our projects. Markus > > and me doesn't have a company or something that could serve as legal > > entity for (re-)license assignments granted by us and future > > contributors. Each contributor regains the right to grant other licenses for his individually contributed parts, even proprietary. This does *not* apply for parts contributed by other project volunteers. Re-licensing of the whole project would have to be done by FSFE, legally. Should that need arise re-licensing would become a decision of FSFE. In practice the FSFE would essentially leave us the choice, although the may discuss with us if they feel that a certain choice would be better. The FSFE also suggested that we can use their FLA but instead of FSFE as right holder with another organisation als legal entity. I don't see the need for another organisation due to the reputaiton and history of the FSFE. > > > > > > C) FLA AND FURTHER PROCEEDING [...] > > a) Would the initial and future contributors of our projects sign one > > FLA for FreeGee and one for GenEA? yes, but: As far as I understood at huge contributions for years by a contributor it can be useful to repeat this FLA signing later. But I will ask if I understood this right. > > b) Would this allow the appropriate project - FreeGee or GenEA - to > > publish the undersigner's contributions under LGPL/FDL and, if needed in > > future, under other licenses? yes, re-licensing by FSFE, see earlier. > > c) Would the FLA have a default description in §3 for FreeGee in one > > template and a GenEA description in an other template? yes, see earlier > > d) Would the copyright statement say something like: "(C) Free Software > > Foundation Europe. ...."? yes. 'Copyright (C) Free Software Foundation.' Alternatively: 'for USA: Copyright FSFE, for Europe: Exlusive Exploitation Rights FSFE'. But I think the simple copyright notice above is preferred since people are used to. > > e) How would we process the hard-copies, in particular: How will an > > admin of our projects know, who signed the FLA and is allowed to > > contribute to the appropriate project (since the undersigned FLA seems > > to be send to FSF-Europe? yes, see earlier Now, decisions are needed: My picture on these legal stuff is getting much clearer. Do you think the approaches described here are okay and we can continue with the a) FLA as copyright assignment regulation? b) FSFE as legal entity for holding copyrights? c) LGPL for critical parts distributed d) GFDL for all other parts? Anastasios |
|
From: Anastasios H. <ah...@gm...> - 2004-12-10 08:19:34
|
FYI, today I send this email to the Free Software Foundation Europe. You will find in detail the considerations on legal issues. -----Forwarded Message----- > From: Anastasios Hatzis <ah...@gm...> > To: fl...@fs... > Subject: FLA for two OSS projects > Date: Fri, 10 Dec 2004 08:56:29 +0100 > > Dear FSF Europe, > > I'm co-admin of two projects FreeGee (already free software: > http://freegee.sf.net) and GenEA (will become free: > http://genea.sf.net). I would like to know, if the Fiduciary License > Agreement (FLA) of the Free Software Foundation Europe is a possible > solution for our needs. > > First, I want to describe briefly the license situation of the two > projects. Second, I try to state our legal considerations. > Third and last, I kindly ask you if the FLA meets our needs and if you > have any advice for us how to proceed. > > A) PROJECTS LICENSING > FreeGee consists of several existing 3rd-party OSS modules, for example, > Python, PostgreSQL, and others (incl. some documentation) that are > published under LGPL, GPL, and other free OSS licenses. Our own > FreeGee-specific code for installation, integration, configuration etc. > - all written by Markus Hillebrand - is already published under LGPL. > The GenEA project which is based exclusively on code written by Markus > Hillebrand will be published solely under LGPL. The FreeGee-specific > documentation and the entire GenEA documentation has been written by me > and also Markus and are planned to be published under LGPL. Some parts > like Web site texts, figures and other stuff not included in products > will be published under Free Documentation License. > > In the next step we want to establish a stable and open development > process. But we have the strong feeling that we have to solve some legal > issues before doing this, to protect us, our future contributors, and > our users of getting severe problems in future. > > B) LEGAL CONSIDERATIONS > In particular I mean following: > > 1) We don't accept stolen code or other infringement of copyright, > authorship right - neither a contributor should steal from a 3rd-party > (e.g. from his employer or a commercial product) to commit it to our > projects, nor a 3rd-party developer should steal code/documentation from > our projects non-compliant to our licenses. This would require an > agreement of all contributors that they don't infringe 3rd-party rights > by contributing to our projects. > a) I don't think that this would protect us from charges on court, but > AFAIK it's the only practical thing we can do. > b) We don't have the resources to enforce the licenses of our projects > against license violations by 3rd-parties. And we don't have a legal > entity entitled to proceed such an approach. This issue is less > important than 1a) and the license assignment below, but it would be > nice to have an option here. > > 2) I want all contributors to assign copyright and whatever is needed to > us or some legal entity to publish their contributions under LGPL or > FDL. This should protect our projects and users of our free software if > a contributor changes his mind and thinks we were not allowed to publish > their contributions under LGPL/FDL. > a) This assignment should be done with probative force, maybe therefor > it is required in form of undersigned hard-copies. > b) The ability to re-license the project under other licences according > to the idea of free software (maybe any OSI approved OSS license?), to > meet future technical or legal changes. > c) I think the (re-)license agreements would require a single entity > which could be copyright holder and re-licenser of our projects. Markus > and me doesn't have a company or something that could serve as legal > entity for (re-)license assignments granted by us and future > contributors. > > > C) FLA AND FURTHER PROCEEDING > > During my research to find a solution for our legal considerations I > found several solutions. I think the Joint Copyright Assignment (JCA) of > the OpenOffice.org project is not that bad. But it would require a legal > entity, while we don't have one. Finally I found at ifrOSS a link to an > article about the European FLA. I think the FLA could be a good > solution, but maybe I didn't understand the FLA correctly. > > a) Would the initial and future contributors of our projects sign one > FLA for FreeGee and one for GenEA? > b) Would this allow the appropriate project - FreeGee or GenEA - to > publish the undersigner's contributions under LGPL/FDL and, if needed in > future, under other licenses? > c) Would the FLA have a default description in §3 for FreeGee in one > template and a GenEA description in an other template? > d) Would the copyright statement say something like: "(C) Free Software > Foundation Europe. ...."? > e) How would we process the hard-copies, in particular: How will an > admin of our projects know, who signed the FLA and is allowed to > contribute to the appropriate project (since the undersigned FLA seems > to be send to FSF-Europe? > > > Well, hopefully I didn't overwhelm you with all these information and > questions. We would be glad to hear from you. If you have any questions, > please contact me by email: ah...@gm... or I can call you back. My > phone number is: +49-30-20005020 (or inside Germany 030-20005020). > > Many thanks and best regards, > Anastasios |
|
From: Anastasios H. <ah...@gm...> - 2004-12-10 08:18:35
|
I made some further research and considerations on our legal issues. I tried to figure out how other projects are coping with these issues. Here the most important results and examples: PostgreSQL: I talked to Josh Berkus. PostgreSQL has 16 years of code in the project, so due to historical reasons the PostgreSQL Development Group didn't introduce some kind of copyright assignment and plans to do this now were not appreciated by some developers contributing for many years. Additionally, since they use a BSD-like license it's not much comparible with our projects. OpenOffice.org: I also had a look to the OOo project. They had a Copyright Assignment that have been signed by contributors to assign all copyrights exclusively to Sun Microsystems, Inc. Later they replaced this agreement by the Joint Copyright Assignment (JCA) where assignment is non-exclusively, so contributor can still use its contribution in other projects. It seems that they revised it with Droit d'Auteur (authorship right, common in France, Germany and other continental EU-members) in mind, but in the JCA I couldn't find explicit references to authorship right. As we lack of a legal entity where the rights can be assigned to, this is nice solution for a company or foundation, but not helpful for us. Free Software Foundation Europe: Fiduciary Licence Agreement (FLA) I found an article on ifrOSS about the FLA of the FSF Europe. It is an agreement where a contributor assigns its copyrights to the FSF Europe, likely the FLA of FSF North-America, but also compliant to authorship right in continental Europe. I don't know if this solution meets our needs, but I send an email to FSF Europe with the neccessary information and questions (copy will follow seperated). I will send you an update later if they replied to it. Links: Here the links to some interesting resources mentioned earlier in this posting: An article in German on ifrOSS about FSF Europe's FLA: http://www.ifross.de/ifross_html/art33.pdf Free Software Foundation Europe: Fiduciary Licence Agreement (FLA) http://www.fsfeurope.org/projects/fla/ FLA http://www.fsfeurope.org/projects/fla/FLA-1.0.de.pdf FLA (in German) http://www.fsfeurope.org/projects/fla/FLA-1.0.de.pdf Licensing FAQ (OOo): http://www.openoffice.org/FAQs/faq-licensing.html Example list of copyright-approved persons and companies (OOo) - different from a CREDITS list: http://www.openoffice.org/copyright/copyrightapproved.html JCA (OpenOffice.org / SUN) http://www.openoffice.org/licenses/jca.pdf Anastasios |
|
From: Anastasios H. <ah...@gm...> - 2004-12-09 19:29:36
|
As announced on FreeGee-general list, I want to discuss some technical and administrative issues about contributions to the FreeGee application framework. Maybe you already noticed that the last official FreeGee releases (Beta-1) where we published sources and binaries are a bit old - with some patches published later. To be honest: In the last months some buddies and me worked internally with more recent FreeGee releases (RC-1 and RC-2) which have not been published due to several reasons: First, we ever wanted FreeGee to be available on every important OS, also on Windows (whatever someone may think about it, but FreeGee should be a solution to help people *upgrading* from Windows to Linux or other OS). Beside some other issues a FreeGee Professional for Windows requires the native Windows support of PostgreSQL available with v. 8.0 which hasn't been released yet. Before this we didn't want to release a productive version of FreeGee. Second, we wanted to have more practical (in-project) experiences with FreeGee instead of going further on with all the publicity and support cases likely in this phase. Since February we used FreeGee in several projects and improved some issues (also documentation). I think this was important since - according to users feedbacks - Beta-1 naturally left too many questions open. This doesn't mean that next release will be perfect, but it will show better what FreeGee does and how users will benefit. Third and last, we had serious lack of time (also because of the projects). We decided to invest our few resources better in doing our homework and make improvements, correcting the causes instead of the effects (support troubles etc.). Well, you are right: this is where open-source development can help. But several reasons prevented us from establishing contribution process, in particular the CVS on SourceForge.net and the efforts required to establish a stable development process, like contribution guidelines etc. As in all our work, we wanted to give the project a good base and direction before trying to expand number of users and contributors. We have now more time again (and ideas) to prepair the codes, guidelines etc. for contributions. By using the term 'contribution' I don't mean exlusively code contributions, bug-fixing, portings etc., I also mean documentation, Web content, press releases and so on. Since FreeGee is an application framework on the one hand it contains '3rd-party' modules like Python, PostgreSQL, Apache etc. and parts of their documentation. On the other hand it consists of installation, configuration scripts, adaptors, documentation etc. that are provided by ourselves to realize a convenient, easy-to-use integration of the mentioned modules. The term 'contribution' covers our own parts, not 3rd-party artefacts - contributions to them are not subject of this posting. Given this we need some tools and rules to establish a stable contribution process. I suggest the following goals: A) Value for Users: The application framework should win at aspects of quality, usability, platform availability, shorter release cycles, public awareness and -most important- user acceptance B) Motivation: Contributors should be motivated to contribute; mentioning all authors in appropriate places (I don't know if we should accept SF.net donations in future and how to handle them; however, I think donations are neither the best nor the only motivation in OSS development) C) Collaboration: Collaboration of contributors should be easy and organized (well, currently it should be even possible) D) Legal Stuff: Legal aspects should be addressed, in particular that we don't accept stolen code (or other infringement of copyright, authorship right), neither by our contributors nor by others which infringe our license and the rights of our contributors; defining which license to use now for FreeGee-specific code and documentation (I suggest GNU LGPL) Comments, suggestions welcome. Anastasios |
|
From: Anastasios H. <ah...@gm...> - 2004-12-07 12:38:51
|
no text |