{"id":1763,"date":"2011-06-03T11:04:35","date_gmt":"2011-06-03T15:04:35","guid":{"rendered":"http:\/\/2d823b65bb.nxcli.io\/?p=1763"},"modified":"2011-06-03T11:04:35","modified_gmt":"2011-06-03T15:04:35","slug":"apache-openoffice-how-to-get-involved","status":"publish","type":"post","link":"https:\/\/www.robweir.com\/blog\/2011\/06\/apache-openoffice-how-to-get-involved.html","title":{"rendered":"Apache OpenOffice: How to Get Involved"},"content":{"rendered":"<p>A follow-up to my previous post on the\u00a0 Apache Incubation proposal to <a href=\"https:\/\/2d823b65bb.nxcli.io\/blog\/2011\/06\/apache-openoffice.html\">move OpenOffice.org over to Apache<\/a> and continue the project there.\u00a0 In that post, I described how Apache projects are run via a meritocracy, that members gain additional rights and responsibilities based on the approval of their peers, etc.\u00a0 But I have received a variety of questions related to this, and I&#8217;ve done my best to track down some answers.\u00a0\u00a0 So here are what I found out, in my words, paraphrasing the questions and giving answers, possibly with my mistakes, but I&#8217;ll correct them as they are identified.<\/p>\n<p>Question:\u00a0 How do I sign up to be a project member?<\/p>\n<p>Answer:\u00a0 For now, since we&#8217;re in the proposal stage, and the project has not officially started, we don&#8217;t have a website, mailing lists,\u00a0 a repository, etc.\u00a0 So there is no direct project work to do yet.\u00a0 However, anyone who wants to &#8220;get in on the ground floor&#8221; with Apache OpenOffice, can sign up by adding their name to the &#8220;<a href=\"http:\/\/wiki.apache.org\/incubator\/OpenOfficeProposal\">Initial Committers&#8221;<\/a> table at the proposal wiki.\u00a0 If you don&#8217;t have a login for the wiki (and you probably don&#8217;t) then you can quickly get one by clicking &#8220;log in&#8221; and then following the instructions to create a new account.\u00a0 If you have interest in this, I&#8217;d encourage you to sign up.\u00a0 Even though we can&#8217;t code yet, we can edit the proposal itself, and there are thin spots there that we could certainly use help filling in.\u00a0 If you want to contribute you should also <a href=\"http:\/\/incubator.apache.org\/guides\/lists.html\">sign up on the incubator general list<\/a>.\u00a0 This is where the proposal is being discussed.<\/p>\n<p>Question: This meritocracy sounds very programmer-oriented. But OpenOffice.org,\u00a0 as an end-user, mass-market application, involves a broader community of contributors, from test to translation to documentation to marketing, etc.\u00a0 Do they fit into this meritocracy at all?\u00a0 Is a marketing person or an event organizer or a build engineer a valued contributor?<\/p>\n<p>Answer:\u00a0 Yes.\u00a0 Absolutely.\u00a0 Each Apache project determines the criteria used to identify those members whose sustained contributions to the project warranted recognition and advancement.\u00a0\u00a0 I think that in the case of an end-user facing application like OpenOffice.org, contributions come in many flavors.\u00a0 It is not limited to coders, or even to those who check in &#8220;assets&#8221; like translations and test scripts.\u00a0 We&#8217;ll need a wide range of contributors with a diverse set of skills to take OpenOffice.org to the next level.<\/p>\n<p>Question:\u00a0 Do I need to sign a copyright assignment to contribute to Apache?\u00a0 I heard a lot of bad things about the paperwork that Sun required from OpenOffice contributors.<\/p>\n<p>Answer:\u00a0 In Sun&#8217;s case it was the JCA by which the copyright of all code contributions was assigned to Sun.\u00a0 Instead Apache has a &#8220;Contributor License Agreement&#8221; which they have in both <a href=\"http:\/\/www.apache.org\/licenses\/icla.txt\">individual<\/a> and <a href=\"http:\/\/www.apache.org\/licenses\/cla-corporate.txt\">corporate<\/a> forms.\u00a0 This agreement does not require copyright assignment to a single entity, not even to Apache.\u00a0 It does not aggregate copyright.\u00a0 But it does require that you agree to license the copyright to Apache as well as to anyone using the software.\u00a0 IANAL, but this sounds like a good thing.\u00a0 If you are comfortable with the Apache 2.0 license, I can&#8217;t see why you would have a problem with the Apache iCLA, since it pretty much restates those same terms.<\/p>\n<p>Question:\u00a0 What kinds of contributors are you looking for?\u00a0 What roles and skills?<\/p>\n<p>Answer: If you look at the range of skills and contributors that went into making OpenOffice.org, you will have a good idea of what is involved:<\/p>\n<ul>\n<li>C++ and Java programmers &#8212; same thing really, any programmer over 40 ;-)<\/li>\n<li>Testers, both manual as well as those able to help with test automation<\/li>\n<li>Translators &#8212; I&#8217;d especially like to see some OOo National Language Projects sign up.<\/li>\n<li>Documentation \/ technical writers<\/li>\n<li>Accessibility<\/li>\n<li>Web admin \/server admin &#8212; We&#8217;re going to take over the OpenOffice.org website, but we&#8217;ll need to migrate to our own server<\/li>\n<li>Build engineer \/ build management<\/li>\n<li>Community development<\/li>\n<li>Event organizing<\/li>\n<li>Marketing \/ brand development<\/li>\n<li>Education \/ training \/ certification<\/li>\n<li>Package and liaise with Linux distros<\/li>\n<\/ul>\n<p>What we don&#8217;t need, at least not at the project level, are things  that are more in the nature of foundation-defined roles, like fundraisers, board of  director members, membership committees, press release authors, etc.\u00a0 In this sense Apache OpenOffice  is different from the OOo under Sun\/oracle or from LibreOffice.\u00a0 We&#8217;re imbedded  in a very capable and well-respected open source foundation.\u00a0 Apache has governance already established.\u00a0 Certainly individuals can get  involved in that if they wish, and more importantly if they have the  support and votes of their peers to advance to that point, but this is  not something we need to reinvent for the project.\u00a0 We can concentrate  on the project work itself.\u00a0 100% of the effort will be on improving OpenOffice.<\/p>\n<p>In particular, I&#8217;d welcome existing contributors from the OpenOffice.org community, including those from Oracle Hamburg (check with\u00a0 HR first, of course), from the Symphony team and from other parts of IBM (send me a note if you have questions), from companies with desktop Linux distributions (you need a strong story for productivity applications to be viable in the enterprise), from those other companies with downstream business based on OpenOffice (consultants, trainers, authors, migration experts), and of course members of the large and vibrant LibreOffice community.<\/p>\n<p>And remember, contributing to an Apache project is not an exclusive thing.\u00a0 You as the author of code, documentation, translations, etc., own the copyright to your original work. You may choose to license your work under\u00a0 Apache 2.0 and contribute it to Apache OpenOffice and then attach a different set of licenses and contribute it to LibreOffice.\u00a0\u00a0\u00a0 This is a good way to get your work out to the maximum number of users.\u00a0 And who knows?\u00a0 You might find out that you like Apache and decide to move your tent over there.\u00a0 That&#8217;s your choice.\u00a0 If you do that, you can contribute just to\u00a0 Apache and then have LO suck down the changes from the Apache project.\u00a0 This is because Apache 2.0 and GPLv3 are compatible in that direction.\u00a0 So you still can impact both projects by contributing code to one place, namely Apache.\u00a0 But it does not work in the other direction.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A follow-up to my previous post on the\u00a0 Apache Incubation proposal to move OpenOffice.org over to Apache and continue the project there.\u00a0 In that post, I described how Apache projects are run via a meritocracy, that members gain additional rights and responsibilities based on the approval of their peers, etc.\u00a0 But I have received a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"categories":[22],"tags":[],"class_list":{"0":"post-1763","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-openoffice","7":"entry"},"_links":{"self":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts\/1763","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/comments?post=1763"}],"version-history":[{"count":3,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts\/1763\/revisions"}],"predecessor-version":[{"id":1767,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts\/1763\/revisions\/1767"}],"wp:attachment":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/media?parent=1763"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/categories?post=1763"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/tags?post=1763"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}