I can help co-maintaining and I think I can bring another co-maintainer.
We've been creating custom libreoffice packages for a project so, we can
bring a little experience

El jue, 1 jun 2023 a las 14:17, Gwyn Ciesla via devel (<
devel@lists.fedoraproject.org>) escribió:

> I've taken ownership of libreoffice for the time being, at least to keep
> the lights on. Co-maintainers, as always, welcome.
>
>
>
> --
> Gwyn Ciesla
> she/her/hers
> ------------------------------------------------
> in your fear, seek only peace
> in your fear, seek only love
> -d. bowie
>
>
> Sent with Proton Mail secure email.
>
> ------- Original Message -------
> On Thursday, June 1st, 2023 at 1:30 PM, Matthias Clasen <
> mcla...@redhat.com> wrote:
>
>
> > Hey,
> >
>
> > as you've probably seen, the LibreOffice RPMS have recently been
> orphaned, and I thought it would be good to explain the reasons
> > behind this.
> >
>
> > The Red Hat Display Systems team (the team behind most of Red Hat’s
> desktop efforts) has maintained the LibreOffice packages in Fedora for
> years as part of our work to support LibreOffice for Red Hat Enterprise
> Linux. We are adjusting our engineering priorities for RHEL for
> Workstations and focusing on gaps in Wayland, building out HDR support,
> building out what’s needed for color-sensitive work, and a host of other
> refinements required by Workstation users. This is work that will improve
> the workstation experience for Fedora as well as RHEL users, and which, we
> hope, will be positively received by the entire Linux community.
> >
>
> > The tradeoff is that we are pivoting away from work we had been doing on
> desktop applications and will cease shipping LibreOffice as part of RHEL
> starting in a future RHEL version. This also limits our ability to maintain
> it in future versions of Fedora.
> >
>
> > We will continue to maintain LibreOffice in currently supported versions
> of RHEL (RHEL 7, 8 and 9) with needed CVEs and similar for the lifetime of
> those releases (as published on the Red Hat website). As part of that, the
> engineers doing that work will contribute some fixes upstream to ensure
> LibreOffice works better as a Flatpak, which we expect to be the way that
> most people consume LibreOffice in the long term.
> >
>
> > Any community member is of course free to take over maintenance, both
> for the RPMS in Fedora and the Fedora LibreOffice Flatpak, but be aware
> that this is a sizable block of packages and dependencies and a significant
> amount of work to keep up with.
> >
>
> > Matthias
> > _______________________________________________
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> > Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to