[native-lang] Re: [project leads] Re: [native-lang] Change in Lead
On 10/18/2010 11:37 AM, Charles-H. Schulz wrote: Please define why my new role would confuse the OpenOffice.org community. maybe http://www.openoffice.org/servlets/ReadMsg?list=releasesmsgNo=16165 helps understanding, Martin - To unsubscribe, e-mail: dev-unsubscr...@native-lang.openoffice.org For additional commands, e-mail: dev-h...@native-lang.openoffice.org
[native-lang] Re: [project leads] Re: [native-lang] Re: [project leads] Re: [native-lang] Re: [project leads] Re: [native-lang] Change in Lead
On 10/18/2010 06:50 PM, Christian Lippka wrote: Hi Charles, Am 18.10.2010 17:28, schrieb Charles-H. Schulz: Le Mon, 18 Oct 2010 16:10:44 +0200, Pavel Janíkpa...@janik.cz a écrit : On 18.10.2010, at 15:56, Charles-H. Schulz wrote: Martin: the community is leaving. No no. Charles and co left (or leaving, slowly so the damage to the OOo and the project is bigger...). That's correct. Nothing else. Community didn't left. Community of OpenOffice.org is still here. No No No. The community (most of the NLC, not you Pavel, most of the QA community, probably most of the Marketing volunteers, the independent developers and non Oracle developers (not you Pavel) are moving to the Document Foundation. But I accept the term Charles and co, it's somewhat reducing though :-) Sorry, but this gets confusing. You are saying you are leaving, but you say you also stay. You say you are most of the community (except Oracle and Pavel obviously) but at the same time you leave 'the community' no choice because where should they go if they do not want to leave with you? Since if they just stay here they are at the same position that you are leaving to. Maybe I'm not educated enough in graph theories but I'm not sure where you are, where you want to stay and how you can leave without moving. Is it that you leave but stay at the same place and expect Oracle and Pavel to drift away? Maybe there are drugs that can help me solve this mystery no, it's not worth the effort, just put him into ignore mode since he is only trying to provoke us, to be able to tell the story that we are the bad guys throwing him out the council. Instead of following these fruitless threads we should concentrate on the work we have to do, to address the issues and concerns our community has, the work and feedback we get is indeed invaluable and we would be insane if we would not continue to work on this. But I also have respect of those who decided to go their own way and open alternatives. And most of community people are in the comfortable situation to continue to contribute to both projects for a long time before they might be in the need to decide for one of the branches and let the facts decide. But I expect from the leader of the LO efforts not to play kindergarten but to really lead their fork, otherwise they might end in confinement on a lonely island. Anyway let me formulate a question, where should the part of the pre foundation fork community go that do not like to identify with the foundation? I'm not talking about Oracle people here we will do just fine, I'm talking about Pavel and others. Is it fair from your side to rob them the name 'OpenOffice.org community' ? Why are you not wearing your colors, walk and march under the libre flag, show it proud (as you do on press releases and events). +1 Regards, Christian Martin - To unsubscribe, e-mail: project_leads-unsubscr...@openoffice.org For additional commands, e-mail: project_leads-h...@openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@native-lang.openoffice.org For additional commands, e-mail: dev-h...@native-lang.openoffice.org
[native-lang] Quarterly review meetings for identifying important issues and enhancements
Hi, in the past there were several complaints raised that some defects and also requirements got not the right priority. In fact we've got a long list of RFE in IssueTracker (either assigned to requirements or bh) and it is not obvious if there is ongoing work on these issues or not. Also it is often not that transparent how decision making on spending resources to that issues is made. The OpenOffice.org project leads agreed to support the proposal http://wiki.services.openoffice.org/wiki/Quarterly_Review to introduce quarterly review meetings to identify the most important issues and request for enhancements. please use the [EMAIL PROTECTED] mailing list for feedback and watch that list for announcements for the schedule of the various review meetings, Martin Proposal: Quarterly reviews Quarterly review meetings should identify the most important issues and enhancements and establish a plan for their resolution. The outcome or agenda of those meetings may look like this: 1. Status of the project 1. what are the most severe issues in the current release 2. which are the most requested (or needed) features (in the press, user forums, issues, other feedback) 2. short term planning 1. which defect needs to go into the next release 2. which features will be worked on for the half year. 3. which issues needs an assignment 3. mid/long term planning 1. which features/bugfixes needs to be addressed in the next two/three years 2. unassigned feature/bugixes The outcome of these items should be a prioritized list of issues, in case of not being able to assign the resources the escalation path should be look like this: 1. Project Lead of the project 2. [EMAIL PROTECTED] 3. Engineering Steering Committee (ESC) 4. Community Council (CC) To come to a balanced assessment of issues there should be a least in those meetings: - the project lead - a qa lead - if available one representative from user experience - if available one representative for user base (user forum or user mailing list maintainer and/or a marketing rep) - if available representative from marketing project - if available: more developer and qa folks pr any other contributing members of the OpenOffice.org project I suggest to start with our main, visible projects like Writer, Calc, Impress and Base and see later if we need to involve also other projects in this effort. I would like to encourage these teams to organize those meetings within the first two weeks of the each quarter (next slot would be April 1-14th) Implementation of Review It is almost impossible to get a slot defined where all parties together at a time for an irc meeting. To involve as much poeple as possible there might be an offline phase before an online meeting: * call for important issues on the project mailing list dev@project.openoffice.org and put them into the wiki * irc meeting to check if all important issues are raised and sort out the unimportant ones * call for review the list and suggest a priorization of issues on the mailing list and put the result into the wiki * irc meeting to confirm the priorization * send out the result to [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[native-lang] Language Packs
Hi, recently I got several questions like where do I get the Language Pack foo for platform bar. Since I know that there are some releases of some local communities of the language packs, there was no comprehensive list on where to download language pack for testing (or just trying) purposes. That why I created http://wiki.services.openoffice.org/wiki/Download_OpenOffice.org_LanguagePacks to provide such a list. I find the list of 65 language packs quite impressive and also think that this list might also be used for marketing purposes. So now I'm thinking of: * also linking to the download pages of the local projects * add a how-to install language packs * adding Linux deb packages and MacOSX packages * add links to dictionaries * using bouncer for that downloads * split the table into pieces and add some nice graphics for the platforms I think the main entry point to localized version of OpenOffice.org should stay as is in the native-lang communities but I'm also convinced that such overview pages might also help to increase visibility of the project and participation in the native-lang communities. Shall we continue such an effort ? Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
