diff options
author | Michael Meeks <michael.meeks@novell.com> | 2008-04-29 10:13:43 +0000 |
---|---|---|
committer | Michael Meeks <michael.meeks@novell.com> | 2008-04-29 10:13:43 +0000 |
commit | fe0c3e66bff4d84ab168d115530fda04693ff774 (patch) | |
tree | 4a4ff5a2d371b32ae0b22d44898151edf1cdd0c7 /index.php | |
parent | aae29e18e6fa1c69ec288423b3253ca2cef1e85d (diff) |
Update front page: done ? - getting review.
Diffstat (limited to 'index.php')
-rw-r--r-- | index.php | 31 |
1 files changed, 21 insertions, 10 deletions
@@ -52,23 +52,34 @@ $content = <<<EOT <h3>Freer licensing</h3> <p> - For the code to live, grow and improve, and to encourage participation - we - need licensing that encourages: ie. copy-left. Simultaneously it is a travesty - ... IBM - CDDL is ok for them - Sun, abuse of position etc. ... - <a href="http://council.openoffice.org/files/documents/126/4135/OOoAdvisoryBoard_01Nov2007_MeetingNotes_v4.pdf"> - </a> - Sun - patent double talk (?) - Thus our work is wherever possible dual-licensed under LGPLv3 & CDDL. + For the code to live, grow and improve, to encourage participation, and + compete with the other office suite - we need sensible licensing: ie. + weak copy-left. While in general we think LGPLv3 is a great & sufficient + license for our code, <a + href="http://council.openoffice.org/files/documents/126/4135/OOoAdvisoryBoard_01Nov2007_MeetingNotes_v4.pdf"> + others</a> (eg. IBM) prefer the CDDL (a weak copy-left license + akin to Mozilla's). Luckily dual licensing under the LGPLv3 / CDDL solves + this problem - and we recommend this for the majority of our code. + </p> + <p> + We believe that copyright assignment to a single corporate entity opens + the door for substantial abuse of the best-interests of the codebase + and developer community. As such, we prefer either eclectic ownership + (cf. Mozilla, GNOME, KDE, Linux), or an independent, meritocratic foundation + (cf. Eclipse, Apache) to own the rights. Having said that we recognise and + applaud Sun's technical contribution to OpenOffice and recommend + that small patches & fixes to existing Sun code should be assigned to + them under the SCA, and up-streamed. </p> <h3>Freer politics</h3> <p> Go-oo is a developer run meritocracy. If you want to contribute something concrete: code, bug fixes, bug triage, significant translation, build-bot - maintainance etc. then there is a place for you to form a key part of the + maintainance etc. then there is a place for you as a key part of the team. If instead, you want to market Go-oo, install it, talk about it - - that's great too, but this is not our goal: there are no formal roles in - the project for this work. + that's really excellent, but this is not our focus: there are no formal + roles in development to reflect this valuable work. </p> <div> <p><a href="/download/">Download OpenOffice.org</a></p> |