On Wed, Apr 25, 2018 at 7:48 AM, Peter Karman <[EMAIL PROTECTED]> wrote:

Sorry for the late reply; this email has been sitting half-done in my
Drafts folder for days. Although these questions have reasonably
straightforward answers, and none of the paths forward are wrong or
bad, it's been a bit challenging for me to choose amongst them, given
the gratitude I feel towards the rest of the Lucy community.

All software projects have a life cycle, and new technologies rise all
the time. In my time as an Incubator administrator and on the ASF
Board, I've seen many great projects complete their arcs sooner than
Lucy.

The ideal for the ASF is not that codebases should last forever, but
for those who participate in ASF communities to be willing to
participate in another ASF project. As an ASF advocate, I hope you've
all had a good experience here.

It's been about a year and a half since I've actively developed Lucy
and Clownfish. They were my main gig for a decade, for which I feel
incredibly fortunate; now other things have taken priority, and at
this point it's hard to foresee returning to active development.
However, thankfully we have not come across any sort of soul-crushing
security or legal problems, so the maintenance burden hasn't been a
heavy lift.

It would be fine with me to continue for some time.  It would also be
fine to retire. I'm OK with whatever path the community chooses.

Marvin Humphrey
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB