Date: prev next · Thread: first prev next last
2022 Archives by date, by thread · List index

Hi Florian,

Florian Effenberger wrote on 03/06/2022 11:23:

the last link doesn't seem to point to a file, so I'm not sure if what

(I already had a bit fishy feeling with the file, hence I pasted all my changes in the mail ;) )

... so I'm not sure if what you write below is already in the document from the first link.

For sure not. ("On May 9 I added some suggestions to the Nextcloud version that apparently have gone lost:")

* Maintain and improve the user-facing (frontend) part of our (custom) web applications and (internal and external focused) websites

That's quite a mouthful. ;-) I'd rephrase it as

* Maintain and improve the user-facing (frontend) part of our web applications. This includes external and internal applications, and some custom projects.


We then need to update also the next line, "...fixes to the applications we use".

* Collaborate with volunteer contributors around the globe.
   => Collaboration is not a task as such, but a way in which the tasks are achieved..

Yes, but I think it's nice to mention that. We can add it to the section title as "As our future Web Technology Export, you work with a great team of currently twelve, and collaborate with volunteers around the globe to:"

Yes, adding it to a different section makes sense indeed.

* Take care of tools we use for localisation and of accessibility requirements

The tools are already covered by the "web applications" term. What is meant here, IMHO, is that for all our tools we should ensure proper accessibility as well as localization options, that having a focus on that is a part of the role.

Ah :) So "Take care of...  our tools"?

* Make our tools usable both with desktop and mobile devices
   => No idea if that is far reaching, in the sense that it can be very complicated? So maybe add 'as far as reasonable achievable'

We had issues in the past e.g. with the LibOCon website that was not usable from a mobile, so I think this is a key competence the person needs.

Yes, I agree.

These days, with devices ranging from desktop to tablet to mobile, at least where sensible we should ask for that. How about "Make as many of our tools usable ... as possible"?

Yes, something like that. Just to recognize maybe something falls off the plate.

* Follow web technologies and trends and bring them to TDF web services with suggesting, discussing and implementation.

In the current document there is "Suggest, discuss and follow..." - I think that is easier to read thatn "with suggesting, discussing and implementation". We could make it even easier and say "Evaluate web technologies and bring them...".

That's indeed clearer.

I propose that Ilmari and me finish the tender based on the latest edits, and aim to publish it early next week.

Looks good - thanks!


Cor Nouws, member Board of Directors
The Document Foundation, Kurfürstendamm 188, 10707 Berlin
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details:

GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28  A038 E49D 7365 B134 80A6
mobile  : +31 (0)6 25 20 7001
skype   : cornouws
blog    :
jabber  :

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.