AW: [board-discuss] WollMux adoption proposal for The Document Foundation

2023-01-11 Thread Björn Ranft
Hi Samuel, Hi All,



sry for my late reply, I was on the rest on my vacation.


wollmux-conf-service ist currently not used @LHM but has been prepared to 
reduce dependencies, the process is:


1) Linux/Windows - Script which reads the logged in user name

2) query username to GOsa (https://de.wikipedia.org/wiki/GOsa), read 
WollMux-Parameters from GOsa depending on the group assignment of the user. For 
a group, below wollmux parameters can be set.

3) response parameters are like:


DEFAULT_CONTEXT "http://department.wollmux.de/;
%include "http://department.wollmux.de/conf/main.conf;
%include "http://department.wollmux.de/conf/wollmuxbar_standard.conf;

4) Script (1) writes parameters in "wollmux.conf" in the user dir or further 
locations (hard coded in wollmux)
5) When WollMux starts, it reads wollmux.conf and receives the whole 
configuration for the user (group) as described by Samuel.


wollmux-conf-service would get rid of the script (read logged in username by 
Java in WollMux itself, create request to conf-service). conf-service can 
(should?) be expanded to use the assignments  in i.e. ActiveDirectory.



Regards,

Björn
--


[it@M Logo]


Landeshauptstadt München
IT-Referat
it@M

Geschäftsfeld Infrastruktur, Basisservices und Support
Servicebereich Stadtweite Basisanwendungen
Serviceteam Office, Templates, Makros
Wollmux Entwicklung/Last-Level Support

E-Mail: bjoern.ra...@muenchen.de



[Link zur Webseite]<https://muenchen.digital/it-at-m/> [Link zu YouTube] 
<https://www.youtube.com/playlist?list=PL5674kRR4tH2qht-twLsBNb9YeR5wGGM9>  
[Link zu Twitter] <https://twitter.com/MuenchenDigital>  [Link zu Instagram] 
<https://www.instagram.com/muenchen.digital/>

Elektronische Kommunikation mit der Landeshauptstadt München siehe:
https://www.muenchen.de/ekomm

Bitte denken Sie an die Umwelt, bevor Sie diese E-Mail ausdrucken. Pro Blatt 
sparen Sie durchschnittlich 15g Holz, 260ml Wasser, 0,05kWh Strom und 5g CO2.


Von: Samuel Mehrbrodt 
Gesendet: Montag, 9. Januar 2023 09:23:32
An: Thorsten Behrens; TDF Board Discussion; Björn Ranft
Cc: Marina Latini
Betreff: Re: [board-discuss] WollMux adoption proposal for The Document 
Foundation


Hi,

Am 02.01.23 um 10:37 schrieb Thorsten Behrens:


- wollmux-config-service (not used in WollMux yet, might be
  effectively abandoned - Björn, what do you think?)

wollmux-conf-service is a server side helper to deliver user specific conf 
files (to avoid deploying different wollmux.conf manually).

The local wollmux config must have a URL pointing to the config server and then 
WollMux will query the given 
URL<https://github.com/LibreOffice/WollMux/blob/5092aa8726da50759fe433ed53964c8f915556e8/core/src/main/java/de/muenchen/allg/itd51/wollmux/WollMuxFiles.java#L185-L198>
 to retrieve the config for the current user.

So the wollmux-conf-service<https://github.com/WollMux/wollmux-conf-service> 
repo is still relevant and should also be migrated over to the LibreOffice 
GitHub organization.

Regards
Samuel


--

Samuel Mehrbrodt

Software-Entwickler LibreOffice
–––

[allotropia logo]

allotropia software GmbH
Versmannstr. 4
20457 Hamburg
–––
T +49 040 2093 4085-2

samuel.mehrbr...@allotropia.de<mailto:samuel.mehrbr...@allotropia.de>
–––
Sitz: Hamburg
Registergericht Hamburg, HRB 165405
Geschäftsführer: Dipl.-Inf. Thorsten Behrens
USt.-Ident.-Nr. DE 335606919
–––


Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2023-01-09 Thread Samuel Mehrbrodt

Hi,

Am 02.01.23 um 10:37 schrieb Thorsten Behrens:

- wollmux-config-service (not used in WollMux yet, might be
   effectively abandoned - Björn, what do you think?)
wollmux-conf-service is a server side helper to deliver user specific 
conf files (to avoid deploying different wollmux.conf manually).


The local wollmux config must have a URL pointing to the config server 
and then WollMux will query the given URL 
 
to retrieve the config for the current user.


So the wollmux-conf-service 
 repo is still relevant 
and should also be migrated over to the LibreOffice GitHub organization.


Regards
Samuel


--

*Samuel Mehrbrodt*

Software-Entwickler LibreOffice
–––

allotropia logo

*allotropia software GmbH*
Versmannstr. 4
20457 Hamburg
–––
T +49 040 2093 4085-2

samuel.mehrbr...@allotropia.de 
–––
Sitz: Hamburg
Registergericht Hamburg, HRB 165405
Geschäftsführer: Dipl.-Inf. Thorsten Behrens
USt.-Ident.-Nr. DE 335606919
–––


Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2023-01-02 Thread Uwe Altmann

Hi

Am 02.01.23 um 13:25 schrieb Thorsten Behrens:

Doesn't feel terribly off-topic here (dev list would also not be a
100% on-topic match, neither website or marketing? - but for very
generic discussions, there's always the global discuss list of
course).


You could open a topic at https://community.documentfoundation.org :-)
--
Have a nice 2023
Uwe Altmann


--
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

2023-01-02 Thread sophi

Hi Thorsten, Marina, all,
Le 02/01/2023 à 13:25, Thorsten Behrens a écrit :

Hi Marina, all,


[...]


Doesn't feel terribly off-topic here (dev list would also not be a
100% on-topic match, neither website or marketing? - but for very
generic discussions, there's always the global discuss list of
course).


The global discuss list has many more subscribers (more than the double) 
than this list, so I think you are right that it would be more suitable 
for this discussion.


Something else - does anybody see the need for a dedicated wollmux
mailing list? I didn't ask for one (and actually try to avoid silo-ed
low-traffic email lists, and nudge people onto the main dev list), but
not strictly against one either. The old wollmux project had one at
joinup IIRC, but it's dormant since a long time.


As we are pushing for Community forum, maybe this is a good candidate 
for a category here (if it is seen as needed of course)?

Cheers
Sophie

--
Sophie Gautier so...@libreoffice.org
GSM: +33683901545
IRC: soph
Foundation coordinator
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

2023-01-02 Thread susanne.mohn-lo
Hi all, 
Hi Marina, 

I have wollmux installed
With the latest released version from last year from December 30 2022, you
need JRE 11. 

I'm using Windows 11, the wollmux.conf must look like this
DEFAULT_CONTEXT "./config/"
%include "./config/conf/main.conf"
%include "./config/conf/wollmuxbar_standard.conf"

Unfortunately, not all templates are found yet, even though they are in the
correct folder. 

I don't think an extra WollMux mailing list makes not sense. This does not
promote the awareness of wollmux.
Possibly.  Perhaps mark the subject with [WollMux]?

Greetings
Susanne

-Ursprüngliche Nachricht-
Von: Thorsten Behrens  
Gesendet: Montag, 2. Januar 2023 13:26
An: Marina Latini 
Cc: TDF Board Discussion 
Betreff: Re: [board-discuss] WollMux adoption proposal for The Document
Foundation

Hi Marina, all,

Marina Latini wrote:
> No no, it makes sense to keep WollMux under the LibreOffice org, I 
> agree. If you are fine with the current status, can we start to work on
WollMux?
> 
I'd love to! :)

(Gabor is getting the last few handbook pages' existing German  translation
put up on the wiki; and I'll see to get at least a basic  CI job setup going
by early next week - but none of that should block  others from starting the
work)

> But, apart from WollMux... I think we could take this opportunity also 
> for a clean-up of repos in https://github.com/tdf. ;) You mentioned 
> the DLP libraries, but libcmis is hosted under the TDF organisation, 
> and, if I'm not mistaken, the libraries from the DLP aren't 
> LibreOffice only but can be reused also elsewhere.
>
Yep, that's true - Calligra, Inkscape and Scribus use at least some of them.

> Under the TDF organisation there are also other repos that should 
> probably be archived (but we are going semi off-topic now). ;)
>
Also true, e.g. when looking at website stuff. BTW, 'archiving' on github is
something conceptually very close to our atticization - we should evaluate
setting the archive flag within that framework IMO.

> We could also mention that we have the other LibreOffice organisation 
> and cross link from tdf to LibreOffice too.
>
Given that the main readme was misleading you, that's certainly useful.

> But...for this clean-up, where we can continue this discussion? this 
> list doesn't look like the right place to me. :)
> 
Doesn't feel terribly off-topic here (dev list would also not be a 100%
on-topic match, neither website or marketing? - but for very generic
discussions, there's always the global discuss list of course).

Something else - does anybody see the need for a dedicated wollmux mailing
list? I didn't ask for one (and actually try to avoid silo-ed low-traffic
email lists, and nudge people onto the main dev list), but not strictly
against one either. The old wollmux project had one at joinup IIRC, but it's
dormant since a long time.

Cheers,

-- Thorsten


--
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

2023-01-02 Thread Thorsten Behrens
Hi Marina, all,

Marina Latini wrote:
> No no, it makes sense to keep WollMux under the LibreOffice org, I agree. If
> you are fine with the current status, can we start to work on WollMux?
> 
I'd love to! :)

(Gabor is getting the last few handbook pages' existing German
 translation put up on the wiki; and I'll see to get at least a basic
 CI job setup going by early next week - but none of that should block
 others from starting the work)

> But, apart from WollMux... I think we could take this opportunity also for a
> clean-up of repos in https://github.com/tdf. ;)
> You mentioned the DLP libraries, but libcmis is hosted under the TDF
> organisation, and, if I'm not mistaken, the libraries from the DLP aren't
> LibreOffice only but can be reused also elsewhere.
>
Yep, that's true - Calligra, Inkscape and Scribus use at least some of
them.

> Under the TDF organisation there are also other repos that should probably
> be archived (but we are going semi off-topic now). ;)
>
Also true, e.g. when looking at website stuff. BTW, 'archiving' on
github is something conceptually very close to our atticization - we
should evaluate setting the archive flag within that framework IMO.

> We could also mention that we have the other LibreOffice organisation and
> cross link from tdf to LibreOffice too.
>
Given that the main readme was misleading you, that's certainly useful.

> But...for this clean-up, where we can continue this discussion? this list
> doesn't look like the right place to me. :)
> 
Doesn't feel terribly off-topic here (dev list would also not be a
100% on-topic match, neither website or marketing? - but for very
generic discussions, there's always the global discuss list of
course).

Something else - does anybody see the need for a dedicated wollmux
mailing list? I didn't ask for one (and actually try to avoid silo-ed
low-traffic email lists, and nudge people onto the main dev list), but
not strictly against one either. The old wollmux project had one at
joinup IIRC, but it's dormant since a long time.

Cheers,

-- Thorsten

signature.asc
Description: PGP signature


Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2023-01-02 Thread Marina Latini

On 02.01.2023 12:08, Thorsten Behrens wrote:

Hi Marina, all,

marina latini wrote:

The WollMux repos are now under the LibreOffice GitHub organisation
that, to my understanding, should be just a read only mirror from
our git instance hosting the LibreOffice source code.


That place was picked on purpose, since (in contrast to e.g. the ODF
toolkit), WollMux is exclusively meant for LibreOffice. You'll also
find other repos there, with equally strong ties to the main code base
(impress_remote, loeclipse, noa-libre, the barcode extension, and the
DLP libraries).


...indeed, the LibreOffice organisation is a mix of read-only and push 
allowed repos.


I got fooled by the main description:
"Read Only Mirror fo Libreoffice-related git repos (see url for code 
submission)"

and I didn't noticed that only some repos are read-only.




I'm wondering if the TDF organisation could be a better place for
WollMux instead of the LibreOffice one.


It's of course not a problem to move the repos further, but - at least
to me it appears currently more consistent with the existing layout.


No no, it makes sense to keep WollMux under the LibreOffice org, I 
agree. If you are fine with the current status, can we start to work on 
WollMux?


But, apart from WollMux... I think we could take this opportunity also 
for a clean-up of repos in https://github.com/tdf. ;)
You mentioned the DLP libraries, but libcmis is hosted under the TDF 
organisation, and, if I'm not mistaken, the libraries from the DLP 
aren't LibreOffice only but can be reused also elsewhere.
Under the TDF organisation there are also other repos that should 
probably be archived (but we are going semi off-topic now). ;)
We could also mention that we have the other LibreOffice organisation 
and cross link from tdf to LibreOffice too.
But...for this clean-up, where we can continue this discussion? this 
list doesn't look like the right place to me. :)


Cheers,
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] WollMux adoption proposal for The Document Foundation

2023-01-02 Thread Thorsten Behrens
Hi Marina, all,

marina latini wrote:
> The WollMux repos are now under the LibreOffice GitHub organisation
> that, to my understanding, should be just a read only mirror from
> our git instance hosting the LibreOffice source code.
>
That place was picked on purpose, since (in contrast to e.g. the ODF
toolkit), WollMux is exclusively meant for LibreOffice. You'll also
find other repos there, with equally strong ties to the main code base
(impress_remote, loeclipse, noa-libre, the barcode extension, and the
DLP libraries).

> I'm wondering if the TDF organisation could be a better place for
> WollMux instead of the LibreOffice one.
>
It's of course not a problem to move the repos further, but - at least
to me it appears currently more consistent with the existing layout.

Cheers,

-- Thorsten

signature.asc
Description: PGP signature


Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2023-01-02 Thread marina latini
Hello Thorsten, hi all,

Thanks for taking care of those changes. I have a doubt that I would like to 
clarify before starting to have contributors pushing changes to this new place.

The WollMux repos are now under the LibreOffice GitHub organisation that, to my 
understanding, should be just a read only mirror from our git instance hosting 
the LibreOffice source code. 

We also have a different organisation (https://github.com/tdf) where we moved 
in the past the ODFtoolkit. The same place is also hosting other tools and 
collateral repos like the LibreOffice metadata.
I'm wondering if the TDF organisation could be a better place for WollMux 
instead of the LibreOffice one. 

Looking forward to hearing from you,
Marina

Sent from Nine

Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2023-01-02 Thread Thorsten Behrens
Dear all,

I wrote:
> Since there seems to be no general concerns, I'd then use the quiet
> period next week, to switch the github repos over to the libreoffice
> org. After that, we can look into the Jenkins setup.
> 
This has happened meanwhile:

- WollMux - https://github.com/LibreOffice/WollMux
- UnoHelper - https://github.com/LibreOffice/UNOHelper
- wollmux-config - https://github.com/LibreOffice/wollmux-config

I've renamed 'master' branch to 'main' for all three repos. FWICT
github will issue a useful warning if you accidentally try to push
into master. All pending pull requests got auto-transmogrified, with
the new branch name as destination.

Leaving behind all archived repos under https://github.com/WollMux,
plus the following, defacto dormant ones:

- WollMuxHandbuch (now moved into the wiki - we should probably set
  the 'archived' flag on the repo, to avoid content diverging?)

- wollmux-core (not needed for main anymore, nor in 18.2 - I'd also
  prefer this to somehow stated that more clearly, or perhaps also
  archive it?)

- wollmux-config-service (not used in WollMux yet, might be
  effectively abandoned - Björn, what do you think?)

Cheers,

-- Thorsten

signature.asc
Description: PGP signature


Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2022-12-23 Thread Thorsten Behrens
Dear all,

Marina Latini wrote:
> On 05.12.2022 08:10, Samuel Mehrbrodt wrote:
> > Yes, these should be converted to master (after checking they are still
> > valid).
> 
> yes, some help in closing invalid issues will be extremely valuable.
> 
We can certainly look into that next year (CI needs going first, so
we've got something to distribute & test).

> > 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.
> 
Ok, I'll try to get this setup then (alongside the Jenkins job).

> 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. :)
> 
..and we made some progress on the translation front already - after
talking to Sophie and Ilmari, the originally-German WollMux handbook
is now (almost) converted to translatable mediawiki content, with the
source language being English.

See the work-in-progress from Gabor linked from here:

 https://wiki.documentfoundation.org/Documentation/WollMux/en

Since there seems to be no general concerns, I'd then use the quiet
period next week, to switch the github repos over to the libreoffice
org. After that, we can look into the Jenkins setup.

Cheers,

-- Thorsten

signature.asc
Description: PGP signature


AW: [board-discuss] WollMux adoption proposal for The Document Foundation

2022-12-06 Thread susanne.mohn-lo
Moin moin Stephan

Wie know this Word in the North of Germany too.
Translate it with deepl.com: 
Translate "Eierlegendewollmilchsau" : Egg Laying Wooly Pig

That is not a good name for a good tool like WollMux.

Susanne


-Ursprüngliche Nachricht-
Von: Stephan Ficht  
Gesendet: Dienstag, 6. Dezember 2022 08:06
An: susanne.mohn...@kiel-pries.de; 'Marina Latini' 
; 'Samuel Mehrbrodt' 

Cc: 'Thorsten Behrens' ; 'Björn Ranft' 
; 'TDF Board Discussion' 

Betreff: 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



--
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

2022-12-05 Thread Stephan Ficht

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

2022-12-05 Thread susanne.mohn-lo
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

2022-12-05 Thread Marina Latini

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] WollMux adoption proposal for The Document Foundation

2022-12-04 Thread Thorsten Behrens
Hi Marina, all,

to keep this conversation going -

I wrote:
> Marina Latini wrote:
> > As per today, there are  8 open pull requests[5] and some of them are in
> > German. Is there any  plan to translate the content or close the PRs in
> > German and reopen new PRs in English?
> >
> I'd leave that to the maintainers. But sure, having PRs in English would
> presumably increase the chances of getting them merged.
> 
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).

> > As per today, there are 14 open issues[6] and some of them are in German.
> > Like for the case of the pull requests, is there any plan to translate the
> > content or close the issues in German and reopen new issues in English?
> > 
> Same answer as for PRs, that should be decided by those doing the work.
> 
But yeah, my preference would be switching also the existing ones to
English (Samuel or Björn, what's your take here?).

> > The jenkinsfile is mentioning the integration with SonarQube[9] for
> > the the security scans, is there any plan to also move the SonarQube
> > setup under the TDF infra?
> >
> I'd also leave that to the maintainers, and our infra team. SonarQube
> needs an extra server (I think), and has an opencore business model -
> so whether that's a good fit for TDF infra needs discussion.
>
Samuel or Björn: is there any value in migrating that Jenkinsfile
wholesale?

Cheers,

-- Thorsten

signature.asc
Description: PGP signature


Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2022-11-28 Thread Thorsten Behrens
Hi Marina,

Marina Latini wrote:
> The license is "EUPL-1.1" but looking at some of the subfolders I found for
> example also mentions to GNU LGPLv2 [1].
>
Yep, that's part of the LibreOffice l10n tools, that Samuel was
cloning recently from there (and as such a build-time, not a runtime
component).

> Did the ESC (or anyone else) make an analysis of the source code
> looking for other licenses mentioned? Could it be possible to make
> use of the REUSE[2] project started by FSFE?
>
REUSE is AFAIK working with already-existing metadata. I did run
scancode a while ago without anything surprising sticking out, but
it's a good point to run it again, before any possible final switch.

> In the potential move under the TDF umbrella, is there any plan to
> also re-license it following the usual licenses of LibreOffice?
>
I can ask LHM if that is an option. But would we really need that?
LibreOffice itself only has the core code (mostly) under MPL. The
binary itself has a massive bouquet of other licenses, and other
libraries TDF is hosting, feature licenses ranging from GPL to ASL or
BSD.

> For example, looking at the GitHub project the main branch is called
> "master".
>
Ah yep, thx for mentioning. That's an easy fix, and I'll also run the
usual greps regarding other anachronisms in the code. Branch rename
might though only happen immediately before or after the move (if/when
approved).

> Some comments are also affected by a similar non inclusive writing like for
> example here [4] where the comment states "the bookmarks aren't deleted and
> the user is request to confirm, that he wants to create a" and there's the
> assumption that the user can be only a male.
> 
If you share your greps with me, I can have a look.

> As per today, there are  8 open pull requests[5] and some of them are in
> German. Is there any  plan to translate the content or close the PRs in
> German and reopen new PRs in English?
>
I'd leave that to the maintainers. But sure, having PRs in English would
presumably increase the chances of getting them merged.

> Some of the existing pull requests use a tag "trac" but I could't find any
> reference to this naming convention? Is this something private that the
> mentioned maintainers from 2 organizations will take care of document? Could
> it be possible to know more about those tags?
> 
trac# is like the internal StarOffice bugtracker references in
OOo/LibreOffice commit messages and code. I'm near certain that data
cannot be published.

> As per today, there are 14 open issues[6] and some of them are in German.
> Like for the case of the pull requests, is there any plan to translate the
> content or close the issues in German and reopen new issues in English?
> 
Same answer as for PRs, that should be decided by those doing the work.

> The security policy[7] seems to be not defined. Which is the
> agreement here?  Are the two mentioned maintainers supposed to take
> over everything or WollMux will also be covered by the LibreOffice
> security[8] policy? With that amount of lines of code I suppose the
> ESC should have a clear view of the status of the project.
>
At least for the foreseeable future, we (allotropia) can look into any
security reports. If/when the move happens, my suggestion would be
reporting to secur...@documentfoundation.org, just like for DLP and
LibreOffice. The only relevant issues over the time I see there is
third party stuff, e.g. WollMux was affected by the log4j fallout.

> The jenkinsfile is mentioning the integration with SonarQube[9] for
> the the security scans, is there any plan to also move the SonarQube
> setup under the TDF infra?
>
I'd also leave that to the maintainers, and our infra team. SonarQube
needs an extra server (I think), and has an opencore business model -
so whether that's a good fit for TDF infra needs discussion.

> Which is the potential timeline for having the localization on
> Weblate? Is there any ongoing discussion with the L10N team at
> LibreOffice?
>
Hard to say, those things can I guess only happen (and then be
discussed with the community), if/when the move has happened.

> Should the L10N community consider also WollMux as a priority
> project to be translated with high priority like LibreOffice (UI,
> Help, Guides)?
>
I would not expect that. Then again, the effort (after initial
translation) is likely very, very small per release.

> The main WollmMux website[11] has  a link to a catalog on JoinUp[12] that
> describes WollMux as an extension for OpenOffice. Is this just an old
> catalog description or WollMux is really intended for working with both
> LibreOffice and Apache OpenOffice (and it will need to support both?)
>
Pretty sure that's stale. Then again, the OXT has this:

 

, so there's even more staleness (given that there was no sidebar
support in that version, which is required now). Ultimately, which
version(s) of LibreOffice and/or OpenOffice the maintainers want to
support, is up to them (I'd certainly not expect 

Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2022-11-24 Thread sophi

Hi Marina,

Thanks a lot for your analysis, I jump on two subjects:

Le 24/11/2022 à 22:35, Marina Latini a écrit :

On 23.11.2022 12:12, Thorsten Behrens wrote:

Dear community,


Hello Thorsten, hello all,


[...]


# Topic: naming and conventions

I'm aware that there's an ongoing translation from German to English.
In this translation and renaming, is there any plan/agreement to also 
look at harmful and exclusionary language[3]?
For example, looking at the GitHub project the main branch is called 
"master".
Some comments are also affected by a similar non inclusive writing like 
for example here [4] where the comment states "the bookmarks aren't 
deleted and the user is request to confirm, that he wants to create a" 
and there's the assumption that the user can be only a male.


This one is something I would like we work on, have inclusive language 
all over our pages, so thanks for mentioning it.

I've added this link to our wiki for reference:
https://www.linuxfoundation.org/research/the-2021-linux-foundation-report-on-diversity-equity-and-inclusion-in-open-source
I think we, as a inclusive community, should show and be exemplary here

[...]



# Topic: localization
The proposal mentions the move of the localization to Weblate. There's 
also an open issue intended for modernizing the localization environment 
from "one config file" to .po files[10].
Which is the potential timeline for having the localization on Weblate? 
Is there any ongoing discussion with the L10N team at LibreOffice? 
Should the L10N community consider also WollMux as a priority project to 
be translated with high priority like LibreOffice (UI, Help, Guides)?


There is no discussion currently on the l10n list. In my view it's not 
needed right now as there is a lot of translation that have to happen in 
the code (and we are not far from a major release too).
Thorsten confirmed yesterday that it's an extension. Our l10n team 
doesn't translate external extensions or it will be a never ending work 
that could hamper translation of UI and help files with any extension 
creator requesting translation.
What is possible and already happened, is to post the request for 
translation to the l10n list with a link to the files. That way, it 
doesn't make the translation mandatory for the teams like UI and help are.


Cheers
Sophie

--
Sophie Gautier so...@libreoffice.org
GSM: +33683901545
IRC: soph
Foundation coordinator
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



Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2022-11-24 Thread Marina Latini

On 23.11.2022 12:12, Thorsten Behrens wrote:

Dear community,


Hello Thorsten, hello all,


as announced during LibOCon, and subsequently discussed in the ESC,
here's the formal adoption proposal for the "WollMux" template / form
letter / mail merge engine / Java extension, from the City of Munich.

Reply-To: board-discuss please, unless there's technical questions to
discuss (for those, I copy the developer list).



I would like to ask some questions but I'm keeping the dev-list out for 
not disturbing them.
@Thorsten, please, feel free to pull the dev list again in if you think 
that their feedback is needed too.


My memory of WollMux is a bit rusty and I had a look at the source code 
on GitHub[0].


# Topic: license
The license is "EUPL-1.1" but looking at some of the subfolders I found 
for example also mentions to GNU LGPLv2 [1].
Did the ESC (or anyone else) make an analysis of the source code looking 
for other licenses mentioned? Could it be possible to make use of the 
REUSE[2] project started by FSFE?
In the potential move under the TDF umbrella, is there any plan to also 
re-license it following the usual licenses of LibreOffice?


# Topic: naming and conventions

I'm aware that there's an ongoing translation from German to English.
In this translation and renaming, is there any plan/agreement to also 
look at harmful and exclusionary language[3]?
For example, looking at the GitHub project the main branch is called 
"master".
Some comments are also affected by a similar non inclusive writing like 
for example here [4] where the comment states "the bookmarks aren't 
deleted and the user is request to confirm, that he wants to create a" 
and there's the assumption that the user can be only a male.


# Topic: pull requests and issues

## pull requests
As per today, there are  8 open pull requests[5] and some of them are in 
German. Is there any  plan to translate the content or close the PRs in 
German and reopen new PRs in English?
Some of the existing pull requests use a tag "trac" but I could't find 
any reference to this naming convention? Is this something private that 
the mentioned maintainers from 2 organizations will take care of 
document? Could it be possible to know more about those tags?


## issues
As per today, there are 14 open issues[6] and some of them are in 
German. Like for the case of the pull requests, is there any plan to 
translate the content or close the issues in German and reopen new 
issues in English?


# Topic: security
The security policy[7] seems to be not defined. Which is the agreement 
here? Are the two mentioned maintainers supposed to take over everything 
or WollMux will also be covered by the LibreOffice security[8] policy? 
With that amount of lines of code I suppose the ESC should have a clear 
view of the status of the project.
The jenkinsfile is mentioning the integration with SonarQube[9]  for the 
the security scans, is there  any plan to also move the SonarQube setup 
under the TDF infra?


# Topic: localization
The proposal mentions the move of the localization to Weblate. There's 
also an open issue intended for modernizing the localization environment 
from "one config file" to .po files[10].
Which is the potential timeline for having the localization on Weblate? 
Is there any ongoing discussion with the L10N team at LibreOffice? 
Should the L10N community consider also WollMux as a priority project to 
be translated with high priority like LibreOffice (UI, Help, Guides)?


# Topic: support
The main WollmMux website[11] has  a link to a catalog on JoinUp[12] 
that describes WollMux as an extension for OpenOffice. Is this just an 
old catalog description or WollMux is really intended for working with 
both LibreOffice and Apache OpenOffice (and it will need to support 
both?)

On which operating systems WollMux is suppose to be supported?

Thanks a lot for your feedback.
Happy hacking,
Marina

[0] https://github.com/WollMux/WollMux
[1] 
https://github.com/WollMux/WollMux/blob/master/bin/text_cat/Copyright

[2] https://reuse.software/
[3] https://inclusivenaming.org/
[4] 
https://github.com/WollMux/WollMux/blob/011270779d9fce4efc195eae66d95c95a64a3cee/core/src/main/java/de/muenchen/allg/itd51/wollmux/slv/events/OnMarkBlock.java#L150

[5] https://github.com/WollMux/WollMux/pulls
[6] https://github.com/WollMux/WollMux/issues
[7] https://github.com/WollMux/WollMux/security
[8] https://www.libreoffice.org/about-us/security/
[9] 
https://github.com/WollMux/WollMux/blob/011270779d9fce4efc195eae66d95c95a64a3cee/Jenkinsfile

[10] https://github.com/WollMux/WollMux/issues/398
[11] https://wollmux.org/
[12] https://joinup.ec.europa.eu/collection/egovernment/solution/wollmux

--
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

Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2022-11-23 Thread Thorsten Behrens
Hi Sophie,

sophi wrote:
> just for clarity for all, what would prevent it to be released as an
> extension on the extension site? is it too complex?
>
No, not at all, just needs someone updating it there (an older release
is available already:
https://extensions.libreoffice.org/en/extensions/show/wollmux).

> > > Is everything (code comments, strings, doc) still in German?
> > > 
> > See proposal, pretty far down the list - start with code & comment
> > translation DE->EN.
> > 
> > So the answer is, the work has started. ;)
> 
> great, is it a lot of work? do you have an idea of when it will be
> available for the whole community?
>
It is not massive (but it's still large enough that we'd like to ask
people to jump in & help). Code has around 80 kLOC, but quite a lot of
the main sources are already in English (comments, variable names, test
assertion outputs etc).

Documentation is in markdown, and currently only in German. Looking at
the most recent version (for 18.2), this is the size:

 $ find WollMuxHandbuch/markdown/18.2 -iname '*.md' | xargs wc
...
 lines: 9870  words: 86501 in total

Best,

-- Thorsten

signature.asc
Description: PGP signature


Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2022-11-23 Thread Thorsten Behrens
Hi Susanne, all,

Susanne LO wrote:
> I will try to install wollmux, it does not work today. 
> If it works, ipost some examples.
> 
WollMux 18.2.10
(https://github.com/WollMux/WollMux/releases/tag/RELEASE_18.2.10), the
latest release, is only tested to work with LibreOffice 6.4.

For 7.3/7.4, please everyone build directly from source, the current
master branch was fixed to work with newest LibreOffice releases.

Best,

-- Thorsten


signature.asc
Description: PGP signature


Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2022-11-23 Thread sophi

Hi Thorsten,

Your answer bring me some more questions :)
Le 23/11/2022 à 17:15, Thorsten Behrens a écrit :

Hi Sophie,

sophi wrote:

Will that stay as an extension or will it be integrated to
LibreOffice core?


There's currently no plans to do so, no. I don't think that is
technically desirable, since the implementation is
Java-only.


ok, thanks, just for clarity for all, what would prevent it to be 
released as an extension on the extension site? is it too complex?



Is everything (code comments, strings, doc) still in German?


See proposal, pretty far down the list - start with code & comment
translation DE->EN.

So the answer is, the work has started. ;)


great, is it a lot of work? do you have an idea of when it will be 
available for the whole community?



Are there some examples of how it works and what it does and for
which users it is expected?


Can I refer you to our LibOCon talk? I can ask Mike if the video is
perhaps ready soonish, so that can then be part of the public
information here.


Thanks a lot, I'll find the video and will have a look
Cheers
Sophie

--
Sophie Gautier so...@libreoffice.org
GSM: +33683901545
IRC: soph
Foundation coordinator
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



Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2022-11-23 Thread Thorsten Behrens
Hi Sophie,

sophi wrote:
> Will that stay as an extension or will it be integrated to
> LibreOffice core?
>
There's currently no plans to do so, no. I don't think that is
technically desirable, since the implementation is
Java-only.

> Is everything (code comments, strings, doc) still in German?
>
See proposal, pretty far down the list - start with code & comment
translation DE->EN.

So the answer is, the work has started. ;)

> Are there some examples of how it works and what it does and for
> which users it is expected?
>
Can I refer you to our LibOCon talk? I can ask Mike if the video is
perhaps ready soonish, so that can then be part of the public
information here.

Best,

-- Thorsten


signature.asc
Description: PGP signature


Re: [board-discuss] WollMux adoption proposal for The Document Foundation

2022-11-23 Thread Susanne LO
Hi all!, hi Sophie,

There will be translation to english- see technical project info.

I will try to install wollmux, it does not work today. 
If it works, ipost some examples.

Susanne 

—
Susanne Mohn

> Am 23.11.2022 um 16:13 schrieb sophi :
> 
> Hi Thorsten,
> 
>> Le 23/11/2022 à 12:12, Thorsten Behrens a écrit :
>> Dear community,
>> as announced during LibOCon, and subsequently discussed in the ESC,
>> here's the formal adoption proposal for the "WollMux" template / form
>> letter / mail merge engine / Java extension, from the City of Munich.
>> For reference, I attach the full proposal (so the initial version gets
>> archived). For interacting with it, please use this direct edit link
>> on Nextcloud though:
>>  https://nextcloud.documentfoundation.org/s/ftrSdx3A5dgmNR8
>> Reply-To: board-discuss please, unless there's technical questions to
>> discuss (for those, I copy the developer list).
>> Plan is to give this 1-2 weeks for discussion. Depending on the
>> feedback, the hope is, the proposal can then be referred to the board
>> for a final decision.
> 
> I have some questions :)
> 
> Will that stay as an extension or will it be integrated to LibreOffice core?
> 
> Is everything (code comments, strings, doc) still in German?
> 
> Are there some examples of how it works and what it does and for which users 
> it is expected?
> 
> Thanks in advance,
> Cheers
> Sophie
> 
> -- 
> Sophie Gautier so...@libreoffice.org
> GSM: +33683901545
> IRC: soph
> Foundation coordinator
> 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
> 


--
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

2022-11-23 Thread sophi

Hi Thorsten,

Le 23/11/2022 à 12:12, Thorsten Behrens a écrit :

Dear community,

as announced during LibOCon, and subsequently discussed in the ESC,
here's the formal adoption proposal for the "WollMux" template / form
letter / mail merge engine / Java extension, from the City of Munich.

For reference, I attach the full proposal (so the initial version gets
archived). For interacting with it, please use this direct edit link
on Nextcloud though:

  https://nextcloud.documentfoundation.org/s/ftrSdx3A5dgmNR8

Reply-To: board-discuss please, unless there's technical questions to
discuss (for those, I copy the developer list).

Plan is to give this 1-2 weeks for discussion. Depending on the
feedback, the hope is, the proposal can then be referred to the board
for a final decision.


I have some questions :)

Will that stay as an extension or will it be integrated to LibreOffice 
core?


Is everything (code comments, strings, doc) still in German?

Are there some examples of how it works and what it does and for which 
users it is expected?


Thanks in advance,
Cheers
Sophie

--
Sophie Gautier so...@libreoffice.org
GSM: +33683901545
IRC: soph
Foundation coordinator
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

2022-11-23 Thread susanne.mohn-lo
Dear all

This is a very good idea!
In order to make the Wollmux Extension available for large organizations, a
central distribution (Windows: via ActiveDirectorie or SCCM) must be
possible. As well as checking whether JAVA Runtime is installed and the
Installation/provision of a customized config. File. 
Another question: Under LO 7.4.2. I get the message when adding the
extension: Error status of the extension is not known.

Regards, 
Susanne

-Ursprüngliche Nachricht-
Von: Thorsten Behrens  
Gesendet: Mittwoch, 23. November 2022 12:13
An: TDF Board Discussion 
Cc: LibreOffice ; Samuel Mehrbrodt
; Björn Ranft 
Betreff: [board-discuss] WollMux adoption proposal for The Document
Foundation

Dear community,

as announced during LibOCon, and subsequently discussed in the ESC, here's
the formal adoption proposal for the "WollMux" template / form letter / mail
merge engine / Java extension, from the City of Munich.

For reference, I attach the full proposal (so the initial version gets
archived). For interacting with it, please use this direct edit link on
Nextcloud though:

 https://nextcloud.documentfoundation.org/s/ftrSdx3A5dgmNR8

Reply-To: board-discuss please, unless there's technical questions to
discuss (for those, I copy the developer list).

Plan is to give this 1-2 weeks for discussion. Depending on the feedback,
the hope is, the proposal can then be referred to the board for a final
decision.

Looking forward to your feedback, all the best,

-- Thorsten


--
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



[board-discuss] WollMux adoption proposal for The Document Foundation

2022-11-23 Thread Thorsten Behrens
Dear community,

as announced during LibOCon, and subsequently discussed in the ESC,
here's the formal adoption proposal for the "WollMux" template / form
letter / mail merge engine / Java extension, from the City of Munich.

For reference, I attach the full proposal (so the initial version gets
archived). For interacting with it, please use this direct edit link
on Nextcloud though:

 https://nextcloud.documentfoundation.org/s/ftrSdx3A5dgmNR8

Reply-To: board-discuss please, unless there's technical questions to
discuss (for those, I copy the developer list).

Plan is to give this 1-2 weeks for discussion. Depending on the
feedback, the hope is, the proposal can then be referred to the board
for a final decision.

Looking forward to your feedback, all the best,

-- Thorsten
# WollMux adoption proposal for The Document Foundation

## Summary

The [city of Munich](https://muenchen.digital/it-at-m/) (with the help
of [allotropia software GmbH](https://allotropia.de/)) offers TDF to
adopt the WollMux template and mail merge system, in production use at
the city and elsewhere since 2007. The project has been migrated from
OpenOffice to LibreOffice alongside the city-wide adoption of
LibreOffice in 2013. It provides professional, battle-tested
functionality for complex template, form letter and mail merge needs,
as one frequently finds in public sector and corporate office
workflows.

## History

- 2004: Munich announces LiMux, based on OpenOffice
- 2005: work on WollMux development starts
- 2012: Major upgrade & rework, migration to LibreOffice (from OOo)
- 2013: Completion of MailMerge work for LibreOffice
  - since Release 13.10 (target was LibreOffice 3.6)
- 2014: work on update to LibreOffice 4.1
  - since release 14.04
- 2016: work on update to LibreOffice 5.2
  - since release 16.10
- 2017: Munich announces plan to return to Microsoft
- 2019: work on update to LibreOffice 6.1
  - supported since release 18.1
  - move from ant to maven in the build system
- 2020/21: Update to LibreOffice 6.4 (since Release 18.2)
  - migration from Java Swing to native LibreOffice GUI
  - support for sidebar added
- 2023: scheduled end of migration to Microsoft

## Architecture

- written in Java, and deployed as a single, full-featured LibreOffice extension
  - using LibreOffice's Java UNO API
  - and much of Writer's advanced features, like RDF annotations,
bookmarks, and text visibility
  - the WollMux gui was reworked, and now resides in dedicated sidebar
decks, using native LibreOffice gui elements
- core code uses UNOHelper classes
  - UNOHelper is a wrapper for frequently used API calls
  - to make Java programmer's life easier & code more readable
  - UNOHelper is available as a separate git project, and likely a
useful productivity boost for all LibreOffice java integrators
  - this could be the next ScriptForge-alike project, but for Java
- configuration
  - contains template fragments, datasources, and more …
  - as well as a plugin system
  - can be maintained locally, or remote (nice for large-scale deployments)

## Key project features

- project mission: have a single, integrated application for letterheads, form
  templates, and mail merge, deeply intergrated with LibreOffice
  - there were only disjoint, proprietary solutions before
  - in 2004 - no software available that met all requirements
  - extends LibreOffice mail merge for business needs - 1000s of
recipients possible, in decent time (1-2 mins for 1000 copies)
- integrates deeply with LibreOffice, and nicely embeds within its GUI
- OpenSource – licensed under European Union Public License (EUPL)

## Key benefits for TDF

- this is a show-case extension project - for putting on display what is
  possible with LibreOffice
- professionally developed since 2008
- a success story & a production-ready, powerful template management & 
programming environment
- commitment to further cleanup, improve & maintain
- existing user base, thus adopting it serves TDF's mission of
  providing FLOSS office productivity for everyone
- and in addition, it's an excellent QA project tool, for integration-testing 
Java and UNO
  API functions - aka "if WollMux works, every Writer java extension
  will work"

## Adoption proposal

- the ESC has looked at the project, discussed the matter, and
  [approves of the 
migration](https://lists.freedesktop.org/archives/libreoffice-qa/2022-October/011302.html)
- after discussion & acceptance, the following steps would be taken:
  - move the existing, public git repositories into the libreoffice
organisation at github:
- 
- don't migrate the 'public archive' ones (or move them straight
  into the TDF attic, if the project sees value in retaining them on
  our infra)
- the code is available under the EUPL-1.1 (weak copyleft),
  documentation is under CC-BY-SA-4.0 - as such, this appears
  compatible with project norms
- two developers from two