On 10/28/2010 07:00 PM, Ingrid Halama wrote:
> I look at the votes of the issues. Looking at them is a possibility. However, the history of Issuezilla clearly demonstrates that votes have zero impact and zero influence in what Sun allowed to be added to OOo. Voting was clearly a sham, a means of creating the delusion that Sun was allowing the community to state their preferences. > convincing and voting is the method to influence where the program goes. Which explains why the issue with the most votes was, for years, ignored. (I don't remember if it was that one, or a different issue in the top five, in terms of votes, that was closed with "won't fix".) > Write good bug reports, write good feature request. Give additional arguments to existing bugs or feature requests and vote! An interesting theory, that history proves to be false. >>> Who is now in charge of the code our volunteers contribute? >> If it goes into the OOo cvs system, Oracle. If it goes into the >> LibreOffice, Go-OO, OxygenOffice, etc cvs system, the community. > Again I need to correct jonathon. Code committed to OpenOffice.org is open to be taken and used from all others. go-oo did that in the past What is being ignored here, is that Oracle _OWNS_ the code that is in the OOo cvs system. So much so, that it can, and does legally distribute that code under a closed source, proprietary license. > In contrary go-oo and LibreOffice have choosen a license politics that > make it impossible to take their code and integrate it into > OpenOffice.org. Er no. The issue is that neither Sun nor Oracle grokked FLOSS, and are simply using it as q way to get, or more preceisly, attempt to obtain developers that they (Sun, and then Oracle) do not have to pay. Sun, and subsequently Oracle, deliberately chose a Non-FLOSS license that they require all code to be distributed under. The ones that are playign the policital game, by choosing clsoed soruce licensing is Sun, and Oracle, not Go-OO and LibreOffice. > So if you contribute code to OpenOffice.org it will went into most flavors or forks. Whilst that part is more or less accurate, consider that that is due to non-FLOSS forks that Sun, and subsequently Oracle have licensed the code to. >If you choose to contribute to LibreOffice in contrary the code will only be there. Code contributed to Go-OO or LibreOffice can be used by any project that uses a compatible license. As such, Code in those projects can be used by Oracle, _when_ it decides that it will no longer create a closed source proprietary software, and change their license requirement accordingly. jonathon -- No human will see non-list, non-bulk, non-junk email sent to this address. It all gets forwarded to /dev/null <javascript:void(0);>
signature.asc
Description: OpenPGP digital signature
