+1 On Tue, Jul 7, 2026 at 5:16 PM Allen Wittenauer <[email protected]> wrote:
> > I was about to submit, but I made some minor changes to the Project > Activity section to clean it up and make it a bit more accurate: > > ## Project Activity: > Quite a bit of activity in March, April, and May with some big updates, > including switching the operating system of the base container. We are now > dealing with fallout from those changes with an eye towards making a 0.16 > release later this year. > > > > > > > On Jul 7, 2026, at 1:25 AM, Nick Dimiduk <[email protected]> wrote: > > > > +1 > > > > Thanks Allen! > > > > On Mon, Jul 6, 2026 at 6:00 PM Allen Wittenauer <[email protected]> wrote: > > > >> (Sorry everyone, the report slipped my mind last month) > >> > >> ## Description: > >> Apache Yetus provides libraries and tools that enable contribution and > >> release > >> processes for software projects. > >> > >> ## Project Status: > >> Current project status: Dormant > >> Issues for the board: None > >> > >> ## Membership Data: > >> Apache Yetus was founded 2015-09-15 (11 years ago) > >> There are currently 12 committers and 9 PMC members in this project. > >> The Committer-to-PMC ratio is 4:3. > >> > >> Community changes, past quarter: > >> - No new PMC members. Last addition was Akira Ajisaka on 2018-12-17. > >> - No new committers. Last addition was Akira Ajisaka on 2018-02-06. > >> > >> ## Project Activity: > >> Quite a bit of activity in March and April with some big updates, > including > >> switching the base operating system of the base container. We are now > >> dealing with fallout from those changes with an eye towards making a > 0.16 > >> release this year. > >> > >> ## Community Health: > >> Despite the lack of a board report last month (that's on aw@ being > >> forgetful), > >> we're fine. While not a whole lot is happening in the mailing lists, > there > >> are > >> definitely signs of life in commits, github PRs, and JIRA issues. Two > PMC > >> members being the most visible and others are watching so getting a > release > >> out shouldn't be an issue. > >
