I'll try to provide as much context as I can, since it seems there are
some folks interested in joining Apache Bloodhound!
On 2023/08/19 13:22:15 Nikolay Tsanov wrote:
Dear Greg and Shane (and everyone else who could weigh in),
I would like to kindly reiterate my question of Fri, Aug 18, 2023 at
9:29 AM ET: can we make GitHub (https://github.com/apache/bloodhound) our
main development repository and if so, what are your expectations in terms
of number of pull requests per period of time so that Bloodhound stays off
the attic?
First: we're all volunteers, so please be patient and wait for replies.
Also, no Board decisions would be made until the next 20-September
meeting at the earliest. If we can show there's interest and some plan
from existing PMC members to revive the project, then the board would
defer any decision until the October meeting.
--> The critical path now is finding some existing PMC members or
committers to help folks speaking up now organize the effort to onboard
new volunteers, or otherwise help plan how to revive the project here at
the ASF. I've directly included Gary Martin to see if he has ideas.
- ASF projects require oversight by at least three PMC members. That
matches the user expectation that any top level project is actively
managed and could fix urgent security bugs in the future, for example.
The board doesn't need those three members to be doing active
development, just to be present enough for critical bugs. Ensuring all
Apache projects can provide oversight is important, read on:
https://apache.org/dev/pmc.html#move-to-attic
- In terms of using GitHub as a primary repo, that's fine as long as
some existing PMC members can help do the work to change the settings.
Plenty of ASF projects use GitHub workflows. The requirement is that
the ASF also have a fully independent mirror on our own services (in
case GitHub goes down/goes away someday). Since the live-bloodhound
server appears to be down, I dunno how the repos here work personally.
- We can't just add people here as committers. We need some existing
folk(s) who understand Bloodhound to help guide new folks. If there are
specific changes people want to see, please submit Issues or PRs.
- Users are welcome to fork any ASF code. However you cannot fork the
name or branding, since those are trademarks of the ASF as a whole.
- Moving to the Attic merely means that all existing resources will be
turned read-only. Folks can still use past releases, access the
website, code repos, mailing lists, etc. just not change them in place.
Does that make sense?
Note I am not subscribed to this list, so please cc: me directly if you
need my help.
--
- Shane
Director
The Apache Software Foundation
