{{Community_Council}}
== Upcoming Meeting ==

Date: 2010-10-14 (Derived from the [[Community Council/Calendar|Community Council Meeting Calendar]])

Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=14&month=10&year=2010&hour=18&min=30&sec=0&p1=0 18.30 UTC] (click on the link to show world clock times)

Location: IRC

== Agenda and Work Status ==

The following table represents the agenda of the upcoming meeting and the current work status of topics / action items. Working with this table is described in the [[Community Council/Meeting Guidelines|Community Council Meeting Guidelines]].

{| class="prettytable sortable"
|-
! scope="col" | ID 
! scope="col" | Topic 
! scope="col" | Status 
! scope="col" | Responsible 
! scope="col" | Last Update 
! scope="col" | Details 
|-
| 00 
| Where do we stand 
| ''new'' 
| all 
| .. 
|
*Now that many members of the community council support the Document Foundation: how do find the best way to go on?
|-
| 0 
| List of Action Items of previous meeting for approval 
| ''none'' 
| all 
| 2010-09-23 
|
*Meeting minutes of previous meeting at [[Community Council/Minutes#2010-09-23|Minutes#2010-09-23]] 
*Result: (to be confirmed)

|-
| 2010-03-04#2 
| Refresh Incubator and NLC Project processes 
| Accepted 
| Louis 
| 2010-03-18 
|
*No new proposal available. Louis will work on that. 
*Next steps: Will be discussed in next meeting.

|-
| 2010-03-04#6 
| Talk to Education Project Leads about structure and remit 
| Stalled 
| John, Cor 
| 2010-03-18 
|
*Cor to prepare a draft and present it to the Community Council. Nothing done yet.
*Next steps: Will be discussed in next meeting. 

|-
| 2010-04-01#1 
| Community situation 
| Accepted 
| All 
| 2010-09-23 
|
*What do we see, where are we, what are we going to do about it. 
*Activities:
**All CC members are asked to think about it and Cor will prepare a proposal for an detailed agenda. 
**Leif already collected some issues (e.g. rare communication via blogs) and will send that to Cor. 
*Next Steps: Proposal that the CC will work on that at the OOoCon in Budapest.
**Cor send a mail on 2010-08-12 with some items for the agenda. 
* 2010-09-03/09-21: Page with draft plan [[Community_Council/collaboration_in_the_OOo-community | improvement community collaboration]]

|-
| 2010-04-29#2 
|
Missing OOo desktop presence

| Accepted 
| Christoph, Stefan
| 2010-09-21 
|
*Request by a community member to discuss / decide the following question: "''Why should OpenOffice.org give away it's presence on the user's desktop - the main place to be recognized by the people - only to support the "application independency" of ODF?'' A Sun employee stated "The idea of supporting ODF as a application independent open standard is the priority." This leads / will lead to changes with regard to the document and application icon design. The current ODF "only" icons seem to be undesired by the community. Original request to the CC on ooo-discuss: [http://www.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=65958 initial mail (2010-04-14)], [http://www.openoffice.org/servlets/BrowseList?listName=discuss&from=2361081&to=2361081&count=28&by=thread&first=1&windowSize=1000 full mail thread]
*Discussion:
**2010-04-29: Some members stated that the request should be "more actionable" and "better framed" to be decided by the community. Proposal has been made to forward the request to council-discuss to propose how to proceed.
**2010-05-02: Christoph forwarded the [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2564 request to the CC mailing list]. A first discussion took place.
**2010-05-20: Intensive discussion about the request and how to address it. Stefan and Christoph agreed to work out a request to the ODF Icons team to iterate on the design and/or processes. Maybe a "refreshed" team which may provide an agreed-upon proposal. Stefan stated that there shouldn't be any dependency to the next/other releases.
**2010-06-08: Some opinions have been requested from people who initially worked in the branding initiative. Either there isn't feedback yet, or the people aren't currently available to support the i-Team. Ongoing ...
**2010-06-30: Still ongoing ...
**2010-07-22: Andreas provided some insight what currently happens within Oracle. The topic "icons" is currently addressed ...
***A discussion took place with Michael Bemmer and other people at Oracle.
***Outcome: Oracle marketing made a decision that is supposed to be communicated shortly. --> Icons will be redesigned, for the long run, with constraints.
***Motivation: The current design fails with regard to usability aspects. --> Redesign is intended with focus on usability.
***Constraints: The activity will be run open with all necessary involvements.
***Question to Andreas/Martin to discuss whether the official statement may be discussed with the community before it is going to be published "officially".
***Decision to keep this CC Action Item open until there is more visible activity.
**2010-08-12: Marketing contact is in vacation, and information also depends on others at Oracle. More information defitively to come at the OOoCon, presentation "[http://www.ooocon.org/index.php/ooocon/2010/paper/view/215 Brand Refresh and new Brand Initiative]". 
**2010-09-21: Request for update sent to Oracle, nothing new yet.
*Next steps: Waiting for the reaction by Oracle, either getting in touch with the community or an official announcement. 
*Cornouws: discussed during OOoCon; looks as if we were able to bring accros the importancy, however, other tasks ask attention first from Oracle people. 

|}

 

== Minutes of Previous Meetings ==

To be found [[Community Council/Minutes|here]].

[[Category:Community_Council]]

Community Council/Agenda

2010-10-14T12:36:17Z

CorNouws:

Community Council Log 20100923

2010-10-08T09:18:02Z

CorNouws: Created page with '{{Community_Council}} == IRC Log 2010-09-23 == * Location: IRC == Council Members == === Attendees === *Christoph Noack (christoph_n) *Cor Nouws (CorNouws) *Charles-H. Sch…'

{{Community_Council}}

== IRC Log 2010-09-23 ==

* Location: IRC

== Council Members ==

=== Attendees ===

*Christoph Noack (christoph_n)
*Cor Nouws (CorNouws)
*Charles-H. Schulz (southerncross__)
*Matthias Hütsch (mhu)
*Jürgen Schmidt (jsc)
*Stefan Taxhet (stx12)

=== Absent ===

*Andreas Bartel (Andreas_UX)
*Louis Suárez-Potts
*Olivier Hallot (olivierhallot)
*Eike Rathke (erAck)

== Log ==

Times are in CEST (UTC+2)

(20:45:43) christoph_n: Okay, guys, do we want to start? 
(20:45:50) jsc: do we have any official descendant 
(20:46:01) jsc: you was faster ;-) i think we shoudl 
(20:46:42) CorNouws: ok 
(20:46:46) jsc: well we have no real minutes from our meeting in Budapest 
(20:47:12) christoph_n: For the next 40 min (or less), I can offer to mimic the moderator ... may I? 
(20:47:29) jsc: go ahead 
(20:47:40) ***mhu wonders what he might have missed from the meeting in Budapest. Anything I should know? 
(20:48:14) christoph_n: mhu: I think it was rather a social meeting with interesting discussions. So I am not aware of anything so important be be called "missed"? Or am I wrong, anybody? 
(20:49:20) jsc: no, you missed nothing. I would agree to Christoph. 
(20:49:33) christoph_n: Okay, the agenda of the last IRC meeting can be found here: http://wiki.services.openoffice.org/wiki/Community_Council/Agenda 
(20:49:36) mhu: thanks, christoph_n, jsc 
(20:50:01) christoph_n: Item 0: List of Action Items of previous meeting for approval 
(20:50:28) christoph_n: Since we just mentioned that there are no minutes / list of actions, please approve the current ones. Or better, raise your hand if not. 
(20:51:05) christoph_n: (counting *g*) 
(20:51:12) christoph_n: Item 2010-03-04#2: Refresh Incubator and NLC Project processes 
(20:51:14) CorNouws: [hands still down] 
(20:51:36) christoph_n: Since Louis seems not available, I propose to skip that item. 
(20:52:15) CorNouws: sorry, unless our meeting in Budapest, I'm finished with poking LSP 
(20:52:17) christoph_n: mhu: We had a discussion concerning the rather old tasks in our list (and in general) 
(20:52:48) mhu: okay 
(20:53:11) christoph_n: Well Cor, you have been faster. Louis (for example) asked for being poked officially in such a case. 
(20:53:50) christoph_n: Anybody who wants to comment? 
(20:54:07) christoph_n: Item 2010-03-04#3: Publicize the open slot at the start of the CC meetings 
(20:54:24) jsc: no not at the moment. We should continue with poking ... at least until the next meeting 
(20:54:51) jsc: ok it's mine and i think it's done and can be removed 
(20:54:58) christoph_n: Jürgen, I saw the Q&A dates in the calendar. Thanks for that! Yep, can be removed ... 
(20:55:16) jsc: the next public part will be in front of our next meeting 
(20:55:38) christoph_n: I'll be happy to be poked ;-) 
(20:55:58) christoph_n: Item 2010-03-04#6: Talk to Education Project Leads about structure and remit 
(20:56:13) CorNouws: no change, afaiac 
(20:56:14) christoph_n: Cor, nothing new, I assume. Skip it? 
(20:56:28) ***CorNouws me is still faster 
(20:56:40) ***christoph_n looks better ;-) 
(20:57:00) christoph_n: Item 2010-04-01#7: Talk to NLC about ‘NLC of the Month’ for OOo Newsletter 
(20:57:18) christoph_n: Charles, something we marked "done" in Budapest ... or? 
(20:57:27) southerncross__: yes 
(20:57:43) southerncross__: it will now follow a normal "inter-project" process. 
(20:57:47) southerncross__: no need to interfere.... 
(20:57:54) christoph_n: ... or support ;-) 
(20:58:02) southerncross__: yes. 
(20:58:28) christoph_n: Okay, then let's remove it from the list. (The list gets damn short) 
(20:58:28) ***jsc is enjoying a tasty whisky -> The Dalmore, 15 years old, sorry guys ;-) 
(20:58:56) christoph_n: Golf, Whisky ... I seem to have the wrong job ;-) 
(20:59:26) jsc: job? you do the wrong things in your spare time 
(20:59:47) christoph_n: bye bye (just kidding) 
(20:59:48) CorNouws: christoph_n: how does he know ;-) 
(21:00:10) christoph_n: CorNouws: Inter-webcam access ... 
(21:00:34) CorNouws: BTW: no news from Eike? 
(21:00:56) jsc: i assume he forgot it. He is at least back from sailing 
(21:01:21) christoph_n: (Golf, Whisky, Sailing, ...) 
(21:01:27) jsc: oh, please don't get a wrong picture from us guys in HH 
(21:01:35) CorNouws: and Andreas? 
(21:01:54) CorNouws: Whisky or beer :-) 
(21:02:06) jsc: wine tasting 
(21:02:11) CorNouws: jsc: already too late ;-) 
(21:02:11) christoph_n: Don't know ... I asked concerning the ODF icons some days ago. He should be aware ... 
(21:02:41) ***christoph_n thinks Cor does some "mind-reading" 
(21:03:06) christoph_n: Guys, there are items left ... 
(21:03:06) christoph_n: Item 2010-04-01#1: Community situation 
(21:03:43) CorNouws: ugh ... Stefan and I talked about at least our takst while drinking some nice cofee in Budapest 
(21:04:01) christoph_n: So how was it, both the coffee and the talk? 
(21:04:10) CorNouws: s/takst/task 
(21:04:26) ***christoph_n thinks Cor needs an even faster keyboard 
(21:04:36) CorNouws: bit double feelings, afaiac 
(21:04:40) jsc: in general i noticed some suspect silence and i am thinking about it 
(21:05:04) CorNouws: we started long time ago bit frustrated but in good mood - now I have the feeling it has all taken too long :-( 
(21:05:05) christoph_n: I'm sure you are referring to 2010-04-29#2 ;-) 
(21:05:48) christoph_n: Cor, so what to do? Is there anything we - being the other CC members - can do? 
(21:05:51) CorNouws: christoph_n: no, pls see the latest comment at #1 
(21:06:12) CorNouws: see, pls see the latest comment at #1 ;-) 
(21:06:21) stx12: no, CorNouws isn't; there is a plan in the wiki now CorNouws is refering to. 
(21:07:14) christoph_n: (reading) 
(21:07:24) ***mhu thinks, the new plan in wiki is at least a way the we can go to improve 
(21:07:39) stx12: christoph_n: you may want to read over the page we finalized during coffee 
(21:08:44) ***stx12 thought of offline-readibng... 
(21:08:58) jsc: would have been nice to get the pointer a little bit earlier -> draft from 93., 21.9 -> last update AI 12.8 
(21:09:37) ***jsc have to read more careful 
(21:09:39) stx12: jsc: see the history of the document; earlier you have looked at an empty page 
(21:09:42) christoph_n: Mmmh, looks good to me. Although I don't think that "anonymity" is possible ... but however, it is a plan. 
(21:10:48) christoph_n: The point is, when referring to the management, is there "commitment" concerning these steps? How "open" are they for discussion ... and who is the management in such a case. 
(21:11:13) CorNouws: mhu: yes, initially, but having learned a bit more about backgrounds of some situations, while drinking coffee from different mugs, I am affraid that in the current set up it is inavoidable to run in such nasty, maybe even embarassing situations 
(21:11:42) southerncross__: folks: I'll have to leave, sorry.... 
(21:11:50) christoph_n: Bye! 
(21:12:40) southerncross__: bye! 
(21:12:42) christoph_n: Cor, Stefan: Before I forget it, thanks for continuing this effort. That's really needed ... 
(21:12:47) southerncross__ is weggegaan (quit: Quit: southerncross__). 
(21:12:57) mhu: CorNouws: understood; still, the only thing I (or stx12) can do, is to continue to talk to people and talk, and talk, ... 
(21:13:36) CorNouws: mhu: I agree and appreciate that very much 
(21:13:51) stx12: .. and involve management and ask for the needed commitment 
(21:13:53) christoph_n: mhu: I don't really get it ... you mean within the company? 
(21:14:05) christoph_n: stx12: Thanks, got it. 
christoph_n CorNouws 
(21:14:47) mhu: christoph_n: ...to people within the "community" and within companies (being part of that community) 
(21:14:49) ***CorNouws stx12 was faster too - did you have enough sleep christoph_n? 
(21:15:19) christoph_n: Cor: I have a day job, of course ;-) 
(21:15:54) mhu: ...and your day job does not involve OOo, uuuh 
(21:15:57) christoph_n: So, sorry for the strange question, what is the intended next step? Direct contacts, mails, internal clarification? 
(21:16:14) christoph_n: mhu: But "the other Office" :-) 
(21:16:21) mhu: :-) 
(21:16:47) stx12: christoph_n: see 1.D Steps 
(21:17:07) CorNouws: Let's take a week for further feedback of all cc members, and then stx12 & I can plan steps or so.. 
(21:17:09) CorNouws: stx12: ? 
(21:17:29) christoph_n: stx12, CorNouws: Was also a timing question and has been answered, thanks. 
(21:17:31) stx12: CorNouws: fine with me 
(21:17:53) christoph_n: Cor: Will you ask for comments on council-discuss? So the others can join the discussion? 
(21:18:06) CorNouws: yes, let me do that. 
(21:18:28) christoph_n: Great! 
(21:18:59) christoph_n: If I can help with something, then please ping me. 
(21:19:12) christoph_n: Any other comments here? 
(21:20:07) christoph_n: Let's move on to ... 
(21:20:12) christoph_n: Item 2010-04-29#2: Missing OOo desktop presence (a.k.a. icons and such stuff) 
(21:20:31) christoph_n: Cor, did you recently add the last comment? 
(21:20:38) CorNouws: well, you say 'move on' .. that is what should have happened 
(21:20:49) CorNouws: yes, two days agoo IIRC 
(21:21:05) christoph_n: Okay, I added "nothing new yet" :-) 
(21:21:41) christoph_n: Stefan, do you know more? Did something happen in the last days? 
(21:22:14) stx12: christoph_n: yes, people are travelling around the world. is this what you where asking for? 
(21:22:21) CorNouws: I had a short mail with Rosana last week, while she was busy prepraing for Oracle Open World, so I wouldn't ask too much of her precious time then 
(21:23:27) stx12: christoph_n: the real answer is that there is no other update than the reraised importance of the open item.it's on the table... 
(21:23:27) ***CorNouws sorry, my comment wasn't mentioned as an intervenrion between you two guys 
(21:24:04) christoph_n: Stx12: Okay ... 
(21:24:14) jsc: anything else on this AI for today? 
(21:24:29) jsc: otherwise i can give a short update on the intership program 
(21:24:48) jsc: sorry i forget to put it on the agenda 
(21:25:00) christoph_n: Jürgen: I'm sorry, I have to leave. Maybe I'll read on, but I expect a phone call ... sorry! 
(21:25:11) mhu: jsc: yes, please do so 
(21:25:13) christoph_n: So Jürgen, could you please take the moderator role? 
(21:25:27) jsc: yes, should easy ... 
(21:25:32) jsc: bye Christoph 
(21:25:34) christoph_n: Thanks!!! 
(21:26:15) jsc: ok, we planned a mid term evaluation starting September 20th... 
(21:27:20) jsc: i asked all mentors to give some feedback about their projects and to give some advice if we should continue or not 
(21:27:49) jsc: I also asked the students to give us feedback form their point of view 
(21:28:21) jsc: Overall all projects are still running and only once is a little bit difficult 
(21:29:12) jsc: At least for this one project the mentor mentioned that he would like to stop this project if there is no significant progress in the next 2-3 weeks 
(21:29:25) mhu: so, the mid-term eval is done, and okay, and we can send them the mid-term money? 
(21:29:42) mhu: message overlapped ... 
(21:29:44) jsc: yes, more or less i will summarize it tomorrow 
(21:29:51) mhu: okay, thanks 
(21:30:21) CorNouws: jsc: thanks, I thought I swiftly saw most mails, but think I missed the one with the tough, difficult project 
(21:30:31) jsc: the other projects are good so far and the feedback from the students was very positive. The mentors did a very good job ... 
(21:30:49) jsc: But also the students and i think we will get some good results 
(21:31:13) jsc: you missed the feedback from the mentors ;-) 
(21:31:46) jsc: the projects is not really bad but more difficult than the others 
(21:32:11) jsc: i will prepare a summary for you all. 
(21:32:25) CorNouws: I saw at least two report from mentors, I thougt, but thats not so important 
(21:32:54) CorNouws: good to see how it works! 
(21:32:54) jsc: I think we can pay the mid term payment for all projects and maybe we will stop this one later ... 
(21:33:04) ***mhu thinks, we (the mentors) should be a little patient with even difficult students, so that we can get more students next year 
(21:33:25) jsc: yes, the good thing is that most of the projects works without to much mentoring work 
(21:33:43) mhu: yes that is always best :-) 
(21:33:44) jsc: well the mentors have to bother sometimes for some updates but overall the projects work 
(21:33:54) CorNouws: patient yes, too weak no - we've seen more than enough enthusiastic apliants 
(21:34:18) mhu: ah, yes, of course, I should not forget that 
(21:34:35) CorNouws: mhu: ;-) 
(21:34:41) mhu: ...and xyes, we should not be week 
(21:34:47) mhu: s/week/weak/ 
(21:34:56) mhu: s/xyes/yes/ 
(21:35:01) CorNouws: /s/s/s/s/s 
(21:35:08) ***mhu needs a faster keyboard 
(21:35:15) mhu: :-) 
(21:35:16) jsc: we should definitely try to repeat this next year, maybe with more projects 
(21:35:32) CorNouws: yip .. 
(21:35:36) mhu: yes 
(21:35:47) jsc: that's it for today from me 
(21:35:59) jsc: anything else from you? 
(21:36:12) CorNouws: for me too - I guess nothing is left on the agenda? 
(21:36:19) ***jsc the whisky is empty ... 
(21:36:31) CorNouws: burp .. 
(21:36:33) mhu: ...and the agenda too

NL/Bijeenkomsten/OOoCafe

2010-09-25T12:01:41Z

CorNouws: /* 25 september 2010 .. nl-OpenOffice.org-Café in Breda */

== Wat is nl-OpenOffice.org Café ?! ==

* Een bijeenkomst waar je makkelijk binnen kunt lopen.
* Een eenvoudig programma, waaraan ieder mag bijdragen.
* Internettoegang en stroom, dus computer meenemen :-)
* Leuke weetjes delen en lastige vragen aan anderen voorleggen.
* De mensen ontmoeten, die je meestal alleen van de e-mail kent.

== 25 september 2010 .. nl-OpenOffice.org-Café in Breda ==
=== laatste nieuws - andere locatie ===
We zitten in Inspire Coffee, Veemarktstraat!

=== Even bijkomen van de vakantie, ervaringen uitwisselen, bijpraten over de OOoCon in Hongarije ... ===
Locatie: De Wasserette, Vlaszak 2, 4811 Breda. 
De Wasserette is een soort kunst-café, maar met een losse sfeer leent het zich gedurende de middag ook prima voor een ontmoeten van open office-actievelingen. 
De Wasserette is een makkelijke plek aan de rand van het centrum van Breda. Niet ver van het station en met parkeergarages is de buurt.

Tijd: 12:00 - 15/16..

Er zijn, afgezien van wat we gebruiken, geen kosten aan de bijeenkomst verbonden.

== 3 oktober 2009 nl-OpenOffice.org-Café in Eindhoven ==

=== Op het bekende open source event T-Dose ===
Tijdens de "T-Dose", waar enkelen toch al zijn, hebben we op 3 oktober ons volgende nl-OpenOffice.org-Café.

Tijd: van 11:00 tot ca. 14:30 uur.
Het programma van de T-Dose gaat dan nog door - ook op de zondag!

Website van [http://www.t-dose.org/ T-Dose]

== 6 juni te gast bij NLLGG ==
Op 6 juni zijn we te gast in Utrecht bij de NLLGG (Nederlandse Linux Gebruikers Groep). Tijd: van 11:00 tot 16:00.

Omdat we bij de NLLGG zijn, is er een iets ruimer programma met lezingen. Je vindt dat (voorlopige) programma en info over plaats op de site van [http://www.nllgg.nl/bijeenkomst_20090606 de NLLGG].

=== T-Shirts ===
Op 6 juni is er een stapeltje coole OpenOffice.org T-shirts aanwezig.
De bedoeling is dat die allemaal door andere mensen worden meegenomen ;-)

== OOo Café Carrousel ==
We gaan een circuit opzetten met als plaatsen bijvoorbeeld Amersfoort, Breda en Eindhoven. Mooie spreiding lijkt ons. Naar locaties wordt gezocht .. suggesties welkom.

== OpenOffice.org Café 21 maart 2009 ==

Het komende nl.OOo-Café op 21 maart!
Er zal daar veel aandacht voor nieuwe functies in de komende OpenOffice.org 3.1 en deskundige hulp bij proberen daarvan en QA.

[[Image:NlOOoCafe-09-03-14.png]]

=== Programma ===
(wijzigingen voorbehouden)
* 11.00 : Functies in de nieuwe versie van OpenOffice.org
* 12.00 : tafel-sessies
* 13.30 : Testen van nieuwe functies in bijvoorbeeld Developer Builds
* 14.30 : Ideeën over de oprichting van een vereniging voor Nl.OpenOffice.org
* 15.00 : Tafel-sessies

=== Praktische info ===
* Tijd: 10.00 - 15.00 (...)
* Plaats: [http://www.amershof.nl/route.html Amersfhof] in Amersfoort. (5 minuten lopen vanaf het NS-station.)
* Toegang: aanmelden is handig (hoe vol is vol?!) en kan op het mailadres [mailto:nl_OOo_cafe@openoffice.org nl_OOo_cafe]
* Kosten: geen (uitgezonderd consumpties). Vrijwillige bijdrage voor nl.OOo uiteraard welkom.

== 14 juni 2008 - 's Hertogenbosch ==

=== Primeur!===
Het éérste OpenOffice.org-café van de Nederlands/Vlaamse OOo-gemeenschap.

Doel: een bijeenkomst waar OpenOffice.org geïnteresseerden en belangstellingen makkelijk binnen kunnen lopen.
Er is een eenvoudig programma - zie verder. 
Uiteraard internettoegang en stroom, dus PC's en laptops meenemen is een pré. 
Leuke weetjes met anderen delen? Eindelijk eens vragen hoe iemand anders dat lastige vraagstuk oplost? Het kan op deze zaterdag!

=== Programma ===
(voorlopig)
* 10.30 - 11.00 : Presentatie OpenOffice.org op de server, door Jef Peeraer
* 11.30 - 12.00 : Testen en QA van OpenOffice.org, door Arthur Buijs / ...

=== Praktische info ===
* Tijd: 9.00 - 13.00
* Plaats: Koning Willem I College - Campus Techniek - Onderwijsboulevard 3, 5223 DE ‘s Hertogenbosch ( 5 minuten lopen vanaf de achteruitgang van het NS-station.)
* Toegang: aanmelden wordt aangeraden (hoe vol is vol?!) en kan op het mailadres [mailto:nl_OOo_cafe@openoffice.org nl_OOo_cafe]
* Kosten: geen (uitgez. consumpties), vrijwillige bijdrage voor nl.OOo uiteraard welkom.

[[Category:NL.OpenOffice.org|Bijeenkomsten]]

OpenOffice.org Internship/Projects

2010-09-25T11:40:12Z

CorNouws: improve ODF import :-D should be PDF-import - with greetings from the nl-OOo-Cafe

[[Category:Marketing]][[Category:Development]][[Category:Education]]
{{DISPLAYTITLE:Accepted projects for the Summer 2010 Internship}}

{| class="prettytable sortable"
|-
! scope="col" | Project
! scope="col" | Student
! scope="col" | Mentor
|-
| [[OpenOffice.org_Internship/Projects/2010/Statistical_Data_Analysis_Tool|Statistical Data Analysis Tool]]
| Pivithuru Wijegunawardana
| Niklas Nebel
|-
| [[OpenOffice.org_Internship/Projects/2010/Add_new_spreadsheet_functions_and_parameters_according_to_ODFF|Add new spreadsheet functions and parameters according to ODFF]]
| Marina Plakalovic
| Eike Rathke
|-
| [[OpenOffice.org_Internship/Projects/2010/Improve_PDF_Import|Improve PDF Import]]
| Marcin Mosiolek
| Kai Ahrens
|-
| [[OpenOffice.org_Internship/Projects/2010/Customizable_html_export_for_Impress|Customizable html export for Impress]]
| Kushal Likhi
| Christian Lippka
|-
| [[OpenOffice.org_Internship/Projects/2010/Optional_OpenType_features|Optional OpenType features]]
| Milos Hadzic
| Herbert Duerr
|-
| [[OpenOffice.org_Internship/Projects/2010/New_Context_Menu_Implementation|New Context Menu Implementation]]
| [[User:Arielch|Ariel Constenla-Haile]]
| Carsten Driesner
|}

Community Council/Agenda

2010-09-21T21:32:09Z

CorNouws:

{{Community_Council}}
== Upcoming Meeting ==

Date: 2010-08-12 (Derived from the [[Community Council/Calendar|Community Council Meeting Calendar]])

Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=12&month=08&year=2010&hour=18&min=30&sec=0&p1=0 18.30 UTC] (click on the link to show world clock times)

Location: IRC

== Agenda and Work Status ==

The following table represents the agenda of the upcoming meeting and the current work status of topics / action items. Working with this table is described in the [[Community Council/Meeting Guidelines|Community Council Meeting Guidelines]].

{| class="prettytable sortable"
|-
! scope="col" | ID 
! scope="col" | Topic 
! scope="col" | Status 
! scope="col" | Responsible 
! scope="col" | Last Update 
! scope="col" | Details 
|-
| 0 
| List of Action Items of previous meeting for approval 
| ''none'' 
| all 
| 2010-08-12 
|
*Meeting minutes of previous meeting at [[Community Council/Minutes#2010-08-12|Minutes#2010-08-12]] 
*Result: (to be confirmed)

|-
| 2010-03-04#2 
| Refresh Incubator and NLC Project processes 
| Accepted 
| Louis 
| 2010-03-18 
|
*No new proposal available. Louis will work on that. 
*Next steps: Will be discussed in next meeting.

|-
| 2010-03-04#3 
| Publicize the open slot at the start of the CC meetings 
| Done 
| Juergen 
| 2010-08-12 
|
*History:
**Proposal had been presented on March 30th and agreed on 
**Martin to prepare announcement on discuss before next meeting -- AI transferred to Jürgen
*Activities: 
**add new section under '''Procedures''' in the meeting guideline, see [[Community Council/Meeting Guidelines#Public_QA|Meeting Guidelines - Public QA]]
**add 2 new public QA session in the meeting calendar, see [[Community Council/Calendar#Meetings_in_2010|Meetings in 2010]]
**post information email to council-discuss
*After the first session, improvements required for:
**Naming seems to be ambiguous (QA and Q&A are already project names, proposals: "Ask the Community Council", "Discuss with the Community Council", "Community and Council",  "Questions-and-Answers Session")
**Wider announcement of the Questions-and-Answers session (proposal: discuss@ooo, dev@ooo, NLCs should also announce it, Blog?)
**Exact begin of the open slot (it was unclear whether it should start 30 minutes before the official CC session or starts at the usual CC time)
*Next Steps: Ask Juergen to work on the improvements.
*Updated the meeting guidelines and change the name of our public session, [[Community Council/Meeting Guidelines|Meet_the_Community_Council|Meet the Community Council]]. Add a note for a public reminder and provide an initial template for the reminder ([[Community Council/Meeting Guidelines/Public Invitation Reminder Template|Public Invitation Reminder Template]]).

|-
| 2010-03-04#6 
| Talk to Education Project Leads about structure and remit 
| Stalled 
| John, Cor 
| 2010-03-18 
|
*Cor to prepare a draft and present it to the Community Council. Nothing done yet.
*Next steps: Will be discussed in next meeting. 

|-
| 2010-04-01#7 
| Talk to NLC about ‘NLC of the Month’ for OOo Newsletter 
| Accepted 
| Charles 
| 2010-04-01 
|
*Inteview with the Irish team has been done. No further information available by his deputy (Leif). 
*Next steps: Few projects agree to respond to the interview for the NLC project of the month. This month the Hungarian team will be highlighted for obvious reasons, and in September the Italian community is scheduled. 

|-
| 2010-04-01#1 
| Community situation 
| Accepted 
| All 
| 2010-08-12 
|
*What do we see, where are we, what are we going to do about it. 
*Activities:
**All CC members are asked to think about it and Cor will prepare a proposal for an detailed agenda. 
**Leif already collected some issues (e.g. rare communication via blogs) and will send that to Cor. 
*Next Steps: Proposal that the CC will work on that at the OOoCon in Budapest.
**Cor send a mail on 2010-08-12 with some items for the agenda. 
* 2010-09-03/09-21: Page with draft plan [[Community_Council/collaboration_in_the_OOo-community | improvement community collaboration]]

|-
| 2010-04-29#2 
|
Missing OOo desktop presence

| Accepted 
| Christoph, Stefan
| 2010-09-21 
|
*Request by a community member to discuss / decide the following question: "''Why should OpenOffice.org give away it's presence on the user's desktop - the main place to be recognized by the people - only to support the "application independency" of ODF?'' A Sun employee stated "The idea of supporting ODF as a application independent open standard is the priority." This leads / will lead to changes with regard to the document and application icon design. The current ODF "only" icons seem to be undesired by the community. Original request to the CC on ooo-discuss: [http://www.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=65958 initial mail (2010-04-14)], [http://www.openoffice.org/servlets/BrowseList?listName=discuss&from=2361081&to=2361081&count=28&by=thread&first=1&windowSize=1000 full mail thread]
*Discussion:
**2010-04-29: Some members stated that the request should be "more actionable" and "better framed" to be decided by the community. Proposal has been made to forward the request to council-discuss to propose how to proceed.
**2010-05-02: Christoph forwarded the [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2564 request to the CC mailing list]. A first discussion took place.
**2010-05-20: Intensive discussion about the request and how to address it. Stefan and Christoph agreed to work out a request to the ODF Icons team to iterate on the design and/or processes. Maybe a "refreshed" team which may provide an agreed-upon proposal. Stefan stated that there shouldn't be any dependency to the next/other releases.
**2010-06-08: Some opinions have been requested from people who initially worked in the branding initiative. Either there isn't feedback yet, or the people aren't currently available to support the i-Team. Ongoing ...
**2010-06-30: Still ongoing ...
**2010-07-22: Andreas provided some insight what currently happens within Oracle. The topic "icons" is currently addressed ...
***A discussion took place with Michael Bemmer and other people at Oracle.
***Outcome: Oracle marketing made a decision that is supposed to be communicated shortly. --> Icons will be redesigned, for the long run, with constraints.
***Motivation: The current design fails with regard to usability aspects. --> Redesign is intended with focus on usability.
***Constraints: The activity will be run open with all necessary involvements.
***Question to Andreas/Martin to discuss whether the official statement may be discussed with the community before it is going to be published "officially".
***Decision to keep this CC Action Item open until there is more visible activity.
**2010-08-12: Marketing contact is in vacation, and information also depends on others at Oracle. More information defitively to come at the OOoCon, presentation "[http://www.ooocon.org/index.php/ooocon/2010/paper/view/215 Brand Refresh and new Brand Initiative]". 
**2010-09-21: Request for update sent to Oracle, nothing new yet.
*Next steps: Waiting for the reaction by Oracle, either getting in touch with the community or an official announcement. 
*Cornouws: discussed during OOoCon; looks as if we were able to bring accros the importancy, however, other tasks ask attention first from Oracle people. 

|}

 

== Minutes of Previous Meetings ==

To be found [[Community Council/Minutes|here]].

[[Category:Community_Council]]

Community Council/collaboration in the OOo-community

2010-09-21T21:25:38Z

CorNouws: Version 1.0/ Date 2010-09-03/ By Cor Nouws/Stefan Taxhet

{{Community_Council}}

Community council project
== 1 Title: case studies of work and lessons for collaboration in the OpenOffice.org community ==
Short title: Collaboration in the OOo-Community

===1.A Short description===
This project is a joint effort of OpenOffice.org community members to understand how they experienced situations with good and bad cooperation, and what lessons we can learn to work together more effectively and with more fun.
===1.B Background===
This project is born from the experience that the branding group had early 2010. The branding group went through a period of discussions and experiments where the constraints of the effort were not well defined. At different stages it was not clearly enough communicated by the trademark holder initiating the effort, what the expected outcome of a discussion or work could be. This led to disappointments for volunteers as well as full-time sponsored project members that could have been avoided. In this project 'Collaboration in the OOo-Community', we'll work together with people involved in the branding effort and in other cases to understand how they experienced it and what lessons we all can learn. (For details on the initial mention of the idea see <council log>)

===1.C Team===
* Stefan Taxhet
* Cor Nouws
* (feel free to contact us)
===1.D Steps===
I. find cases (either positive or negative) that we can investigate;
* ask people directly, and also mail to discuss@OOo
* collect information about similar efforts in the past

II. prioritize cases we can use;

III. interview participants
* prepare questions
* invite people engaged in different roles in selected cases for an interview;
* run interviews (1)
* assure (inform and explain) people that this effort is about learning, processes, and not about their personal participation;
* follow privacy policies
* when necessary, interview people for a second time, to really understand what were the essential details in the process;

IV. prepare a report from the information
* ensure anonymity
* gives a summary of the answers
* defines things to be learned
* defines means(2) to apply the recommended changes/activities
* prepare an evaluation after 8 months and after 14 months;

V. discuss this report with
* Community Council
* management involved
* people interviewed
* active members in the community

VI. publish final report
* educate results
* introduce recommended improvements / activities

''1) Has to be prepared, script, questionaire, interview face to face or by mail / phone, circumstantial/depending on situation, if we know people well, … so to be decided during the work''

''2) Possible ideas checklists, training, ...''

''Version 1.0/ Date 2010-09-03/ By Cor Nouws/Stefan Taxhet''

NL/QA/Testen

2010-08-16T22:08:26Z

CorNouws: alle localization@ vervangen door dev@

== Werken met nog niet officiële versies van OpenOffice.org ==

=== Waarom ===
* Het is leuk om de nieuwste ontwikkelingen op de voet te volgen ...
* Hoe eerder fouten in de software worden ontdekt, bij voorkeur nog voor de beta-versies, hoe makkelijker het is om ze te repareren. 
OpenOffice.org brengt vier keer per jaar een nieuwe versie uit (twee keer met nieuwe functies en twee keer met alleen verbeteringen). Er is dus steeds veel nieuws te beleven en te testen.

In de ontwikkelcyclus van het product zijn achtereenvolgens de volgende versies, stadia, te onderscheiden:
* developer builds (snapshots) - om de paar weken;
* beta versies - tegen de tijd dat de nieuwe versie bijna klaar is;
* release kandidaten - een release kandidaat kan de uiteindelijke nieuwe versie worden;
* stabiele versies

Het testen kan heel gestructureerd, maar ook door de software gewoon te installeren en er mee te werken en dan kijken wat voor bijzonderheden je aantreft. Meer hierover verder op deze pagina.
Testen kan heel leuk zijn, want je leert er vaak weer wat van en kunt zelf snel met de nieuwste functies aan de slag. En het helpt om zo vroeg mogelijk zoveel mogelijk fouten op te sporen. Kortom: hulp met testen is altijd welkom!

== Nu beschikbaar om te proberen en te testen ==

===Algemeen: downloaden===
Snapshots enzovoorts zijn steeds te vinden via [http://download.openoffice.org/next/ http://download.openoffice.org/next/]. Rechts op die pagina staan ook verwijzingen naar nuttige aanvullende uitleg. 
Controle van de integriteit van de downloads kan met de MD5 CheckSum test. Uitleg en controle-getallen zijn altijd te vinden op de [http://download.openoffice.org/next/md5sums/ md5sums]-pagina.

=== Versie voor testen vertaling 3.3.0 beschikbaar ===
Op 26 juli is de test-versie met de vertaling voor OpenOffice.org 3.3.0 beschikbaar gekomen. Te downloaden van [http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/ooo330l10n/ deze pagina]. (Voor Linux zijn alleen de taalpakketten en een complete eng-GB versie beschikbaar.) 
Er is in het Engels al informatie over de functies [[Feature_Freeze_Testing_3.3 | beschikbaar]]. 
Heb je zin om in het Nederlands gebruikers-informatie te maken, neem dan even contact op.. Dank!

(Diverse info: [[OOoRelease33]], [[Translation_for_3.3]])

===Beta voor 3.3.0 beschikbaar!===
De beta voor OpenOffice.org 3.3.0 is er! Te downloaden van http://download.openoffice.org/all_beta.html#untested-full.
Veel plezier er mee!

===Snapshots voor de 3.4.x===
Sinds in juli 2010 de tak voor de 3.3.x is losgemaakt uit de hoofdstam, wordt de lijn DEV300 verder ontwikkeld richting 3.4.0 etc.

Nieuwsgierig? De eerste snapshots zijn via [http://download.openoffice.org/next/ http://download.openoffice.org/next/] te vinden.

===Snapshot met nieuwe afdrukvensters - Belangrijke mijlplaal in de ontwikkeling van versie 3.3.0!===
Sinds half januari is Developer build [http://download.openoffice.org/next/ DEV300 m70] beschikbaar.

Daarin is de code opgenomen voor de nieuwe afdrukvensters. Pluspunten: elk afdrukvenster toont een afdrukvoorbeeld, en biedt direct toegang tot alle instellingen.
Lees daarover meer op [http://blogs.sun.com/GullFOSS/entry/new_print_ui_now_integrated GullFoss].

Het is een heel nieuw stuk in OpenOffice.org, dat stevig aan de tand moet worden gevoeld voor de 3.3.0 uit komt. Je kunt deze snapshot downloaden en installeren naast je normale OpenOffice.org versie. (Zie de uitleg elders op deze wiki-pagina.)

== Meer over de achtereenvolgende versies in de ontwikkelcyclus ==

=== Developer builds (snapshots) ===
Zijn redelijk stabiel, maar worden niet aangeraden voor dagelijks werk. 
Installeert apart, naast de normale versie van OpenOffice.org. 
Op de OOo-site staan de nieuwste [http://download.openoffice.org/next/other.htm developer builds], maar die zijn niet in het Nederlands beschikbaar. Op die pagina's is onder de link 'Release Notes' ook een verwijzing naar informatie over de nieuwe functies.

=== Beta versies ===
Het product is bijna gereed, men verwacht dat het product zonder serieuze problemen gebruikt kan worden. De nieuwe functies worden met de beta-uitgaven door veel mensen gebruikt, wat weer extra reacties oplevert. 
Een beta installeert naast een bestaande versie van OpenOffice.org.
=== Release kandidaten ===
Een release kandidaat verschijnt zodra men verwacht dat het product gereed is. Het is tijd voor de laatste tests. 
Bij het installeren, vervangt de release kandidaat de al geïnstalleerde versie van OpenOffice.org, tenzij er wordt gekozen voor parallelle installatie. Die procedure is elders op deze pagina beschreven: [[NL/TipsEnTrucs/Meerdere_versies_van_OOo_uitvoeren| Meerdere versies van OOo uitvoeren]]. 
Als er geen ernstige problemen meer worden gevonden, zal de release kandidaat als de nieuwe stabliele versie worden vrijgegeven.

=== Goedkeuring voor een nieuwe release ===
Voordat een nieuwe versie officieel wordt vrijgegeven, moet er natuurlijk wel wat gebeuren.
Op [[Release_Action_List_for_QA#Approval_of_Builds | deze plek]] staat hoe dat in zijn werk gaat.

== Meerdere versies en talen installeren ==

=== Meerdere versies installeren===
Het is verstandig om de diverse (testversies) naast je huidige OpenOffice.org te installeren. Je kunt dan ook makkelijk functies vergelijken. Op [[NL/TipsEnTrucs/Meerdere_versies_van_OOo_uitvoeren| Meerdere versies van OOo uitvoeren]] staat uitgelegd hoe dat werkt. Kom je ergens niet uit? Mail dan naar [mailto:dev@nl.openoffice.org dev@nl.openoffice.org]

=== Taalversies ===
Het is ook mogelijk om een niet Nederlandse versie van OpenOffice.org (bijv. Engels) te installeren en dan een taalpakket (language pack) voor Nederlands.
Als eerst de volledige versie wordt geïnstalleerd en dan (snelstarter uit!) het Nederlandse taalpakket, kan in Tools>Options>Language settings>Language 'Nederlands' worden gekozen voor de gebruikers interface. Al de menu's, vensters en Help worden dan Engels- of Nederlandstalig.

== Hoe testen ==

=== Inleiding ===
Het zoeken (en oplossen) van fouten gebeurt in verschillende fasen.
* Tijdens de ontwikkeling door het testen van en werken met de developer-builds en beta-releases.
* Bij release-kandidaten gaat het alleen nog om het vinden en corrigeren van echt grote problemen.
* Van de laatste release kandidaat moet ook voor de Nederlandstalige versie een akkoord worden gegeven, alvorens die kan worden vrijgegeven.

=== Geautomatiseerd testen ===
Volgens testplannen worden allemaal functies geautomatiseerd uitgevoerd.
Dit is een doorlopend proces en gebeurt (vooral door de mensen van Sun en RedFlag) dus ook in een vroeg stadium.

Voor de geïnteresseerden, is er de nodige informatie, zoals over de [[Testtool|testtool]] voor geautomatiseerd testen en over het eventueel vertalen daarvan: [[HowTo_localize_qatesttool_environment|how to localiza it]].

=== Testen met TCM ===
Testen volgens TCM is vooral nuttig voor het controleren van nieuwe functies, en tijdens het testen van release-kandidaten.
* Nieuwe functies moeten in een redelijk vroeg stadium worden getest, uiterlijk met een beta-versie, en niet met de release-kandidaten. Bij release kandidaten worden alleen nog heel ernstige bugs gecorrigeerd, en niet als een nieuwe functie niet helemaal perfect werkt ...
* Testen volgens TCM geeft ook een houvast voor het testen van hoofdfuncties, die wel moeten worden gecontroleerd bij een release-kandidaat.

====Localisatie testen van nieuwe uitgaven van OOo====
Voordat je resultaten van je testen kunt invoeren in TCM, of kunt TCM gebruiken voor testideeën, moet je als gebruiker aan TCM worden toegevoegd. 
Mail daarvoor naar [mailto:dev@nl.openoffice.org de lijst voor actieve bijdragen] of naar één van de andere actieve projectleden.
* De startpagina van TCM is [http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_login.cgi?tcm_config=newooo hier].
* Je kunt daar inloggen met username en password
* Ga dan door op stap 5: Test Result Update
* Kies de versie van OOo, de tests die op jouw naam staan, etc.
** Bijvoorbeeld: Klik op 'OpenOffice.org(3.2RC)' in de kolom 'Build Number'
** Zoek in de volgende tabel de regel met je inlognaam.
** Klik in die regel op 'Scenario(Release sanity scenario)'
** Er zijn dan meer dan 20 test beschikbaar.
het is niet altijd nodig dat iedere tester elke test doet ...
het zijn geen ingewikkelde tests, maar kies eventueel dus tests die je graag doet, of overleg per mail met anderen.
** Bij een uitgevoerde test invullen: pass, fail of skip, en voer eventueel commentaar in
** Je kunt ook kijken naar de linkjes naar al eerder gevonden bugs.
*** Het is goed mogelijk dat daar al opgeloste bugs tussen staan - het is nog niet geregeld dat die worden verwijderd/gefilterd.
over criteria om een test op fail te zetten:
dat gebeurt niet om kleinere problemen, alleen als iets echt goed fout zit
vul evt. commentaar in. En al weer: bij vragen is er op de mail lijst altijd hulp!

Vragen, opmerkingen, suggesties welkom!

Zeer nuttige uitgebreide informatie staat in de wiki op de [[Test_Case_Management|de TCM pagina]] en in de uitleg over TCM/testen en de release cyclus [[Release Action List for QA]]

===Minimale check op gelocaliseerde versies===
Wanneer het niet mogelijk is om alle TCM tests te doen, kan worden terug gevallan op een [[NL/QA/SanityCheck_van_Localisaties | lijst met minimale tests]] voor de vrijgave.

Maar we moeten er om denken, dat als iedereen alleen maar 'minimaal' gaat zitten testen, we gauw een probleem hebben ..

=== Testen door er mee te werken ===
Dit kan iedereen doen. Snapshots en beta-versies downloaden en er mee aan de slag gaan.

=== Je ervaringen delen ===
Als je bijzonderheden tegenkomt - meestal fouten ;-) - dan is het de bedoeling dat die in Issuetracker worden geplaatst. Of dat je met je waarneming een issue van een ander bevestigt, of verduidelijkt, of nuanceert.

Informatie voor het gebruiken van Issuetracker staat [http://nl.openoffice.org/about-issuezilla.html hier].

Vaak is het handig om ervaringen te bespreken voordat je de moeite neemt om een issue te maken. Soms heeft iemand anders al een antwoord of issue, of is het probleem in een nieuwe snapshot opgelost. Dat scheelt je dan weer het aanmaken van een issue.
En kom je ergens zelf niet uit: vraag het dan gewoon op dev@nl.openoffice.org.

=== Coördinatie van & informatie over testen===
Al enkele keren genoemd: dev@nl.openoffice.org. Dit is de mailinglijst waar alle lijntjes samen komen. Dus het is leuk en nuttig om je daar voor aan te melden ([mailto:dev-subscribe@nl.openoffice.org dev-subscribe@nl.openoffice.org]).

[[Category:NL.OpenOffice.org|QA]]

NL/QA/Testen

2010-08-16T22:06:41Z

CorNouws: /* Beta voor 3.3.0 gaat er aan komen */

== Werken met nog niet officiële versies van OpenOffice.org ==

=== Waarom ===
* Het is leuk om de nieuwste ontwikkelingen op de voet te volgen ...
* Hoe eerder fouten in de software worden ontdekt, bij voorkeur nog voor de beta-versies, hoe makkelijker het is om ze te repareren. 
OpenOffice.org brengt vier keer per jaar een nieuwe versie uit (twee keer met nieuwe functies en twee keer met alleen verbeteringen). Er is dus steeds veel nieuws te beleven en te testen.

In de ontwikkelcyclus van het product zijn achtereenvolgens de volgende versies, stadia, te onderscheiden:
* developer builds (snapshots) - om de paar weken;
* beta versies - tegen de tijd dat de nieuwe versie bijna klaar is;
* release kandidaten - een release kandidaat kan de uiteindelijke nieuwe versie worden;
* stabiele versies

Het testen kan heel gestructureerd, maar ook door de software gewoon te installeren en er mee te werken en dan kijken wat voor bijzonderheden je aantreft. Meer hierover verder op deze pagina.
Testen kan heel leuk zijn, want je leert er vaak weer wat van en kunt zelf snel met de nieuwste functies aan de slag. En het helpt om zo vroeg mogelijk zoveel mogelijk fouten op te sporen. Kortom: hulp met testen is altijd welkom!

== Nu beschikbaar om te proberen en te testen ==

===Algemeen: downloaden===
Snapshots enzovoorts zijn steeds te vinden via [http://download.openoffice.org/next/ http://download.openoffice.org/next/]. Rechts op die pagina staan ook verwijzingen naar nuttige aanvullende uitleg. 
Controle van de integriteit van de downloads kan met de MD5 CheckSum test. Uitleg en controle-getallen zijn altijd te vinden op de [http://download.openoffice.org/next/md5sums/ md5sums]-pagina.

=== Versie voor testen vertaling 3.3.0 beschikbaar ===
Op 26 juli is de test-versie met de vertaling voor OpenOffice.org 3.3.0 beschikbaar gekomen. Te downloaden van [http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/ooo330l10n/ deze pagina]. (Voor Linux zijn alleen de taalpakketten en een complete eng-GB versie beschikbaar.) 
Er is in het Engels al informatie over de functies [[Feature_Freeze_Testing_3.3 | beschikbaar]]. 
Heb je zin om in het Nederlands gebruikers-informatie te maken, neem dan even contact op.. Dank!

(Diverse info: [[OOoRelease33]], [[Translation_for_3.3]])

===Beta voor 3.3.0 beschikbaar!===
De beta voor OpenOffice.org 3.3.0 is er! Te downloaden van http://download.openoffice.org/all_beta.html#untested-full.
Veel plezier er mee!

===Snapshots voor de 3.4.x===
Sinds in juli 2010 de tak voor de 3.3.x is losgemaakt uit de hoofdstam, wordt de lijn DEV300 verder ontwikkeld richting 3.4.0 etc.

Nieuwsgierig? De eerste snapshots zijn via [http://download.openoffice.org/next/ http://download.openoffice.org/next/] te vinden.

===Snapshot met nieuwe afdrukvensters - Belangrijke mijlplaal in de ontwikkeling van versie 3.3.0!===
Sinds half januari is Developer build [http://download.openoffice.org/next/ DEV300 m70] beschikbaar.

Daarin is de code opgenomen voor de nieuwe afdrukvensters. Pluspunten: elk afdrukvenster toont een afdrukvoorbeeld, en biedt direct toegang tot alle instellingen.
Lees daarover meer op [http://blogs.sun.com/GullFOSS/entry/new_print_ui_now_integrated GullFoss].

Het is een heel nieuw stuk in OpenOffice.org, dat stevig aan de tand moet worden gevoeld voor de 3.3.0 uit komt. Je kunt deze snapshot downloaden en installeren naast je normale OpenOffice.org versie. (Zie de uitleg elders op deze wiki-pagina.)

== Meer over de achtereenvolgende versies in de ontwikkelcyclus ==

=== Developer builds (snapshots) ===
Zijn redelijk stabiel, maar worden niet aangeraden voor dagelijks werk. 
Installeert apart, naast de normale versie van OpenOffice.org. 
Op de OOo-site staan de nieuwste [http://download.openoffice.org/next/other.htm developer builds], maar die zijn niet in het Nederlands beschikbaar. Op die pagina's is onder de link 'Release Notes' ook een verwijzing naar informatie over de nieuwe functies.

=== Beta versies ===
Het product is bijna gereed, men verwacht dat het product zonder serieuze problemen gebruikt kan worden. De nieuwe functies worden met de beta-uitgaven door veel mensen gebruikt, wat weer extra reacties oplevert. 
Een beta installeert naast een bestaande versie van OpenOffice.org.
=== Release kandidaten ===
Een release kandidaat verschijnt zodra men verwacht dat het product gereed is. Het is tijd voor de laatste tests. 
Bij het installeren, vervangt de release kandidaat de al geïnstalleerde versie van OpenOffice.org, tenzij er wordt gekozen voor parallelle installatie. Die procedure is elders op deze pagina beschreven: [[NL/TipsEnTrucs/Meerdere_versies_van_OOo_uitvoeren| Meerdere versies van OOo uitvoeren]]. 
Als er geen ernstige problemen meer worden gevonden, zal de release kandidaat als de nieuwe stabliele versie worden vrijgegeven.

=== Goedkeuring voor een nieuwe release ===
Voordat een nieuwe versie officieel wordt vrijgegeven, moet er natuurlijk wel wat gebeuren.
Op [[Release_Action_List_for_QA#Approval_of_Builds | deze plek]] staat hoe dat in zijn werk gaat.

== Meerdere versies en talen installeren ==

=== Meerdere versies installeren===
Het is verstandig om de diverse (testversies) naast je huidige OpenOffice.org te installeren. Je kunt dan ook makkelijk functies vergelijken. Op [[NL/TipsEnTrucs/Meerdere_versies_van_OOo_uitvoeren| Meerdere versies van OOo uitvoeren]] staat uitgelegd hoe dat werkt. Kom je ergens niet uit? Mail dan naar [mailto:localization@nl.openoffice.org localization@nl.openoffice.org]

=== Taalversies ===
Het is ook mogelijk om een niet Nederlandse versie van OpenOffice.org (bijv. Engels) te installeren en dan een taalpakket (language pack) voor Nederlands.
Als eerst de volledige versie wordt geïnstalleerd en dan (snelstarter uit!) het Nederlandse taalpakket, kan in Tools>Options>Language settings>Language 'Nederlands' worden gekozen voor de gebruikers interface. Al de menu's, vensters en Help worden dan Engels- of Nederlandstalig.

== Hoe testen ==

=== Inleiding ===
Het zoeken (en oplossen) van fouten gebeurt in verschillende fasen.
* Tijdens de ontwikkeling door het testen van en werken met de developer-builds en beta-releases.
* Bij release-kandidaten gaat het alleen nog om het vinden en corrigeren van echt grote problemen.
* Van de laatste release kandidaat moet ook voor de Nederlandstalige versie een akkoord worden gegeven, alvorens die kan worden vrijgegeven.

=== Geautomatiseerd testen ===
Volgens testplannen worden allemaal functies geautomatiseerd uitgevoerd.
Dit is een doorlopend proces en gebeurt (vooral door de mensen van Sun en RedFlag) dus ook in een vroeg stadium.

Voor de geïnteresseerden, is er de nodige informatie, zoals over de [[Testtool|testtool]] voor geautomatiseerd testen en over het eventueel vertalen daarvan: [[HowTo_localize_qatesttool_environment|how to localiza it]].

=== Testen met TCM ===
Testen volgens TCM is vooral nuttig voor het controleren van nieuwe functies, en tijdens het testen van release-kandidaten.
* Nieuwe functies moeten in een redelijk vroeg stadium worden getest, uiterlijk met een beta-versie, en niet met de release-kandidaten. Bij release kandidaten worden alleen nog heel ernstige bugs gecorrigeerd, en niet als een nieuwe functie niet helemaal perfect werkt ...
* Testen volgens TCM geeft ook een houvast voor het testen van hoofdfuncties, die wel moeten worden gecontroleerd bij een release-kandidaat.

====Localisatie testen van nieuwe uitgaven van OOo====
Voordat je resultaten van je testen kunt invoeren in TCM, of kunt TCM gebruiken voor testideeën, moet je als gebruiker aan TCM worden toegevoegd. 
Mail daarvoor naar [mailto:localization@nl.openoffice.org de localisatie lijst] of naar één van de andere actieve projectleden.
* De startpagina van TCM is [http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_login.cgi?tcm_config=newooo hier].
* Je kunt daar inloggen met username en password
* Ga dan door op stap 5: Test Result Update
* Kies de versie van OOo, de tests die op jouw naam staan, etc.
** Bijvoorbeeld: Klik op 'OpenOffice.org(3.2RC)' in de kolom 'Build Number'
** Zoek in de volgende tabel de regel met je inlognaam.
** Klik in die regel op 'Scenario(Release sanity scenario)'
** Er zijn dan meer dan 20 test beschikbaar.
het is niet altijd nodig dat iedere tester elke test doet ...
het zijn geen ingewikkelde tests, maar kies eventueel dus tests die je graag doet, of overleg per mail met anderen.
** Bij een uitgevoerde test invullen: pass, fail of skip, en voer eventueel commentaar in
** Je kunt ook kijken naar de linkjes naar al eerder gevonden bugs.
*** Het is goed mogelijk dat daar al opgeloste bugs tussen staan - het is nog niet geregeld dat die worden verwijderd/gefilterd.
over criteria om een test op fail te zetten:
dat gebeurt niet om kleinere problemen, alleen als iets echt goed fout zit
vul evt. commentaar in. En al weer: bij vragen is er op de mail lijst altijd hulp!

Vragen, opmerkingen, suggesties welkom!

Zeer nuttige uitgebreide informatie staat in de wiki op de [[Test_Case_Management|de TCM pagina]] en in de uitleg over TCM/testen en de release cyclus [[Release Action List for QA]]

===Minimale check op gelocaliseerde versies===
Wanneer het niet mogelijk is om alle TCM tests te doen, kan worden terug gevallan op een [[NL/QA/SanityCheck_van_Localisaties | lijst met minimale tests]] voor de vrijgave.

Maar we moeten er om denken, dat als iedereen alleen maar 'minimaal' gaat zitten testen, we gauw een probleem hebben ..

=== Testen door er mee te werken ===
Dit kan iedereen doen. Snapshots en beta-versies downloaden en er mee aan de slag gaan.

=== Je ervaringen delen ===
Als je bijzonderheden tegenkomt - meestal fouten ;-) - dan is het de bedoeling dat die in Issuetracker worden geplaatst. Of dat je met je waarneming een issue van een ander bevestigt, of verduidelijkt, of nuanceert.

Informatie voor het gebruiken van Issuetracker staat [http://nl.openoffice.org/about-issuezilla.html hier].

Vaak is het handig om ervaringen te bespreken voordat je de moeite neemt om een issue te maken. Soms heeft iemand anders al een antwoord of issue, of is het probleem in een nieuwe snapshot opgelost. Dat scheelt je dan weer het aanmaken van een issue.
En kom je ergens zelf niet uit: vraag het dan gewoon op localization@nl.openoffice.org.

=== Coördinatie van & informatie over testen===
Al enkele keren genoemd: localization@nl.openoffice.org. Dit is de mailinglijst waar alle lijntjes samen komen. Dus het is leuk en nuttig om je daar voor aan te melden ([mailto:localization-subscribe@nl.openoffice.org localization-subscribe@nl.openoffice.org]).

[[Category:NL.OpenOffice.org|QA]]

OOoCon2010Stay

2010-08-16T11:02:56Z

CorNouws: /* CEU Residence Center */

__NOTOC__ {{DISPLAYTITLE:Where do you stay at OOoCon 2010?}}

= Introduction =

In order to plan meetings and have common places to gather together, we'll try to collect all the hotels where OOoCon participants will stay. If it doesn't exist in the list already, please add your hotel and name to the list, if you want to share the information with the public. You can also add your e-mail address and mobile number, if you want people to reach you - the more the merrier ;-)

The OOoCon organizers would like to encourage everyone to add their details to this wiki page. Please note that all information on this wiki is public, and once published, '''cannot''' be removed anymore, not even by the administrators, so be '''careful''' with what you add.

= Stays =

The format of the entries is name, role, e-mail address, mobile phone number, arrival and departure

== Hotel Boutique Bristol, Kenyérmező u. 4. ==
[http://maps.google.de/maps?f=d&source=s_d&saddr=1081+Budapest,+VIII.+ker%C3%BClet,+Keny%C3%A9rmez%C5%91+utca+4,+Ungarn&daddr=1051+Budapest,+N%C3%A1dor+utca+9,+Ungarn&hl=de&geocode=Fd7E1AIdsBgjASkxSDqiYdxBRzHBjYYUAyHm4Q%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=ls&sll=47.498068,19.064498&sspn=0.020963,0.038581&ie=UTF8&ll=47.498648,19.063296&spn=0.020963,0.038581&z=15 Google Map Route to Hotel Boutique Bristol]
*Florian Effenberger, Marketing Project Lead, [mailto:floeff@openoffice.org floeff@openoffice.org], +49 151 14424108, 29-Aug, 4-Sep
*Peter Junge, Marketing Project co-Lead, [mailto:pj@openoffice.org pj@openoffice.org], +49 1578 8615057, 29-Aug, 6-Sep

== Camping Haller, Haller utca 27. ==
[http://maps.google.de/maps?f=d&source=s_d&saddr=Haller+utca&daddr=1051+Budapest,+N%C3%A1dor+utca+9,+Ungarn&hl=de&geocode=Fa9w1AIdKi8jAQ%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=dme&mrcr=0&mrsp=0&sz=16&sll=47.476593,19.0816&sspn=0.010486,0.01929&ie=UTF8&ll=47.489021,19.066257&spn=0.041933,0.077162&z=14 Google Map Route to Camping Haller]
*Stefan Weigel, no rank - not title, [[Special:EmailUser/Stefanw|StefanW]], 31-Aug, 4-Sep

== Hotel Eurostars Center, Kossuth Lajos u. 7-9. ==
[http://maps.google.es/maps?f=d&source=s_d&saddr=1051+Budapest,+N%C3%A1dor+utca+9,+Magyarorsz%C3%A1g+(CEU)&daddr=1053+Budapest,+V.+ker%C3%BClet,+Kossuth+Lajos+utca+7,+Hungr%C3%ADa&hl=es&geocode=FbXM1AIdoasiASFviAnhB6gN3Ckn0F0LFdxBRzEgEaZnEyeKJQ%3BFXmy1AIdd8wiASkvQb2ZQ9xBRzGC63PU5eFNQg&mra=pe&mrcr=0&sll=47.507092,19.066579&sspn=0.246292,0.441513&ie=UTF8&t=h&z=16 Google Map Route to Hotel Eurostars Center]

* Manu Arjó, VicePresident Business Development at [http://www.sironta.com Sironta], [mailto:manuel.arjo@sironta.com manuel.arjo@sironta.com], +34 933 535 627, 2-Sep, 3-Sep

== CEU Residence Center ==
[http://maps.google.com/maps?f=d&source=s_d&saddr=1106+Budapest,+Kerepesi+%FAt+87,+Magyarorsz%E1g&daddr=1051+Budapest,+N%E1dor+utca+9,+Magyarorsz%E1g+(CEU)&geocode=Fd_f1AIdMEokASndS7kXqcRBRzEDYtkELVo0bw%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=prev&sll=47.499835,19.10243&sspn=0.051608,0.154324&ie=UTF8&z=13 Google Map Route to CEU]

* Andrea Pescetti, Italian N-L Project Lead, pescetti@ooo, - , 31 Aug, 3 Sep
* Gustavo Buzzatti Pacheco, BrOffice.org/OpenOffice.org Brazil, [mailto:gbpacheco@openoffice.org gbpacheco@openoffice.org], +555184029927, 29-Aug, 5-Sep
* Leo Moons, Translator/member nl.openoffice.org, Belgian, [mailto:vpanter@openoffice.org vpanter@openoffice.org], +32 475 241646, 30 Aug - 4 Sep
* Cor Nouws, community representative Community Council, marketing nl-OpenOffice.org, owner Nou&Off, Netherlands,[mailto:oolst@nouenoff.nl oolst@nouenoff.nl], + 31 625 207001, 29/30 Aug - 5 Sep

== Alta Moda Fashion Hotel, 13 Nádor Utca 1051. ==
[http://www.splendia.com/en/alta-moda-fashion-hotel-budapest.html#map Map]
* [http://www4.plala.or.jp/k21/ Katsuya Kobayashi], Marketing Project member, [[Special:EmailUser/kynh|kynh]], , 30-Aug, 4-Sep

== Mercure Budapest Duna, Soroksari ut 12 ==

[http://maps.google.com/maps?q=Mercure+Budapest+Duna&hl=en&cd=1&ei=_bliTLXII5DyObH1mBk&vps=2&jsv=264c&sll=47.4793,19.0684&sspn=1.258326,3.140552&ie=UTF8&lr=lang_pt|lang_en&view=map&cid=15417917116959416148&iwloc=A&ved=0CIkBEKUG&sa=X Map]

*Leif Lodahl, Danish language coord, lodahl@openoffice.org
*Paulo Vilela, Marketing OOo Portugal, [mailto:pvilela@openoffice.org pvilela@openoffice.org], +351912591908, 30-Aug to 3- Sep

== Mercure Budapest Buda, Krisztina Korut 41-43 ==

[http://maps.google.com/maps/place?cid=15227343547741076547&q=Mercure+Budapest+Buda+Krisztina+Korut+41-43+Hungary&hl=en&cd=1&ei=-BtjTI7XGYz8Oajx0dUC&sig2=NO51ehG49IYr2_G81o43Hw&dtab=0&sll=47.4987,19.0272&sspn=0.071946,0.1348&ie=UTF8&ll=47.51523,19.000769&spn=0,0&z=14&iwloc=A Map]

*Dmitri Popov, Freelance contributor, [mailto:dmpop@openoffice.org dmpop@openoffice.org], August 30 - September 3

 

[[Category:Marketing]]

OOoCon2010Stay

2010-08-16T10:59:37Z

CorNouws: /* Hotel Eurostars Center, Kossuth Lajos u. 7-9. */

__NOTOC__ {{DISPLAYTITLE:Where do you stay at OOoCon 2010?}}

= Introduction =

In order to plan meetings and have common places to gather together, we'll try to collect all the hotels where OOoCon participants will stay. If it doesn't exist in the list already, please add your hotel and name to the list, if you want to share the information with the public. You can also add your e-mail address and mobile number, if you want people to reach you - the more the merrier ;-)

The OOoCon organizers would like to encourage everyone to add their details to this wiki page. Please note that all information on this wiki is public, and once published, '''cannot''' be removed anymore, not even by the administrators, so be '''careful''' with what you add.

= Stays =

The format of the entries is name, role, e-mail address, mobile phone number, arrival and departure

== Hotel Boutique Bristol, Kenyérmező u. 4. ==
[http://maps.google.de/maps?f=d&source=s_d&saddr=1081+Budapest,+VIII.+ker%C3%BClet,+Keny%C3%A9rmez%C5%91+utca+4,+Ungarn&daddr=1051+Budapest,+N%C3%A1dor+utca+9,+Ungarn&hl=de&geocode=Fd7E1AIdsBgjASkxSDqiYdxBRzHBjYYUAyHm4Q%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=ls&sll=47.498068,19.064498&sspn=0.020963,0.038581&ie=UTF8&ll=47.498648,19.063296&spn=0.020963,0.038581&z=15 Google Map Route to Hotel Boutique Bristol]
*Florian Effenberger, Marketing Project Lead, [mailto:floeff@openoffice.org floeff@openoffice.org], +49 151 14424108, 29-Aug, 4-Sep
*Peter Junge, Marketing Project co-Lead, [mailto:pj@openoffice.org pj@openoffice.org], +49 1578 8615057, 29-Aug, 6-Sep

== Camping Haller, Haller utca 27. ==
[http://maps.google.de/maps?f=d&source=s_d&saddr=Haller+utca&daddr=1051+Budapest,+N%C3%A1dor+utca+9,+Ungarn&hl=de&geocode=Fa9w1AIdKi8jAQ%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=dme&mrcr=0&mrsp=0&sz=16&sll=47.476593,19.0816&sspn=0.010486,0.01929&ie=UTF8&ll=47.489021,19.066257&spn=0.041933,0.077162&z=14 Google Map Route to Camping Haller]
*Stefan Weigel, no rank - not title, [[Special:EmailUser/Stefanw|StefanW]], 31-Aug, 4-Sep

== Hotel Eurostars Center, Kossuth Lajos u. 7-9. ==
[http://maps.google.es/maps?f=d&source=s_d&saddr=1051+Budapest,+N%C3%A1dor+utca+9,+Magyarorsz%C3%A1g+(CEU)&daddr=1053+Budapest,+V.+ker%C3%BClet,+Kossuth+Lajos+utca+7,+Hungr%C3%ADa&hl=es&geocode=FbXM1AIdoasiASFviAnhB6gN3Ckn0F0LFdxBRzEgEaZnEyeKJQ%3BFXmy1AIdd8wiASkvQb2ZQ9xBRzGC63PU5eFNQg&mra=pe&mrcr=0&sll=47.507092,19.066579&sspn=0.246292,0.441513&ie=UTF8&t=h&z=16 Google Map Route to Hotel Eurostars Center]

* Manu Arjó, VicePresident Business Development at [http://www.sironta.com Sironta], [mailto:manuel.arjo@sironta.com manuel.arjo@sironta.com], +34 933 535 627, 2-Sep, 3-Sep

== CEU Residence Center ==
[http://maps.google.com/maps?f=d&source=s_d&saddr=1106+Budapest,+Kerepesi+%FAt+87,+Magyarorsz%E1g&daddr=1051+Budapest,+N%E1dor+utca+9,+Magyarorsz%E1g+(CEU)&geocode=Fd_f1AIdMEokASndS7kXqcRBRzEDYtkELVo0bw%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=prev&sll=47.499835,19.10243&sspn=0.051608,0.154324&ie=UTF8&z=13 Google Map Route to CEU]

* Andrea Pescetti, Italian N-L Project Lead, pescetti@ooo, - , 31 Aug, 3 Sep
* Gustavo Buzzatti Pacheco, BrOffice.org/OpenOffice.org Brazil, [mailto:gbpacheco@openoffice.org gbpacheco@openoffice.org], +555184029927, 29-Aug, 5-Sep
* Leo Moons, Translator/member nl.openoffice.org, Belgian, [mailto:vpanter@openoffice.org vpanter@openoffice.org], +32 475 241646, 30 Aug - 4 Sep

== Alta Moda Fashion Hotel, 13 Nádor Utca 1051. ==
[http://www.splendia.com/en/alta-moda-fashion-hotel-budapest.html#map Map]
* [http://www4.plala.or.jp/k21/ Katsuya Kobayashi], Marketing Project member, [[Special:EmailUser/kynh|kynh]], , 30-Aug, 4-Sep

== Mercure Budapest Duna, Soroksari ut 12 ==

[http://maps.google.com/maps?q=Mercure+Budapest+Duna&hl=en&cd=1&ei=_bliTLXII5DyObH1mBk&vps=2&jsv=264c&sll=47.4793,19.0684&sspn=1.258326,3.140552&ie=UTF8&lr=lang_pt|lang_en&view=map&cid=15417917116959416148&iwloc=A&ved=0CIkBEKUG&sa=X Map]

*Leif Lodahl, Danish language coord, lodahl@openoffice.org
*Paulo Vilela, Marketing OOo Portugal, [mailto:pvilela@openoffice.org pvilela@openoffice.org], +351912591908, 30-Aug to 3- Sep

== Mercure Budapest Buda, Krisztina Korut 41-43 ==

[http://maps.google.com/maps/place?cid=15227343547741076547&q=Mercure+Budapest+Buda+Krisztina+Korut+41-43+Hungary&hl=en&cd=1&ei=-BtjTI7XGYz8Oajx0dUC&sig2=NO51ehG49IYr2_G81o43Hw&dtab=0&sll=47.4987,19.0272&sspn=0.071946,0.1348&ie=UTF8&ll=47.51523,19.000769&spn=0,0&z=14&iwloc=A Map]

*Dmitri Popov, Freelance contributor, [mailto:dmpop@openoffice.org dmpop@openoffice.org], August 30 - September 3

 

[[Category:Marketing]]

OOoCon2010Stay

2010-08-16T10:59:19Z

CorNouws: /* Camping Haller, Haller utca 27. */

__NOTOC__ {{DISPLAYTITLE:Where do you stay at OOoCon 2010?}}

= Introduction =

In order to plan meetings and have common places to gather together, we'll try to collect all the hotels where OOoCon participants will stay. If it doesn't exist in the list already, please add your hotel and name to the list, if you want to share the information with the public. You can also add your e-mail address and mobile number, if you want people to reach you - the more the merrier ;-)

The OOoCon organizers would like to encourage everyone to add their details to this wiki page. Please note that all information on this wiki is public, and once published, '''cannot''' be removed anymore, not even by the administrators, so be '''careful''' with what you add.

= Stays =

The format of the entries is name, role, e-mail address, mobile phone number, arrival and departure

== Hotel Boutique Bristol, Kenyérmező u. 4. ==
[http://maps.google.de/maps?f=d&source=s_d&saddr=1081+Budapest,+VIII.+ker%C3%BClet,+Keny%C3%A9rmez%C5%91+utca+4,+Ungarn&daddr=1051+Budapest,+N%C3%A1dor+utca+9,+Ungarn&hl=de&geocode=Fd7E1AIdsBgjASkxSDqiYdxBRzHBjYYUAyHm4Q%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=ls&sll=47.498068,19.064498&sspn=0.020963,0.038581&ie=UTF8&ll=47.498648,19.063296&spn=0.020963,0.038581&z=15 Google Map Route to Hotel Boutique Bristol]
*Florian Effenberger, Marketing Project Lead, [mailto:floeff@openoffice.org floeff@openoffice.org], +49 151 14424108, 29-Aug, 4-Sep
*Peter Junge, Marketing Project co-Lead, [mailto:pj@openoffice.org pj@openoffice.org], +49 1578 8615057, 29-Aug, 6-Sep

== Camping Haller, Haller utca 27. ==
[http://maps.google.de/maps?f=d&source=s_d&saddr=Haller+utca&daddr=1051+Budapest,+N%C3%A1dor+utca+9,+Ungarn&hl=de&geocode=Fa9w1AIdKi8jAQ%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=dme&mrcr=0&mrsp=0&sz=16&sll=47.476593,19.0816&sspn=0.010486,0.01929&ie=UTF8&ll=47.489021,19.066257&spn=0.041933,0.077162&z=14 Google Map Route to Camping Haller]
*Stefan Weigel, no rank - not title, [[Special:EmailUser/Stefanw|StefanW]], 31-Aug, 4-Sep

== Hotel Eurostars Center, Kossuth Lajos u. 7-9. ==
[http://maps.google.es/maps?f=d&source=s_d&saddr=1051+Budapest,+N%C3%A1dor+utca+9,+Magyarorsz%C3%A1g+(CEU)&daddr=1053+Budapest,+V.+ker%C3%BClet,+Kossuth+Lajos+utca+7,+Hungr%C3%ADa&hl=es&geocode=FbXM1AIdoasiASFviAnhB6gN3Ckn0F0LFdxBRzEgEaZnEyeKJQ%3BFXmy1AIdd8wiASkvQb2ZQ9xBRzGC63PU5eFNQg&mra=pe&mrcr=0&sll=47.507092,19.066579&sspn=0.246292,0.441513&ie=UTF8&t=h&z=16 Google Map Route to CEU]

* Manu Arjó, VicePresident Business Development at [http://www.sironta.com Sironta], [mailto:manuel.arjo@sironta.com manuel.arjo@sironta.com], +34 933 535 627, 2-Sep, 3-Sep

== CEU Residence Center ==
[http://maps.google.com/maps?f=d&source=s_d&saddr=1106+Budapest,+Kerepesi+%FAt+87,+Magyarorsz%E1g&daddr=1051+Budapest,+N%E1dor+utca+9,+Magyarorsz%E1g+(CEU)&geocode=Fd_f1AIdMEokASndS7kXqcRBRzEDYtkELVo0bw%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=prev&sll=47.499835,19.10243&sspn=0.051608,0.154324&ie=UTF8&z=13 Google Map Route to CEU]

* Andrea Pescetti, Italian N-L Project Lead, pescetti@ooo, - , 31 Aug, 3 Sep
* Gustavo Buzzatti Pacheco, BrOffice.org/OpenOffice.org Brazil, [mailto:gbpacheco@openoffice.org gbpacheco@openoffice.org], +555184029927, 29-Aug, 5-Sep
* Leo Moons, Translator/member nl.openoffice.org, Belgian, [mailto:vpanter@openoffice.org vpanter@openoffice.org], +32 475 241646, 30 Aug - 4 Sep

== Alta Moda Fashion Hotel, 13 Nádor Utca 1051. ==
[http://www.splendia.com/en/alta-moda-fashion-hotel-budapest.html#map Map]
* [http://www4.plala.or.jp/k21/ Katsuya Kobayashi], Marketing Project member, [[Special:EmailUser/kynh|kynh]], , 30-Aug, 4-Sep

== Mercure Budapest Duna, Soroksari ut 12 ==

[http://maps.google.com/maps?q=Mercure+Budapest+Duna&hl=en&cd=1&ei=_bliTLXII5DyObH1mBk&vps=2&jsv=264c&sll=47.4793,19.0684&sspn=1.258326,3.140552&ie=UTF8&lr=lang_pt|lang_en&view=map&cid=15417917116959416148&iwloc=A&ved=0CIkBEKUG&sa=X Map]

*Leif Lodahl, Danish language coord, lodahl@openoffice.org
*Paulo Vilela, Marketing OOo Portugal, [mailto:pvilela@openoffice.org pvilela@openoffice.org], +351912591908, 30-Aug to 3- Sep

== Mercure Budapest Buda, Krisztina Korut 41-43 ==

[http://maps.google.com/maps/place?cid=15227343547741076547&q=Mercure+Budapest+Buda+Krisztina+Korut+41-43+Hungary&hl=en&cd=1&ei=-BtjTI7XGYz8Oajx0dUC&sig2=NO51ehG49IYr2_G81o43Hw&dtab=0&sll=47.4987,19.0272&sspn=0.071946,0.1348&ie=UTF8&ll=47.51523,19.000769&spn=0,0&z=14&iwloc=A Map]

*Dmitri Popov, Freelance contributor, [mailto:dmpop@openoffice.org dmpop@openoffice.org], August 30 - September 3

 

[[Category:Marketing]]

OOoCon2010Stay

2010-08-16T10:59:02Z

CorNouws: /* Hotel Boutique Bristol, Kenyérmező u. 4. */

__NOTOC__ {{DISPLAYTITLE:Where do you stay at OOoCon 2010?}}

= Introduction =

In order to plan meetings and have common places to gather together, we'll try to collect all the hotels where OOoCon participants will stay. If it doesn't exist in the list already, please add your hotel and name to the list, if you want to share the information with the public. You can also add your e-mail address and mobile number, if you want people to reach you - the more the merrier ;-)

The OOoCon organizers would like to encourage everyone to add their details to this wiki page. Please note that all information on this wiki is public, and once published, '''cannot''' be removed anymore, not even by the administrators, so be '''careful''' with what you add.

= Stays =

The format of the entries is name, role, e-mail address, mobile phone number, arrival and departure

== Hotel Boutique Bristol, Kenyérmező u. 4. ==
[http://maps.google.de/maps?f=d&source=s_d&saddr=1081+Budapest,+VIII.+ker%C3%BClet,+Keny%C3%A9rmez%C5%91+utca+4,+Ungarn&daddr=1051+Budapest,+N%C3%A1dor+utca+9,+Ungarn&hl=de&geocode=Fd7E1AIdsBgjASkxSDqiYdxBRzHBjYYUAyHm4Q%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=ls&sll=47.498068,19.064498&sspn=0.020963,0.038581&ie=UTF8&ll=47.498648,19.063296&spn=0.020963,0.038581&z=15 Google Map Route to Hotel Boutique Bristol]
*Florian Effenberger, Marketing Project Lead, [mailto:floeff@openoffice.org floeff@openoffice.org], +49 151 14424108, 29-Aug, 4-Sep
*Peter Junge, Marketing Project co-Lead, [mailto:pj@openoffice.org pj@openoffice.org], +49 1578 8615057, 29-Aug, 6-Sep

== Camping Haller, Haller utca 27. ==
[http://maps.google.de/maps?f=d&source=s_d&saddr=Haller+utca&daddr=1051+Budapest,+N%C3%A1dor+utca+9,+Ungarn&hl=de&geocode=Fa9w1AIdKi8jAQ%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=dme&mrcr=0&mrsp=0&sz=16&sll=47.476593,19.0816&sspn=0.010486,0.01929&ie=UTF8&ll=47.489021,19.066257&spn=0.041933,0.077162&z=14 Google Map Route to CEU]
*Stefan Weigel, no rank - not title, [[Special:EmailUser/Stefanw|StefanW]], 31-Aug, 4-Sep

== Hotel Eurostars Center, Kossuth Lajos u. 7-9. ==
[http://maps.google.es/maps?f=d&source=s_d&saddr=1051+Budapest,+N%C3%A1dor+utca+9,+Magyarorsz%C3%A1g+(CEU)&daddr=1053+Budapest,+V.+ker%C3%BClet,+Kossuth+Lajos+utca+7,+Hungr%C3%ADa&hl=es&geocode=FbXM1AIdoasiASFviAnhB6gN3Ckn0F0LFdxBRzEgEaZnEyeKJQ%3BFXmy1AIdd8wiASkvQb2ZQ9xBRzGC63PU5eFNQg&mra=pe&mrcr=0&sll=47.507092,19.066579&sspn=0.246292,0.441513&ie=UTF8&t=h&z=16 Google Map Route to CEU]

* Manu Arjó, VicePresident Business Development at [http://www.sironta.com Sironta], [mailto:manuel.arjo@sironta.com manuel.arjo@sironta.com], +34 933 535 627, 2-Sep, 3-Sep

== CEU Residence Center ==
[http://maps.google.com/maps?f=d&source=s_d&saddr=1106+Budapest,+Kerepesi+%FAt+87,+Magyarorsz%E1g&daddr=1051+Budapest,+N%E1dor+utca+9,+Magyarorsz%E1g+(CEU)&geocode=Fd_f1AIdMEokASndS7kXqcRBRzEDYtkELVo0bw%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=prev&sll=47.499835,19.10243&sspn=0.051608,0.154324&ie=UTF8&z=13 Google Map Route to CEU]

* Andrea Pescetti, Italian N-L Project Lead, pescetti@ooo, - , 31 Aug, 3 Sep
* Gustavo Buzzatti Pacheco, BrOffice.org/OpenOffice.org Brazil, [mailto:gbpacheco@openoffice.org gbpacheco@openoffice.org], +555184029927, 29-Aug, 5-Sep
* Leo Moons, Translator/member nl.openoffice.org, Belgian, [mailto:vpanter@openoffice.org vpanter@openoffice.org], +32 475 241646, 30 Aug - 4 Sep

== Alta Moda Fashion Hotel, 13 Nádor Utca 1051. ==
[http://www.splendia.com/en/alta-moda-fashion-hotel-budapest.html#map Map]
* [http://www4.plala.or.jp/k21/ Katsuya Kobayashi], Marketing Project member, [[Special:EmailUser/kynh|kynh]], , 30-Aug, 4-Sep

== Mercure Budapest Duna, Soroksari ut 12 ==

[http://maps.google.com/maps?q=Mercure+Budapest+Duna&hl=en&cd=1&ei=_bliTLXII5DyObH1mBk&vps=2&jsv=264c&sll=47.4793,19.0684&sspn=1.258326,3.140552&ie=UTF8&lr=lang_pt|lang_en&view=map&cid=15417917116959416148&iwloc=A&ved=0CIkBEKUG&sa=X Map]

*Leif Lodahl, Danish language coord, lodahl@openoffice.org
*Paulo Vilela, Marketing OOo Portugal, [mailto:pvilela@openoffice.org pvilela@openoffice.org], +351912591908, 30-Aug to 3- Sep

== Mercure Budapest Buda, Krisztina Korut 41-43 ==

[http://maps.google.com/maps/place?cid=15227343547741076547&q=Mercure+Budapest+Buda+Krisztina+Korut+41-43+Hungary&hl=en&cd=1&ei=-BtjTI7XGYz8Oajx0dUC&sig2=NO51ehG49IYr2_G81o43Hw&dtab=0&sll=47.4987,19.0272&sspn=0.071946,0.1348&ie=UTF8&ll=47.51523,19.000769&spn=0,0&z=14&iwloc=A Map]

*Dmitri Popov, Freelance contributor, [mailto:dmpop@openoffice.org dmpop@openoffice.org], August 30 - September 3

 

[[Category:Marketing]]

Community Council/Agenda

2010-08-12T18:26:01Z

CorNouws: /* Agenda and Work Status */

{{Community_Council}}
== Upcoming Meeting ==

Date: 2010-08-12 (Derived from the [[Community Council/Calendar|Community Council Meeting Calendar]])

Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=12&month=08&year=2010&hour=18&min=30&sec=0&p1=0 18.30 UTC] (click on the link to show world clock times)

Location: IRC

== Agenda and Work Status ==

The following table represents the agenda of the upcoming meeting and the current work status of topics / action items. Working with this table is described in the [[Community Council/Meeting Guidelines|Community Council Meeting Guidelines]].

{| class="prettytable sortable"
|-
! scope="col" | ID 
! scope="col" | Topic 
! scope="col" | Status 
! scope="col" | Responsible 
! scope="col" | Last Update 
! scope="col" | Details 
|-
| 0 
| List of Action Items of previous meeting for approval 
| ''none'' 
| all 
| 2010-07-24 
|
*Meeting minutes of previous meeting at [[Community Council/Minutes#2010-07-22|Minutes#2010-07-22]] 
*Result: (to be confirmed)

|-
| 2010-03-04#2 
| Refresh Incubator and NLC Project processes 
| Accepted 
| Louis 
| 2010-03-18 
|
*No new proposal available. Louis will work on that. 
*Next steps: Will be discussed in next meeting.

|-
| 2010-03-04#3 
| Publicize the open slot at the start of the CC meetings 
| Accepted 
| Juergen 
| 2010-08-12 
|
*History:
**Proposal had been presented on March 30th and agreed on 
**Martin to prepare announcement on discuss before next meeting -- AI transferred to Jürgen
*Activities: 
**add new section under '''Procedures''' in the meeting guideline, see [[Community Council/Meeting Guidelines#Public_QA|Meeting Guidelines - Public QA]]
**add 2 new public QA session in the meeting calendar, see [[Community Council/Calendar#Meetings_in_2010|Meetings in 2010]]
**post information email to council-discuss
*After the first session, improvements required for:
**Naming seems to be ambiguous (QA and Q&A are already project names, proposals: "Ask the Community Council", "Discuss with the Community Council", "Community and Council",  "Questions-and-Answers Session")
**Wider announcement of the Questions-and-Answers session (proposal: discuss@ooo, dev@ooo, NLCs should also announce it, Blog?)
**Exact begin of the open slot (it was unclear whether it should start 30 minutes before the official CC session or starts at the usual CC time)
*Next Steps: Ask Juergen to work on the improvements.
* Updated the meeting guidelines and change the name of our public session, [[Community Council/Meeting Guidelines#|Meet_the_Community_Council|Meet the Community Council]]. Add a note for a public reminder and provide an initial template for the reminder ([[Community_Council/Meeting_Guidelines/Public_Invitation_Reminder_Template|Public Invitation Reminder Template]]).
|-
| 2010-03-04#6 
| Talk to Education Project Leads about structure and remit 
| Stalled 
| John, Cor 
| 2010-03-18 
|
*Cor to prepare a draft and present it to the Community Council. Nothing done yet.
*Next steps: Will be discussed in next meeting. 

|-
| 2010-04-01#7 
| Talk to NLC about ‘NLC of the Month’ for OOo Newsletter 
| Accepted 
| Charles 
| 2010-04-01 
|
*Inteview with the Irish team has been done. No further information available by his deputy (Leif). 
*Next steps: Few projects agree to respond to the interview for the NLC project of the month. This month the Hungarian team will be highlighted for obvious reasons, and in September the Italian community is scheduled. 

|-
| 2010-04-01#1 
| Community situation 
| Accepted 
| All 
| 2010-07-22 
|
*What do we see, where are we, what are we going to do about it. 
*Activities:
**All CC members are asked to think about it and Cor will prepare a proposal for an detailed agenda. 
**Leif already collected some issues (e.g. rare communication via blogs) and will send that to Cor. 
*Next Steps: Proposal that the CC will work on that at the OOoCon in Budapest.
** Cor send a mail on 2010-08-12 with some items for the agenda.
|-
| 2010-04-29#2 
|
Missing OOo desktop presence

| Accepted 
| Christoph, Stefan
| 2010-07-22 
|
*Request by a community member to discuss / decide the following question: "''Why should OpenOffice.org give away it's presence on the user's desktop - the main place to be recognized by the people - only to support the "application independency" of ODF?'' A Sun employee stated "The idea of supporting ODF as a application independent open standard is the priority." This leads / will lead to changes with regard to the document and application icon design. The current ODF "only" icons seem to be undesired by the community. Original request to the CC on ooo-discuss: [http://www.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=65958 initial mail (2010-04-14)], [http://www.openoffice.org/servlets/BrowseList?listName=discuss&from=2361081&to=2361081&count=28&by=thread&first=1&windowSize=1000 full mail thread]
*Discussion:
**2010-04-29: Some members stated that the request should be "more actionable" and "better framed" to be decided by the community. Proposal has been made to forward the request to council-discuss to propose how to proceed.
**2010-05-02: Christoph forwarded the [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2564 request to the CC mailing list]. A first discussion took place.
**2010-05-20: Intensive discussion about the request and how to address it. Stefan and Christoph agreed to work out a request to the ODF Icons team to iterate on the design and/or processes. Maybe a "refreshed" team which may provide an agreed-upon proposal. Stefan stated that there shouldn't be any dependency to the next/other releases.
**2010-06-08: Some opinions have been requested from people who initially worked in the branding initiative. Either there isn't feedback yet, or the people aren't currently available to support the i-Team. Ongoing ...
**2010-06-30: Still ongoing ...
**2010-07-22: Andreas provided some insight what currently happens within Oracle. The topic "icons" is currently addressed ...
***A discussion took place with Michael Bemmer and other people at Oracle.
***Outcome: Oracle marketing made a decision that is supposed to be communicated shortly. --> Icons will be redesigned, for the long run, with constraints.
***Motivation: The current design fails with regard to usability aspects. --> Redesign is intended with focus on usability.
***Constraints: The activity will be run open with all necessary involvements.
***Question to Andreas/Martin to discuss whether the official statement may be discussed with the community before it is going to be published "officially".
***Decision to keep this CC Action Item open until there is more visible activity.
*Next steps: Waiting for the reaction by Oracle, either getting in touch with the community or an official announcement. 

|}

 

== Minutes of Previous Meetings ==

To be found [[Community Council/Minutes|here]].

[[Category:Community_Council]]

NL/QA/Testen

2010-07-26T21:36:46Z

CorNouws: /* Versie voor testen vertaling 3.3.0 beschikbaar */

== Werken met nog niet officiële versies van OpenOffice.org ==

=== Waarom ===
* Het is leuk om de nieuwste ontwikkelingen op de voet te volgen ...
* Hoe eerder fouten in de software worden ontdekt, bij voorkeur nog voor de beta-versies, hoe makkelijker het is om ze te repareren. 
OpenOffice.org brengt vier keer per jaar een nieuwe versie uit (twee keer met nieuwe functies en twee keer met alleen verbeteringen). Er is dus steeds veel nieuws te beleven en te testen.

In de ontwikkelcyclus van het product zijn achtereenvolgens de volgende versies, stadia, te onderscheiden:
* developer builds (snapshots) - om de paar weken;
* beta versies - tegen de tijd dat de nieuwe versie bijna klaar is;
* release kandidaten - een release kandidaat kan de uiteindelijke nieuwe versie worden;
* stabiele versies

Het testen kan heel gestructureerd, maar ook door de software gewoon te installeren en er mee te werken en dan kijken wat voor bijzonderheden je aantreft. Meer hierover verder op deze pagina.
Testen kan heel leuk zijn, want je leert er vaak weer wat van en kunt zelf snel met de nieuwste functies aan de slag. En het helpt om zo vroeg mogelijk zoveel mogelijk fouten op te sporen. Kortom: hulp met testen is altijd welkom!

== Nu beschikbaar om te proberen en te testen ==

===Algemeen: downloaden===
Snapshots enzovoorts zijn steeds te vinden via [http://download.openoffice.org/next/ http://download.openoffice.org/next/]. Rechts op die pagina staan ook verwijzingen naar nuttige aanvullende uitleg. 
Controle van de integriteit van de downloads kan met de MD5 CheckSum test. Uitleg en controle-getallen zijn altijd te vinden op de [http://download.openoffice.org/next/md5sums/ md5sums]-pagina.

=== Versie voor testen vertaling 3.3.0 beschikbaar ===
Op 26 juli is de test-versie met de vertaling voor OpenOffice.org 3.3.0 beschikbaar gekomen. Te downloaden van [http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/ooo330l10n/ deze pagina]. (Voor Linux zijn alleen de taalpakketten en een complete eng-GB versie beschikbaar.) 
Er is in het Engels al informatie over de functies [[Feature_Freeze_Testing_3.3 | beschikbaar]]. 
Heb je zin om in het Nederlands gebruikers-informatie te maken, neem dan even contact op.. Dank!

(Diverse info: [[OOoRelease33]], [[Translation_for_3.3]])

===Beta voor 3.3.0 gaat er aan komen===
De beta voor OpenOffice.org 3.3.0 wordt medio augustus verwacht! De developer snapshots (DEV300_m82 en nieuwer) laten al veel van de nieuwe functies zien!

===Snapshots voor de 3.4.x===
Sinds in juli 2010 de tak voor de 3.3.x is losgemaakt uit de hoofdstam, wordt de lijn DEV300 verder ontwikkeld richting 3.4.0 etc.

Nieuwsgierig? De eerste snapshots zijn via [http://download.openoffice.org/next/ http://download.openoffice.org/next/] te vinden.

===Snapshot met nieuwe afdrukvensters - Belangrijke mijlplaal in de ontwikkeling van versie 3.3.0!===
Sinds half januari is Developer build [http://download.openoffice.org/next/ DEV300 m70] beschikbaar.

Daarin is de code opgenomen voor de nieuwe afdrukvensters. Pluspunten: elk afdrukvenster toont een afdrukvoorbeeld, en biedt direct toegang tot alle instellingen.
Lees daarover meer op [http://blogs.sun.com/GullFOSS/entry/new_print_ui_now_integrated GullFoss].

Het is een heel nieuw stuk in OpenOffice.org, dat stevig aan de tand moet worden gevoeld voor de 3.3.0 uit komt. Je kunt deze snapshot downloaden en installeren naast je normale OpenOffice.org versie. (Zie de uitleg elders op deze wiki-pagina.)

== Meer over de achtereenvolgende versies in de ontwikkelcyclus ==

=== Developer builds (snapshots) ===
Zijn redelijk stabiel, maar worden niet aangeraden voor dagelijks werk. 
Installeert apart, naast de normale versie van OpenOffice.org. 
Op de OOo-site staan de nieuwste [http://download.openoffice.org/next/other.htm developer builds], maar die zijn niet in het Nederlands beschikbaar. Op die pagina's is onder de link 'Release Notes' ook een verwijzing naar informatie over de nieuwe functies.

=== Beta versies ===
Het product is bijna gereed, men verwacht dat het product zonder serieuze problemen gebruikt kan worden. De nieuwe functies worden met de beta-uitgaven door veel mensen gebruikt, wat weer extra reacties oplevert. 
Een beta installeert naast een bestaande versie van OpenOffice.org.
=== Release kandidaten ===
Een release kandidaat verschijnt zodra men verwacht dat het product gereed is. Het is tijd voor de laatste tests. 
Bij het installeren, vervangt de release kandidaat de al geïnstalleerde versie van OpenOffice.org, tenzij er wordt gekozen voor parallelle installatie. Die procedure is elders op deze pagina beschreven: [[NL/TipsEnTrucs/Meerdere_versies_van_OOo_uitvoeren| Meerdere versies van OOo uitvoeren]]. 
Als er geen ernstige problemen meer worden gevonden, zal de release kandidaat als de nieuwe stabliele versie worden vrijgegeven.

=== Goedkeuring voor een nieuwe release ===
Voordat een nieuwe versie officieel wordt vrijgegeven, moet er natuurlijk wel wat gebeuren.
Op [[Release_Action_List_for_QA#Approval_of_Builds | deze plek]] staat hoe dat in zijn werk gaat.

== Meerdere versies en talen installeren ==

=== Meerdere versies installeren===
Het is verstandig om de diverse (testversies) naast je huidige OpenOffice.org te installeren. Je kunt dan ook makkelijk functies vergelijken. Op [[NL/TipsEnTrucs/Meerdere_versies_van_OOo_uitvoeren| Meerdere versies van OOo uitvoeren]] staat uitgelegd hoe dat werkt. Kom je ergens niet uit? Mail dan naar [mailto:localization@nl.openoffice.org localization@nl.openoffice.org]

=== Taalversies ===
Het is ook mogelijk om een niet Nederlandse versie van OpenOffice.org (bijv. Engels) te installeren en dan een taalpakket (language pack) voor Nederlands.
Als eerst de volledige versie wordt geïnstalleerd en dan (snelstarter uit!) het Nederlandse taalpakket, kan in Tools>Options>Language settings>Language 'Nederlands' worden gekozen voor de gebruikers interface. Al de menu's, vensters en Help worden dan Engels- of Nederlandstalig.

== Hoe testen ==

=== Inleiding ===
Het zoeken (en oplossen) van fouten gebeurt in verschillende fasen.
* Tijdens de ontwikkeling door het testen van en werken met de developer-builds en beta-releases.
* Bij release-kandidaten gaat het alleen nog om het vinden en corrigeren van echt grote problemen.
* Van de laatste release kandidaat moet ook voor de Nederlandstalige versie een akkoord worden gegeven, alvorens die kan worden vrijgegeven.

=== Geautomatiseerd testen ===
Volgens testplannen worden allemaal functies geautomatiseerd uitgevoerd.
Dit is een doorlopend proces en gebeurt (vooral door de mensen van Sun en RedFlag) dus ook in een vroeg stadium.

Voor de geïnteresseerden, is er de nodige informatie, zoals over de [[Testtool|testtool]] voor geautomatiseerd testen en over het eventueel vertalen daarvan: [[HowTo_localize_qatesttool_environment|how to localiza it]].

=== Testen met TCM ===
Testen volgens TCM is vooral nuttig voor het controleren van nieuwe functies, en tijdens het testen van release-kandidaten.
* Nieuwe functies moeten in een redelijk vroeg stadium worden getest, uiterlijk met een beta-versie, en niet met de release-kandidaten. Bij release kandidaten worden alleen nog heel ernstige bugs gecorrigeerd, en niet als een nieuwe functie niet helemaal perfect werkt ...
* Testen volgens TCM geeft ook een houvast voor het testen van hoofdfuncties, die wel moeten worden gecontroleerd bij een release-kandidaat.

====Localisatie testen van nieuwe uitgaven van OOo====
Voordat je resultaten van je testen kunt invoeren in TCM, of kunt TCM gebruiken voor testideeën, moet je als gebruiker aan TCM worden toegevoegd. 
Mail daarvoor naar [mailto:localization@nl.openoffice.org de localisatie lijst] of naar één van de andere actieve projectleden.
* De startpagina van TCM is [http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_login.cgi?tcm_config=newooo hier].
* Je kunt daar inloggen met username en password
* Ga dan door op stap 5: Test Result Update
* Kies de versie van OOo, de tests die op jouw naam staan, etc.
** Bijvoorbeeld: Klik op 'OpenOffice.org(3.2RC)' in de kolom 'Build Number'
** Zoek in de volgende tabel de regel met je inlognaam.
** Klik in die regel op 'Scenario(Release sanity scenario)'
** Er zijn dan meer dan 20 test beschikbaar.
het is niet altijd nodig dat iedere tester elke test doet ...
het zijn geen ingewikkelde tests, maar kies eventueel dus tests die je graag doet, of overleg per mail met anderen.
** Bij een uitgevoerde test invullen: pass, fail of skip, en voer eventueel commentaar in
** Je kunt ook kijken naar de linkjes naar al eerder gevonden bugs.
*** Het is goed mogelijk dat daar al opgeloste bugs tussen staan - het is nog niet geregeld dat die worden verwijderd/gefilterd.
over criteria om een test op fail te zetten:
dat gebeurt niet om kleinere problemen, alleen als iets echt goed fout zit
vul evt. commentaar in. En al weer: bij vragen is er op de mail lijst altijd hulp!

Vragen, opmerkingen, suggesties welkom!

Zeer nuttige uitgebreide informatie staat in de wiki op de [[Test_Case_Management|de TCM pagina]] en in de uitleg over TCM/testen en de release cyclus [[Release Action List for QA]]

===Minimale check op gelocaliseerde versies===
Wanneer het niet mogelijk is om alle TCM tests te doen, kan worden terug gevallan op een [[NL/QA/SanityCheck_van_Localisaties | lijst met minimale tests]] voor de vrijgave.

Maar we moeten er om denken, dat als iedereen alleen maar 'minimaal' gaat zitten testen, we gauw een probleem hebben ..

=== Testen door er mee te werken ===
Dit kan iedereen doen. Snapshots en beta-versies downloaden en er mee aan de slag gaan.

=== Je ervaringen delen ===
Als je bijzonderheden tegenkomt - meestal fouten ;-) - dan is het de bedoeling dat die in Issuetracker worden geplaatst. Of dat je met je waarneming een issue van een ander bevestigt, of verduidelijkt, of nuanceert.

Informatie voor het gebruiken van Issuetracker staat [http://nl.openoffice.org/about-issuezilla.html hier].

Vaak is het handig om ervaringen te bespreken voordat je de moeite neemt om een issue te maken. Soms heeft iemand anders al een antwoord of issue, of is het probleem in een nieuwe snapshot opgelost. Dat scheelt je dan weer het aanmaken van een issue.
En kom je ergens zelf niet uit: vraag het dan gewoon op localization@nl.openoffice.org.

=== Coördinatie van & informatie over testen===
Al enkele keren genoemd: localization@nl.openoffice.org. Dit is de mailinglijst waar alle lijntjes samen komen. Dus het is leuk en nuttig om je daar voor aan te melden ([mailto:localization-subscribe@nl.openoffice.org localization-subscribe@nl.openoffice.org]).

[[Category:NL.OpenOffice.org|QA]]

NL/QA/Testen

2010-07-26T21:21:15Z

CorNouws: /* Beta voor 3.3.0 gaat er aan komen */

== Werken met nog niet officiële versies van OpenOffice.org ==

=== Waarom ===
* Het is leuk om de nieuwste ontwikkelingen op de voet te volgen ...
* Hoe eerder fouten in de software worden ontdekt, bij voorkeur nog voor de beta-versies, hoe makkelijker het is om ze te repareren. 
OpenOffice.org brengt vier keer per jaar een nieuwe versie uit (twee keer met nieuwe functies en twee keer met alleen verbeteringen). Er is dus steeds veel nieuws te beleven en te testen.

In de ontwikkelcyclus van het product zijn achtereenvolgens de volgende versies, stadia, te onderscheiden:
* developer builds (snapshots) - om de paar weken;
* beta versies - tegen de tijd dat de nieuwe versie bijna klaar is;
* release kandidaten - een release kandidaat kan de uiteindelijke nieuwe versie worden;
* stabiele versies

Het testen kan heel gestructureerd, maar ook door de software gewoon te installeren en er mee te werken en dan kijken wat voor bijzonderheden je aantreft. Meer hierover verder op deze pagina.
Testen kan heel leuk zijn, want je leert er vaak weer wat van en kunt zelf snel met de nieuwste functies aan de slag. En het helpt om zo vroeg mogelijk zoveel mogelijk fouten op te sporen. Kortom: hulp met testen is altijd welkom!

== Nu beschikbaar om te proberen en te testen ==

===Algemeen: downloaden===
Snapshots enzovoorts zijn steeds te vinden via [http://download.openoffice.org/next/ http://download.openoffice.org/next/]. Rechts op die pagina staan ook verwijzingen naar nuttige aanvullende uitleg. 
Controle van de integriteit van de downloads kan met de MD5 CheckSum test. Uitleg en controle-getallen zijn altijd te vinden op de [http://download.openoffice.org/next/md5sums/ md5sums]-pagina.

=== Versie voor testen vertaling 3.3.0 beschikbaar ===
Op 26 juli is de test-versie met de vertaling voor OpenOffice.org 3.3.0 beschikbaar gekomen. Te downloaden van [http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/ooo330l10n/ deze pagina]. (Voor Linux zijn alleen de taalpakketten en een complete eng-GB versie beschikbaar.) 
Er is in het Engels al informatie over de functies [[Feature_Freeze_Testing_3.3 | beschikbaar]]. 
Heb je zin om in het Nederlands gebruikers-informatie te maken, neem dan even contact op.. Dank!

===Beta voor 3.3.0 gaat er aan komen===
De beta voor OpenOffice.org 3.3.0 wordt medio augustus verwacht! De developer snapshots (DEV300_m82 en nieuwer) laten al veel van de nieuwe functies zien!

===Snapshots voor de 3.4.x===
Sinds in juli 2010 de tak voor de 3.3.x is losgemaakt uit de hoofdstam, wordt de lijn DEV300 verder ontwikkeld richting 3.4.0 etc.

Nieuwsgierig? De eerste snapshots zijn via [http://download.openoffice.org/next/ http://download.openoffice.org/next/] te vinden.

===Snapshot met nieuwe afdrukvensters - Belangrijke mijlplaal in de ontwikkeling van versie 3.3.0!===
Sinds half januari is Developer build [http://download.openoffice.org/next/ DEV300 m70] beschikbaar.

Daarin is de code opgenomen voor de nieuwe afdrukvensters. Pluspunten: elk afdrukvenster toont een afdrukvoorbeeld, en biedt direct toegang tot alle instellingen.
Lees daarover meer op [http://blogs.sun.com/GullFOSS/entry/new_print_ui_now_integrated GullFoss].

Het is een heel nieuw stuk in OpenOffice.org, dat stevig aan de tand moet worden gevoeld voor de 3.3.0 uit komt. Je kunt deze snapshot downloaden en installeren naast je normale OpenOffice.org versie. (Zie de uitleg elders op deze wiki-pagina.)

== Meer over de achtereenvolgende versies in de ontwikkelcyclus ==

=== Developer builds (snapshots) ===
Zijn redelijk stabiel, maar worden niet aangeraden voor dagelijks werk. 
Installeert apart, naast de normale versie van OpenOffice.org. 
Op de OOo-site staan de nieuwste [http://download.openoffice.org/next/other.htm developer builds], maar die zijn niet in het Nederlands beschikbaar. Op die pagina's is onder de link 'Release Notes' ook een verwijzing naar informatie over de nieuwe functies.

=== Beta versies ===
Het product is bijna gereed, men verwacht dat het product zonder serieuze problemen gebruikt kan worden. De nieuwe functies worden met de beta-uitgaven door veel mensen gebruikt, wat weer extra reacties oplevert. 
Een beta installeert naast een bestaande versie van OpenOffice.org.
=== Release kandidaten ===
Een release kandidaat verschijnt zodra men verwacht dat het product gereed is. Het is tijd voor de laatste tests. 
Bij het installeren, vervangt de release kandidaat de al geïnstalleerde versie van OpenOffice.org, tenzij er wordt gekozen voor parallelle installatie. Die procedure is elders op deze pagina beschreven: [[NL/TipsEnTrucs/Meerdere_versies_van_OOo_uitvoeren| Meerdere versies van OOo uitvoeren]]. 
Als er geen ernstige problemen meer worden gevonden, zal de release kandidaat als de nieuwe stabliele versie worden vrijgegeven.

=== Goedkeuring voor een nieuwe release ===
Voordat een nieuwe versie officieel wordt vrijgegeven, moet er natuurlijk wel wat gebeuren.
Op [[Release_Action_List_for_QA#Approval_of_Builds | deze plek]] staat hoe dat in zijn werk gaat.

== Meerdere versies en talen installeren ==

=== Meerdere versies installeren===
Het is verstandig om de diverse (testversies) naast je huidige OpenOffice.org te installeren. Je kunt dan ook makkelijk functies vergelijken. Op [[NL/TipsEnTrucs/Meerdere_versies_van_OOo_uitvoeren| Meerdere versies van OOo uitvoeren]] staat uitgelegd hoe dat werkt. Kom je ergens niet uit? Mail dan naar [mailto:localization@nl.openoffice.org localization@nl.openoffice.org]

=== Taalversies ===
Het is ook mogelijk om een niet Nederlandse versie van OpenOffice.org (bijv. Engels) te installeren en dan een taalpakket (language pack) voor Nederlands.
Als eerst de volledige versie wordt geïnstalleerd en dan (snelstarter uit!) het Nederlandse taalpakket, kan in Tools>Options>Language settings>Language 'Nederlands' worden gekozen voor de gebruikers interface. Al de menu's, vensters en Help worden dan Engels- of Nederlandstalig.

== Hoe testen ==

=== Inleiding ===
Het zoeken (en oplossen) van fouten gebeurt in verschillende fasen.
* Tijdens de ontwikkeling door het testen van en werken met de developer-builds en beta-releases.
* Bij release-kandidaten gaat het alleen nog om het vinden en corrigeren van echt grote problemen.
* Van de laatste release kandidaat moet ook voor de Nederlandstalige versie een akkoord worden gegeven, alvorens die kan worden vrijgegeven.

=== Geautomatiseerd testen ===
Volgens testplannen worden allemaal functies geautomatiseerd uitgevoerd.
Dit is een doorlopend proces en gebeurt (vooral door de mensen van Sun en RedFlag) dus ook in een vroeg stadium.

Voor de geïnteresseerden, is er de nodige informatie, zoals over de [[Testtool|testtool]] voor geautomatiseerd testen en over het eventueel vertalen daarvan: [[HowTo_localize_qatesttool_environment|how to localiza it]].

=== Testen met TCM ===
Testen volgens TCM is vooral nuttig voor het controleren van nieuwe functies, en tijdens het testen van release-kandidaten.
* Nieuwe functies moeten in een redelijk vroeg stadium worden getest, uiterlijk met een beta-versie, en niet met de release-kandidaten. Bij release kandidaten worden alleen nog heel ernstige bugs gecorrigeerd, en niet als een nieuwe functie niet helemaal perfect werkt ...
* Testen volgens TCM geeft ook een houvast voor het testen van hoofdfuncties, die wel moeten worden gecontroleerd bij een release-kandidaat.

====Localisatie testen van nieuwe uitgaven van OOo====
Voordat je resultaten van je testen kunt invoeren in TCM, of kunt TCM gebruiken voor testideeën, moet je als gebruiker aan TCM worden toegevoegd. 
Mail daarvoor naar [mailto:localization@nl.openoffice.org de localisatie lijst] of naar één van de andere actieve projectleden.
* De startpagina van TCM is [http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_login.cgi?tcm_config=newooo hier].
* Je kunt daar inloggen met username en password
* Ga dan door op stap 5: Test Result Update
* Kies de versie van OOo, de tests die op jouw naam staan, etc.
** Bijvoorbeeld: Klik op 'OpenOffice.org(3.2RC)' in de kolom 'Build Number'
** Zoek in de volgende tabel de regel met je inlognaam.
** Klik in die regel op 'Scenario(Release sanity scenario)'
** Er zijn dan meer dan 20 test beschikbaar.
het is niet altijd nodig dat iedere tester elke test doet ...
het zijn geen ingewikkelde tests, maar kies eventueel dus tests die je graag doet, of overleg per mail met anderen.
** Bij een uitgevoerde test invullen: pass, fail of skip, en voer eventueel commentaar in
** Je kunt ook kijken naar de linkjes naar al eerder gevonden bugs.
*** Het is goed mogelijk dat daar al opgeloste bugs tussen staan - het is nog niet geregeld dat die worden verwijderd/gefilterd.
over criteria om een test op fail te zetten:
dat gebeurt niet om kleinere problemen, alleen als iets echt goed fout zit
vul evt. commentaar in. En al weer: bij vragen is er op de mail lijst altijd hulp!

Vragen, opmerkingen, suggesties welkom!

Zeer nuttige uitgebreide informatie staat in de wiki op de [[Test_Case_Management|de TCM pagina]] en in de uitleg over TCM/testen en de release cyclus [[Release Action List for QA]]

===Minimale check op gelocaliseerde versies===
Wanneer het niet mogelijk is om alle TCM tests te doen, kan worden terug gevallan op een [[NL/QA/SanityCheck_van_Localisaties | lijst met minimale tests]] voor de vrijgave.

Maar we moeten er om denken, dat als iedereen alleen maar 'minimaal' gaat zitten testen, we gauw een probleem hebben ..

=== Testen door er mee te werken ===
Dit kan iedereen doen. Snapshots en beta-versies downloaden en er mee aan de slag gaan.

=== Je ervaringen delen ===
Als je bijzonderheden tegenkomt - meestal fouten ;-) - dan is het de bedoeling dat die in Issuetracker worden geplaatst. Of dat je met je waarneming een issue van een ander bevestigt, of verduidelijkt, of nuanceert.

Informatie voor het gebruiken van Issuetracker staat [http://nl.openoffice.org/about-issuezilla.html hier].

Vaak is het handig om ervaringen te bespreken voordat je de moeite neemt om een issue te maken. Soms heeft iemand anders al een antwoord of issue, of is het probleem in een nieuwe snapshot opgelost. Dat scheelt je dan weer het aanmaken van een issue.
En kom je ergens zelf niet uit: vraag het dan gewoon op localization@nl.openoffice.org.

=== Coördinatie van & informatie over testen===
Al enkele keren genoemd: localization@nl.openoffice.org. Dit is de mailinglijst waar alle lijntjes samen komen. Dus het is leuk en nuttig om je daar voor aan te melden ([mailto:localization-subscribe@nl.openoffice.org localization-subscribe@nl.openoffice.org]).

[[Category:NL.OpenOffice.org|QA]]

NL/QA/Testen

2010-07-26T21:10:55Z

CorNouws: /* Snapshots voor de 3.3.x */

== Werken met nog niet officiële versies van OpenOffice.org ==

=== Waarom ===
* Het is leuk om de nieuwste ontwikkelingen op de voet te volgen ...
* Hoe eerder fouten in de software worden ontdekt, bij voorkeur nog voor de beta-versies, hoe makkelijker het is om ze te repareren. 
OpenOffice.org brengt vier keer per jaar een nieuwe versie uit (twee keer met nieuwe functies en twee keer met alleen verbeteringen). Er is dus steeds veel nieuws te beleven en te testen.

In de ontwikkelcyclus van het product zijn achtereenvolgens de volgende versies, stadia, te onderscheiden:
* developer builds (snapshots) - om de paar weken;
* beta versies - tegen de tijd dat de nieuwe versie bijna klaar is;
* release kandidaten - een release kandidaat kan de uiteindelijke nieuwe versie worden;
* stabiele versies

Het testen kan heel gestructureerd, maar ook door de software gewoon te installeren en er mee te werken en dan kijken wat voor bijzonderheden je aantreft. Meer hierover verder op deze pagina.
Testen kan heel leuk zijn, want je leert er vaak weer wat van en kunt zelf snel met de nieuwste functies aan de slag. En het helpt om zo vroeg mogelijk zoveel mogelijk fouten op te sporen. Kortom: hulp met testen is altijd welkom!

== Nu beschikbaar om te proberen en te testen ==

===Algemeen: downloaden===
Snapshots enzovoorts zijn steeds te vinden via [http://download.openoffice.org/next/ http://download.openoffice.org/next/]. Rechts op die pagina staan ook verwijzingen naar nuttige aanvullende uitleg. 
Controle van de integriteit van de downloads kan met de MD5 CheckSum test. Uitleg en controle-getallen zijn altijd te vinden op de [http://download.openoffice.org/next/md5sums/ md5sums]-pagina.

===Beta voor 3.3.0 gaat er aan komen===
De beta voor OpenOffice.org 3.3.0 wordt medio augustus verwacht! De developer snapshots (DEV300_m82 en nieuwer) laten al veel van de nieuwe functies zien!

===Snapshots voor de 3.4.x===
Sinds in juli 2010 de tak voor de 3.3.x is losgemaakt uit de hoofdstam, wordt de lijn DEV300 verder ontwikkeld richting 3.4.0 etc.

Nieuwsgierig? De eerste snapshots zijn via [http://download.openoffice.org/next/ http://download.openoffice.org/next/] te vinden.

===Snapshot met nieuwe afdrukvensters - Belangrijke mijlplaal in de ontwikkeling van versie 3.3.0!===
Sinds half januari is Developer build [http://download.openoffice.org/next/ DEV300 m70] beschikbaar.

Daarin is de code opgenomen voor de nieuwe afdrukvensters. Pluspunten: elk afdrukvenster toont een afdrukvoorbeeld, en biedt direct toegang tot alle instellingen.
Lees daarover meer op [http://blogs.sun.com/GullFOSS/entry/new_print_ui_now_integrated GullFoss].

Het is een heel nieuw stuk in OpenOffice.org, dat stevig aan de tand moet worden gevoeld voor de 3.3.0 uit komt. Je kunt deze snapshot downloaden en installeren naast je normale OpenOffice.org versie. (Zie de uitleg elders op deze wiki-pagina.)

== Meer over de achtereenvolgende versies in de ontwikkelcyclus ==

=== Developer builds (snapshots) ===
Zijn redelijk stabiel, maar worden niet aangeraden voor dagelijks werk. 
Installeert apart, naast de normale versie van OpenOffice.org. 
Op de OOo-site staan de nieuwste [http://download.openoffice.org/next/other.htm developer builds], maar die zijn niet in het Nederlands beschikbaar. Op die pagina's is onder de link 'Release Notes' ook een verwijzing naar informatie over de nieuwe functies.

=== Beta versies ===
Het product is bijna gereed, men verwacht dat het product zonder serieuze problemen gebruikt kan worden. De nieuwe functies worden met de beta-uitgaven door veel mensen gebruikt, wat weer extra reacties oplevert. 
Een beta installeert naast een bestaande versie van OpenOffice.org.
=== Release kandidaten ===
Een release kandidaat verschijnt zodra men verwacht dat het product gereed is. Het is tijd voor de laatste tests. 
Bij het installeren, vervangt de release kandidaat de al geïnstalleerde versie van OpenOffice.org, tenzij er wordt gekozen voor parallelle installatie. Die procedure is elders op deze pagina beschreven: [[NL/TipsEnTrucs/Meerdere_versies_van_OOo_uitvoeren| Meerdere versies van OOo uitvoeren]]. 
Als er geen ernstige problemen meer worden gevonden, zal de release kandidaat als de nieuwe stabliele versie worden vrijgegeven.

=== Goedkeuring voor een nieuwe release ===
Voordat een nieuwe versie officieel wordt vrijgegeven, moet er natuurlijk wel wat gebeuren.
Op [[Release_Action_List_for_QA#Approval_of_Builds | deze plek]] staat hoe dat in zijn werk gaat.

== Meerdere versies en talen installeren ==

=== Meerdere versies installeren===
Het is verstandig om de diverse (testversies) naast je huidige OpenOffice.org te installeren. Je kunt dan ook makkelijk functies vergelijken. Op [[NL/TipsEnTrucs/Meerdere_versies_van_OOo_uitvoeren| Meerdere versies van OOo uitvoeren]] staat uitgelegd hoe dat werkt. Kom je ergens niet uit? Mail dan naar [mailto:localization@nl.openoffice.org localization@nl.openoffice.org]

=== Taalversies ===
Het is ook mogelijk om een niet Nederlandse versie van OpenOffice.org (bijv. Engels) te installeren en dan een taalpakket (language pack) voor Nederlands.
Als eerst de volledige versie wordt geïnstalleerd en dan (snelstarter uit!) het Nederlandse taalpakket, kan in Tools>Options>Language settings>Language 'Nederlands' worden gekozen voor de gebruikers interface. Al de menu's, vensters en Help worden dan Engels- of Nederlandstalig.

== Hoe testen ==

=== Inleiding ===
Het zoeken (en oplossen) van fouten gebeurt in verschillende fasen.
* Tijdens de ontwikkeling door het testen van en werken met de developer-builds en beta-releases.
* Bij release-kandidaten gaat het alleen nog om het vinden en corrigeren van echt grote problemen.
* Van de laatste release kandidaat moet ook voor de Nederlandstalige versie een akkoord worden gegeven, alvorens die kan worden vrijgegeven.

=== Geautomatiseerd testen ===
Volgens testplannen worden allemaal functies geautomatiseerd uitgevoerd.
Dit is een doorlopend proces en gebeurt (vooral door de mensen van Sun en RedFlag) dus ook in een vroeg stadium.

Voor de geïnteresseerden, is er de nodige informatie, zoals over de [[Testtool|testtool]] voor geautomatiseerd testen en over het eventueel vertalen daarvan: [[HowTo_localize_qatesttool_environment|how to localiza it]].

=== Testen met TCM ===
Testen volgens TCM is vooral nuttig voor het controleren van nieuwe functies, en tijdens het testen van release-kandidaten.
* Nieuwe functies moeten in een redelijk vroeg stadium worden getest, uiterlijk met een beta-versie, en niet met de release-kandidaten. Bij release kandidaten worden alleen nog heel ernstige bugs gecorrigeerd, en niet als een nieuwe functie niet helemaal perfect werkt ...
* Testen volgens TCM geeft ook een houvast voor het testen van hoofdfuncties, die wel moeten worden gecontroleerd bij een release-kandidaat.

====Localisatie testen van nieuwe uitgaven van OOo====
Voordat je resultaten van je testen kunt invoeren in TCM, of kunt TCM gebruiken voor testideeën, moet je als gebruiker aan TCM worden toegevoegd. 
Mail daarvoor naar [mailto:localization@nl.openoffice.org de localisatie lijst] of naar één van de andere actieve projectleden.
* De startpagina van TCM is [http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_login.cgi?tcm_config=newooo hier].
* Je kunt daar inloggen met username en password
* Ga dan door op stap 5: Test Result Update
* Kies de versie van OOo, de tests die op jouw naam staan, etc.
** Bijvoorbeeld: Klik op 'OpenOffice.org(3.2RC)' in de kolom 'Build Number'
** Zoek in de volgende tabel de regel met je inlognaam.
** Klik in die regel op 'Scenario(Release sanity scenario)'
** Er zijn dan meer dan 20 test beschikbaar.
het is niet altijd nodig dat iedere tester elke test doet ...
het zijn geen ingewikkelde tests, maar kies eventueel dus tests die je graag doet, of overleg per mail met anderen.
** Bij een uitgevoerde test invullen: pass, fail of skip, en voer eventueel commentaar in
** Je kunt ook kijken naar de linkjes naar al eerder gevonden bugs.
*** Het is goed mogelijk dat daar al opgeloste bugs tussen staan - het is nog niet geregeld dat die worden verwijderd/gefilterd.
over criteria om een test op fail te zetten:
dat gebeurt niet om kleinere problemen, alleen als iets echt goed fout zit
vul evt. commentaar in. En al weer: bij vragen is er op de mail lijst altijd hulp!

Vragen, opmerkingen, suggesties welkom!

Zeer nuttige uitgebreide informatie staat in de wiki op de [[Test_Case_Management|de TCM pagina]] en in de uitleg over TCM/testen en de release cyclus [[Release Action List for QA]]

===Minimale check op gelocaliseerde versies===
Wanneer het niet mogelijk is om alle TCM tests te doen, kan worden terug gevallan op een [[NL/QA/SanityCheck_van_Localisaties | lijst met minimale tests]] voor de vrijgave.

Maar we moeten er om denken, dat als iedereen alleen maar 'minimaal' gaat zitten testen, we gauw een probleem hebben ..

=== Testen door er mee te werken ===
Dit kan iedereen doen. Snapshots en beta-versies downloaden en er mee aan de slag gaan.

=== Je ervaringen delen ===
Als je bijzonderheden tegenkomt - meestal fouten ;-) - dan is het de bedoeling dat die in Issuetracker worden geplaatst. Of dat je met je waarneming een issue van een ander bevestigt, of verduidelijkt, of nuanceert.

Informatie voor het gebruiken van Issuetracker staat [http://nl.openoffice.org/about-issuezilla.html hier].

Vaak is het handig om ervaringen te bespreken voordat je de moeite neemt om een issue te maken. Soms heeft iemand anders al een antwoord of issue, of is het probleem in een nieuwe snapshot opgelost. Dat scheelt je dan weer het aanmaken van een issue.
En kom je ergens zelf niet uit: vraag het dan gewoon op localization@nl.openoffice.org.

=== Coördinatie van & informatie over testen===
Al enkele keren genoemd: localization@nl.openoffice.org. Dit is de mailinglijst waar alle lijntjes samen komen. Dus het is leuk en nuttig om je daar voor aan te melden ([mailto:localization-subscribe@nl.openoffice.org localization-subscribe@nl.openoffice.org]).

[[Category:NL.OpenOffice.org|QA]]

NL/Bijeenkomsten/OOoCafe

2010-07-24T14:02:10Z

CorNouws: /* 3 oktober 2009 nl-OpenOffice.org-Café in Eindhoven */

== Wat is nl-OpenOffice.org Café ?! ==

* Een bijeenkomst waar je makkelijk binnen kunt lopen.
* Een eenvoudig programma, waaraan ieder mag bijdragen.
* Internettoegang en stroom, dus computer meenemen :-)
* Leuke weetjes delen en lastige vragen aan anderen voorleggen.
* De mensen ontmoeten, die je meestal alleen van de e-mail kent.

== 25 september 2010 .. nl-OpenOffice.org-Café in Breda ==
=== Even bijkomen van de vakantie, ervaringen uitwisselen, bijpraten over de OOoCon in Hongarije ... ===
Locatie: De Wasserette, Vlaszak 2, 4811 Breda. 
De Wasserette is een soort kunst-café, maar met een losse sfeer leent het zich gedurende de middag ook prima voor een ontmoeten van open office-actievelingen. 
De Wasserette is een makkelijke plek aan de rand van het centrum van Breda. Niet ver van het station en met parkeergarages is de buurt.

Tijd: 12:00 - 15/16..

Er zijn, afgezien van wat we gebruiken, geen kosten aan de bijeenkomst verbonden.

== 3 oktober 2009 nl-OpenOffice.org-Café in Eindhoven ==

=== Op het bekende open source event T-Dose ===
Tijdens de "T-Dose", waar enkelen toch al zijn, hebben we op 3 oktober ons volgende nl-OpenOffice.org-Café.

Tijd: van 11:00 tot ca. 14:30 uur.
Het programma van de T-Dose gaat dan nog door - ook op de zondag!

Website van [http://www.t-dose.org/ T-Dose]

== 6 juni te gast bij NLLGG ==
Op 6 juni zijn we te gast in Utrecht bij de NLLGG (Nederlandse Linux Gebruikers Groep). Tijd: van 11:00 tot 16:00.

Omdat we bij de NLLGG zijn, is er een iets ruimer programma met lezingen. Je vindt dat (voorlopige) programma en info over plaats op de site van [http://www.nllgg.nl/bijeenkomst_20090606 de NLLGG].

=== T-Shirts ===
Op 6 juni is er een stapeltje coole OpenOffice.org T-shirts aanwezig.
De bedoeling is dat die allemaal door andere mensen worden meegenomen ;-)

== OOo Café Carrousel ==
We gaan een circuit opzetten met als plaatsen bijvoorbeeld Amersfoort, Breda en Eindhoven. Mooie spreiding lijkt ons. Naar locaties wordt gezocht .. suggesties welkom.

== OpenOffice.org Café 21 maart 2009 ==

Het komende nl.OOo-Café op 21 maart!
Er zal daar veel aandacht voor nieuwe functies in de komende OpenOffice.org 3.1 en deskundige hulp bij proberen daarvan en QA.

[[Image:NlOOoCafe-09-03-14.png]]

=== Programma ===
(wijzigingen voorbehouden)
* 11.00 : Functies in de nieuwe versie van OpenOffice.org
* 12.00 : tafel-sessies
* 13.30 : Testen van nieuwe functies in bijvoorbeeld Developer Builds
* 14.30 : Ideeën over de oprichting van een vereniging voor Nl.OpenOffice.org
* 15.00 : Tafel-sessies

=== Praktische info ===
* Tijd: 10.00 - 15.00 (...)
* Plaats: [http://www.amershof.nl/route.html Amersfhof] in Amersfoort. (5 minuten lopen vanaf het NS-station.)
* Toegang: aanmelden is handig (hoe vol is vol?!) en kan op het mailadres [mailto:nl_OOo_cafe@openoffice.org nl_OOo_cafe]
* Kosten: geen (uitgezonderd consumpties). Vrijwillige bijdrage voor nl.OOo uiteraard welkom.

== 14 juni 2008 - 's Hertogenbosch ==

=== Primeur!===
Het éérste OpenOffice.org-café van de Nederlands/Vlaamse OOo-gemeenschap.

Doel: een bijeenkomst waar OpenOffice.org geïnteresseerden en belangstellingen makkelijk binnen kunnen lopen.
Er is een eenvoudig programma - zie verder. 
Uiteraard internettoegang en stroom, dus PC's en laptops meenemen is een pré. 
Leuke weetjes met anderen delen? Eindelijk eens vragen hoe iemand anders dat lastige vraagstuk oplost? Het kan op deze zaterdag!

=== Programma ===
(voorlopig)
* 10.30 - 11.00 : Presentatie OpenOffice.org op de server, door Jef Peeraer
* 11.30 - 12.00 : Testen en QA van OpenOffice.org, door Arthur Buijs / ...

=== Praktische info ===
* Tijd: 9.00 - 13.00
* Plaats: Koning Willem I College - Campus Techniek - Onderwijsboulevard 3, 5223 DE ‘s Hertogenbosch ( 5 minuten lopen vanaf de achteruitgang van het NS-station.)
* Toegang: aanmelden wordt aangeraden (hoe vol is vol?!) en kan op het mailadres [mailto:nl_OOo_cafe@openoffice.org nl_OOo_cafe]
* Kosten: geen (uitgez. consumpties), vrijwillige bijdrage voor nl.OOo uiteraard welkom.

[[Category:NL.OpenOffice.org|Bijeenkomsten]]

OpenOffice.org Internship/Applications

2010-07-21T21:00:51Z

CorNouws: correction wrt active projects

[[Category:Marketing]][[Category:Development]][[Category:Education]]
{{DISPLAYTITLE:Applications for the Summer 2010 Internship}}

Applications for the Summer 2010 Internship, accepted by the Supervisory Team.

{| class="prettytable sortable"
|-
! scope="col" | Project Description
! scope="col" | Project Page
! scope="col" | Student
! scope="col" | Mentor
|-
| [[OpenOffice.org_Internship/ProjectProposals#Statistical_Data_Analysis_Tool|Statistical Data Analysis Tool]]
| [[OpenOffice.org_Internship/Projects/2010/Statistical_Data_Analysis_Tool|Statistical Data Analysis Tool]]
| Pivithuru Wijegunawardana
| Niklas Nebel
|-
| [[OpenOffice.org_Internship/ProjectProposals#Add_new_spreadsheet_functions_and_parameters_according_to_ODFF|Add new spreadsheet functions and parameters according to ODFF]]
| [[OpenOffice.org_Internship/Projects/2010/Add_new_spreadsheet_functions_and_parameters_according_to_ODFF|Add new spreadsheet functions and parameters according to ODFF]]
| Marina Plakalovic
| Eike Rathke
|-
| Improve PDF Import
| [[OpenOffice.org_Internship/Projects/2010/Improve_PDF_Import|Improve PDF Import]]
| Marcin Mosiolek
| Kai Ahrens
|-
| [[OpenOffice.org_Internship/ProjectProposals#Customizable_html_export_for_impress|Customizable html export for Impress]]
| [[OpenOffice.org_Internship/Projects/2010/Customizable_html_export_for_Impress|Customizable html export for Impress]]
| Kushal Likhi
| Christian Lippka
|-
| Optional OpenType features
| [[OpenOffice.org_Internship/Projects/2010/Optional_OpenType_features|Optional OpenType features]]
| Milos Hadzic
| Herbert Duerr
|-
| New Context Menu Implementation
| [[OpenOffice.org_Internship/Projects/2010/New_Context_Menu_Implementation|New Context Menu Implementation]]
| Ariel Constenla-Haile
| Carsten Driesner
|}

OpenOffice.org Internship/Projects

2010-07-21T20:59:46Z

CorNouws: correction wrt active projects

[[Category:Marketing]][[Category:Development]][[Category:Education]]
{{DISPLAYTITLE:Accepted projects for the Summer 2010 Internship}}

{| class="prettytable sortable"
|-
! scope="col" | Project
! scope="col" | Student
! scope="col" | Mentor
|-
| [[OpenOffice.org_Internship/Projects/2010/Statistical_Data_Analysis_Tool|Statistical Data Analysis Tool]]
| Pivithuru Wijegunawardana
| Niklas Nebel
|-
| [[OpenOffice.org_Internship/Projects/2010/Add_new_spreadsheet_functions_and_parameters_according_to_ODFF|Add new spreadsheet functions and parameters according to ODFF]]
| Marina Plakalovic
| Eike Rathke
|-
| [[OpenOffice.org_Internship/Projects/2010/Improve_PDF_Import|Improve ODF Import]]
| Marcin Mosiolek
| Kai Ahrens
|-
| [[OpenOffice.org_Internship/Projects/2010/Customizable_html_export_for_Impress|Customizable html export for Impress]]
| Kushal Likhi
| Christian Lippka
|-
| [[OpenOffice.org_Internship/Projects/2010/Optional_OpenType_features|Optional OpenType features]]
| Milos Hadzic
| Herbert Duerr
|-
| [[OpenOffice.org_Internship/Projects/2010/New_Context_Menu_Implementation|New Context Menu Implementation]]
| Ariel Constenla-Haile
| Carsten Driesner
|}

NL/Documentation/Makkelijk overstappen van Excel naar Calc

2010-07-15T11:03:59Z

CorNouws: /* Beveiliging */ opm over celopmaakprofielen toegevoegd

__NOTOC__
* De functies in OpenOffice.org, en het gebruiken daarvan, lijken heel sterk op die in andere office-programma's, zoals die van Microsoft. Dit document helpt op weg met enkele punten waar het wel verschilt.
* Van toepassing op OpenOffice.org versie 2.x/3.x

== Algemeen ==
=== OpenOffice.org is één programma ===
* Vanuit Calc kan net zo makkelijk een nieuw werkblad (spreadsheet) worden gemaakt, als een presentatie worden gestart als een tekstdocument worden geopend etc.
* Als er meerdere documenten open zijn, ook van een gelijk type, en in het ene wordt bijvoorbeeld een afdrukbereik ingesteld, of een printopdracht gegeven, kan nog steeds in alle andere documenten worden gewerkt.

== Documenten ==
=== Documenten verspreiden ===
* menu Bestand|Verzenden|Als PDF e-mailen (evt. ''Selectie'' kiezen in venster ''Opties'')
* menu Bestand|Verzenden|Als Microsoft Excel e-mailen
* conversie ingevoegde objecten instellen via Extra|Opties|Laden en opslaan|MsOffice

=== Sjablonen ===
* opslaan: Bestand|Sjablonen|Opslaan
* bewerken: Bestand|Sjablonen|Bewerken

=== Nieuw document uit sjabloon ===
* menu Bestand|Nieuw|Sjablonen en Documenten

== Beveiliging ==
=== Beveiliging ===
* menu Extra|Beveiligen|Blad / Document
* beveiligen op niveau van structuur, scenario's e.d. kan nog niet in OpenOffice.org.
* wel is een heel handige mogelijkheid om beveiliging in te stellen in celopmaakprofielen, waardoor dus ook groepen cellen met bijvoorbeeld formules in één keer te beveiligen zijn.

== Afdrukken ==
=== Pagina voor afdrukken instellen ===
* menu Opmaak|Afdrukbereiken
* eventueel per blad een ''paginaopmaakprofiel'' (bijv. liggend/staand)
* herhaling van rijen/kolommen in afdrukken via Opmaak|Afdrukbereiken

=== Opties voor afdrukken ===
* kies – naast het gebruiken van ''afdrukbereiken'' of het maken van ''een selectie'' – bijvoorbeeld voor ''Alleen geselecteerde bladen''

== Opmaak ==
=== Opmaakprofielen ===
* venster ''Stijlen en Opmaak'' – F11
* er zijn opmaakprofielen voor cellen en pagina's

=== Voorwaardelijke opmaak ===
* werkt met ''opmaakprofielen'', en niet met directe opmaak

=== Getalopmaak – Financieel ===
* OpenOffice.org Calc kent die (nog) niet. Het is wel mogelijk om deze zelf te definiëren.
Versie 3.2 kent de button met 4 stapeltjes geld naast het percentage teken

=== Datums en tijden ===
* opmaak afhankelijk van taalinstelling

=== Randen – streeplijnen ===
* minder keuzen dan in Excel

== Bewerken ==
=== Selectie verslepen ===
* kan op elke plek worden opgepakt met de muis, niet alleen aan de rand

=== Inhoud van cel verwijderen ===
* ''Backspace'' verwijderd inhoud (niet de opmaak)
* ''Delete'' geeft venster met keuzen voor wat moet worden verwijderd

=== Ctrl-D ===
* geeft in OpenOffice.org een keuzelijst van alle teksten in een kolom, dit is niet de functie ''Naar beneden kopiëren'' (is wel via Extra|Aanpassen toe te voegen)

=== Kopiëren en plakken ===
* selectie (stippellijn) blijft niet na plakken

=== Filteren en plakken ===
* knippen/plakken van verborgen rijen/kolommen werkt deels anders

== Inhoud ==
=== Getallen opgemaakt als tekst ===
* een getal dat als tekst is opgemaakt, wordt als nulwaarde gezien, dus ''nìet meegerekend'' – In Excel wel bij rekenkundige bewerkingen, maar niet in formules

=== Verwijzingen ===
* werkt ook met relatieve adressen van bladen – dat kan niet in Excel

=== Overzicht inhoud ===
* ''Navigator'' – F5 toont alle elementen van actieve document, en desgewenst van een ander geopend, niet-actief, document

{{CCBY}}

10YearsOOo

2010-07-05T21:03:27Z

CorNouws: /* Personalized Stamps */

{{DISPLAYTITLE:Ideas for Celebrating Ten Years of OpenOffice.org}} {{Marketing}} {{Documentation/Note|For discussions on that topic, please refer to our [mailto:dev@marketing.openoffice.org main marketing mailing list].}}

= A Note =

Please add all your ideas to this wiki page. Having ideas in the mailing list archives is good, but it's much better to have a compilation in the wiki for easy reference.

= Personalized Stamps =

*producing personalized stamps with OOo logo
*Hungarian post: Kami
*German post: Florian(?)
*Netherlands: cornouws

= Hosting a Worldwide Event =

*Set up a venue in each country, or even several venues per country
*Link all of those with video conferencing
*If it's multinational, talk about something multinational, e.g. localisations

= Do a Countdown =

*Count down the days to our anniversary (October 13th) from OOoCon on
*Issue something every week, e.g.
**Monday: business case
**Friday: community insight
*use videos

== Countdown Timeline ==

*Week 36 - launch - (Tuesday, August 31, 2010 – Friday, September 3, 2010) - [http://www.ooocon.org/index.php/ooocon/2010 OOoCon]
*Week 37 -
*Week 38 - highlight - (Saturday, September 18) [http://wiki.softwarefreedomday.org/ Software Freedom Day]
*Week 39 -
*Week 40 -
*Week 41 -
*Week 42 - finale (Wednesday, October 13) - OOo Turns Ten!

= Press =

*Encourage magazines to have a special 10-year-anniversary isuse
**BrOffice magazine
**Ubuntu FullCircle
**Free Software Magazine
*Make interviews with the community (Charles Schulz currently does some)

= Questions to ask =

*What do you expect from OOo?
*What did OOo give you?
*How do you feel about it?
*How they use OOo in regular activities?
*What has been the biggest advantage from using it?
*How they got started using OOo and why?
*What they expect from an office suite ten years from now?
*Where did you first see OOo and when?
*When did you first install a copy of OOo and on what?
*How many upgrades have you been through and where did you source them?
*One item of advice for the marketers, developers and new users!

Community Council/Funding And Budgets

2010-07-01T08:15:48Z

CorNouws: /* What you must know, before requesting for funding */ bit clearer

{{Community_Council}}
= OpenOffice.org Community Council Payments Procedure =
== What you must know, before requesting for funding ==
* Requests must (in general) be approved before the expenditure is done;
* Fundings are possible for spendings; in general, the work in the community is done on voluntary basis - exeptions are rare;
* Requests must be send to the budget holder ([[Community_Council/Funding_And_Budgets#Budgets |read more]]).

== Introduction ==
=== Devolving financial decision-making ===
The OpenOffice.org Community Council is responsible for managing the funds donated centrally to the Community. Decisions on releasing funds are generally taken at meetings of the Community Council. However, the Community Council may decide on an annual basis to approve a Budget, which allows expenditure decisions to be delegated to Budget Holders and Authorisers within the limits set by the Budget. The Community Council expects Budget Holders to consult relevant Community members about how the Budget is spent (e.g. on a ''dev@'' mailing list.). For contacting the Council and holding discussions by Budget authorisers, we have budget@council.openoffice.org, a discuss list requiring subscription for unmoderated posting.

=== Responsibilities ===
Budget Holders will be appointed by the Community Council. They may nominate one or more Authorisers for approval by the Council. Budget Holders and Authorisers must confirm their agreement to comply with this Procedure on appointment - any Budget Holder not following this Procedure will be personally responsible for any liabilities incurred. Budget Holders and Authorisers must also register with the Treasurer the email address they will use. The Community Council strongly encourages the use of signed emails for any correspondence covered by this Procedure.

Under this Procedure, the Community Council Treasurer (or deputy) is responsible for recording total amounts committed, making payments from the central funds, and reporting periodically to the Community Council.

== Purchasing Goods and Services ==
=== Approving a Request to Purchase ===
Budget Holders may raise a Request to Purchase themselves, or process them for other Community members. The Budget Holder may request an email Quotation from the Supplier (note: obtaining a quotation is recommended for all purchases, and is mandatory for purchases of €1,000 or more).

The Budget Holder forwards the Quotation / writes an email detailing:

* what the expenditure is for
* where the good/services should be delivered
* which budget category it falls under
* value / currency including taxes
* Supplier name and address

and emails this Request to Purchase to the Authoriser.

The Authoriser checks the Request to Purchase and either returns it to the Budget Holder with a reason for rejection, or approves it and forwards to the Treasurer.

The Treasurer checks the Budget Holder and Authoriser details on the Request to Purchase, and either returns it to the Budget Holder with a reason for rejection, or accepts it. If accepted, the Request to Purchase is recorded as a commitment on the Purchasing Log. The Treasurer will check on the Purchasing Log that the total committed to date including this new Request is within the approved Budget for this Budget Holder.

If there is funding available, the Treasurer emails the Budget Holder, authorising expenditure and issuing the next Purchase Order Number from the Purchasing Log.

=== Issuing a Purchase Order ===
Once the Budget Holder receives the Purchase Order Number from the Treasurer, the Purchase Order may be issued to the Supplier, quoting the Purchase Order Number, specifying the delivery address (where the goods/services are required) and the invoice address (the Treasurer). A recommended Purchase Order template is available from the Treasurer.

=== Receiving Goods/Services ===
When the good/services are delivered satisfactorily, the Budget Holder must email the Treasurer promptly, quoting the Purchase Order Number, to state the Invoice may now be paid. The Treasurer records the date of the email on the Purchasing Log.

=== Processing an Invoice ===
Invoices must be sent direct from the Supplier to the Treasurer. Any Invoices received from Suppliers without a valid Purchase Order Number will be returned unpaid. On receipt of a Supplier’s Invoice with a valid Purchase Order Number, the Treasurer will check the Purchasing Log to ensure that the details match the Request to Purchase, and that the Invoice has been approved for payment. If approved, the Treasurer will pay the Supplier within the Supplier’s payment terms.

If there are discrepancies, the Treasurer will email the Supplier and the Budget Holder to resolve the differences. If the resolution results in an invoice amount greater than the original Request to Purchase, then the Budget Holder must seek approval from an Authoriser for the additional spend.

== Travel and Expenses ==
=== Approving a Expense Request ===
Any Community member wishing to be refunded by the Community for travel or miscellaneous purchases must obtain approval in advance from a Budget Holder. The request must specify:

* name of the individual and role within the Community
* budget category
* nature of the expense
* if for travel:
* date / duration / nature of the event
* reason for attendance (e.g. presenting a paper, manning a stall...)
* transport details (if any)
* accommodation details (if any)
* value / currency including taxes
* bank account details for reimbursement (unless cash – see below)

The Budget Holder must satisfy themselves that the amount requested is reasonable and appropriate. If the Request is approved, the Budget Holder will email a Travel Approval to the Traveller, with a copy to the Treasurer. The Treasurer will note the amount as a Commitment against the Budget in the Purchasing Log.

Note: the Community will generally not issue advances to fund travel or other miscellaneous expenses. It is the responsibility of the Traveller to ensure they have the necessary funding to cover their expenses until reimbursement is received.

=== Refund of Expenses – Bank Transfer ===
When the trip is complete the Traveller should submit details of the expenditure actually incurred to the Treasurer. The Treasurer will check that the amount is within the amount authorised on the Travel Approval and if so, will issue a refund to the Traveller.

If the amount claimed exceeds the authorised amount the Treasurer will seek approval from the Budget Holder for the excess before making any repayment.

=== Refund of Expenses – Cash ===
At events such as OOoCon it may be more convenient for a Budget Holder or Nominee to issue cash refunds to Travellers in person. In this case, the Budget Holder should request a cash advance from Treasurer sufficient to cover all the Travel Approvals which have been raised for the event. The Budget Holder or Nominee should then arrange to meet the Community Members who require refunds. Each Member should present a copy of their Travel Approval, a statement of the expenses actually incurred, and – if they are not personally known to the Budget Holder - some form of photo identification. The Budget Holder or Nominee must obtain a receipt for all cash disbursed, so the Budget Holder can use these to reconcile any cash balances with the Treasurer at the end of the event.

== Treasurer Responsibilities ==
=== Recording ===
The Treasurer shall be responsible for maintaining accurate and up to date records as described in this Procedure, i.e. a Purchasing Log and details of Budget Holders and Authorisers.

=== Reporting ===
The Treasurer shall use the information in the Purchasing Log to report to the Community Council on expenditures, committed and incurred, versus budget. Every quarter the Community Council will review a summary financial statement and agree whether any changes are required to the budget for the rest of the year. This summary financial statement will be posted to the website.

=== Legal and Statutory considerations ===
This Procedure is designed to satisfy the requirements of the OpenOffice.org Community Council only. It may need to be supplemented by additional procedures to meet the needs of legal, accounting, or other regulatory bodies.

== Handling /routing of requests ==
1. A request must be sent to the budget holder (see under [[Community_Council/Funding_And_Budgets#Budgets | budget]]);
any request that pops up anywhere else, must be redirected there.

2. The budget holder:
# Can ask for more information;
# Can discuss with other budget holders (and/or the CC) if she/he thinks another budget is more appropriate;
# Can think the request is OK and ask the approvers their opinion;
# Consult the relevant Community members as to whether the expenditure should be approved (e.g. on a dev@ mailing list);
# Can ask the whole cc for a decision in case for example the available budget is not clear or to low.
3. The budget holder then informs the one that made the request, and continues as written in [[Community_Council/Funding_And_Budgets#Purchasing_Goods_and_Services | Purchasing Goods and Services]] and [[Community_Council/Funding_And_Budgets#Travel_and_Expenses | Travel and Expenses]].

= Budgets =

See the following pages for the budget holders, details of budgets and expenditure.

* [[Community_Council/Funding_And_Budgets/Budget_2010 | 2010]]
* [[Community_Council/Funding_And_Budgets/Budget_2009 | 2009]]

[[Category:Community Council]]

Community Council/Agenda

2010-06-30T21:39:17Z

CorNouws: /* Agenda and Work Status */

{{Community_Council}}
== Upcoming Meeting ==

Date: 2010-07-01 (Derived from the [[Community Council/Calendar|Community Council Meeting Calendar]])

Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=01&month=07&year=2010&hour=18&min=30&sec=0&p1=0 18.30 UTC] (click on the link to show world clock times)

Location: IRC

== Agenda and Work Status ==

The following table represents the agenda of the upcoming meeting and the current work status of topics / action items. Working with this table is described in the [[Community Council/Meeting Guidelines|Community Council Meeting Guidelines]].

{| class="prettytable sortable"
|-
! scope="col" | ID 
! scope="col" | Topic 
! scope="col" | Status 
! scope="col" | Responsible 
! scope="col" | Last Update 
! scope="col" | Details 
|-
| 0 
| List of Action Items of previous meeting for approval 
| ''none'' 
| all 
| 2010-05-20 
|
*Meeting minutes of previous meeting at [[Community Council/Minutes#2010-04-29|Minutes#2010-04-29]] 
*Result: Meeting minutes have been approved in the CC meeting.

|-
| 2010-03-04#2 
| Refresh Incubator and NLC Project processes 
| Accepted 
| Louis 
| 2010-03-18 
|
*No new proposal available. Louis will work on that. 
*Next steps: Will be discussed in next meeting.

|-
| 2010-03-04#3 
| Publicize the open slot at the start of the CC meetings 
| Accepted 
| Martin 
| 2010-06-10 
|
*proposal had been presented on March 30th and agreed on 
*Martin to prepare announcement on discuss before next meeting 

|-
| 2010-03-04#4 
| Work with Clayton on estimates for Developing developers documentation 
| Accepted 
| Jürgen 
| 2010-06-30 
|
*New proposal has been sent to the list by Jürgen ([http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2505 here]). The basic idea is to provide bounties instead of contracting one writer. 
*For any proposal, the development budget may require an upgrade. Matthias, Stefan and Martin will provide a proposal (Cor will join, see 2010-03-04#5).
*Juergen talked with Clayton and they will come up with some drafts for the first bounties and in relation to the drafts with a set of basic rules/guideline that are necessary to run such a bounty program (see [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2540 mail on council-discuss]). 
*Next steps:
**Juergen will summarize some information on a wiki page. 
**Budget discussion will be continued in next CC meeting. It is assumed that there will be more information on how much will be provided for each work package.

*No real update, simply because the lack of time
**Clayton and i are working on a wiki page to present/describe the idea of bounties and to present the first 4-5 bounty ideas. I expect that we can publish it soon, currently we make slow progress because of vacation or general unavailability.
*We have prepared the [http://wiki.services.openoffice.org/wiki/Documentation/Bounties initial wiki] page (still a draft) and have described the first two bounties. More bounties will coming soon ... We already have some more ideas but we want to talk with some people about it before we put it as a bounty in the wiki. Important at this point was to define the basic rules and conditions for the bounty program. If there are no complaints we plan to announce the bounty program next week.
* The bounty program is up and running. Two projects are already assigned. We will review the program after 2-3 finished bounties to analyze and to improve the process and how it works in general.
* AI is done!

|-
| 2010-03-04#6 
| Talk to Education Project Leads about structure and remit 
| Stalled 
| John, Cor 
| 2010-03-18 
|
*Cor to prepare a draft and present it to the Community Council. Nothing done yet.
*Next steps: Will be discussed in next meeting. 

|-
| 2010-04-01#7 
| Talk to NLC about ‘NLC of the Month’ for OOo Newsletter 
| Accepted 
| Charles 
| 2010-04-01 
|
*Inteview with the Irish team has been done. No further information available by his deputy (Leif). 
*Next steps: Charles has scheduled the next project to be interviewed (the Sinhala project). He would also like to discuss how to extend the media impact of these interviews. 

|-
| 2010-04-01#1 
| Community situation 
| Accepted 
| All 
| 2010-04-01 
|
*What do we see, where are we, what are we going to do about it.

|-
| 2010-04-29#1
| CC Election (Product Development Representative)
| Accepted
| Christoph
| 2010-06-28
|
*In the election [http://wiki.services.openoffice.org/wiki/Community_Council/Elections/2010-03 2010-03], one of the three roles hasn't been confirmed. We'll re-do the whole election cycle for the "Product Development Representative". 
*Status:
**Overview: See current state of the election [[Community Council/Elections/2010-06|2010-06]].
**Current Phase: Voting 
*Question: There has been a comment by the community whether the voting period should be extended due to the holiday season. Any comments? 
*Next steps: Waiting for the voting to be finished (by time). 

|-
| 2010-04-29#2 
|
Missing OOo desktop presence

| Accepted 
| Christoph, Stefan
| 2010-06-08 
|
*Request by a community member to discuss / decide the following question: "''Why should OpenOffice.org give away it's presence on the user's desktop - the main place to be recognized by the people - only to support the "application independency" of ODF?'' A Sun employee stated "The idea of supporting ODF as a application independent open standard is the priority." This leads / will lead to changes with regard to the document and application icon design. The current ODF "only" icons seem to be undesired by the community. Original request to the CC on ooo-discuss: [http://www.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=65958 initial mail (2010-04-14)], [http://www.openoffice.org/servlets/BrowseList?listName=discuss&from=2361081&to=2361081&count=28&by=thread&first=1&windowSize=1000 full mail thread]
*Discussion:
**2010-04-29: Some members stated that the request should be "more actionable" and "better framed" to be decided by the community. Proposal has been made to forward the request to council-discuss to propose how to proceed.
**2010-05-02: Christoph forwarded the [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2564 request to the CC mailing list]. A first discussion took place.
**2010-05-20: Intensive discussion about the request and how to address it. Stefan and Christoph agreed to work out a request to the ODF Icons team to iterate on the design and/or processes. Maybe a "refreshed" team which may provide an agreed-upon proposal. Stefan stated that there shouldn't be any dependency to the next/other releases.
**2010-06-08: Some opinions have been requested by people who initially worked in the branding initiative. Either there isn't feedback yet, or the people aren't currently available to support the i-Team. Ongoing ...
*Next steps: Christoph will formulate a proposal to be discussed with Stefan. This will be presented to the CC on the CC discuss mailing list. 

|-
| 2010-05-20#1
| Next Council Coordinator
| Accepted
| Christoph
| 2010-06-08
|
*There is a need to elect a new Council Coordinator. Time seems to be up for Christoph according to the [http://wiki.services.openoffice.org/wiki/Community_Council#Council_coordinator Council Wiki Page].
*Status:
**2010-05-20: Due to time constraints, the item has been skipped in the CC meeting. 
**2010-05-27: Christoph sent [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2615 a request] to the CC discuss mailing list. No reply yet... 
*Next steps: Christoph waits for somebody to step in. 

|}

 

== Minutes of Previous Meetings ==

To be found [[Community Council/Minutes|here]].

[[Category:Community_Council]]

Community Council/Agenda

2010-06-30T21:38:04Z

CorNouws: /* Agenda and Work Status */

{{Community_Council}}
== Upcoming Meeting ==

Date: 2010-07-01 (Derived from the [[Community Council/Calendar|Community Council Meeting Calendar]])

Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=01&month=07&year=2010&hour=18&min=30&sec=0&p1=0 18.30 UTC] (click on the link to show world clock times)

Location: IRC

== Agenda and Work Status ==

The following table represents the agenda of the upcoming meeting and the current work status of topics / action items. Working with this table is described in the [[Community Council/Meeting Guidelines|Community Council Meeting Guidelines]].

{| class="prettytable sortable"
|-
! scope="col" | ID 
! scope="col" | Topic 
! scope="col" | Status 
! scope="col" | Responsible 
! scope="col" | Last Update 
! scope="col" | Details 
|-
| 0 
| List of Action Items of previous meeting for approval 
| ''none'' 
| all 
| 2010-05-20 
|
*Meeting minutes of previous meeting at [[Community Council/Minutes#2010-04-29|Minutes#2010-04-29]] 
*Result: Meeting minutes have been approved in the CC meeting.

|-
| 2010-03-04#2 
| Refresh Incubator and NLC Project processes 
| Accepted 
| Louis 
| 2010-03-18 
|
*No new proposal available. Louis will work on that. 
*Next steps: Will be discussed in next meeting.

|-
| 2010-03-04#3 
| Publicize the open slot at the start of the CC meetings 
| Accepted 
| Martin 
| 2010-06-10 
|
*proposal had been presented on March 30th and agreed on 
*Martin to prepare announcement on discuss before next meeting 

|-
| 2010-03-04#4 
| Work with Clayton on estimates for Developing developers documentation 
| Accepted 
| Jürgen 
| 2010-06-30 
|
*New proposal has been sent to the list by Jürgen ([http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2505 here]). The basic idea is to provide bounties instead of contracting one writer. 
*For any proposal, the development budget may require an upgrade. Matthias, Stefan and Martin will provide a proposal (Cor will join, see 2010-03-04#5).
*Juergen talked with Clayton and they will come up with some drafts for the first bounties and in relation to the drafts with a set of basic rules/guideline that are necessary to run such a bounty program (see [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2540 mail on council-discuss]). 
*Next steps:
**Juergen will summarize some information on a wiki page. 
**Budget discussion will be continued in next CC meeting. It is assumed that there will be more information on how much will be provided for each work package.

*No real update, simply because the lack of time
**Clayton and i are working on a wiki page to present/describe the idea of bounties and to present the first 4-5 bounty ideas. I expect that we can publish it soon, currently we make slow progress because of vacation or general unavailability.
*We have prepared the [http://wiki.services.openoffice.org/wiki/Documentation/Bounties initial wiki] page (still a draft) and have described the first two bounties. More bounties will coming soon ... We already have some more ideas but we want to talk with some people about it before we put it as a bounty in the wiki. Important at this point was to define the basic rules and conditions for the bounty program. If there are no complaints we plan to announce the bounty program next week.
* The bounty program is up and running. Two projects are already assigned. We will review the program after 2-3 finished bounties to analyze and to improve the process and how it works in general.
* AI is done!

|-
| 2010-03-04#6 
| Talk to Education Project Leads about structure and remit 
| Stalled 
| John, Cor 
| 2010-03-18 
|
*Cor to prepare a draft and present it to the Community Council. Nothing done yet.
*Next steps: Will be discussed in next meeting. 

|-
| 2010-04-01#7 
| Talk to NLC about ‘NLC of the Month’ for OOo Newsletter 
| Accepted 
| Charles 
| 2010-04-01 
|
*Inteview with the Irish team has been done. No further information available by his deputy (Leif). 
*Next steps: Charles has scheduled the next project to be interviewed (the Sinhala project). He would also like to discuss how to extend the media impact of these interviews. 

|-
| 2010-04-01#1 
| Community situation 
| Accepted 
| All 
| 2010-04-01 
|
*What do we see, where are we, what are we going to do about it.

|-
| 2010-04-29#1
| CC Election (Product Development Representative)
| Accepted
| Christoph
| 2010-06-28
|
*In the election [http://wiki.services.openoffice.org/wiki/Community_Council/Elections/2010-03 2010-03], one of the three roles hasn't been confirmed. We'll re-do the whole election cycle for the "Product Development Representative". 
*Status:
**Overview: See current state of the election [[Community Council/Elections/2010-06|2010-06]].
**Current Phase: Voting 
*Question: There has been a comment by the community whether the voting period should be extended due to the holiday season. Any comments? 
*Next steps: Waiting for the voting to be finished (by time). 

|-
| 2010-04-29#2 
|
Missing OOo desktop presence

| Accepted 
| Christoph, Stefan
| 2010-06-08 
|
*Request by a community member to discuss / decide the following question: "''Why should OpenOffice.org give away it's presence on the user's desktop - the main place to be recognized by the people - only to support the "application independency" of ODF?'' A Sun employee stated "The idea of supporting ODF as a application independent open standard is the priority." This leads / will lead to changes with regard to the document and application icon design. The current ODF "only" icons seem to be undesired by the community. Original request to the CC on ooo-discuss: [http://www.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=65958 initial mail (2010-04-14)], [http://www.openoffice.org/servlets/BrowseList?listName=discuss&from=2361081&to=2361081&count=28&by=thread&first=1&windowSize=1000 full mail thread]
*Discussion:
**2010-04-29: Some members stated that the request should be "more actionable" and "better framed" to be decided by the community. Proposal has been made to forward the request to council-discuss to propose how to proceed.
**2010-05-02: Christoph forwarded the [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2564 request to the CC mailing list]. A first discussion took place.
**2010-05-20: Intensive discussion about the request and how to address it. Stefan and Christoph agreed to work out a request to the ODF Icons team to iterate on the design and/or processes. Maybe a "refreshed" team which may provide an agreed-upon proposal. Stefan stated that there shouldn't be any dependency to the next/other releases.
**2010-06-08: Some opinions have been requested by people who initially worked in the branding initiative. Either there isn't feedback yet, or the people aren't currently available to support the i-Team. Ongoing ...
*Next steps: Christoph will formulate a proposal to be discussed with Stefan. This will be presented to the CC on the CC discuss mailing list. 

|-
| 2010-05-07#1
| Do not promote proprietary software through the OpenOffice.org extensions library
| Rejected
|   (none)
| 2010-05-20
|
*Source: User "Juca" added this item 2010-05-07.
*OpenOffice.org is free software, but some of the extensions it offers to the users are proprietary. OpenOffice.org extensions library should not promote proprietary extensions. 
*Result: The Council already discussed this issue due to a request by the FSF. The reply can be found [http://www.openoffice.org/servlets/ReadMsg?list=announce&msgNo=417 here].

|-
| 2010-05-20#1
| Next Council Coordinator
| Accepted
| Christoph
| 2010-06-08
|
*There is a need to elect a new Council Coordinator. Time seems to be up for Christoph according to the [http://wiki.services.openoffice.org/wiki/Community_Council#Council_coordinator Council Wiki Page].
*Status:
**2010-05-20: Due to time constraints, the item has been skipped in the CC meeting. 
**2010-05-27: Christoph sent [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2615 a request] to the CC discuss mailing list. No reply yet... 
*Next steps: Christoph waits for somebody to step in. 

|}

 

== Minutes of Previous Meetings ==

To be found [[Community Council/Minutes|here]].

[[Category:Community_Council]]

Community Council/Minutes

2010-06-30T21:09:25Z

CorNouws: /* IRC Log */

{{Community_Council}}
= Minutes of Meetings =

== 2010-06-10 ==

=== IRC Log ===

See  [[Community Council Log 20100610]]

=== minutes ===

{| class="prettytable sortable"
|-
! scope="col" | ID 
! scope="col" | Topic 
! scope="col" | Status 
! scope="col" | Responsible 
! scope="col" | Last Update 
! scope="col" | Details 
|-
| 0 
| List of Action Items of previous meeting for approval 
| ''none'' 
| all 
| 2010-05-20 
|
*Meeting minutes of previous meeting at [[Community Council/Minutes#2010-04-29|Minutes#2010-04-29]] 
*Result: Meeting minutes have been approved in the CC meeting.

|-
| 2010-03-04#2 
| Refresh Incubator and NLC Project processes 
| Accepted 
| Louis 
| 2010-03-18 
|
*No new proposal available. Louis will work on that. 
*Next steps: Will be discussed in next meeting.

|-
| 2010-03-04#3 
| Publicize the open slot at the start of the CC meetings 
| Accepted 
| Martin 
| 2010-06-10 
|
*proposal had been presented on March 30th and agreed on 
*Martin to prepare announcement on discuss before next meeting 

|-
| 2010-03-04#4 
| Work with Clayton on estimates for Developing developers documentation 
| Accepted 
| Jürgen 
| 2010-06-30 
|
*New proposal has been sent to the list by Jürgen ([http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2505 here]). The basic idea is to provide bounties instead of contracting one writer. 
*For any proposal, the development budget may require an upgrade. Matthias, Stefan and Martin will provide a proposal (Cor will join, see 2010-03-04#5).
*Juergen talked with Clayton and they will come up with some drafts for the first bounties and in relation to the drafts with a set of basic rules/guideline that are necessary to run such a bounty program (see [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2540 mail on council-discuss]). 
*Next steps:
**Juergen will summarize some information on a wiki page. 
**Budget discussion will be continued in next CC meeting. It is assumed that there will be more information on how much will be provided for each work package.

*No real update, simply because the lack of time
**Clayton and i are working on a wiki page to present/describe the idea of bounties and to present the first 4-5 bounty ideas. I expect that we can publish it soon, currently we make slow progress because of vacation or general unavailability.
*We have prepared the [http://wiki.services.openoffice.org/wiki/Documentation/Bounties initial wiki] page (still a draft) and have described the first two bounties. More bounties will coming soon ... We already have some more ideas but we want to talk with some people about it before we put it as a bounty in the wiki. Important at this point was to define the basic rules and conditions for the bounty program. If there are no complaints we plan to announce the bounty program next week.
* The bounty program is up and running. Two projects are already assigned. We will review the program after 2-3 finished bounties to analyze and to improve the process and how it works in general.
* AI is done!

|-
| 2010-03-04#5 
| OpenOffice.org Internship 
| Finalized 
| Cor, John 
| 2010-05-20 
|
*Original topic: Talk to Google about 2010 SoC. We have been informed that Google refuses projects from OpenOffice.org. It had been decided before to go for the own "OpenOffice.org Internship" in that situation.
*A draft for the internship program had been worked out ([[OpenOffice.org Internship|here]]). All CC members were asked to comment this proposal on the CC mailing list before Tuesday March 23. Budget may be possible issue, since required for here and for documentation (AI 2010-03-04#4). Cor joined the discussion to work on a proposal.
*The OpenOffice.org Internship Programme has been officially announced on several channels, e.g. [http://www.openoffice.org/servlets/ReadMsg?list=announce&msgNo=418 a mail on the announce-list].
*Result: In the CC meeting it has been decided to mark this item "finalized".

|-
| 2010-03-04#6 
| Talk to Education Project Leads about structure and remit 
| Accepted 
| John, Cor 
| 2010-03-18 
|
*Cor to prepare a draft and present it to the Community Council. Nothing done yet.
*Next steps: Will be discussed in next meeting. 

|-
| 2010-04-01#7 
| Talk to NLC about ‘NLC of the Month’ for OOo Newsletter 
| Accepted 
| Charles 
| 2010-04-01 
|
*Inteview with the Irish team has been done. No further information available by his deputy (Leif). 
*Next steps: Charles has scheduled the next project to be interviewed (the Sinhala project). He would also like to discuss how to extend the media impact of these interviews. 

|-
| 2010-04-01#1 
| Community situation 
| Accepted 
| All 
| 2010-04-01 
|
*What do we see, where are we, what are we going to do about it.

|-
| 2010-04-29#1
| CC Election (Product Development Representative)
| Accepted
| Christoph
| 2010-06-28
|
*In the election [http://wiki.services.openoffice.org/wiki/Community_Council/Elections/2010-03 2010-03], one of the three roles hasn't been confirmed. We'll re-do the whole election cycle for the "Product Development Representative". 
*Status:
**Overview: See current state of the election [[Community Council/Elections/2010-06|2010-06]].
**Current Phase: Voting 
*Question: There has been a comment by the community whether the voting period should be extended due to the holiday season. Any comments? 
*Next steps: Waiting for the voting to be finished (by time). 

|-
| 2010-04-29#2 
|
Missing OOo desktop presence

| Accepted 
| Christoph, Stefan
| 2010-06-08 
|
*Request by a community member to discuss / decide the following question: "''Why should OpenOffice.org give away it's presence on the user's desktop - the main place to be recognized by the people - only to support the "application independency" of ODF?'' A Sun employee stated "The idea of supporting ODF as a application independent open standard is the priority." This leads / will lead to changes with regard to the document and application icon design. The current ODF "only" icons seem to be undesired by the community. Original request to the CC on ooo-discuss: [http://www.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=65958 initial mail (2010-04-14)], [http://www.openoffice.org/servlets/BrowseList?listName=discuss&from=2361081&to=2361081&count=28&by=thread&first=1&windowSize=1000 full mail thread]
*Discussion:
**2010-04-29: Some members stated that the request should be "more actionable" and "better framed" to be decided by the community. Proposal has been made to forward the request to council-discuss to propose how to proceed.
**2010-05-02: Christoph forwarded the [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2564 request to the CC mailing list]. A first discussion took place.
**2010-05-20: Intensive discussion about the request and how to address it. Stefan and Christoph agreed to work out a request to the ODF Icons team to iterate on the design and/or processes. Maybe a "refreshed" team which may provide an agreed-upon proposal. Stefan stated that there shouldn't be any dependency to the next/other releases.
**2010-06-08: Some opinions have been requested by people who initially worked in the branding initiative. Either there isn't feedback yet, or the people aren't currently available to support the i-Team. Ongoing ...
*Next steps: Christoph will formulate a proposal to be discussed with Stefan. This will be presented to the CC on the CC discuss mailing list. 

|-
| 2010-05-07#1
| Do not promote proprietary software through the OpenOffice.org extensions library
| Rejected
|   (none)
| 2010-05-20
|
*Source: User "Juca" added this item 2010-05-07.
*OpenOffice.org is free software, but some of the extensions it offers to the users are proprietary. OpenOffice.org extensions library should not promote proprietary extensions. 
*Result: The Council already discussed this issue due to a request by the FSF. The reply can be found [http://www.openoffice.org/servlets/ReadMsg?list=announce&msgNo=417 here].

|-
| 2010-05-20#1
| Next Council Coordinator
| Accepted
| Christoph
| 2010-06-08
|
*There is a need to elect a new Council Coordinator. Time seems to be up for Christoph according to the [http://wiki.services.openoffice.org/wiki/Community_Council#Council_coordinator Council Wiki Page].
*Status:
**2010-05-20: Due to time constraints, the item has been skipped in the CC meeting. 
**2010-05-27: Christoph sent [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2615 a request] to the CC discuss mailing list. No reply yet... 
*Next steps: Christoph waits for somebody to step in. 

|}

== 2010-05-20 ==

=== IRC Log ===

See  [[Community Council Log 20100520]]

=== Minutes ===

tbd

== 2010-04-29 ==

=== IRC Log ===

See [[Community Council Log 20100429]]

=== Minutes ===

Note: Council members didn't update their actions items appropriately. If you have doubts, please have a look at the IRC Log (above).

{| class="prettytable sortable"
|-
! scope="col" | ID 
! scope="col" | Topic 
! scope="col" | Status 
! scope="col" | Responsible 
! scope="col" | Last Update 
! scope="col" | Details 
|-
| 0 
| List of Action Items of previous meeting for approval 
| ''none'' 
| all 
| 2010-04-29 
|
*Meeting minutes of previous meeting at [[Community Council/Minutes#2010-04-15|Minutes#2010-04-15]] 
*Result: Minutes have been approved.

|-
| 2010-03-04#1 
| CC Elections (Martin, Pavel, John) 
| Finalized 
| Louis, Christoph 
| 2010-04-29 
|
*Voting phase has been finished. Two of the three candidates have been confirmed. Final result is available here: [[Community Council/Elections/2010-03|Elections/2010-03]]. 
**Follow-up action item 2010-04-23#1 to decide how to deal with the unconfirmed "Product Development Representative". 
**According to meeting 2010-04-01: Christoph will update the Election Process bylaw once the current election is over. The change will describe the exclusive use of dedicated tooling for the voting, e.g. LimeSurvey. The version of the bylaw will be changed from 1.0 to 1.1. 
*Result 2010-04-29: Item has been finalized.

|-
| 2010-03-04#2 
| Refresh Incubator and NLC Project processes 
| Accepted 
| Louis 
| 2010-03-18 
|
*No new proposal available. Louis will work on that. 
*Next steps: Will be discussed in next meeting.

|-
| 2010-03-04#3 
| Publicize the open slot at the start of the CC meetings 
| Accepted 
| Martin 
| 2010-03-18 
|
*According to Martin, the current proposal has to be reworked. It is being worked on. 
*It has been clarified to provide this "open slot" on a regular basis (e.g. monthly, or each CC meeting). 
*Proposal: Martin will provide a new proposal in the next few days. 

|-
| 2010-03-04#4 
| Work with Clayton on estimates for Developing developers documentation 
| Accepted 
| Jürgen 
| 2010-05-20 
|
*New proposal has been sent to the list by Jürgen ([http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2505 here]). The basic idea is to provide bounties instead of contracting one writer. 
*For any proposal, the development budget may require an upgrade. Matthias, Stefan and Martin will provide a proposal (Cor will join, see 2010-03-04#5).
*Juergen talked with Clayton and they will come up with some drafts for the first bounties and in relation to the drafts with a set of basic rules/guideline that are necessary to run such a bounty program (see [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2540 mail on council-discuss]). 
*Next steps:
**Juergen will summarize some information on a wiki page. 
**Budget discussion will be continued in next CC meeting. It is assumed that there will be more information on how much will be provided for each work package.

*No real update, simply because the lack of time
**Clayton and i are working on a wiki page to present/describe the idea of bounties and to present the first 4-5 bounty ideas. I expect that we can publish it soon, currently we make slow progress because of vacation or general unavailability.
*We have prepared the [http://wiki.services.openoffice.org/wiki/Documentation/Bounties initial wiki] page (still a draft) and have described the first two bounties. More bounties will coming soon ... We already have some more ideas but we want to talk with some people about it before we put it as a bounty in the wiki. Important at this point was to define the basic rules and conditions for the bounty program. If there are no complaints we plan to announce the bounty program next week.

|-
| 2010-03-04#5 
| OpenOffice.org Internship (was: Talk to Google about 2010 SoC) 
| Accepted 
| Cor, John 
| 2010-03-18 
|
*We have been informed that Google refuses projects from OpenOffice.org. It had been decided before to go for the own "OpenOffice.org Internship" in that situation.
*A draft for the internship program is worked out ([[OpenOffice.org Internship|here]]). All CC members are asked to comment this proposal on the CC mailing list before Tuesday March 23.
*Budget may be possible issue, since required for here and for documentation (AI 2010-03-04#4). Cor will join the discussion to work on a proposal.
*Next steps:
**Cor joins the the budget discussion.
**Prepare approval and launch asap.

|-
| 2010-03-04#6 
| Talk to Education Project Leads about structure and remit 
| Accepted 
| John, Cor 
| 2010-03-18 
|
*Cor to prepare a draft and present it to the Community Council. Nothing done yet.
*Next steps: Will be discussed in next meeting. 

|-
| 2010-04-01#7 
| Talk to NLC about ‘NLC of the Month’ for OOo Newsletter 
| Accepted 
| Charles 
| 2010-04-01 
|
*Inteview with the Irish team has been done. No further information available by his deputy (Leif). 
*Next steps: Charles has scheduled the next project to be interviewed (the Sinhala project). He would also like to discuss how to extend the media impact of these interviews. 

|-
| 2010-04-01#1 
| Community situation 
| Accepted 
| All 
| 2010-04-01 
|
*What do we see, where are we, what are we going to do about it.

|-
| 2010-04-29#1
| CC Election (Product Development Representative)
| Accepted
|   Christoph
| 2010-04-29
|
*Initial situation: In the election [http://wiki.services.openoffice.org/wiki/Community_Council/Elections/2010-03 2010-03], one of the three roles hasn't been confirmed. How to proceed?
*Proposal: Re-do the whole election cycle for the "Product Development Representative". 
*Result: All agreed to proposal.
*Next steps:
**Christoph will create a new wiki page for the elections 2010-05.
**Elections itself will be started as soon as possible.

|-
| 2010-04-29#2 
| Missing OOo desktop presence
| New 
|   ??? 
| 2010-04-29 
|
*Request by a community member to discuss / decide the following question: "''Why should OpenOffice.org give away it's presence on the user's desktop - the main place to be recognized by the people - only to support the "application independency" of ODF?'' A Sun employee stated "The idea of supporting ODF as a application independent open standard is the priority." This leads / will lead to changes with regard to the document and application icon design. The current ODF "only" icons seem to be undesired by the community. Original request to the CC on ooo-discuss: [http://www.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=65958 initial mail (2010-04-14)], [http://www.openoffice.org/servlets/BrowseList?listName=discuss&from=2361081&to=2361081&count=28&by=thread&first=1&windowSize=1000 full mail thread]
*Discussion:
**Some members stated that the request should be "more actionable" and "better framed" to be decided by the community.
**Proposal has been made to forward the request to council-discuss to propose how to proceed.
*Next steps: Christoph will forward the request to council-discuss. 

|-
| 2010-04-29#3
| CC Meetings Calendar
| Finalized
| Christoph
| 2010-04-29
|
*Two months ago, the CC decided to meet each 2 weeks instead of 3 for a "test period". Now there is a need to decide how to continue and to update the [http://wiki.services.openoffice.org/wiki/Community_Council/Calendar CC meeting calender] page.
*Result: We proceed with the 3 weeks schedule for the next meetings.
*Next steps: [[Community Council/Calendar|CC meeting calender]] has been updated. 

|}

== 2010-04-15 ==

=== IRC Log ===

See [[Community Council Log 20100415]]

=== Minutes ===

To be done (hopefully). In the meantime, you may refer to the [http://wiki.services.openoffice.org/w/index.php?title=Community_Council/Agenda&oldid=162224 Agenda and Work status page (2010-04-01)].

== 2010-04-01 ==

=== IRC Log ===

See [[Community Council Log 20100401]]

=== Minutes ===

tbd

== 2010-03-18 ==

=== IRC Log ===

See [[Community Council Log 20100318]]

=== Minutes ===

{| class="prettytable sortable"
|-
! scope="col" | ID 
! scope="col" | Topic 
! scope="col" | Status 
! scope="col" | Responsible 
! scope="col" | Last Update 
! scope="col" | Details 
|-
| 0 
| List of Action Items of previous meeting for approval 
| ''none'' 
| all 
| ''none'' 
|
*No meeting minutes available for 2010-03-04 
*Instead, all agreed on the minutes log [[Community Council Log 20100304]]

|-
| 2010-03-04#1 
| CC Elections (Martin, Pavel, John) 
| Accepted 
| Louis, Christoph 
| 2010-03-18 
|
*Mail for nominations have been done; several nominations received. 
*Next phase, introduction of the nominees, will be started.
*Overall status can be tracked at [[Community Council/Elections/2010-03|Elections/2010-03]].
*Next steps: Christoph will announce the next phase "introduction". 

|-
| 2010-03-04#2 
| Refresh Incubator and NLC Project processes 
| Accepted 
| Louis 
| 2010-03-18 
|
*No new proposal available. Louis will work on that. 
*Next steps: Will be discussed in next meeting.

|-
| 2010-03-04#3 
| Publicize the open slot at the start of the CC meetings 
| Accepted 
| Martin 
| 2010-03-18 
|
*According to Martin, the current proposal has to be reworked. It is being worked on. 
*It has been clarified to provide this "open slot" on a regular basis (e.g. monthly, or each CC meeting). 
*Proposal: Martin will provide a new proposal in the next few days. 

|-
| 2010-03-04#4 
| Work with Clayton on estimates for Developing developers documentation 
| Accepted 
| Jürgen 
| 2010-03-18 
|
*New proposal has been sent to the list by Jürgen ([http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2505 here]). The basic idea is to provide bounties instead of contracting one writer. 
*All CC members are asked to comment the proposal on the CC mailing list.
*For any proposal, the development budget may require an upgrade. Matthias, Stefan and Martin will provide a proposal (Cor will join, see 2010-03-04#5).
*Reminder to keep an eye how to provide consistency for the different pieces. Will be discussed with Clayton. 
*Next steps: Ongoing discussion on the CC mailing list. 

|-
| 2010-03-04#5 
| OpenOffice.org Internship (was: Talk to Google about 2010 SoC) 
| Accepted 
| Cor, John 
| 2010-03-18 
|
*We have been informed that Google refuses projects from OpenOffice.org. It had been decided before to go for the own "OpenOffice.org Internship" in that situation.
*A draft for the internship program is worked out ([[OpenOffice.org Internship|here]]). All CC members are asked to comment this proposal on the CC mailing list before Tuesday March 23.
*Budget may be possible issue, since required for here and for documentation (AI 2010-03-04#4). Cor will join the discussion to work on a proposal.
*Next steps:
**Cor joins the the budget discussion.
**Prepare approval and launch asap.

|-
| 2010-03-04#6 
| Talk to Education Project Leads about structure and remit 
| Accepted 
| John, Cor 
| 2010-03-18 
|
*Cor to prepare a draft and present it to the Community Council. Nothing done yet.
*Next steps: Will be discussed in next meeting. 

|-
| 2010-03-04#7 
| Talk to NLC about ‘NLC of the Month’ for OOo Newsletter 
| Accepted 
| Charles 
| 2010-03-18 
|
*Inteview with the Irish team has been done. No further information available by his deputy (Leif). 
*Next steps: Charles is asked to provide updates on the CC mailing list. 

|-
| 2010-03-04#8 
| New template for CC meetings 
| Finalized 
| Christoph 
| 2010-03-18 
|
*Current proposal is available at [[Community Council/Proposed Improvements|Proposed_Improvements]]. 
*Everyone (except Leif, deputy of Charles) voted to use it from now on. Charles may add comments in the next few days, if required.
*Next steps: Christoph will update the minutes according the new template. Accepted proposal will be moved to a more "official" wiki page. Announcement to be made on the CC mailing list.

|-
| 2010-03-04#9 
| Refresh Budget Pages on the Wiki with input from Matthias 
| Finalized 
| John 
| 2010-03-18 
|
*Was already finalized in last meeting.
*Next steps: none

|-
| 2010-03-04#10 
| Confirm/discuss [[Community Council/Calendar|proposed dates]] for future council meetings 
| Finalized 
| All 
| 2010-03-18 
|
*Was already finalized in some of the previous meetings.
*Reminder: Request confirmation for future dates (e.g. end of April 2010)
*Next steps: none 

|-
| 2010-03-04#11 
| Trademark 
| Rejected 
| Stefan 
| 2010-03-18 
|
*No updates; will be rejected for now. 
*Next steps: Stefan will re-open this item when a revised policy is available.

|}

== 2010-03-04 ==

=== IRC Log ===

See [[Community Council Log 20100304]]

=== Minutes ===

Minutes and action items are not available.

=== Agenda Items ===

Since no meeting minutes are available, the original agenda will be used instead.

{| class="prettytable"
|-
! No
! Action Item
! Owner
! Due Date
! Additional Information 
|-
| 0
| List of Action Items of previous meeting for approval
| All 
| 
| See [[Community Council/Minutes#2010-02-18|Community_Council/Minutes#2010-02-18]]. 
|-
| 1 
| Hold CC Elections (Martin, Pavel, John)
| Louis / Christoph 
| 
|
2010-03-03: Louis sent the mail for nomination on 2010-02-27. The nomination phase will end 2010-03-15 15 at 24:00 UTC. 

Next Steps: ???

|-
| 2 
| Refresh Incubator and NLC Project processes
| Louis
| 
| 
|-
| 3 
| Publicise the open slot at the start of the CC meetings
| Louis 
| 
| 
|-
| 4
| Work with Clayton on estimates for ''Developing developers'' documentation
| Jürgen 
| 
|
Next Steps: 

*back to rework on a new proposal how to move forward
*Based on a further talk with Clayton Juergen has sent out a new idea of a bounty program on the discuss@council.openoffice.org mailing list. The main idea of it is to define many smaller and more fine grained projects and make them publicly available. Each projects will be honored with a appropriate amount of money depending on the project. For more details see the email. 

|-
| 5
| Talk to Google about 2010 SoC
| John
| 
|
Next Steps: 

*Cor and John will keep the Community Council updated. 
*The topic will be raised in the next meeting which will be held in two weeks of time. 

|-
| 6
| Talk to Education Project Leads about structure and remit
| Cor
| 
|
Next Step: Cor will prepare a draft and present it to the Community Council. 

|-
| 7
| Talk to NLC about ‘NLC of the Month’ for OOo Newsletter
| Charles
| 
|
Next Steps: 

*Charles currently prepares an interview (source: internal mail). 
*Action item will be kept "in progress" until Charles is back. 

|-
| 8
| New template for CC meetings
| Christoph
| 
|
2010-03-02: The revised proposal is available at [[Community Council/Proposed Improvements|Proposed_Improvements]]. It has been refined to make working with it easier and more efficient. Basically, it is now a continuous table which can be sorted according to several status labels. Originally, I proposed to use different sections to markup the status of action items. Additionally, the proposal to move the "record date" to the action item ID has been incorporated. Please review the proposal - or even better - accept it :-) 

Next Steps:

*If accepted, then the current agenda wiki page will be transformed to respect the proposed format. Additionally, the content of the "Proposed Improvements" page will be moved to a more "official" place.
*If rejected, then ...nothing.
*JSC: +1

|-
| 9
| Refresh Budget Pages on the Wiki with input from Matthias
| John
| 
|
Next Step: John will work on that until the next meeting. 

|-
| 10
| Confirm/discuss [http://wiki.services.openoffice.org/wiki/Community_Council/Calendar proposed dates] for future council meetings
| Christoph
| 2010-03-04 
|
2010-03-02: The revised proposal is available at [[Community Council/Calendar|Community Council Calendar]].

Next Steps: None planned. 

|-
| 11 
| Trademark
| Stefan 
| 
|
Next Step: Stefan will provide some updates in the next meeting.

|}

== 2010-02-18 ==

=== IRC Log ===

List of attendees and IRC log can be found here: [[Community Council Log 20100218]]

=== Minutes ===

{| class="prettytable"
|-
! No
! Action Item
! Owner
! Status
! Additional Information 
|-
| 0
| List of Action Items of previous meeting for approval
| - 
| Approved 
| 
|-
| 1 
| Prepare wiki page for ‘Events’
| Louis
| Done
|
List of events interesting for OpenOffice.org available at [http://wiki.services.openoffice.org/wiki/Events#Year_2010 Events, Year 2010]. From now on, it needs to be completed by MarCon.

|-
| 2 
| Hold CC Elections (Martin, Pavel, John)
| Louis / Christoph 
| In progress 
|
Louis is currently preparing the initial email "New election for Community Council". A second draft is already available and feedback has already been provided. 

Next Steps: 

*Louis is asked to send the initial email - if its ready. 
*Christoph will have a look at the election process and (support to) trigger the next steps. 

|-
| 3 
| Refresh Incubator and NLC Project processes
| Louis
| 
| No update. Will be discussed in next meeting. 
|-
| 4 
| Publicise the open slot at the start of the CC meetings
| Louis 
| 
| No update. Will be discussed in next meeting. 
|-
| 5
| Work with Clayton on estimates for ''Developing developers'' documentation
| Jürgen 
| In progress
|
Clayton has send a first draft to council-discuss ([http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2454 Draft of the Community Council proposal to hire a Tech Writer]), we need some confirmation how to proceed keeping the proposed quote in mind. 

Discussion: 

*The costs are estimated to be roughly 40 K USD. It has been agreed that this seems to be a realistic estimation and maintainability is a very important question. 
*These costs do not fit in any currently planned budget. Some proposals were made how this work might be split / separated to get more manageable pieces (in terms of budget). But it has also been raised that it might only make sense if it is worked on the full documentation. 
*It has been agreed that - before any further decision can be made - all people should have a closer look at Clayton's proposal. 

Next Steps: 

*All CC members will have a closer look at the proposal (link above). (Added by Christoph: Everybody is free to provide proposals how to proceed.) 
*A funding proposal request has to be worked out for the the next meeting. 

|-
| 6
| Talk to Google about 2010 SoC
| John
| In progress 
|
John has sent a mail to the Google representative Leslie Hawthorn a couple of days ago. We are waiting for an answer.

Discussion: It has been raised that the applications for "would-be mentoring applications" is open from 2010-03-08 to 2010-03-12 ([http://groups.google.com/group/google-summer-of-code-discuss/browse_thread/thread/d839c0b02ac15b3f source]). 

Next Steps: 

*Cor and John will keep the Community Council updated. 
*The topic will be raised in the next meeting which will be held in two weeks of time. 

|-
| 7
| Talk to Education Project Leads about structure and remit
| Cor
| In progress 
|
Next Step: Cor will prepare a draft and present it to the Community Council. 

|-
| 8
| Talk to NLC about ‘NLC of the Month’ for OOo Newsletter
| Charles
| In progress 
|
Announcement has been made on the NLC list. One "volunteer" project found for the first month month, the Irish Gaelic project. 

Discussion (a little bit off-topic): 

*John did also inform the responsible for the OpenOffice.org Newsletter (Kay Koll) to use some information from the Community Council minutes. 
*The question was raised how to support Kay to ensure valid information. Sophie stated that usually the newsletter draft is reviewed. 

Next Steps: 

*Charles currently prepares an interview (source: internal mail). 
*Action item will be kept "in progress" until Charles is back. 

|-
| 9
| Talk to Marketing Project about OOoCon support for remote attendees
| John
| Done 
|
Request has been discussed with the Hungarian OOoCon team and with MarCon. The proposal that the MP should set up a 'permanent' arrangement for video for all OOoCons may need finance - probably next year's budget though. The Marketing Project is still discussing if this is a better approach. 

Discussion (a little bit off-topic): 

*Short discussion of whether the location of the OOoCons should be fixed or not. A comparison has been made to FOSDEM. 
*The action item will be closed, because the Marketing Project is aware of this issue. 

|-
| 10
| Reply to FSF Extensions Repository
| Louis
| Done 
| Louis sent the mail and the FSF (Peter Brown) already replied. 
|-
| 11
| New template for CC meetings
| Christoph
| In progress 
|
Some of the proposals from the face-to-face meeting in Hamburg have been summarized. Work on a draft has been started. It is available at [http://wiki.services.openoffice.org/wiki/Community_Council/Proposed_Improvements Community_Council/Proposed_Improvements]. 

Discussion: 

*Cor estimated this work to be close-to-final. 
*A discussion on how to name the Action Items. The basic requirement is to identify the "age" of the items. Several proposals have been made. 

Next Steps: 

*Everybody will have a look at the draft and provide feedback (if required). 
*Christoph will finalize the proposal and present it in the next meeting to officially accept or reject it. 

|-
| 12
| Refresh Budget Pages on the Wiki with input from Matthias
| John
| 
|
No update. John will work on that until the next meeting. 

Remark: The budget has already been accepted in the face-to-face meeting in Hamburg.

|-
| 13
| Confirm/discuss [http://wiki.services.openoffice.org/wiki/Community_Council/Calendar proposed dates] for future council meetings
| Christoph
| In progress 
|
A first proposal is available at [[Community Council/Calendar|Community Council Calendar]].

Discussion:

*According to Stefan the need for information might be higher during the next months.
*It has been proposed to change the schedule so that the Community Council meetings will be held each two weeks. This applies to the meetings in the next two months to check if this is applicable.
*Some people expressed the demand to reduce the meeting time to about one hour.

Next Step: Christoph will re-work the proposed dates and inform the Community Council members. 

|-
|
| Update of the OpenOffice.org logo and the branding initiative
| -
|
|
Additional discussion.

Discussion:

*Two proposals have been presented to the branding working group.
*A due date has been proposed to finalize the effort.

|-
|
| Trademark
| -
|
|
Additional discussion.

Discussion: Stefan will provide some updates in the next meeting.

|}

 

== 2010-02-04/05 (F2F Meeting in Hamburg) ==

=== Attendees ===

{| class="prettytable"
|-
! Name
! Initials (not the OOo user name)
|-
| Martin Hollmichel
| MHo
|-
| Matthias Huetsch
| MHu
|-
| Cor Nouws
| CNou
|-
| Christoph Noack
| CN
|-
| Louis Suarez-Potts
| LS-P
|-
| Charles-H. Schulz
| C-HS
|-
| John McCreesh
| JPMcC
|-
| Stefan Taxhet
| ST
|-
| Jürgen Schmidt
| JS
|}

=== Minutes ===

==== Status Updates from CC Sponsored Activities ====

'''Trademark Policy'''

ST reported that the draft trademark policy was being reviewed by Sun Legal, but no major changes were expected.

'''Developing developers'''

''The CC welcomed Clayton Cornell for this item'' 

The CC discussed three areas where documentation could be improved: 

*how-to get into core development (technical) 
*how-to engage in the community development process (people) 
*how-to get into extension development (technical) 

There was a discussion on the merits of traditional paper-based documentation versus webinars etc for each of these. 

The CC agreed to focus on extensions, possibly based on Per’s current work with Kai on a gallery extension. Clayton was actioned to come back with a budgetary estimate for the work.

The CC agreed to talk to Google to see whether the Oracle takeover meant that OOo would be accepted this year for the Summer of Code exercise. If not, the CC should press on with its own internship exercise.

'''Pootle Infrastructure'''

''The CC welcomed Rafaella Braconi for this item''

*A new Pootle sys admin was now in place and was actively managing the system
*Some background scripts had been removed. Feedback from the engineers was that performance of Pootle was not hardware constrained.
*the latest version of Pootle would be installed as soon as OOo 3.2 was released

Overall the position had stabilised. Engagement with the Pootle developers was good. We should look to get feedback from the community again in Q2 after the software upgrade. The CC would be willing to help the Pootle team carry out developments to meet OOo requirements if required.

'''Download Infrastructure Migration (MirrorBrain)'''

JPMcC reported that the Marketing Project download reporting system was now being fed from both Bouncer and MirrorBrain, and 3.2 would be released via MirrorBrain. He thanked the MirrorBrain team for their help in meeting OOo’s requirements.

'''Site Infrastructure Migration (Kenai)'''

ST reported on the project to migrate OOo from Collabnet to Kenai. Kenai is based on open source technologies such as Zoomla, Bugzilla, and Rails, but will be managed as a service by a team within Oracle. The OOo Project Leads and Web Project are now actively engaged on the migration which is planned to have three phases:

*fit-gap analysis of Kenai features vs OOo requirements (underway)
*any resulting OOo ‘must have’ features implemented in Kenai
*data migration scripts developed and proven (underway - Collabnet data dump received)

Migration must be complete by end of June. ST believed this was ambitious but achievable, as a pilot project (netbeans.org) had already migrated successfully. There would still be a requirement for a ‘*.services.oo.o’ for OOo-specific requirements.

Link: [http://kenai.com/projects/ooo-migration/pages/Home http://kenai.com/projects/ooo-migration/pages/Home]

==== Agenda Items ====

The additional agenda can be found [[Community Council/Agenda/Face2Face|here]].

'''Oracle / Sun'''

The CC noted the contents of the recent webcasts by Oracle, and that the formal Legal Entity Consolidation of Oracle and Sun Microsystems was due this month. The CC had always valued the relationship with Sun, and looked forward to a similarly fruitful relationship with Oracle. The CC extended their best wishes to the formerly Sun-sponsored community contributors in their new home as a global business unit within Oracle Corporation. The CC had no comment to make on Oracle’s announcement of a commercial ‘Cloud Office’ product other than to state new entrants are always welcome to the ODF ecosystem.

'''Education Project'''

Following on from the ''Developing developers'' initiative and the work with Seneca, the CC debated where these activities should be best placed with OOo. The Education Project would seem an obvious home, but the project had recently undertaken a number of initiatives which were already taking it in several different directions. The CC agreed to talk to the project leads about the structure and remit of the project, to give greater focus and avoid conflicts with other projects.

'''Branding'''

''The CC welcomed Rosana Ardila Biela for this item''

RAB gave a presentation on the work to refresh and relaunch the visual identity of OOo, as part of a branding initiative within the Marketing Project. She presented a revamped OOo logo which was still work in progress within the working party. The CC warmly welcomed the activity, and encouraged the team to reach consensus on a new logo. If the team was unable to do so, then they should present options to the CC for another decision / route - however, it was far better for the experts in the team to decide, rather than the amateurs on the CC!

'''Native Language Community development'''

The CC discussed ways of encouraging NLC development.

*Requests for financial support for Regional Conferences would be considered on a case by case basis. Funding would be start-up only, as conferences are expected to be self-financing. The CC recommends that OOo teams should be encouraged to join forces with other open-source projects to share the costs and efforts involved in running conferences.
*NLCs should be encouraged to volunteer for a ‘Native Language Community of the Month’ spotlight in the OOo Newsletter - C-HS to organise.
*The CC discussed direct funding of new localisations e.g. at the request of a government. Past experience suggested these did not lead to sustainable versions. The success of the NLC within OOo was based round a team of activists providing a complete package of localisation, QA, training, support, etc.

'''‘Greening’ OpenOffice.org'''

The CC discussed ways of minimising OOo’s carbon footprint. OOo’s infrastructure is mostly donated by third parties, which means the CC cannot make direct decisions about e.g. using only renewable electricity in datacentres. The CC agreed that OOoCon should be made more accessible for remote attendees as a priority, e.g. improved web streaming, dial-in access to sessions, mandatory advance submission of papers, etc. Support of remote attendees should be made a key deciding factor in awarding the 2011 OOoCon. The Marketing Project was also asked to consider options - e.g. should the MP be responsible for a web capability centrally every year rather than rely on local teams?

'''Extensions Repository'''

The Free Software Foundation (FSF) has notified the CC that the OOo Extensions Repository does not conform to FSF principles, as it hosts ‘non-free’ software. As a result, any software distributions wishing to conform to FSF standards should not make use of the OOo Repository. The CC agreed that licence information could be improved on the Repository, as this is an important factor people should consider when choosing extensions. The FSF would be welcomed to help in providing this sorting / filtering mechanism. However, the CC would not support a forking or partitioning of the Repository to exclude ‘non-free’ extensions. OOo respects the right of its users to make their own informed choice of software, and believes this is best achieved by a single Repository offering a full selection of extensions.

'''Community Council Effectiveness'''

CC members used the opportunity of this face to face meeting to brainstorm high and low points of 2009, and consider community goals for 2010/2011. An offline presentation by CN highlighted the lack of a consistent trail from the overall OOo mission statement down to project or release goals.

The CC discussed issues with its current processes:

*CC members over-committing to Action Items, which they then fail to deliver
*the quality of the minutes, which makes it hard for community members to understand what the CC is doing
*the amount of time taken up on IRC presenting status reports, which could be more efficiently done in advance

The CC also needs to improve its communication with the Community. The CC agreed to experiment with starting meetings with a public session. The Minutes should be prepared in a form that anyone can understand without having to work through IRC logs. It should also be possible to copy and paste from the Minutes into the monthly OOo Newsletter to give a ‘This Month in the Community Council’ article.

CN (the current facilitator) agreed to work on a new meeting template including these improvements. JPMcC agreed to write up the minutes for this meeting.

'''2010 Budget'''

MHe reported that the current level of monthly donations was sufficient to support the proposed budget. The majority of these donations came from small contributions via PayPal. The CC agreed to adopt the draft budget for 2010 but review it quarterly to see if the allocation between different headings should be amended. MHe agreed to publish a summary of ‘actual vs budget’ quarterly on the wiki. JPMcC agreed to refresh the budget wiki pages for 2010. All projects should be encouraged to put forward proposals for using all the available funding.

==== Action Items ====

{| class="prettytable"
|-
! No
! Action
! Who
! When
! Status
|-
| 
| Prepare wiki page for ‘Events’
| LS-P
| 
| ongoing
|-
| 
| Hold CC Elections (Martin, Pavel, John)
| LS-P
| 
| transferred to CN with help from JMcC
|-
| 
| Refresh Incubator and NLC Project processes
| LS-P
| 
| 
|-
| 
| Publicise the open slot at the start of the CC meetings
| LS-P
| 
| 
|-
| 402.1
| Work with Clayton on estimates for ''Developing developers'' documentation
| JS
| 
| 
|-
| 402.2
| Talk to Google about 2010 SoC
| JPMcC
| 
| 
|-
| 402.3
| Talk to Education Project Leads about structure and remit
| CNou
| 
| 
|-
| 402.4
| Talk to NLC about ‘NLC of the Month’ for OOo Newsletter
| C-HS
| 
| 
|-
| 402.5
| Talk to Marketing Project about OOoCon support for remote attendees
| JPMcC
| 
| 
|-
| 402.6
| Reply to FSF Extensions Repository
| LS-P
| 
| 
|-
| 402.7
| New template for CC meetings
| CN
| 
| 
|-
| 402.8
| Refresh Budget Pages on the Wiki with input from MHe
| JPMcC
| 
| 
|}

 

== 2010-01-21 ==

=== IRC log ===

*[[Community Council Log 20100121]]

=== AIs ===

#Budget '''Louis: prepare a wiki page with events'''.
#Trademark Policy ''ST to take back to trademark list''
#Elections: first cycle is finished. Next steps:
##''Jürgen: Update council webpage'': (done)
##''Louis: Notification to broader community about results'' (done)
##'''Louis: Initiate phase 2 of the new election for Martin, Pavel, John.''': put on hold until after holidays, viz., post 6 jan
##'''Louis: advertise public part at #ooocouncilpub in the beginning before next council meeting''': Louis suggest we do it for next meeting.
#OpenOffice.org Internship
##'''Martin to put together a proposal for hiring a technical writer to document getting started on OOo development.''': open
##'''AI: "Winter of Code"; Cor to own and cry for help if required.'''; list to be used is mentoring @ ooo: open
#Distribution infrastructure (Bouncer); '''John''': We are on target to use mirrorbrain for 3.2; Louis proposed '''AI: that the CC publicly thanks the volunteer mirrors on the release of 3.2 for 9 plus years of heroic work including and esp. osuosl.'''
#l10n infrastructure (Pootle): ''ST: Pootle version upgrade imminent beginnig 2010''; ''AI: Owner?: find better tool that is a closer fit, if necessary''; '''Cor is going to contact Andre.'''
#Procedures for retirement of a project in Incubator and NLC. '''Louis: deliver final wording after the discussion that was on the mail list - carry forward'''; see [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2101] to be inforporated in http://native-lang.openoffice.org/#terminus and http://www.openoffice.org/about_us/protocols_proposing.html
#Proposal for handling incubator and NLC projects. '''Louis: come with clear proposal, so we can put it on the agenda for a future meeting - carry forward'''
#Budget 2010: ''AI: all budget holders to submit their requests for a share of this 100k''. See proposal from Matthias [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2324]; '''Vote on Matthias' Proposal pending'''
#Council coordinator: '''choosing ST's successor''' (for the period from February 2010 - May 2010). (done)
#'''Juergen: Prepare Agenda for F2F Meeting in Hamburg, February 4/5;'''
#Ja added: How to handle impolite remarks in IssueTracker issues ? See issue 107456. Corresponding user ignores changes made to the issue he wrote. (done)

== Archived Meeting Minutes ==

The following pages archive the old meeting minutes of the Community Council:

*[[Community Council/Minutes 2009|Minutes 2009]]
*[[Community Council/Minutes 2008|Minutes 2008]]
*[[Community Council/Minutes 2007|Minutes 2007]]

[[Category:Community_Council]]

Community Council/Agenda

2010-06-30T21:07:41Z

CorNouws: /* Upcoming Meeting */

{{Community_Council}}
== Upcoming Meeting ==

Date: 2010-07-01 (Derived from the [[Community Council/Calendar|Community Council Meeting Calendar]])

Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=01&month=07&year=2010&hour=18&min=30&sec=0&p1=0 18.30 UTC] (click on the link to show world clock times)

Location: IRC

== Agenda and Work Status ==

The following table represents the agenda of the upcoming meeting and the current work status of topics / action items. Working with this table is described in the [[Community Council/Meeting Guidelines|Community Council Meeting Guidelines]].

{| class="prettytable sortable"
|-
! scope="col" | ID 
! scope="col" | Topic 
! scope="col" | Status 
! scope="col" | Responsible 
! scope="col" | Last Update 
! scope="col" | Details 
|-
| 0 
| List of Action Items of previous meeting for approval 
| ''none'' 
| all 
| 2010-05-20 
|
*Meeting minutes of previous meeting at [[Community Council/Minutes#2010-04-29|Minutes#2010-04-29]] 
*Result: Meeting minutes have been approved in the CC meeting.

|-
| 2010-03-04#2 
| Refresh Incubator and NLC Project processes 
| Accepted 
| Louis 
| 2010-03-18 
|
*No new proposal available. Louis will work on that. 
*Next steps: Will be discussed in next meeting.

|-
| 2010-03-04#3 
| Publicize the open slot at the start of the CC meetings 
| Accepted 
| Martin 
| 2010-06-10 
|
*proposal had been presented on March 30th and agreed on 
*Martin to prepare announcement on discuss before next meeting 

|-
| 2010-03-04#4 
| Work with Clayton on estimates for Developing developers documentation 
| Accepted 
| Jürgen 
| 2010-06-30 
|
*New proposal has been sent to the list by Jürgen ([http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2505 here]). The basic idea is to provide bounties instead of contracting one writer. 
*For any proposal, the development budget may require an upgrade. Matthias, Stefan and Martin will provide a proposal (Cor will join, see 2010-03-04#5).
*Juergen talked with Clayton and they will come up with some drafts for the first bounties and in relation to the drafts with a set of basic rules/guideline that are necessary to run such a bounty program (see [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2540 mail on council-discuss]). 
*Next steps:
**Juergen will summarize some information on a wiki page. 
**Budget discussion will be continued in next CC meeting. It is assumed that there will be more information on how much will be provided for each work package.

*No real update, simply because the lack of time
**Clayton and i are working on a wiki page to present/describe the idea of bounties and to present the first 4-5 bounty ideas. I expect that we can publish it soon, currently we make slow progress because of vacation or general unavailability.
*We have prepared the [http://wiki.services.openoffice.org/wiki/Documentation/Bounties initial wiki] page (still a draft) and have described the first two bounties. More bounties will coming soon ... We already have some more ideas but we want to talk with some people about it before we put it as a bounty in the wiki. Important at this point was to define the basic rules and conditions for the bounty program. If there are no complaints we plan to announce the bounty program next week.
* The bounty program is up and running. Two projects are already assigned. We will review the program after 2-3 finished bounties to analyze and to improve the process and how it works in general.
* AI is done!

|-
| 2010-03-04#5 
| OpenOffice.org Internship 
| Finalized 
| Cor, John 
| 2010-05-20 
|
*Original topic: Talk to Google about 2010 SoC. We have been informed that Google refuses projects from OpenOffice.org. It had been decided before to go for the own "OpenOffice.org Internship" in that situation.
*A draft for the internship program had been worked out ([[OpenOffice.org Internship|here]]). All CC members were asked to comment this proposal on the CC mailing list before Tuesday March 23. Budget may be possible issue, since required for here and for documentation (AI 2010-03-04#4). Cor joined the discussion to work on a proposal.
*The OpenOffice.org Internship Programme has been officially announced on several channels, e.g. [http://www.openoffice.org/servlets/ReadMsg?list=announce&msgNo=418 a mail on the announce-list].
*Result: In the CC meeting it has been decided to mark this item "finalized".

|-
| 2010-03-04#6 
| Talk to Education Project Leads about structure and remit 
| Accepted 
| John, Cor 
| 2010-03-18 
|
*Cor to prepare a draft and present it to the Community Council. Nothing done yet.
*Next steps: Will be discussed in next meeting. 

|-
| 2010-04-01#7 
| Talk to NLC about ‘NLC of the Month’ for OOo Newsletter 
| Accepted 
| Charles 
| 2010-04-01 
|
*Inteview with the Irish team has been done. No further information available by his deputy (Leif). 
*Next steps: Charles has scheduled the next project to be interviewed (the Sinhala project). He would also like to discuss how to extend the media impact of these interviews. 

|-
| 2010-04-01#1 
| Community situation 
| Accepted 
| All 
| 2010-04-01 
|
*What do we see, where are we, what are we going to do about it.

|-
| 2010-04-29#1
| CC Election (Product Development Representative)
| Accepted
| Christoph
| 2010-06-28
|
*In the election [http://wiki.services.openoffice.org/wiki/Community_Council/Elections/2010-03 2010-03], one of the three roles hasn't been confirmed. We'll re-do the whole election cycle for the "Product Development Representative". 
*Status:
**Overview: See current state of the election [[Community Council/Elections/2010-06|2010-06]].
**Current Phase: Voting 
*Question: There has been a comment by the community whether the voting period should be extended due to the holiday season. Any comments? 
*Next steps: Waiting for the voting to be finished (by time). 

|-
| 2010-04-29#2 
|
Missing OOo desktop presence

| Accepted 
| Christoph, Stefan
| 2010-06-08 
|
*Request by a community member to discuss / decide the following question: "''Why should OpenOffice.org give away it's presence on the user's desktop - the main place to be recognized by the people - only to support the "application independency" of ODF?'' A Sun employee stated "The idea of supporting ODF as a application independent open standard is the priority." This leads / will lead to changes with regard to the document and application icon design. The current ODF "only" icons seem to be undesired by the community. Original request to the CC on ooo-discuss: [http://www.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=65958 initial mail (2010-04-14)], [http://www.openoffice.org/servlets/BrowseList?listName=discuss&from=2361081&to=2361081&count=28&by=thread&first=1&windowSize=1000 full mail thread]
*Discussion:
**2010-04-29: Some members stated that the request should be "more actionable" and "better framed" to be decided by the community. Proposal has been made to forward the request to council-discuss to propose how to proceed.
**2010-05-02: Christoph forwarded the [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2564 request to the CC mailing list]. A first discussion took place.
**2010-05-20: Intensive discussion about the request and how to address it. Stefan and Christoph agreed to work out a request to the ODF Icons team to iterate on the design and/or processes. Maybe a "refreshed" team which may provide an agreed-upon proposal. Stefan stated that there shouldn't be any dependency to the next/other releases.
**2010-06-08: Some opinions have been requested by people who initially worked in the branding initiative. Either there isn't feedback yet, or the people aren't currently available to support the i-Team. Ongoing ...
*Next steps: Christoph will formulate a proposal to be discussed with Stefan. This will be presented to the CC on the CC discuss mailing list. 

|-
| 2010-05-07#1
| Do not promote proprietary software through the OpenOffice.org extensions library
| Rejected
|   (none)
| 2010-05-20
|
*Source: User "Juca" added this item 2010-05-07.
*OpenOffice.org is free software, but some of the extensions it offers to the users are proprietary. OpenOffice.org extensions library should not promote proprietary extensions. 
*Result: The Council already discussed this issue due to a request by the FSF. The reply can be found [http://www.openoffice.org/servlets/ReadMsg?list=announce&msgNo=417 here].

|-
| 2010-05-20#1
| Next Council Coordinator
| Accepted
| Christoph
| 2010-06-08
|
*There is a need to elect a new Council Coordinator. Time seems to be up for Christoph according to the [http://wiki.services.openoffice.org/wiki/Community_Council#Council_coordinator Council Wiki Page].
*Status:
**2010-05-20: Due to time constraints, the item has been skipped in the CC meeting. 
**2010-05-27: Christoph sent [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2615 a request] to the CC discuss mailing list. No reply yet... 
*Next steps: Christoph waits for somebody to step in. 

|}

 

== Minutes of Previous Meetings ==

To be found [[Community Council/Minutes|here]].

[[Category:Community_Council]]

Community Council/Funding And Budgets

2010-06-24T19:28:44Z

CorNouws: what you must know - added at the top

{{Community_Council}}
= OpenOffice.org Community Council Payments Procedure =
== What you must know, before requesting for funding ==
* Requests must (in general) be approved before the expenditure is done;
* Many tasks in the community are done on voluntary basis - exeptions are rare;
* Requests must be send to the budget holder ([[Community_Council/Funding_And_Budgets#Budgets |read more]]).

== Introduction ==
=== Devolving financial decision-making ===
The OpenOffice.org Community Council is responsible for managing the funds donated centrally to the Community. Decisions on releasing funds are generally taken at meetings of the Community Council. However, the Community Council may decide on an annual basis to approve a Budget, which allows expenditure decisions to be delegated to Budget Holders and Authorisers within the limits set by the Budget. The Community Council expects Budget Holders to consult relevant Community members about how the Budget is spent (e.g. on a ''dev@'' mailing list.). For contacting the Council and holding discussions by Budget authorisers, we have budget@council.openoffice.org, a discuss list requiring subscription for unmoderated posting.

=== Responsibilities ===
Budget Holders will be appointed by the Community Council. They may nominate one or more Authorisers for approval by the Council. Budget Holders and Authorisers must confirm their agreement to comply with this Procedure on appointment - any Budget Holder not following this Procedure will be personally responsible for any liabilities incurred. Budget Holders and Authorisers must also register with the Treasurer the email address they will use. The Community Council strongly encourages the use of signed emails for any correspondence covered by this Procedure.

Under this Procedure, the Community Council Treasurer (or deputy) is responsible for recording total amounts committed, making payments from the central funds, and reporting periodically to the Community Council.

== Purchasing Goods and Services ==
=== Approving a Request to Purchase ===
Budget Holders may raise a Request to Purchase themselves, or process them for other Community members. The Budget Holder may request an email Quotation from the Supplier (note: obtaining a quotation is recommended for all purchases, and is mandatory for purchases of €1,000 or more).

The Budget Holder forwards the Quotation / writes an email detailing:

* what the expenditure is for
* where the good/services should be delivered
* which budget category it falls under
* value / currency including taxes
* Supplier name and address

and emails this Request to Purchase to the Authoriser.

The Authoriser checks the Request to Purchase and either returns it to the Budget Holder with a reason for rejection, or approves it and forwards to the Treasurer.

The Treasurer checks the Budget Holder and Authoriser details on the Request to Purchase, and either returns it to the Budget Holder with a reason for rejection, or accepts it. If accepted, the Request to Purchase is recorded as a commitment on the Purchasing Log. The Treasurer will check on the Purchasing Log that the total committed to date including this new Request is within the approved Budget for this Budget Holder.

If there is funding available, the Treasurer emails the Budget Holder, authorising expenditure and issuing the next Purchase Order Number from the Purchasing Log.

=== Issuing a Purchase Order ===
Once the Budget Holder receives the Purchase Order Number from the Treasurer, the Purchase Order may be issued to the Supplier, quoting the Purchase Order Number, specifying the delivery address (where the goods/services are required) and the invoice address (the Treasurer). A recommended Purchase Order template is available from the Treasurer.

=== Receiving Goods/Services ===
When the good/services are delivered satisfactorily, the Budget Holder must email the Treasurer promptly, quoting the Purchase Order Number, to state the Invoice may now be paid. The Treasurer records the date of the email on the Purchasing Log.

=== Processing an Invoice ===
Invoices must be sent direct from the Supplier to the Treasurer. Any Invoices received from Suppliers without a valid Purchase Order Number will be returned unpaid. On receipt of a Supplier’s Invoice with a valid Purchase Order Number, the Treasurer will check the Purchasing Log to ensure that the details match the Request to Purchase, and that the Invoice has been approved for payment. If approved, the Treasurer will pay the Supplier within the Supplier’s payment terms.

If there are discrepancies, the Treasurer will email the Supplier and the Budget Holder to resolve the differences. If the resolution results in an invoice amount greater than the original Request to Purchase, then the Budget Holder must seek approval from an Authoriser for the additional spend.

== Travel and Expenses ==
=== Approving a Expense Request ===
Any Community member wishing to be refunded by the Community for travel or miscellaneous purchases must obtain approval in advance from a Budget Holder. The request must specify:

* name of the individual and role within the Community
* budget category
* nature of the expense
* if for travel:
* date / duration / nature of the event
* reason for attendance (e.g. presenting a paper, manning a stall...)
* transport details (if any)
* accommodation details (if any)
* value / currency including taxes
* bank account details for reimbursement (unless cash – see below)

The Budget Holder must satisfy themselves that the amount requested is reasonable and appropriate. If the Request is approved, the Budget Holder will email a Travel Approval to the Traveller, with a copy to the Treasurer. The Treasurer will note the amount as a Commitment against the Budget in the Purchasing Log.

Note: the Community will generally not issue advances to fund travel or other miscellaneous expenses. It is the responsibility of the Traveller to ensure they have the necessary funding to cover their expenses until reimbursement is received.

=== Refund of Expenses – Bank Transfer ===
When the trip is complete the Traveller should submit details of the expenditure actually incurred to the Treasurer. The Treasurer will check that the amount is within the amount authorised on the Travel Approval and if so, will issue a refund to the Traveller.

If the amount claimed exceeds the authorised amount the Treasurer will seek approval from the Budget Holder for the excess before making any repayment.

=== Refund of Expenses – Cash ===
At events such as OOoCon it may be more convenient for a Budget Holder or Nominee to issue cash refunds to Travellers in person. In this case, the Budget Holder should request a cash advance from Treasurer sufficient to cover all the Travel Approvals which have been raised for the event. The Budget Holder or Nominee should then arrange to meet the Community Members who require refunds. Each Member should present a copy of their Travel Approval, a statement of the expenses actually incurred, and – if they are not personally known to the Budget Holder - some form of photo identification. The Budget Holder or Nominee must obtain a receipt for all cash disbursed, so the Budget Holder can use these to reconcile any cash balances with the Treasurer at the end of the event.

== Treasurer Responsibilities ==
=== Recording ===
The Treasurer shall be responsible for maintaining accurate and up to date records as described in this Procedure, i.e. a Purchasing Log and details of Budget Holders and Authorisers.

=== Reporting ===
The Treasurer shall use the information in the Purchasing Log to report to the Community Council on expenditures, committed and incurred, versus budget. Every quarter the Community Council will review a summary financial statement and agree whether any changes are required to the budget for the rest of the year. This summary financial statement will be posted to the website.

=== Legal and Statutory considerations ===
This Procedure is designed to satisfy the requirements of the OpenOffice.org Community Council only. It may need to be supplemented by additional procedures to meet the needs of legal, accounting, or other regulatory bodies.

== Handling /routing of requests ==
1. A request must be sent to the budget holder (see under [[Community_Council/Funding_And_Budgets#Budgets | budget]]);
any request that pops up anywhere else, must be redirected there.

2. The budget holder:
# Can ask for more information;
# Can discuss with other budget holders (and/or the CC) if she/he thinks another budget is more appropriate;
# Can think the request is OK and ask the approvers their opinion;
# Consult the relevant Community members as to whether the expenditure should be approved (e.g. on a dev@ mailing list);
# Can ask the whole cc for a decision in case for example the available budget is not clear or to low.
3. The budget holder then informs the one that made the request, and continues as written in [[Community_Council/Funding_And_Budgets#Purchasing_Goods_and_Services | Purchasing Goods and Services]] and [[Community_Council/Funding_And_Budgets#Travel_and_Expenses | Travel and Expenses]].

= Budgets =

See the following pages for the budget holders, details of budgets and expenditure.

* [[Community_Council/Funding_And_Budgets/Budget_2010 | 2010]]
* [[Community_Council/Funding_And_Budgets/Budget_2009 | 2009]]

[[Category:Community Council]]

NL/QA/Testen

2010-06-22T19:10:37Z

CorNouws: aankondiging beta

== Werken met nog niet officiële versies van OpenOffice.org ==

=== Waarom ===
* Het is leuk om de nieuwste ontwikkelingen op de voet te volgen ...
* Hoe eerder fouten in de software worden ontdekt, bij voorkeur nog voor de beta-versies, hoe makkelijker het is om ze te repareren. 
OpenOffice.org brengt vier keer per jaar een nieuwe versie uit (twee keer met nieuwe functies en twee keer met alleen verbeteringen). Er is dus steeds veel nieuws te beleven en te testen.

In de ontwikkelcyclus van het product zijn achtereenvolgens de volgende versies, stadia, te onderscheiden:
* developer builds (snapshots) - om de paar weken;
* beta versies - tegen de tijd dat de nieuwe versie bijna klaar is;
* release kandidaten - een release kandidaat kan de uiteindelijke nieuwe versie worden;
* stabiele versies

Het testen kan heel gestructureerd, maar ook door de software gewoon te installeren en er mee te werken en dan kijken wat voor bijzonderheden je aantreft. Meer hierover verder op deze pagina.
Testen kan heel leuk zijn, want je leert er vaak weer wat van en kunt zelf snel met de nieuwste functies aan de slag. En het helpt om zo vroeg mogelijk zoveel mogelijk fouten op te sporen. Kortom: hulp met testen is altijd welkom!

== Nu beschikbaar om te proberen en te testen ==

===Algemeen: downloaden===
Snapshots enzovoorts zijn steeds te vinden via [http://download.openoffice.org/next/ http://download.openoffice.org/next/]. Rechts op die pagina staan ook verwijzingen naar nuttige aanvullende uitleg. 
Controle van de integriteit van de downloads kan met de MD5 CheckSum test. Uitleg en controle-getallen zijn altijd te vinden op de [http://download.openoffice.org/next/md5sums/ md5sums]-pagina.

===Beta voor 3.3.0 gaat er aan komen===
De beta voor OpenOffice.org 3.3.0 wordt medio augustus verwacht! De developer snapshots (DEV300_m82 en nieuwer) laten al veel van de nieuwe functies zien!

===Snapshots voor de 3.3.x===
Sinds begin oktober 2009 de tak voor de 3.2.x is losgemaakt uit de hoofdstam, wordt de lijn DEV300 verder ontwikkeld richting 3.3.0 en 3.3.1

Nieuwsgierig? De eerste snapshots zijn via [http://download.openoffice.org/next/ http://download.openoffice.org/next/] te vinden.

===Snapshot met nieuwe afdrukvensters - Belangrijke mijlplaal in de ontwikkeling van versie 3.3.0!===
Sinds half januari is Developer build [http://download.openoffice.org/next/ DEV300 m70] beschikbaar.

Daarin is de code opgenomen voor de nieuwe afdrukvensters. Pluspunten: elk afdrukvenster toont een afdrukvoorbeeld, en biedt direct toegang tot alle instellingen.
Lees daarover meer op [http://blogs.sun.com/GullFOSS/entry/new_print_ui_now_integrated GullFoss].

Het is een heel nieuw stuk in OpenOffice.org, dat stevig aan de tand moet worden gevoeld voor de 3.3.0 uit komt. Je kunt deze snapshot downloaden en installeren naast je normale OpenOffice.org versie. (Zie de uitleg elders op deze wiki-pagina.)

== Meer over de achtereenvolgende versies in de ontwikkelcyclus ==

=== Developer builds (snapshots) ===
Zijn redelijk stabiel, maar worden niet aangeraden voor dagelijks werk. 
Installeert apart, naast de normale versie van OpenOffice.org. 
Op de OOo-site staan de nieuwste [http://download.openoffice.org/next/other.htm developer builds], maar die zijn niet in het Nederlands beschikbaar. Op die pagina's is onder de link 'Release Notes' ook een verwijzing naar informatie over de nieuwe functies.

=== Beta versies ===
Het product is bijna gereed, men verwacht dat het product zonder serieuze problemen gebruikt kan worden. De nieuwe functies worden met de beta-uitgaven door veel mensen gebruikt, wat weer extra reacties oplevert. 
Een beta installeert naast een bestaande versie van OpenOffice.org.
=== Release kandidaten ===
Een release kandidaat verschijnt zodra men verwacht dat het product gereed is. Het is tijd voor de laatste tests. 
Bij het installeren, vervangt de release kandidaat de al geïnstalleerde versie van OpenOffice.org, tenzij er wordt gekozen voor parallelle installatie. Die procedure is elders op deze pagina beschreven: [[NL/TipsEnTrucs/Meerdere_versies_van_OOo_uitvoeren| Meerdere versies van OOo uitvoeren]]. 
Als er geen ernstige problemen meer worden gevonden, zal de release kandidaat als de nieuwe stabliele versie worden vrijgegeven.

=== Goedkeuring voor een nieuwe release ===
Voordat een nieuwe versie officieel wordt vrijgegeven, moet er natuurlijk wel wat gebeuren.
Op [[Release_Action_List_for_QA#Approval_of_Builds | deze plek]] staat hoe dat in zijn werk gaat.

== Meerdere versies en talen installeren ==

=== Meerdere versies installeren===
Het is verstandig om de diverse (testversies) naast je huidige OpenOffice.org te installeren. Je kunt dan ook makkelijk functies vergelijken. Op [[NL/TipsEnTrucs/Meerdere_versies_van_OOo_uitvoeren| Meerdere versies van OOo uitvoeren]] staat uitgelegd hoe dat werkt. Kom je ergens niet uit? Mail dan naar [mailto:localization@nl.openoffice.org localization@nl.openoffice.org]

=== Taalversies ===
Het is ook mogelijk om een niet Nederlandse versie van OpenOffice.org (bijv. Engels) te installeren en dan een taalpakket (language pack) voor Nederlands.
Als eerst de volledige versie wordt geïnstalleerd en dan (snelstarter uit!) het Nederlandse taalpakket, kan in Tools>Options>Language settings>Language 'Nederlands' worden gekozen voor de gebruikers interface. Al de menu's, vensters en Help worden dan Engels- of Nederlandstalig.

== Hoe testen ==

=== Inleiding ===
Het zoeken (en oplossen) van fouten gebeurt in verschillende fasen.
* Tijdens de ontwikkeling door het testen van en werken met de developer-builds en beta-releases.
* Bij release-kandidaten gaat het alleen nog om het vinden en corrigeren van echt grote problemen.
* Van de laatste release kandidaat moet ook voor de Nederlandstalige versie een akkoord worden gegeven, alvorens die kan worden vrijgegeven.

=== Geautomatiseerd testen ===
Volgens testplannen worden allemaal functies geautomatiseerd uitgevoerd.
Dit is een doorlopend proces en gebeurt (vooral door de mensen van Sun en RedFlag) dus ook in een vroeg stadium.

Voor de geïnteresseerden, is er de nodige informatie, zoals over de [[Testtool|testtool]] voor geautomatiseerd testen en over het eventueel vertalen daarvan: [[HowTo_localize_qatesttool_environment|how to localiza it]].

=== Testen met TCM ===
Testen volgens TCM is vooral nuttig voor het controleren van nieuwe functies, en tijdens het testen van release-kandidaten.
* Nieuwe functies moeten in een redelijk vroeg stadium worden getest, uiterlijk met een beta-versie, en niet met de release-kandidaten. Bij release kandidaten worden alleen nog heel ernstige bugs gecorrigeerd, en niet als een nieuwe functie niet helemaal perfect werkt ...
* Testen volgens TCM geeft ook een houvast voor het testen van hoofdfuncties, die wel moeten worden gecontroleerd bij een release-kandidaat.

====Localisatie testen van nieuwe uitgaven van OOo====
Voordat je resultaten van je testen kunt invoeren in TCM, of kunt TCM gebruiken voor testideeën, moet je als gebruiker aan TCM worden toegevoegd. 
Mail daarvoor naar [mailto:localization@nl.openoffice.org de localisatie lijst] of naar één van de andere actieve projectleden.
* De startpagina van TCM is [http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_login.cgi?tcm_config=newooo hier].
* Je kunt daar inloggen met username en password
* Ga dan door op stap 5: Test Result Update
* Kies de versie van OOo, de tests die op jouw naam staan, etc.
** Bijvoorbeeld: Klik op 'OpenOffice.org(3.2RC)' in de kolom 'Build Number'
** Zoek in de volgende tabel de regel met je inlognaam.
** Klik in die regel op 'Scenario(Release sanity scenario)'
** Er zijn dan meer dan 20 test beschikbaar.
het is niet altijd nodig dat iedere tester elke test doet ...
het zijn geen ingewikkelde tests, maar kies eventueel dus tests die je graag doet, of overleg per mail met anderen.
** Bij een uitgevoerde test invullen: pass, fail of skip, en voer eventueel commentaar in
** Je kunt ook kijken naar de linkjes naar al eerder gevonden bugs.
*** Het is goed mogelijk dat daar al opgeloste bugs tussen staan - het is nog niet geregeld dat die worden verwijderd/gefilterd.
over criteria om een test op fail te zetten:
dat gebeurt niet om kleinere problemen, alleen als iets echt goed fout zit
vul evt. commentaar in. En al weer: bij vragen is er op de mail lijst altijd hulp!

Vragen, opmerkingen, suggesties welkom!

Zeer nuttige uitgebreide informatie staat in de wiki op de [[Test_Case_Management|de TCM pagina]] en in de uitleg over TCM/testen en de release cyclus [[Release Action List for QA]]

===Minimale check op gelocaliseerde versies===
Wanneer het niet mogelijk is om alle TCM tests te doen, kan worden terug gevallan op een [[NL/QA/SanityCheck_van_Localisaties | lijst met minimale tests]] voor de vrijgave.

Maar we moeten er om denken, dat als iedereen alleen maar 'minimaal' gaat zitten testen, we gauw een probleem hebben ..

=== Testen door er mee te werken ===
Dit kan iedereen doen. Snapshots en beta-versies downloaden en er mee aan de slag gaan.

=== Je ervaringen delen ===
Als je bijzonderheden tegenkomt - meestal fouten ;-) - dan is het de bedoeling dat die in Issuetracker worden geplaatst. Of dat je met je waarneming een issue van een ander bevestigt, of verduidelijkt, of nuanceert.

Informatie voor het gebruiken van Issuetracker staat [http://nl.openoffice.org/about-issuezilla.html hier].

Vaak is het handig om ervaringen te bespreken voordat je de moeite neemt om een issue te maken. Soms heeft iemand anders al een antwoord of issue, of is het probleem in een nieuwe snapshot opgelost. Dat scheelt je dan weer het aanmaken van een issue.
En kom je ergens zelf niet uit: vraag het dan gewoon op localization@nl.openoffice.org.

=== Coördinatie van & informatie over testen===
Al enkele keren genoemd: localization@nl.openoffice.org. Dit is de mailinglijst waar alle lijntjes samen komen. Dus het is leuk en nuttig om je daar voor aan te melden ([mailto:localization-subscribe@nl.openoffice.org localization-subscribe@nl.openoffice.org]).

[[Category:NL.OpenOffice.org|QA]]

NL/Localisatie/Bijwerken vertalingen

CorNouws: /* Possible projects */