Hey Scott, As you are the sole maintainer, IMO it's your decision to make. Personally I'd be fine with Option (2), but are you willing to maintain the code, review any rare patches submitted, release sporadically etc.? Otherwise I think it's time to archive the project.
Colm. Cop;l, On Wed, Feb 21, 2024 at 9:36 PM Cantor, Scott <canto...@osu.edu> wrote: > > On 2/21/24, 4:07 PM, "Berin Lautenbach" <be...@wingsofhermes.org > <mailto:be...@wingsofhermes.org>> wrote: > > Thanks for weighing in, obviously I think you get some say on this. > > > and there are extra overheads on you if you have to do a level of > > management of the code within the ASF. > > There are, and I don't dispute it, if I were making the decision alone, the > only reason for not forking it is having to consider renaming the artifacts, > which creates a lot of work for me on the packaging side. > > And in fact, we have no plans right now to even produce a subsequent release > of our C++ software that would pull in a new version of this code either, so > it's quite possible I would fork it in principle but not in practice, > depending on how things go. > > Obviously that becomes totally a "me" decision if it's retired here, that's > why I decided it was time to just raise it. > > > So as the only person maintaining - I’d say go the path that is easiest for > > you. > > I definitely will if there isn't push back on doing it. > > Thx, > -- Scott > >
