Re: [board-discuss] WollMux adoption proposal for The Document Foundation
Servus Susanne, = Foreword: I here speak in my capacity as a Member of the Board of Trustees. = Am 06.12.22 um 07:01 schrieb susanne.mohn...@kiel-pries.de: And Woll? It's the german name for wool. AFAICS, in this case it makes reference to the German/Bavarian "Eierlegendewollmilchsau". https://de.wikipedia.org/wiki/Eierlegende_Wollmilchsau and https://bar.wikipedia.org/wiki/Oarlengde_Woimuichsau At the time I was involved with the City of Munich and this was the saying. But perhaps I am wrong. Moin Moin :) Stephan -- Stephan Ficht, Member of the Board of Trustees Affiliation: The Document Foundation -- To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.documentfoundation.org/www/board-discuss/ Privacy Policy: https://www.documentfoundation.org/privacy
AW: [board-discuss] WollMux adoption proposal for The Document Foundation
Moin moin (north german for good morning) Does anyone know, where the wollmux comes from? Change it to English? MUX comes from Linux for Munic. And Woll? It's the german name for wool. It wood be very nice us in Schleswig-Holstein to have this AddIn. Susanne -Ursprüngliche Nachricht- Von: Marina Latini Gesendet: Dienstag, 6. Dezember 2022 01:19 An: Samuel Mehrbrodt Cc: Thorsten Behrens ; Björn Ranft ; TDF Board Discussion Betreff: Re: [board-discuss] WollMux adoption proposal for The Document Foundation On 05.12.2022 08:10, Samuel Mehrbrodt wrote: > Hi, Hi Samuel, nice to read you :) > >> To clarify - my expectation is, once the project would be at TDF's, >> that future PRs would be done in English (as the most inclusive way). > > All current PRs against master are in English already. > > There are a few German ones left which are against the 18.2 branch > which is still maintained by LHM. Over time, these should be merged or > closed. Sure, any contributor can port those PRs against master, and > then they should be filed in English of course. Thanks for the clarification :) And, just to spell it out, I have nothing against German, it's just that having PRs and issues in English could increase that chance to involve more contributors. But for sure, I don't want to add extra work for the maintainers just for having things translated from German to English ;) >> >> But yeah, my preference would be switching also the existing ones to >> English (Samuel or Björn, what's your take here?). > Yes, these should be converted to master (after checking they are > still valid). yes, some help in closing invalid issues will be extremely valuable. > > I think it does make sense to either use the Cloud version of > SonarQube (as we do with Coverity), or host it ourselves (up to Infra > team to decide). Might add value to other TDF java projects as well > (Java parts of LibreOffice, LOEclipse, etc). > yep, from my experience, sonarcloud seems to be good too. P.S: @Thorsten, I saw that some of the feedback we shared in this discussion are now listed as new GitHub issues. Thanks for that. :) Happy hacking and have a lot of fun, Marina -- Marina Latini IRC: deneb_alpha on LiberaChat -- To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.documentfoundation.org/www/board-discuss/ Privacy Policy: https://www.documentfoundation.org/privacy -- To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.documentfoundation.org/www/board-discuss/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [board-discuss] WollMux adoption proposal for The Document Foundation
On 05.12.2022 08:10, Samuel Mehrbrodt wrote: Hi, Hi Samuel, nice to read you :) To clarify - my expectation is, once the project would be at TDF's, that future PRs would be done in English (as the most inclusive way). All current PRs against master are in English already. There are a few German ones left which are against the 18.2 branch which is still maintained by LHM. Over time, these should be merged or closed. Sure, any contributor can port those PRs against master, and then they should be filed in English of course. Thanks for the clarification :) And, just to spell it out, I have nothing against German, it's just that having PRs and issues in English could increase that chance to involve more contributors. But for sure, I don't want to add extra work for the maintainers just for having things translated from German to English ;) But yeah, my preference would be switching also the existing ones to English (Samuel or Björn, what's your take here?). Yes, these should be converted to master (after checking they are still valid). yes, some help in closing invalid issues will be extremely valuable. I think it does make sense to either use the Cloud version of SonarQube (as we do with Coverity), or host it ourselves (up to Infra team to decide). Might add value to other TDF java projects as well (Java parts of LibreOffice, LOEclipse, etc). yep, from my experience, sonarcloud seems to be good too. P.S: @Thorsten, I saw that some of the feedback we shared in this discussion are now listed as new GitHub issues. Thanks for that. :) Happy hacking and have a lot of fun, Marina -- Marina Latini IRC: deneb_alpha on LiberaChat -- To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.documentfoundation.org/www/board-discuss/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [board-discuss] Re: Off-topic character assassinations - do we really need moderation again?
Hi all, I await answers to the questions below. And it looks like if I was not the only one. The action about the moderation of this list was in July this year extra risky because it happened during the elections of the Membership Committee and this list was the main communication medium for the candidates. Thus the action to moderate this list could also be seen as an intrusion into the election process. Because the election of the TDF bodies is an important and sensitive an intrusion into it by the election board is a substantial mistake. Regards, Andreas Am 01.12.22 um 06:50 schrieb Andreas Mantke: Hi Thorsten, Daniel, hi all, Thorsten could you please explain in detail the invitation to the meeting on July, 8th? Who has been in the meeting, and by which medium and during which time frame? Did you document the meeting? Who signed that document? Was the document sent to All members of the board and to the MC? Was the document published? Has the document been archived at TDF archive? The above is the minimum according to par. 9 of the statutes. If this rules were not followed there is definitively no decision taken before the moderation took place. Regards, Andreas Am 1. Dezember 2022 00:52:34 MEZ schrieb Thorsten Behrens : Hi Daniel, Daniel A. Rodriguez wrote: And that does not look like a board decision to me. The vote was to document an earlier decision on Friday, July 8th, that happened via phone, messenger and chat. Mind that it was vacation time, and several directors had no immediate access to their email. Cheers, Thorsten -- Thorsten Behrens, Director, Member of the Board The Document Foundation, Kurfürstendamm 188, 10707 Berlin, Germany Rechtsfähige Stiftung des bürgerlichen Rechts Legal details: http://www.documentfoundation.org/imprint -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet. -- ## Free Software Advocate ## Plone add-on developer ## My blog:http://www.amantke.de/blog
Re: [board-discuss] [DECISION] [VOTE] New proposal for hiring in-house developers.
Hi all, because there are three directors with a CoI (as explained already) the three votes of this directors a null. Thus there are only two valid approvals and two abstain. Because at least four members (those without a CoI) participated the majority of votes is 3. Because only two valid approvals were given, the proposal was disapproved. Regards, Andreas Am 05.12.22 um 12:12 schrieb Cor Nouws: The Board of Directors at the time of voting consists of 7 seat holders (not including deputies). In order to be quorate, the vote needs to have 1/2 or more of the Board of Directors members, which gives 4. A total of 7 Board of Directors members have participated in the vote. The vote is quorate. A quorum could be reached with a simple majority of 4 votes. Result of vote: 5 approvals, 2 abstains, 0 disapprovals. Decision: The proposal has been accepted. One deputy supports the motion. [NB: Rest assured, I would say, that we took notice of the discussion.] Cor Nouws wrote on 02/12/2022 09:24: Dear people, Thanks for the constructive feedback on the proposal. Various changes applied, I now call a vote for the resolution below. Your response within 72 hours from now is much appreciated. Cheers, Cor -%<-- ## TDF Developer Hiring Resolution 2022 "Whereas, - with TDF stewarding, among other things, a well-working symbiosis of various companies and volunteer developers inside of the LibreOffice community; - given that in the current situation, there are certain areas where extra developers can add value with additional activities, that complement the existing contributions; - with this being an ongoing need; Therefore the board resolves that: - TDF will seek to hire a developer(s); - who will report to the ED as a regular team member, and consult weekly with the ESC, which will oversee the technical direction of the work; - who will work in such a way, that both volunteer and ecosystem peers regard them as helpful, supportive and complementing their own work; - for whom as the initial areas of work, the board identifies improving RTL/CTL writing support and accessibility for LibreOffice; as well as mentoring new volunteers in these specific areas. After that, depending on skills available, Writer tables, Base, general regression fixing, Draw, and Math are the next focus areas; - thus, there will be two job postings, with requirements matching the initial focus areas listed above, and one or two developers will be hired initially; - after 6, and after 9 months following the developers starting their work, the board will do an assessment of the situation and results. Requirements for the candidates: * Very good C++ development skills; * Proven experience with Accessibility and/or RTL/CTL, additional CJK experience is a strong plus; * Love for open source; * Team players; * Experience with LibreOffice development is a plus. Footnote: for a requirements analysis on the need for hiring developers, please refer to information on the pages 3-8 of the abandoned dev proposal: https://nextcloud.documentfoundation.org/s/qofn646Jg6bmPYB " -%<-- Cor Nouws wrote on 28/11/2022 10:58: Hi all, As promised. After the previous draft text ended up in a dead-end, with apparently no compromise possible, it is time for a fresh start to get developers hired. The initial discussion was valuable and also informing this proposal. With the following, we suggest a new proposal, brief and positive, that makes clear where we stand, building on trust in the community, and leaves it to the board to pragmatically act, based on their task and responsibility to try to do the best thing for the foundation. Your feedback is much appreciated. Thanks, Cor -%<-- ## TDF Developer Hiring Resolution 2022 "Whereas, - with TDF stewarding, among other things, a well-working symbiosis of various companies and volunteer developers inside of the LibreOffice community; - given that in the current situation, there are certain areas where extra developers can add value with additional activities, that complement the existing contributions; - with this being an ongoing need; Therefore the board resolves that: - TDF will seek to hire a developer(s) reporting to the ESC; - who will work in such a way, that both volunteer and ecosystem peers regard them as helpful, supportive and complementing their own work; - for whom as the initial areas of work, the board identifies improving RTL/CTL writing support and accessibility for LibreOffice core; as well as mentoring new volunteers in these specific areas. After that, depending on skills available, Writer tables, Base, general regression fixing, Draw, and Math are the next focus areas; - thus, there will be
[board-discuss] [DECISION] [VOTE] New proposal for hiring in-house developers.
The Board of Directors at the time of voting consists of 7 seat holders (not including deputies). In order to be quorate, the vote needs to have 1/2 or more of the Board of Directors members, which gives 4. A total of 7 Board of Directors members have participated in the vote. The vote is quorate. A quorum could be reached with a simple majority of 4 votes. Result of vote: 5 approvals, 2 abstains, 0 disapprovals. Decision: The proposal has been accepted. One deputy supports the motion. [NB: Rest assured, I would say, that we took notice of the discussion.] Cor Nouws wrote on 02/12/2022 09:24: Dear people, Thanks for the constructive feedback on the proposal. Various changes applied, I now call a vote for the resolution below. Your response within 72 hours from now is much appreciated. Cheers, Cor -%<-- ## TDF Developer Hiring Resolution 2022 "Whereas, - with TDF stewarding, among other things, a well-working symbiosis of various companies and volunteer developers inside of the LibreOffice community; - given that in the current situation, there are certain areas where extra developers can add value with additional activities, that complement the existing contributions; - with this being an ongoing need; Therefore the board resolves that: - TDF will seek to hire a developer(s); - who will report to the ED as a regular team member, and consult weekly with the ESC, which will oversee the technical direction of the work; - who will work in such a way, that both volunteer and ecosystem peers regard them as helpful, supportive and complementing their own work; - for whom as the initial areas of work, the board identifies improving RTL/CTL writing support and accessibility for LibreOffice; as well as mentoring new volunteers in these specific areas. After that, depending on skills available, Writer tables, Base, general regression fixing, Draw, and Math are the next focus areas; - thus, there will be two job postings, with requirements matching the initial focus areas listed above, and one or two developers will be hired initially; - after 6, and after 9 months following the developers starting their work, the board will do an assessment of the situation and results. Requirements for the candidates: * Very good C++ development skills; * Proven experience with Accessibility and/or RTL/CTL, additional CJK experience is a strong plus; * Love for open source; * Team players; * Experience with LibreOffice development is a plus. Footnote: for a requirements analysis on the need for hiring developers, please refer to information on the pages 3-8 of the abandoned dev proposal: https://nextcloud.documentfoundation.org/s/qofn646Jg6bmPYB " -%<-- Cor Nouws wrote on 28/11/2022 10:58: Hi all, As promised. After the previous draft text ended up in a dead-end, with apparently no compromise possible, it is time for a fresh start to get developers hired. The initial discussion was valuable and also informing this proposal. With the following, we suggest a new proposal, brief and positive, that makes clear where we stand, building on trust in the community, and leaves it to the board to pragmatically act, based on their task and responsibility to try to do the best thing for the foundation. Your feedback is much appreciated. Thanks, Cor -%<-- ## TDF Developer Hiring Resolution 2022 "Whereas, - with TDF stewarding, among other things, a well-working symbiosis of various companies and volunteer developers inside of the LibreOffice community; - given that in the current situation, there are certain areas where extra developers can add value with additional activities, that complement the existing contributions; - with this being an ongoing need; Therefore the board resolves that: - TDF will seek to hire a developer(s) reporting to the ESC; - who will work in such a way, that both volunteer and ecosystem peers regard them as helpful, supportive and complementing their own work; - for whom as the initial areas of work, the board identifies improving RTL/CTL writing support and accessibility for LibreOffice core; as well as mentoring new volunteers in these specific areas. After that, depending on skills available, Writer tables, Base, general regression fixing, Draw, and Math are the next focus areas; - thus, there will be two job postings, with requirements matching the initial focus areas listed above, and one or two developers will be hired initially; - after 6, and after 9 months following the developers starting their work, the board will do an assessment of the situation and results. Requirements for the candidates: * Very good C++ development skills; * Proven experience with Accessibility and/or
[board-discuss] Fwd: [VOTE] New proposal for hiring in-house developers.
[ forwarding Gábors mail to this list as well, for clarity ] Forwarded Message Subject: Re: [VOTE] New proposal for hiring in-house developers. Date: Sun, 4 Dec 2022 23:59:36 +0100 From: Gábor Kelemen To: tdf-direct...@lists.documentfoundation.org Hi all +1 ATB Gabor 2022. 12. 02. 9:24 keltezéssel, Cor Nouws írta: Dear people, Thanks for the constructive feedback on the proposal. Various changes applied, I now call a vote for the resolution below. Your response within 72 hours from now is much appreciated. Cheers, Cor -%<-- ## TDF Developer Hiring Resolution 2022 "Whereas, - with TDF stewarding, among other things, a well-working symbiosis of various companies and volunteer developers inside of the LibreOffice community; - given that in the current situation, there are certain areas where extra developers can add value with additional activities, that complement the existing contributions; - with this being an ongoing need; Therefore the board resolves that: - TDF will seek to hire a developer(s); - who will report to the ED as a regular team member, and consult weekly with the ESC, which will oversee the technical direction of the work; - who will work in such a way, that both volunteer and ecosystem peers regard them as helpful, supportive and complementing their own work; - for whom as the initial areas of work, the board identifies improving RTL/CTL writing support and accessibility for LibreOffice; as well as mentoring new volunteers in these specific areas. After that, depending on skills available, Writer tables, Base, general regression fixing, Draw, and Math are the next focus areas; - thus, there will be two job postings, with requirements matching the initial focus areas listed above, and one or two developers willbe hired initially; - after 6, and after 9 months following the developers starting their work, the board will do an assessment of the situation and results. Requirements for the candidates: * Very good C++ development skills; * Proven experience with Accessibility and/or RTL/CTL, additional CJK experience is a strong plus; * Love for open source; * Team players; * Experience with LibreOffice development is a plus. Footnote: for a requirements analysis on the need for hiring developers, please refer to information on the pages 3-8 of the abandoned dev proposal: https://nextcloud.documentfoundation.org/s/qofn646Jg6bmPYB " -%<-- Cor Nouws wrote on 28/11/2022 10:58: Hi all, As promised. After the previous draft text ended up in a dead-end, with apparently no compromise possible, it is time for a fresh start to get developers hired. The initial discussion was valuable and also informing this proposal. With the following, we suggest a new proposal, brief and positive, that makes clear where we stand, building on trust in the community, and leaves it to the board to pragmatically act, based on their task and responsibility to try to do the best thing for the foundation. Your feedback is much appreciated. Thanks, Cor -%<-- ## TDF Developer Hiring Resolution 2022 "Whereas, - with TDF stewarding, among other things, a well-working symbiosis of various companies and volunteer developers inside of the LibreOffice community; - given that in the current situation, there are certain areas where extra developers can add value with additional activities, that complement the existing contributions; - with this being an ongoing need; Therefore the board resolves that: - TDF will seek to hire a developer(s) reporting to the ESC; - who will work in such a way, that both volunteer and ecosystem peers regard them as helpful, supportive and complementing their own work; - for whom as the initial areas of work, the board identifies improving RTL/CTL writing support and accessibility for LibreOffice core; as well as mentoring new volunteers in these specific areas. After that, depending on skills available, Writer tables, Base, general regression fixing, Draw, and Math are the next focus areas; - thus, there will be two job postings, with requirements matching the initial focus areas listed above, and one or two developers will be hired initially; - after 6, and after 9 months following the developers starting their work, the board will do an assessment of the situation and results. Requirements for the candidates: * Very good C++ development skills; * Proven experience with Accessibility and/or RTL/CTL, additional CJK experience is a strong plus; * Love for open source; * Team players; * Experience with LibreOffice development is a plus. Footnote: for a requirements analysis on the need for hiring developers, please refer to information on the pages 3-8 of the abandoned
