[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [technology-pmc] Eclipse BIRT is dysfunctional
|
+1 from me. STEM
still uses BIRT internally, so we would prefer it to be in an active functional
state rather than just moving it to archive.....
From:
Werner
Keil <werner.keil@xxxxxxx>To:
Technology
PMC <technology-pmc@xxxxxxxxxxx>Date:
02/26/2021
10:31 AMSubject:
[EXTERNAL]
Re: [technology-pmc] Eclipse BIRT is dysfunctionalSent
by: "technology-pmc"
<technology-pmc-bounces@xxxxxxxxxxx>
Then
aren’t projects like that usually archived?
Gesendet
von Mailfür Windows 10
Von:
Chris
Aniszczyk
Gesendet: Freitag, 26. Februar 2021 19:29
An: Technology
PMC
Betreff: Re: [technology-pmc] Eclipse BIRT is dysfunctional
+1,
I've done some more research into the situation and the project is definitely
not in a healthy situation
On
Thu, Feb 25, 2021 at 4:01 AM Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
wrote:
+1
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx,
http://guw.io/
> On Feb 24, 2021, at 21:58, Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
wrote:
>
> Greetings PMC.
>
> The Eclipse BIRT project has not participated in the Eclipse Foundation
Development Process (or the open source process as we define it) for some
time.
>
> The project has not engaged in a release review since June 2018. Their
Jenkins instance was recently shut down due to inactivity. Questions on
the mailing list and forums are unanswered.
>
> Popular questions about the project are generally of the form "is
this project still active?". Eclipse BIRT is the project that I get
the most questions about in the EMO inbox, and--unfortunately--the only
answer I can give is a shrug and a pointer to connect with the communication
channels that I know the project is not monitoring.
>
> Based on a cursory review, the project team has virtually no engagement
via Bugzilla. There's a number of unanswered pull requests dating back
more than one year. A number of pull requests have been merged within
the last year, but based on a cursory review, it appears that only pull
requests by colleagues are being merged.
>
> I have reached out to the project via the mailing list and via personal
correspondence with project leaders. I've been very clear in these communications
that the project team needs to engage in the open source process in general
and the EDP in particular, but have not received any indication that the
existing project team is prepared to do so.
>
> The project team has engaged recently in the CQ process, and so is
clearly not entirely absent from our processes. There is some evidence
of ongoing development, but with no formal releases, it's pretty clear
that that development is not intended to service the open source community.
In one private exchange, a committer stated that (paraphrasing) "From
time to time we synch up the open source code with the commercial product".
That is, the project team is effectively operating behind their corporation's
firewall, making it impossible for others to participate and contribute.
>
> Notwithstanding a few CQs, the project appears to be completely disengaged
from the open source process and uninterested in engaging in the EDP.
>
> I have three parties who are interested in taking on responsibility
for rehabilitating the project, reinstating builds, and bringing the code
up to a modern standard.
>
> I hereby ask that the Eclipse Technology PMC declare the project dysfunctional.
>
> With your declaration, I intend to retire all existing committers
and project leads currently working behind their corporate firewall and
replace them with new volunteers. My expectation is that the new team will
abandon the existing Bugzilla record as many of the bugs are so old that
reconciling them against the current code base is not worth the effort.
>
> Can I get your +1, please?
>
> Wayne
> --
> Wayne Beaton
> Director of Open Source Projects | Eclipse Foundation
> _______________________________________________
> technology-pmc mailing list
> technology-pmc@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/technology-pmc
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/technology-pmc
--
Cheers,
Chris Aniszczyk
http://aniszczyk.org
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/technology-pmc