Hi all,
I'm in complete support of this. Given the current level of interest, I
believe that we should move this project to the attic.

Best,

Casey Stella

On Mon, Nov 2, 2020 at 7:28 PM Justin Leet <justinjl...@gmail.com> wrote:

> Hi all,
>
> I want to start a discussion in the community to consider retiring Metron
> to the Apache Attic and dissolve the project management committee. For
> anyone unaware, an overview is available at Apache Attic
> <https://attic.apache.org/>. In short, it's a way to provide a wind-down
> process for projects reaching their end of life. This process, and
> potential next steps, can be found here:
> http://attic.apache.org/process.html.
>
> We've seen a substantial decrease in contributions (both code and mailing
> lists) over the past year or so (see:
> https://github.com/apache/metron/commits/master). There's been some
> interest in the project, but in my personal opinion, not enough to build or
> sustain real momentum. Additionally, there's been an inability to close the
> loop on paring down the project's scope and building a solid foundation for
> future work (see: Development Activity has dropped to effectively 0, what
> should we do?
> <
> https://lists.apache.org/thread.html/rf7ea1c1afb347e352efff50f58fbd58779f71e6c814d2a5563e381d7%40%3Cdev.metron.apache.org%3E
> >).
> Finally, the last release was over a year ago and I don't see a release
> naturally building anytime soon. We haven't seen much active development or
> participation for a substantial period of time, which to me implies we've
> reached a natural end of life.
>
> The most obvious practical effects would be no new releases, setting source
> read-only, mailing lists closed down, automated processes ended, etc. In
> addition, the PMC would also be dissolved as part of this process.
> Community members may still fork all or part of Metron, but should keep in
> mind that the Metron trademark remains with the ASF.
>
> What opinions are there either in favor of or against moving the project to
> the Attic? Any questions about the process (or comments/corrections anyone
> would like to add)?
>
> Thanks,
> Justin
>

Reply via email to