On Fri, Aug 18, 2023 at 6:08 AM Nikolay Tsanov <[email protected]> wrote:
> Hi Greg, > > Two questions: > 1. Is the verdict to send Bloodhound to the attic already rendered and you > are simply letting us know about it, or there is still room for discussions? > 2. If the debate is still open, how many commits are required per what > period of time in order to keep Bloodhound off the attic? > I'm just relating my experience with "how things work", given my extensive time with the ASF. I've been to over 200 Board meetings, and unfortunately missed the meeting a few days ago where Bloodhound was discussed (I'm traveling right now; which speaks to Shane's point about "give people time; 24h is not enough") Moving is not a given, as Shane noted later in this thread. The Board simply needs to see a community, and if that is present, then it will defer to those people (it is squishy; there are no "commit metrics"; it's about people). For all intents and purposes, there isn't an Apache Bloodhound community right now. ... but given the responses, is there enough? Of course. It only takes a few. So far, Daniel, yourself (Nikolay), and Sz have spoken up to throw in some time to see if we have enough energy to (re)launch Apache Bloodhound. Let me collect a few queries into this single email... * the (archival) repository is in svn, and mirrored to github. - if we want to evolve this, then I'd suggest making svn read-only and carrying forward with a git-based codebase * the "experimental" repository is at: https://github.com/apache/bloodhound-core and https://gitbox.apache.org/repos/asf/bloodhound-core.git - the above is Gary's initial work towards a v2 vision/prototype - there is no community consensus on future direction, so far; individual exploration and input is needed * "jettison burden" means it won't be Apache Bloodhound - personally, I welcome the legal umbrella/shield of the ASF, so I'm happy that I signed an ICLA (which is not a burden, IMO) I think the biggest issue is in the middle there: where is Bloodhound headed? Evolve the existing branch? Strike out on something new, like Gary was exploring (a Django-based solution), or something else? Personally, I'd like to see a Quart-based app server using a sqlite database. Keep it super simple and easy to set up. Regarding the repository: file some PRs. Or maybe we can use the GitHub wiki to figure out a roadmap. "commit" is several steps down the road, and sure: we can easily make that happen. But even if everybody had commit tomorrow, we don't have a consensus vision yet. Cheers, -g ps. note that I also hold a role in Infra; I can directly/immediately make changes to support the community.
