[H-source-users] h-client maintenance

[bill-auger]

as a reminder, the last discussion there was regarding the
client, ended with the decision to merge the h-source and
h-client teams - i do not mind keeping them separate either; but
that is not what we decided - i kept the client code on pagure,
because there is no repo setup for it under the h-source
project; and because we never decided which bug tracker to use,
or if either project was going to remain on savannah, or be
moved to another forge

there was a ticket opened last week, suggesting to delete the
h-client savannah project, probably because the OP read the
mailing list discussions - there is already a ticket for that
with the savannah admins - it was left pending, until the
project admin gave approval; but as far as i know, that did not
happen either - now i see that yuchen has been made admin of the
h-client project; and is suggesting to do the opposite, to keep
the client code on savannah and as a separate project, and has
assigned a new member to that team

new people wanting to join the team is great - i suggested to
apteryx last week, to consider joining the team; but i really
must object to these happenings without discussion

i dont remember any discussion that yuchen would be admin of the
server project either - the only public discussion WRT project
management was in 2019, when damien and i joined the project to
revive it, as the only active members at the time - damien
agreed to maintain the server, and i agreed to maintain the
client; and antonio gave his approval on the mailing list

then last year, yuchen joined for an intern stint with the FSF,
to help damien port the server to PHP7 - at the time, i expected
that to be temporary, as internships usually are; and no one
expected yuchen to have any involvement with the client, because
the intern gig was for the server project - i did everything
possible to the client then, to prepare it for the future; and
had to shelve it until the server work was completed

then somehow between then and now, yuchen became the maintainer
of both projects, without ever looking at the client code, and
after we decided to disband the client project - i am a bit
confused, to say the least

most of the client concerns were left undecided; and that was
only because of the plan to merge the two projects - the
simplest plan was always to leave the organization as it was -
if we had not intended to merge the two projects, the website
could have simply been changed to point people to pagure for the
client code - i was the only one who actually needed to make any
important decisions about the client project; yet i let it
remain in this state of indecision, in the spirit of cooperation

in any case, there was no reason for yuchen to want to admin the
h-client savannah project, which was decided to be closed, there
was no reason for antonio to put a new maintainer before me, and
that happened without discussion, contrary to what actually was
discussed

i am the only person who has touched the h-client in 5 years, i
am the only one who has been publicly endorsed as its
maintainer, and i have many hours invested into it - if the
h-client project is to remain separate, and if anyone besides
antonio should be its admin, then clearly i should have that
role - i am probably going to need it in order to sign and
publish releases anyways, if the project is going to stay on
savannah

but as the only person working on the code-base and giving
user-support, i definitely have not consented to using savannah -
i would prefer not to; because i can not reply to tickets by
email - pagure has suited my purposes well for years; but i would
be content with any forge that i do not need a web browser to
access - if apteryx wants to join the team and do a significant
amount of the work, then whichever forge we want to use, is still
negotiable AFAIAC