On Fri, Jan 5, 2024 at 3:34 AM Ghanshyam Mann <gmann@ghanshyammann.com> wrote:

---- On Thu, 04 Jan 2024 02:50:05 -0800 Sławek Kapłoński wrote ---
> Hi,
>
> Dnia czwartek, 4 stycznia 2024 11:12:02 CET Hoai-Thu Vuong pisze:
> > Hi Jay
> >
> > This is only my interest.
> > Monasca is a part of my company's services. But there are some high
> > priorities than keeping's monasca living.
>
> First of all thx a lot for reaching out and volunteering to maintain this projects. That's great.
> But I have some doubts TBH. If this is Your personal interest and there is no any company support there, maybe it would be better to move Monasca to the "x/" namespace and continue with it as unofficial project. That way it still can use Openinfra resources like before (gerrit, zuul, etc.) but it will not be so constrained with official projects requirements, like releases etc, as Jay already mentioned in his email earlier. Wdyt about it?

++, I like the proposal to move to x/ namespace and it will surly lower the project maintenance
expectation/activities (specially process wise) than what we have in OpenStack. And
moving its development in x/ namespace continue its open source model so that
any other member/company interested in that project can join the maintenance.

-gmann

>
>
> >
> > Thanks.
> >
> >
> >
> >
> > On Wed, Dec 27, 2023 at 12:43 AM Jay Faulkner jay@gr-oss.io> wrote:
> >
> > > First of all, thank you Hoai-Thu; your email is what the inactivity
> > > process is supposed to solicit!
> > >
> > > I agree with Dmitriy for the most part. The one part I'll add -- and note
> > > this isn't official policy, just something that I suspect many TC members
> > > will consider when deciding if Monasca should be considered "active" again,
> > > is the idea of redundancy. If a single person, with no backup, not backed
> > > by a company sponsor or some kind of long-term support guarantee resurrects
> > > the project, we may find ourselves back on this same path in a few months
> > > or a year if you decide to move on as well.
> > >
> > > Is your interest personal, or is it part of a larger investment in Monasca
> > > that could be tied to a longer-term support commitment?
> > >
> > > I'll also note, there are other paths to ensuring Monasca services
> > > continue to exist, including moving it outside of OpenStack governance.
> > > This would help in removing some of the requirements for activity, quality,
> > > and governance but would also mean losing some of the benefits of OpenStack
> > > governance -- such as this process which shines light on the inactivity of
> > > the project, release automation, or assistance with QA as needed.
> > >
> > > Thanks again,
> > > Jay Faulkner
> > > OpenStack TC Chair
> > >
> > >
> > > On Mon, Dec 25, 2023 at 12:19 PM Dmitriy Rabotyagov <
> > > noonedeadpunk@gmail.com> wrote:
> > >
> > >> Hi there!
> > >>
> > >> Changes to any OpenStack project should be submitted through a Gerrit.
> > >> You can check how to setup a Gerrit account and make your first patch here:
> > >> https://docs.openstack.org/contributors/common/setup-gerrit.html
> > >>
> > >> Regarding maintainer status - normal process for that would be having a
> > >> bunch of contributions to the project and nominate yourself as a Project
> > >> Team Leader (PTL) during bi-yearly elections [1].
> > >>
> > >> However, since the project in topic is not properly maintained at the
> > >> moment and we can't wait for next elections without marking project as
> > >> inactive - process might different for such cases.
> > >>
> > >> I think bare minimum would be to get CI of monasca passing and you can
> > >> propose patches for that right away. If there won't be any reaction to
> > >> these patches from the PTL and active core reviewers in a timely manner, it
> > >> should be possible to extend the core reviewers team.
> > >>
> > >> However, I would wait for a TC answer of how they see a potential
> > >> solution for the project if you're interested about helping out with it's
> > >> maintenance. Overall I believe that we as a community interested in keeping
> > >> projects alive and happy to see new ppl stepping up:)
> > >>
> > >>
> > >> [1] https://governance.openstack.org/election/
> > >>
> > >> On Mon, Dec 25, 2023, 10:05 Hoai-Thu Vuong thuvh87@gmail.com> wrote:
> > >>
> > >>> Dear all!
> > >>>
> > >>> I would like to know how to become a monasca maintainer?
> > >>> And how to push to main branch of monasca projects (master, stable/*)
> > >>>
> > >>> On Thu, Dec 21, 2023 at 5:26 PM Sławek Kapłoński skaplons@redhat.com>
> > >>> wrote:
> > >>>
> > >>>> Hi,
> > >>>>
> > >>>> Just a quick reminder about Monasca project. It seems that there is
> > >>>> still no any volunteer who would like to work on e.g. fixes for the
> > >>>> project's gate.
> > >>>>
> > >>>> Milestone 2 of 2024.1 cycle is just around the corner - it's *Jan 8th* so
> > >>>> if there is anyone interested in keeping Monasca alive and have it released
> > >>>> in *2024.1* then You should start fixing main issues asap.
> > >>>>
> > >>>> Just for the record, current stats of the project:
> > >>>>
> > >>>> $ tools/project_stats_check.py -p monasca
> > >>>> **************************************************
> > >>>> Start Project monasca analysis...
> > >>>> Includes repositories: ['openstack/monasca-api',
> > >>>> 'openstack/monasca-log-api', 'openstack/monasca-events-api',
> > >>>> 'openstack/monasca-specs', 'openstack/monasca-notification',
> > >>>> 'openstack/monas
> > >>>> ca-persister', 'openstack/monasca-tempest-plugin',
> > >>>> 'openstack/monasca-thresh', 'openstack/monasca-common',
> > >>>> 'openstack/monasca-ui', 'openstack/python-monascaclient',
> > >>>> 'openstack/monasca-agen
> > >>>> t', 'openstack/monasca-statsd', 'openstack/monasca-ceilometer',
> > >>>> 'openstack/monasca-transform', 'openstack/monasca-grafana-datasource',
> > >>>> 'openstack/monasca-kibana-plugin']
> > >>>> Start analysis branch master...
> > >>>> Validating Gerrit...
> > >>>> * There are 4 ready for review patches generated within 180 days
> > >>>> * There are 2 not reviewed patches generated within 180 days
> > >>>> * There are 2 merged patches generated within 180 days
> > >>>> * Unreviewed patch rate for patches generated within 180 days is 50.0 %
> > >>>> * Merged patch rate for patches generated within 180 days is 50.0 %
> > >>>> * Here's top 10 owner for patches generated within 180 days
> > >>>> (Name/Account_ID: Percentage):
> > >>>> - Dr. Jens Harbott : 50.00%
> > >>>> - Joel Capitao : 50.00%
> > >>>> Validate Zuul...
> > >>>> Set buildsets fetch size to 500
> > >>>> * Repo: openstack/python-monascaclient gate job builds success rate:
> > >>>> 100%
> > >>>> * Repo: openstack/monasca-statsd gate job builds success rate: 95%
> > >>>> * Repo: openstack/monasca-tempest-plugin gate job builds success rate:
> > >>>> 81%
> > >>>> * Repo: openstack/monasca-transform gate job builds success rate: 100%
> > >>>> * Repo: openstack/monasca-thresh gate job builds success rate: 100%
> > >>>> * Repo: openstack/monasca-log-api gate job builds success rate: 82%
> > >>>> * Repo: openstack/monasca-specs gate job builds success rate: 100%
> > >>>> * Repo: openstack/monasca-api gate job builds success rate: 76%
> > >>>> * Repo: openstack/monasca-ui gate job builds success rate: 88%
> > >>>> * Repo: openstack/monasca-events-api gate job builds success rate: 83%
> > >>>> * Repo: openstack/monasca-grafana-datasource gate job builds success
> > >>>> rate: 100%
> > >>>> * Repo: openstack/monasca-kibana-plugin gate job builds success rate:
> > >>>> 83%
> > >>>> * Repo: openstack/monasca-persister gate job builds success rate: 98%
> > >>>> * Repo: openstack/monasca-agent gate job builds success rate: 97%
> > >>>> * Repo: openstack/monasca-common gate job builds success rate: 84%
> > >>>> * Repo: openstack/monasca-ceilometer gate job builds success rate: 100%
> > >>>> * Repo: openstack/monasca-notification gate job builds success rate:
> > >>>> 93%
> > >>>> **************************************************
> > >>>>
> > >>>> Dnia wtorek, 17 października 2023 20:18:01 CET Jay Faulkner pisze:
> > >>>>
> > >>>> > Hello OpenStackers,
> > >>>>
> > >>>> >
> > >>>>
> > >>>> > I wanted to close the loop on this -- Monasca was marked as an
> > >>>> inactive
> > >>>>
> > >>>> > project by the Technical Committee. This means if there is no
> > >>>> volunteer to
> > >>>>
> > >>>> > help restore CI to functionality, bring it up to date for the
> > >>>> release, and
> > >>>>
> > >>>> > take ownership of it as PTL before the M-2 milestone, it will become
> > >>>>
> > >>>> > eligible for full retirement by the TC.
> > >>>>
> > >>>> >
> > >>>>
> > >>>> > Thank you to Slawek for doing the work to get the statistics to
> > >>>> enable this
> > >>>>
> > >>>> > decision.
> > >>>>
> > >>>> >
> > >>>>
> > >>>> > --
> > >>>>
> > >>>> > Jay Faulkner
> > >>>>
> > >>>> > OpenStack TC Chair
> > >>>>
> > >>>> >
> > >>>>
> > >>>> > On Fri, Oct 6, 2023 at 12:59 AM Sławek Kapłoński skaplons@redhat.com
> > >>>> >
> > >>>>
> > >>>> > wrote:
> > >>>>
> > >>>> >
> > >>>>
> > >>>> > > Hi,
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > I just proposed patch [1] to mark Monasca as inactive project. It
> > >>>> was
> > >>>>
> > >>>> > > discussed during last TC meeting on 03.10.2023. Reasons for that are
> > >>>>
> > >>>> > > described in the commit message of the [1] but I will also put all
> > >>>> of it
> > >>>>
> > >>>> > > here:
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > previous cycle there wasn't almost any contributions to that
> > >>>> project and
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > most active contributors in last 180 days were Elod Illes and Dr.
> > >>>> Jens
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > Harbott who were fixing some Zuul configuration issues only.
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > Here are detailed statistics about Monasca projects:
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > Validating Gerrit...
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * There are 7 ready for review patches generated within 180 days
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * There are 2 not reviewed patches generated within 180 days
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * There are 5 merged patches generated within 180 days
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Unreviewed patch rate for patches generated within 180 days is
> > >>>> 28.0 %
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Merged patch rate for patches generated within 180 days is 71.0 %
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Here's top 10 owner for patches generated within 180 days
> > >>>>
> > >>>> > > (Name/Account_ID: Percentage):
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > - Dr. Jens Harbott : 42.86%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > - Joel Capitao : 28.57%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > - Elod Illes : 28.57%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > Validate Zuul...
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > Set buildsets fetch size to 500
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-log-api gate job builds success rate: 82%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-statsd gate job builds success rate: 95%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-tempest-plugin gate job builds success
> > >>>> rate: 81%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-common gate job builds success rate: 84%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-kibana-plugin gate job builds success
> > >>>> rate: 83%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-ceilometer gate job builds success rate:
> > >>>> 100%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-events-api gate job builds success rate:
> > >>>> 83%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-ui gate job builds success rate: 88%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-specs gate job builds success rate: 100%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-grafana-datasource gate job builds
> > >>>> success
> > >>>>
> > >>>> > > rate: 100%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-persister gate job builds success rate:
> > >>>> 98%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-notification gate job builds success
> > >>>> rate: 93%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-thresh gate job builds success rate: 100%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-api gate job builds success rate: 76%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-agent gate job builds success rate: 98%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/python-monascaclient gate job builds success
> > >>>> rate: 100%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > * Repo: openstack/monasca-transform gate job builds success rate:
> > >>>> 100%
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > *What's next?*
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > According to the "Emerging and inactive projects" document [2] if
> > >>>> there
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > will be no volunteers who will step up and want to maintain this
> > >>>> project
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > *before Milestone-2 of the 2024.1 cycle (week of Jan 08 2024)*
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > *there will be no new release of Monasca in the 2024.1 cycle and TC*
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > *will discuss if project should be retired.*
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > So if You are interested in keeping Monasca alive and active,
> > >>>> please reach
> > >>>>
> > >>>> > > out to the TC to discuss that ASAP. Thx in advance.
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > [1] https://review.opendev.org/c/openstack/governance/+/897520
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > [2]
> > >>>>
> > >>>> > >
> > >>>> https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > --
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > Slawek Kaplonski
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > Principal Software Engineer
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> > > Red Hat
> > >>>>
> > >>>> > >
> > >>>>
> > >>>> >
> > >>>>
> > >>>>
> > >>>> --
> > >>>>
> > >>>> Slawek Kaplonski
> > >>>>
> > >>>> Principal Software Engineer
> > >>>>
> > >>>> Red Hat
> > >>>>
> > >>>
> > >>>
> > >>> --
> > >>> Thu.
> > >>>
> > >>
> >
> > --
> > Thu.
> >
>
>
> --
> Slawek Kaplonski
> Principal Software Engineer
> Red Hat