4.1.2_release_blocker requested: [Issue 126305] WebDAV lock on 4.1.1 does not work
Andrea Pescetti pesce...@apache.org has asked for 4.1.2_release_blocker: Issue 126305: WebDAV lock on 4.1.1 does not work https://bz.apache.org/ooo/show_bug.cgi?id=126305 --- Comment #6 from Andrea Pescetti pesce...@apache.org --- Nominating as blocker for OpenOffice 4.1.2. This is the second patch in a set of three patches that, combined, solve a major interoperability (Sharepoint) bug. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.2_release_blocker requested: [Issue 125194] Cannot work with shared documents on Sharepoint webdav
Andrea Pescetti pesce...@apache.org has asked for 4.1.2_release_blocker: Issue 125194: Cannot work with shared documents on Sharepoint webdav https://bz.apache.org/ooo/show_bug.cgi?id=125194 --- Comment #21 from Andrea Pescetti pesce...@apache.org --- Nominating as blocker for OpenOffice 4.1.2. This is the first patch in a set of three patches that, combined, solve a major interoperability (Sharepoint) bug. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
2015-08-26 Role of the Chair
[BCC to the AOO PMC] From the Chair, It is useful to know some specifics concerning the role of a Project Management Committee (PMC) Chair. This is what I rely on as guidance for carrying out my responsibilities. **PLEASE NOTE** It might appear in the material below that the Chair is in a position to be the (benevolent?) dictator of the PMC and the project. That is not the case. The technical decisions and detailed work fall to the PMC, the committers, and, for Apache OpenOffice, the community of contributors all the way out to end-users who submit bugs, complaints, and requests for assistance in difficulties of successful use. You might say that the Chair has oversight on how well that activity is managed and fits under the umbrella of the Foundation. This is not about technical direction to the extent there is no collision with over-riding ASF policy (e.g., in handling of IP). THE PMC AND HOW IT OPERATES Since the PMC Chair is a member of the PMC, an useful place for that important context is the Project Management Committee Guide at http://www.apache.org/dev/pmc.html. The section on PMC Required Policy is very brief and to the point. An aspect of PMC activity that is questioned from time to time is where the PMC conducts its business. The final section of the required policy establishes *strict, mandatory* limitation on what PMC deliberations are allowed on private mailing lists under Conduct Project Business on Mailing Lists. Everyone on the AOO PMC must understand and respect the PMC Required Policy, including myself. We're fully capable of it, despite what are seen as excessive private discussions in the past. THE CHAIR OF THE PMC For the Chair, the PMC FAQ section provides two additional explanations about what is expected. First, all the way down at Changing the PMC Chair there is an important link to Why are PMC Chairs officers of the corporation, http://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers. Some general duties are described in the earlier PMC FAQ section on What Are the Duties of the PMC Chair and How To Perform Them? Beside required administrative activities, there is this particular guidance: Remember, that, as in any meeting, the chair is a Facilitator and their role within the PMC is to Ensure that everyone has a chance to be heard and to enable meetings to flow smoothly. There is no Concept of 'leader' in the Apache way. This section also links to an additional definition of PMC and Chair at http://www.apache.org/foundation/how-it-works.html#pmc. This is important for understanding the relationship of the Chair to the Board: The chair of the PMC is appointed by the Board and is an officer of the ASF (Vice President). The chair has primary responsibility to the Board, and has the power to establish rules and procedures for the day to day management of the communities for which the PMC is responsible, including the composition of the PMC itself. Finally, there is reference to section 6.3 of the Bylaws of The Foundation. The section is essentially the origin of the description above, in its final statements: Subject to the direction of the Board of Directors, the chairman of each Project Management Committee shall be primarily responsible for project(s) managed by such committee, and he or she shall establish rules and procedures for the day to day management of project(s) for which the committee is responsible. The Board of Directors of the corporation may, by resolution, terminate a Project Management Committee at any time. BEYOND THE DRY STUFF It might seem that this could be very heavy-handed and dry. In practice, the philosophy on establishment of sustainable communities that produce software in the public interest involves very great patience and tolerance for how communities come together and ultimately thrive. The idea is for communities to work out a way of working that achieves the purposes of the project and the over-arching ASF principles on how the public good is served, and being able to sustain the project for as long as that is important. At the ASF, I don't expect to ever see a counterpart of the business-world public hanging and those who call for them need to understand this is not how the ASF operates. Period. These examples, also from the FAQ, may be informative: http://www.mail-archive.com/community@apache.org/msg03961.html http://www.mail-archive.com/community@apache.org/msg04005.html I don't need to write any further on this subject. If there is any question about actions on my part as Chair, please check this and the source documents. If I appear to be unfaithful to this, shout out and let's clean it up. Now to the work at hand. - To unsubscribe, e-mail:
Re: 2015-08-25 When Speaking as the Chair
On Tue, Aug 25, 2015 at 8:56 PM, Tony Stevenson t...@pc-tony.com wrote: On Tue, 25 Aug 2015, at 06:09 PM, Dennis E. Hamilton wrote: [BCC to the AOO PMC] From the Chair, It occurs to me that the role of the Chair of the Apache OpenOffice Project Management Committee is often seriously over-estimated. There is also a level of prestige that may be associated with it that tends to give more weight to what I might say than otherwise. Why? I really do not get how you might come to that conclusion. As there is no prestige, or weight to be added when doing day-to-day activities. It is important for me that others understand that for the most part, the PMC Chair is no different than another member of the PMC, other committers, and the many other contributors in the Apache OpenOffice community. Exactly! This is in direct contradiction of your opening paragraph. I don't want to have my communications to now be taken with more authority than they would were I not the Chair. For anyone who knows how the ASF works they will know that this is not even possible. As you are no more senior, and therefore carry no more authority. So, when I am speaking as the Chair, I will always introduce my emails with From the Chair. That means I am operating in the context of my responsibilities as an Officer of the Foundation. Wow. I find this whole line of thinking extremely disheartening and quite frankly condescending and disingenuous. It borders on the ludicrous. Hi Tony, It is always nice to hear the perspective of enlightened Apache Members, but please do recall that the audience of this list is not exclusively made up of such people. We have experience with statements by chairs (and even non-chairs) being misinterpreted by those outside of the project, including the press. This is our actual experience, not some overly-caution supposition. So its seems reasonable to be a bit more explicit about this, for the benefit of those not as enlightened as yourself. Regards, -Rob In all other cases, there is no distinction. If it is about PMC matters, it must be regarded as only something any PMC member could do or say. Again, how does PMC chair change this? It does not. And in all cases, for weighty matters consensus is sought and you will usually know how that has or has not been achieved in the usual way that [PROPOSAL], [DISCUSS], and [VOTE] mail threads are handled. Thank you for the support that I have been offered and the trust you have placed in me as I undertake this new role. I do hope this PMC can see it's way past all this rigmarole and to a lighterweight, flexible and frankly functional (not combative) future. - Dennis Many thanks, -- Tony - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[MWiki] Account creation
Hi Can I please have an account for editing the Wiki? Particularly for testing and qa, which I researched a lot lately, I could write quite a bit about. Preferred username is damjan. Thank you Damjan Jovanovic - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [MWiki] Account creation
Damjan Jovanovic wrote: Hi Can I please have an account for editing the Wiki? Particularly for testing and qa, which I researched a lot lately, I could write quite a bit about. Preferred username is damjan. Thank you Damjan Jovanovic Damjan; Your account has been created and a temporary password will be mailed to this e-mail account shortly. Regards Keith signature.asc Description: OpenPGP digital signature
