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


Hi Uwe, all,

Am 26.05.21 um 23:04 schrieb Uwe Altmann:
Hi Andreas

Am 26.05.21 um 21:17 schrieb Andreas Mantke:
So go on and...arrange 
               ^^^^^^^^^^!!!

That's the point: Stop complaining but go on and nudge a company or a
group of Plone developers to offer something and to give a credible
answer how to ensure 5 years of reliable support on this. As a plone
developer you'll surely know some.
With python we'll have no problem to find someone if we need some
changes in a few years.

your reply showed little up to no knowledge and interest in that
CMS/DMS. Why should I bother /nudge Plone developers and ask them to
spent time on a proposal? Your response shows a very hostile tone
towards the Plone  open source community.
(for your information: https://en.wikipedia.org/wiki/Plone_(software)
--> first stable release Feb. 2003, last major release July 2019, last
security patch: 2021/05/18)
(and for the records: I'm not a Plone developer, but developed Plone
add-ons)


Maybe it's most easy to complain on this. I offered hands-on workshops
with no interest from the TDF community in the past. The TDF admin team
got a training from a Plone core developer some time ago.

...what doesn't change anything on the basic problem. We (in contrast
to your opinion) did not first set up plone (or something else) and
then look for people who perhaps maybe want to learn it (which - if we
had found some - would have been at least the second 

Maybe you have not been part of the crew that worked on the first steps
of the project and it's infrastructure. If individuals or small groups
wouldn't have set up a website based on Silverstripe (without asking for
permissions or without a poll) or a Template and Extension website based
on Plone, maybe the project would discuss have  discussed about this
tooling for month without any visible action. One core principle of the
project is that the doers decide the way and you'll find this form of
action at many places in the project.
This principle will fail (for a volunteer project) once the people that
want to tell the doers what and how they had to work, becomes the
majority or the bosses.

best solution. But we didn't find them).  We have to cut the coat
according to our cloth. (btw.: Similar as the android app. Sad - but
there seems no one out there interested to develop under TDFs umbrella)
Great picture with cutting the coat according to the cloth: it reminds
me on 'The Emperor's New Clothes'.

But there are other software with such Bus_factor in the project, but
nobody is complaining about that (or not loudly / in public).

And what does this contribute to the discussion on the MC tooling?
Please stay focused.

Sorry Uwe but for years I was bantered by a core member of this project
for one mistake which I made in 2012. I never heard something else about
other software and volunteers in this project.
I did my work for TDF and LibreOffice only on volunteer state without
getting any payment or asking for such payment for years.

Regards,
Andreas

-- 
## Free Software Advocate
## Plone add-on developer
## My blog: http://www.amantke.de/blog



--
To unsubscribe e-mail to: board-discuss+unsubscribe@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

Context


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.