Ideas around TDF's future

Hi Sweetshark (Bjoern),

I always think of LibreOffice as a product and a community, is this the wrong association to have?

I download the LibreOffice software (product), I can not download the LibreOffice community.

I celebrate the release of version 7.6 product in a few weeks. I can not celebrate version 7.6 of the community.

King regards,

John

Hello John,

First of all welcome to our community and thank you for participating.

Best,
Stephan

Hi Bjoern,

Again, from Wikipedia:

a product is an object, or system, or service made available for consumer use as of the consumer demand

There are lots of other definitions like this. LibreOffice is a project, yes; but the end result (and what we offer) is a binary installer for end-user software that consumers use. It is by Wikipedia’s and many other definitions a project, with a resulting product.

You see it differently, but almost every definition out there would classify the end-user software that consumers download and install a product. Therefore, LibreOffice is both a project, and a product.

On this topic:

TDF does not universally provide binaries, just a selection

TDF provides binaries for Windows, macOS and Linux, which together make up the vast majority of desktop operating system users. Indeed, looking at the stats, the next biggest desktop OS is FreeBSD, which (while awesome) is tiny. So with TDF providing binaries for 95%+ of desktop operating systems (or even more, depending on the stats source), that’s pretty close to universal, and far more than “just a selection”.

I dont think anyone advocates for that here.

Why do you think it’s important to state that “zur freien Nutzung” doesn’t necessarily mean “zero cost”?

Cheers,
Mike

Hi @jmills59 ,

Somewhat. I know the Document Foundation puts out videos highlighting the new features of each major release, but like all good marketing that is a bit of lying by omission, as there is nobody doing product management at the foundation and there is not even someone prioritizing one feature over another at TDF. Features, the focus in those videos and other marketing material, are rarely even coordinated at TDF: In the release train model used by LibreOffice, for the most part, not even the release manager is having a major influence on the features of a release, because the features of a release are whatever has been added by contributors to the master branch on the day of branch off.

So who is managing features at the foundation? The calendar mostly (and the contributors).

As such, the “product” of TDF is the fact that there will be regular major releases and updates, with whatever the contributors provide. The product of the foundation is that there will be releases, but not what is in those releases.

Product management and providing specific features to non-contributing users is not something the foundation is able to provide – nor should it(*).

All the above is not a narrative that would be easy to tell, so we omit most of it for the outside audience – see @italovignoli s recent posts on that. But that does not change the reality of how the sausage is made. :wink:

Best Regards,

Bjoern

(*) There are both companies and individuals in the ecosystem that can do that though, which is great for users who do not want or cannot be contributors.

I’m sorry but I really must take issue with this perspective.
The “product” of TDF is the fact there will be regular major releases and updates? How can the TDF ensure that there will be any new major releases or updates if there’s no product planning whatsoever, no roadmap for desired/planned features nor any coordination of work to implement complex features besides launching a few tenders?

The TDF should do an effort to do product management and providing specific features, because without those there is no major releases. If you even admit that this narrative is not easy to sell and should be omitted (ironic to even mention that in a public forum) it’s because deep down you know that it is a rotten perspective and effectively you are misleading users about the TDF should actually provide. It should be omitted for the simple reason that outside observers would rightly reach the conclusion that the TDF is an ineffectual organization that does little to ensure that “the sausage” is actually good.

Also what do you define as “non-contributing users”? I’ve donated money in the past, and contribute multiple bug reports. If the philosophy you advocate is effectively how the majority thinks that the TDF should be run and LibO developed then I feel cheated and tricked out of my time and money.
I will refrain to ellaborate further on how despicable I think that position is.

Hello,

from what I see in public here, there is clear feedback.

Not sure what you base your numbers on. Looking at the 2022 budget (Preliminary budget for 2022) we have salaries and compensations 694.840,88 €, various tenders 414.053,54 € and new various tenders 400.000 €. Doesn’t match my definition of “minor”.

And even that one was already seen as “competing with the ecosystem” by some.

Ah, I feel quite on top of things and not confused at all, don’t worry. :wink:

There’s an article from 2011 at German reputable publisher Heise (Die Freiheit, die ich meine … | heise online) that literally says “and at the same time further develop both the community and the product” (German original: “und gleichzeitig sowohl die Community als auch das Produkt weiterzuentwickeln”).

This also matches how we presented TDF and LibreOffice e.g. the various events and trade shows in 2012, the year of incorporation.

Also our annual reports mention “product” (German: “Produkt”) repeatedly, and as I always explain to the board, “the activity report needs to outline how the foundation fulfilled its objectives in 2022 and must give a full overview of its activities.”

So, when TDF was setup, the idea was “free of charge”. Some might have changed their opinion today, but that’s why I am glad we setup a foundation, with objectives that can essentially not be modified. That includes the free of charge, because our statutes are also inspired by the manifesto.

1 Like

Hi @mikesaunders,

That is a bit of self selecting though, because productivity is not just “desktop”. Desktop productivity use itself is getting more and more a corner case: In my day jobs, “desktop” productivity software have not been used anymore by my employers for a decade at least already. Now, the future is not evenly distributed, but the desktop itself is becoming irrelevant.
Are there still people using “desktop” software? Sure, but it is hardly universal in the way you are arguing.

A common trap people fall into is that assuming the LibreOffice project is something you can just wish for your feature to be implemented free of charge or without a contribution (or worse: to be bought by donation). That is obviously not how that works or can work, so it is important that “free of charge” is not a goal in itself, but means: it is the easiest way to unlock and generate future contribution.

By extension, the foundation needs to carefully consider other investments (like e.g. hosting productivity solutions beyond desktop binaries) on if they also enable enable or unlock future contribution in the same way.

Best Regards,
Bjoern

I’m not sure what the argument around a project or product means in practical terms. I mean, if LibreOffice is not a product and TDF is not an organization about a product, what that means in practical terms?

IMHO, TDF’s lack of involvement in “product management” is one of the great failures of LibreOffice (which I did raise back in 2019, so it is not a new opinion of mine), since volunteers can’t fill that role and companies only care about their customers, so who looks after the needs of LibreOffice users? I was hoping that TDF hiring developers is a change in this direction.

Though it is common for open source projects to not care about non-contributing users, certainly a non-profit organization shouldn’t be structured that way, or what is the point of being tax-exempted non-profit if it only cares about its contributors. There is certainly some form of industry consortium that could have been formed instead.

4 Likes

Hi Florian,

I don’t see anyone disagreeing, that having something like a tangible “product” out there was (and is) a very useful thing for TDF to do. And of course the messaging (and this article is a PR statement), in particular at the beginning of the fork, when we were up against OpenOffice, which very clearly was marketed and developed as a product - it was quite mandatory to uphold the impression that we were “similar-just-better”.

It’s just not something that is at the very core of an OpenSource Foundation. I agree with @Sweetshark and others, that providing such “products” are a means to an end, to grow and nurture the community of contributors.

Best, Thorsten

1 Like

Hi @khaledhosny2 ,

The societal benefits of OpenSource (that includes everyone: individual citizens, companies, and the public sector) are undisputed and huge: see e.g. this joinup article from 2012, or the more recent (and more modest, in terms of value) one from the EU Connect Directorate.

So I don’t think this product-vs-code distinction is something that in general affects the beneficial nature of an OpenSource foundation towards society. As such, it probably does not help us in this discussion.

Best, Thorsten

HI @khaledhosny2, Hi @floeff,

I think you raise a few good points, but before being able to care for the needs and desires of non-contributing users, one needs to have an agreement on what those are. A product(*) – unlike a service – inherently wants to minimize the interaction between user and provider. A product free of charge uncouples the user from the provider practically entirely. As such, I am very suspicious about anyone arguing to act on behalf of them.

What the LibreOffice project reliably knows is contributors and it can assume they care for the users (otherwise they would not spend their resources here). Their input (by the trustees via the board of directors) is the best guidance on the direction of the project you can get.

I know, but I think most would naively assume a larger share to be spend on development. Also note that while salaries have been reliably spend, TDF doesnt have the best track record in really spending what was budgeted for tenders (and not all tenders are about code). So the real investment by TDF in code is most certainly lower than most users, donors and contributors expect. Im not saying that is good or bad btw – just that common perception likely quite off here.

LibreOffice is a democratic community and an meritocratic project and not a church or a cult. As such, we dont need priests who interpret the words of prophets from decades gone by, but need to hear the active contributors in 2023 how they see the objectives of the project.

Best Regards,

Bjoern
(*) According to the German wikipedia a product is a “result of an organization that can be produced without any transaction between organization and customer” in ISO9000.

I hope I can still be seen as an active contributor :slight_smile:
I believe LibreOffice the product is empowering communities and is able to save lifes. That is where I’m proud to contribute to the product and where I’m happy to be contracted by TDF to further give people a mean to collect, analyze, illustrate and document the information and the data they need on their daily life wherever they are in the world.

We have, almost each month translators in new languages. Translating less spoken or endangered languages is not only for the beauty of the contribution, LibreOffice here has a key importance because it keeps the language active and evolving and it lets people express themselves in their own language.

So speaking about TDF future, I hope it will still reaffirm its mission of:

  • eliminate the digital divide in society by giving everyone access to office productivity tools free of charge to enable them to participate as full citizens in the 21st century
  • support the preservation of mother tongues by encouraging all peoples to translate, document, support, and promote our office productivity tools in their mother tongue
  • allow users of office productivity software to retain the intellectual property in the documents they create by use of open document formats and open standards
  • an open and transparent peer-reviewed software development process where technical excellence is valued

I’m an open source contributor since 23 years now and I’m well aware on how much it has evolved. I’m also well connected with other foundations, like Eclipse or Software Heritage and others. Which is quite amazing how a collective approach to open source has to differ from one foundation to another to cover the world needs, that’s great :slight_smile:

So fortunately, TDF is not dedicated to develop and promote open source products for the business market, but include the 3 bullet points above that makes it relevant for many more communities and niche usage. That’s up to us to attract them as a community through diversity and inclusiveness (not only in the community but also by product offers), but also by listening to and understanding their needs and being creative to include and answer them. We are not there in my opinion at the moment.

3 Likes

Have you considered users reporting issues or asking for enhancements on Bugzilla?

Hi @sophi, Hi @htietze,

I wrote:

causing @htietze to ask:

You mean taking random enhancement requests that ask for a contribution to LibreOffice and tendering them with a random amount of money? No, I have not considered doing that without consulting with experts who can judge those requests.

Who might be an expert on possible contributions to the LibreOffice project? I think it might be … contributors. Just a guess though.

I think most of that is great, some things need to be updated. I think I drafted something for that a few years ago, I will see if I can still find it.

Best Regards,

Bjoern

Hi Florian,

Hmm, so the actual amount planned for 2023, to spend on staff (including contractors) is about 910k €. Adding to that recurring costs like infra, accounting, conferences, community events & other incidentals, the overall annual recurring expenses is about 1.2M € - with a donation income of around 1.3M € (for 2022), that does not leave that much for anything else, including tenders (in a steady-state situation - that there is a certain backlog of tender projects was already mentioned).

Edit: given the fact that we additionally & usually save around 10% of the overall donation income of each year into a rainy day fund, what’s left for any projects (code-related tenders are the majority, but not 100% of project work) on a steady-state basis, is I would say minor in comparison.

Best, Thorsten

To add on that: The sum planned for projects including tenders for 2023 is 770.008,91 €.

Hi @thb,

lemme rephrase that to see if I understood that correctly.

TDF has currently an donation income of ~1.3 mio. EUR p.a.

TDF currently aims to:

  • put ~130,000 EUR p.a. (10%) in the rainy day reserve
  • spend ~290,000 EUR p.a. in recurring costs for infra, accounting, conferences, community events & other incidentals
  • spend ~910,000 EUR p.a. on staff (including contractors)

for a total planned annual spending of 1.33 mio EUR p.a…

If that is correct:

  • it is already a rainy day: we are cash flow negative by some 30,000 EUR p.a.
  • there is no running budget left for tenders at all.

Therefore any and all direct “product development” from TDF that has been argued about in this discussion would need to come from staff and contractors work time ALONE from now forward in addition to them keeping to provide their usual administrative tasks on the project.

Or am I mistaken?

Best Regards,

Bjoern

Ah, don’t worry, that’s not what I had in mind. :wink:

We do have this conversation here indeed with many active contributors in 2023, and I am very happy to read many of them share the view that a product is vital and a big part of what makes them contribute to and engage in this community.

Hi @Sweetshark ,

Yes, from a 2022er cash flow perspective, that is correct. The currently budgeted sums for tenders and other one-off projects are carry-forwards from earlier years. We had a big jump in staff spending this year, with three new team members joining - but this is at least to some extent compensated by increased donation income. For a projection of that for the full fiscal year, I would defer to @floeff or @italovignoli

Best, Thorsten

1 Like

Hi!

I’m not a TDF member, thus can’t say if I should consider myself as a
“member of the community”. To be honest, I don’t actually know what such
a “community” actually is supposed to be.

I’ve been working with OOo since version 1.1.1 in 2005 and have since
contributed to (FR) documentation, help on mailing lists and Ask web
sites (EN/FR), reported some bugs and also provided a few LibreOffice
extensions.

Perhaps this allows me to bring in some comments as a contributor of sorts.

I’m very stumped by this discussion. Not sure what it is all about,
since English is not my mother language and some seem to be using
tongue-in-cheek. I understand this is all about making LibO a paying tool.

I strongly advise against such a decision which (1) would lead me
out (but that’s of no interest) and (2) would lead many users – as
already stated by others here – to using some free (gratis)
competitors. Such a decision would be highly detrimental to the project,
and to the software altogether.
Also, this would send a very bad message about TDF not fulfilling
their mission and about the project management.

I have the very deep impression that some in this discussion have a very
important conflict of interest and are promoting their employer’s
/apparent/ interest.

The project and the software are NOT separate. The tool is the
project, the project is the tool.

People, don’t try to play some foolery, just follow TDF philosophy and
view as stated in the statutes. Lets play together the same partition!

1 Like