Robot users

Is there a captcha that can be installed on new user creation? Over the past couple weeks, it has become horrendous. The commits@ list is getting buried in user creation notices. Cheers, -g

Re: [Proposal] How to get out of this situation?

On Mon, Oct 23, 2017 at 3:44 PM, Olemis Lang wrote: > On 10/23/17, Allan Swanepoel wrote: > >... > > And, again, nothing against ASF here, but I'm sure migrating the > > source to GH could attract more involvement from more developers. > > > [...] > >

Re: Public Bloodhound is down again

Infra can provide a bare Ubuntu 16.04 VM via puppet, and then you can finish the install from there. No skin off Infra's back. We encourage project VMs to use puppet to easily restore their VM should something go sideways. But if you can easily rebuild another way... hey, fine. Cheers, -g On

Re: Public Bloodhound is down again

On Sun, Nov 5, 2017 at 4:05 AM, John Chambers wrote: > Hi Greg/Dammina, > > I have been looking at how to get a working version of the Bloodhound > instance locally from a backup file I made on August 1st 2017. I have asked > That should be the latest, as the site wasn't

Re: Public Bloodhound is down again

e spin up a VM for Apache Bloodhound. We've been going back/forth on these VMs for a while now, and have yet to succeed. I'm reachable here (as a PMC Member) or on users@infra or via a Jira ticket. Happy to help, but Infra needs some assurances of assistance for your VM(s). Cheers, Greg Stein I

Re: Public Bloodhound is down again

bloodhound-vm3 up and running. I had asked for *two* volunteers. Can Infrastructure delete bloodhound-vm and bloodhound-vm2? I presume there is no data to copy from those? Thanks, Greg Stein Infrastructure Administrator, ASF (and Bloodhound PMC Member) On Sun, Nov 5, 2017 at 7:07 PM, Greg

Re: [Proposal] Core Bloodhound - basic concepts

On Sun, Mar 11, 2018 at 4:21 PM, Gary wrote: >... > How tickets are stored as a whole is also worth tackling, which is what #2 > is trying to broadly decide. Here I am suggesting that the state of a > ticket can be built up from a query that collects all the change

Re: [Proposal] Core Bloodhound - basic concepts

On Mon, Mar 19, 2018 at 8:43 AM, Gary Martin wrote: > Hi everyone, > > I am going to start building out a basic core implementation to play > around with some of the ideas we have discussed. I'll try not to take > things too far before getting this into source control.

Re: looking to get back on track or possible retirement to attic

Hi Gary, Daniel, et al, On Wed, Apr 15, 2020 at 9:17 PM Gary Martin wrote: > Hi Daniel, > > On Sun, 2 Feb 2020, at 9:12 AM, Daniel Brownridge wrote: > >... > > > I see that I hid a number of issues by mentioning that there is some > infrastructure work that is required. Updates to the project

Re: Is it time for Bloodhound to move to the Apache Attic?

Nobody is stopping you. There are a bunch of forks already: https://github.com/apache/bloodhound/network/members On Sat, Sep 12, 2020 at 4:30 PM jason wrote: > > Post it on Github and let us fork it.Sent from my Samsung Galaxy > smartphone. > Original message From: Shane

Re: Is it time for Bloodhound to move to the Apache Attic?

I don't have any coding time, but I do have review/oversight time. That makes (4) for oversight. On Sun, Sep 13, 2020 at 8:54 AM John Chambers wrote: > Hi everyone, I am also still committed to supporting this project going > forward. > I will do my best to take part in any discussions about

Re: git repo for new bloodhound core work

How about just "bloodhound-core" ... the"bh" in "bhcore" seems redundant. Note that we could also ask Infra to perform some "magic" like renaming "bloodhound" to "bloodhound-archive" or such, and then make use of "bloodhound" going forward. Note that requesting a new git repository is available

Re: git repo for new bloodhound core work

On Thu, May 6, 2021 at 5:26 PM Gary Martin wrote: >... > With github in the mix we will naturally open ourselves up to the > possibility of accepting changes from non-committers as pull requests. > Beyond concerns around ownership of the code and how large a change would > require an ICLA, I

Re: ASF Board Report for Bloodhound - Repeated Reminder for August 2021

We're still here. The community hasn't disappeared. It is simply low-energy. On Thu, Aug 19, 2021 at 8:54 PM Gary Martin wrote: > Hi Sander and everyone else, > > Sorry for the unfortunate silence from me for a bit. I'll avoid providing > too much in the way of excuses as I hope that people

Re: Apache Bloodhound will be moving to the Attic

On Fri, Aug 18, 2023 at 6:08 AM Nikolay Tsanov 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

Re: Apache Bloodhound will be moving to the Attic

On Sun, Aug 20, 2023 at 7:59 AM Nikolay Tsanov wrote: >... > The choice of a version control system goes far beyond the tech stack, it > defines the governance at the technology layer of the Bloodhound > architecture > No. Governance is defined by Apache rules of peer conduct. The version

Re: git repo for new bloodhound core work

Following the rest of this thread (archive at https://lists.apache.org/thread/kohw9nr4x94wdh7w46y82x6ghy75znjh), there were three PMC members supporting the move to git (Gary, Greg, John) with implied consent from a fourth (Dammina). Thus, I've gone ahead and made svn readonly [1]. Cheers, -g

Re: Apache Bloodhound will be moving to the Attic

o being >> Django >> >> based. I have to be honest I haven't yet looked in detail at the >> >> experimental work that has been done by Gary in that area yet, but >> that too >> >> is going on my todo list. In general though I really like the idea of >>

Re: Apache Bloodhound will be moving to the Attic

There has been near-zero commit activity for many years. The mailing list is empty. There are a few people "around", but inactive. Note that a move to the Attic will not cause any problems with the 0.8 release. That will always be available for download. The Attic is simply a marker that future

Re: Apache Bloodhound will be moving to the Attic

t; > Many thanks, > > Daniel > > *Daniel Brownridge* > dan...@freshnewpage.com > +44 779 138 5626 > On 21/08/2023 18:08, Greg Stein wrote: > > https://svn.apache.org/repos/asf/bloodhound/site/ > > It is read-only, but I can override that to apply any patches y

Re: switch website to Pelican? (was: Apache Bloodhound will be moving to the Attic)

wrote: > I am happy enough to support moving the site to using Pelican and to having > it's own repo to make life easier when maintaining it. > > Cheers > > John . > > On Tue, 22 Aug 2023 at 16:55, Greg Stein wrote: > > > The site is outside of {trunks, tags

Re: [bloodhound-site] branch asf-site updated: stage the test

Oh, and I didn't touch download.cgi and download.html, as Daniel switched to using closer.lua ... the pages are still there, for when we want to bring back a custom download page On Fri, Aug 25, 2023 at 8:18 PM Greg Stein wrote: > My commit message was wrong. The test/staging site is: >

Re: [bloodhound-site] branch asf-site updated: stage the test

ommit to branch asf-site > in repository https://gitbox.apache.org/repos/asf/bloodhound-site.git > > > The following commit(s) were added to refs/heads/asf-site by this push: > new 7a4eabb stage the test > 7a4eabb is described below > > commit 7a4eabbd0a0170b85c

signing an ICLA

For those who may want to commit in the future (Daniel, Nikolay), please follow the instructions on this page: https://www.apache.org/licenses/contributor-agreements.html#clas Fill in "bloodhound" on the project. That just sends emails to the right places. Then submit your ICLA to

Re: switch website to Pelican? (was: Apache Bloodhound will be moving to the Attic)

-635-7198 > > On Mon, Aug 21, 2023 at 10:20 PM Greg Stein wrote: > > > Rather than using pure HTML/etc, I would suggest that we switch to using > > Pelican for site generation (sources move to markdown). Infra has > provided > > an automated workflow to move edits to

Re: switch website to Pelican? (was: Apache Bloodhound will be moving to the Attic)

ons. > > Cheers, > Gary > > On 22/08/2023 03:19, Greg Stein wrote: > > Rather than using pure HTML/etc, I would suggest that we switch to using > > Pelican for site generation (sources move to markdown). Infra has > provided > > an automated workflow

switch website to Pelican? (was: Apache Bloodhound will be moving to the Attic)

ot;nice to have" for this community (to better understand the tooling). Thoughts? Cheers, -g On Mon, Aug 21, 2023 at 12:08 PM Greg Stein wrote: > https://svn.apache.org/repos/asf/bloodhound/site/ > > It is read-only, but I can override that to apply any patches you send to > dev@ > >