e-mail only

-
Alex

On Thu, May 29, 2025 at 6:19 PM Jason Porter <jpor...@ibm.com.invalid>
wrote:

> Is this up on the wiki, or just through email for now?
>
> --
> Jason Porter
> Software Engineer
> He/Him/His
>
> IBM
>
>
> From: Alex Porcelli <porce...@apache.org>
> Date: Thursday, May 29, 2025 at 16:16
> To: dev@kie.apache.org <dev@kie.apache.org>
> Cc: Andrea Cosentino <anco...@gmail.com>, claus.ib...@gmail.com <
> claus.ib...@gmail.com>, Brian Proffitt <b...@apache.org>
> Subject: [EXTERNAL] Re: Podling Kie Report Reminder - June 2025
> Jason,
>
> Good points, please feel free to amend the previous with additional data.
>
> I just wanted to make sure we had baseline available, so others can
> contribute.
>
> -
> Alex
>
> On Thu, May 29, 2025 at 6:10 PM Jason Porter <jpor...@ibm.com.invalid>
> wrote:
>
> > Thanks for doing this one, Alex. We should include any new contributors
> > during the quarter. I think we’ve had one or two, double check in the
> > private mailing list. We also have some branding issues we need to deal
> > with on the sub project websites. I believe Justin mentioned that a while
> > back.
> >
> > --
> > Jason Porter
> > Software Engineer
> > He/Him/His
> >
> > IBM
> >
> >
> > From: Alex Porcelli <porce...@apache.org>
> > Date: Thursday, May 29, 2025 at 12:40
> > To: dev@kie.apache.org <dev@kie.apache.org>, Andrea Cosentino <
> > anco...@gmail.com>, claus.ib...@gmail.com <claus.ib...@gmail.com>, Brian
> > Proffitt <b...@apache.org>
> > Subject: [EXTERNAL] Re: Podling Kie Report Reminder - June 2025
> > Here follows a proposed draft....
> >
> > Apache KIE
> >
> > Description:
> > Apache KIE is the home of popular open-source business automation
> > technologies. It includes:
> >
> > - Drools: Rule and decision engine
> > - jBPM: Workflow and business process engine
> > - SonataFlow: CNCF-compatible serverless workflow engine
> > - OptaPlanner: Optimization engine for planning problems
> > - Kogito: Cloud-native runtime and infrastructure for business automation
> >
> > These tools are used to model, execute, and optimize business
> > decisions and workflows.
> >
> > Three most important issues to address for graduation:
> >
> > - Replace LGPL dependency (currently Hibernate)
> > - Reduce or replace remaining EPL-licensed source code
> > - Stabilize and standardize CI and release procedures
> >
> > Any issues that the Incubator PMC or ASF Board might need to be aware of:
> > None at this time.
> >
> > How has the community developed since the last report:
> > The community remains active. New contributors are becoming engaged,
> > and a new vendor has started contributing (old community member
> > changed companies).
> >
> > How has the project developed since the last report:
> > The project has seen several improvements across the codebase. Work on
> > the second release is now in progress.
> >
> > How does the podling rate their own maturity:
> > The community has grown stronger and is actively working on graduation
> > requirements. The recent release of Hibernate 7 under the Apache
> > License removes a key blocker. We expect to adopt it within the next
> > few quarters. A new component is being developed to help replace the
> > remaining EPL code. The CI and release process is also improving as
> > part of the ongoing release work.
> >
> > -
> > Alex
> >
> > On Wed, May 21, 2025 at 8:25 PM <jmcl...@apache.org> wrote:
> > >
> > > Dear podling,
> > >
> > > This email was sent by an automated system on behalf of the Apache
> > > Incubator PMC. It is an initial reminder to give you plenty of time to
> > > prepare your quarterly board report.
> > >
> > > The board meeting is scheduled for Wed, 18 June 2025.
> > > The report for your podling will form a part of the Incubator PMC
> > > report. The Incubator PMC requires your report to be submitted 2 weeks
> > > before the board meeting, to allow sufficient time for review and
> > > submission (Wed, June 04).
> > >
> > > Please submit your report with sufficient time to allow the Incubator
> > > PMC, and subsequently board members to review and digest. Again, the
> > > very latest you should submit your report is 2 weeks prior to the board
> > > meeting.
> > >
> > > Candidate names should not be made public before people are actually
> > > elected, so please do not include the names of potential committers or
> > > PPMC members in your report.
> > >
> > > Thanks,
> > >
> > > The Apache Incubator PMC
> > >
> > > Submitting your Report
> > >
> > > ----------------------
> > >
> > > Your report should contain the following:
> > >
> > > *   Your project name
> > > *   A brief description of your project, which assumes no knowledge of
> > >     the project or necessarily of its field
> > > *   A list of the three most important issues to address in the move
> > >     towards graduation.
> > > *   Any issues that the Incubator PMC or ASF Board might wish/need to
> be
> > >     aware of
> > > *   How has the community developed since the last report
> > > *   How has the project developed since the last report.
> > > *   How does the podling rate their own maturity.
> > >
> > > This should be appended to the Incubator Wiki page at:
> > >
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/June2025
> > >
> > > Note: This is manually populated. You may need to wait a little before
> > > this page is created from a template.
> > >
> > > Note: The format of the report has changed to use markdown.
> > >
> > > Mentors
> > > -------
> > >
> > > Mentors should review reports for their project(s) and sign them off on
> > > the Incubator wiki page. Signing off reports shows that you are
> > > following the project - projects that are not signed may raise alarms
> > > for the Incubator PMC.
> > >
> > > Incubator PMC
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
> > > For additional commands, e-mail: dev-h...@kie.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
> > For additional commands, e-mail: dev-h...@kie.apache.org
> >
>

Reply via email to