I admit I expected a bit of a discussion. Instead I got an invite to
current repository, which I accepted and I am able to merge pull requests.
So if you have some change with high priority, please ping me by
@pemensik tag in pull request comment. I will look at them and merge
them if they seem good. I will try to make a review where I would not be
sure. I guess I will merge translations right away.
I will try to process pull open pull requests, but because I am not too
familiar with the avahi code, it might make some time.
On 11/23/22 17:15, Petr Menšík wrote:
Hi Adrian,
I understand you haven't found enough time recently. I think it should
not be a single man project, be it Trent, Adrian, me or any other
single person. I think the more important is silence about any further
actions. What have been told between you and Trent has no public
statement or even a comment. Except very few comments on github,
almost nothing is known. Whatever you talked about has stayed behind
the scene.
I volunteer to help when I can. I think others offered too. But I have
not seen any hint, how I can prove to be worthy enough. I have been
given co-maintainer rights on Fedora's avahi package [1], not sure it
means something here. I made few pull requests with proposed fixes to
prove I understand some code basics. It is up to Trent to decide what
would be enough. If anyone else volunteers, how he/she should prove
himself/herself worthy?
I am not sure if Adrian already has rights to make modifications. It
is the git repository, has a history. I don't think it is necessary to
have rights to delete existing commits (force push). All I ask to say
what a person can to to become at least candidate maintainer. More
brains knows more together. It is obvious the time was scarce. I think
we can afford doing some mistakes instead of a deadly silence.
Please Trent, admit you will not have time for avahi soon and allow
someone other access. At least say what would make you trust someone
to have that. If we can make something to choose a good candidate,
what would that be? I think it would help if someone just created
labels and assigned different labels to existing issues and bugs for a
start. But that would help only if they were reviewed later by
someone. I am not sure Trent would have time for that. It would be
best if he proposed any plan himself.
Cheers,
Petr
1. https://src.fedoraproject.org/rpms/avahi
On 21. 11. 22 3:22, Adrian Cable wrote:
Hi Petr – thanks for reaching out.
Unfortunately, despite best intentions personal and work situations
have conspired to result in me having less time available for
additional activities (like working on Avahi) than I thought I would
a couple of months ago. I did have a good call with Trent back then
and it seems the limitation here is time rather than willingness.
Although this is really Trent’s decision and not my own, I would be
very supportive of new maintainers and/or a new organization to
enable Avahi to move forward.
-Adrian
*From: *Petr Menšík <pemen...@redhat.com>
*Date: *Sunday, November 20, 2022 at 4:41 PM
*To: *Trent Lloyd <tr...@lloyd.id.au>
*Cc: *Avahi ML <avahi@lists.freedesktop.org>, Adrian Cable
<adrian.ca...@gmail.com>
*Subject: *Commit and issue editing rights to Avahi repositories
Hello Trent, Hi Adrian.
I understand you are busy elsewhere and your focus is not on Avahi
project. But there have been multiple people willing to help on issue
#388 [1], without any concrete reply. I would like to ask you here,
whether you would allow any other contributors a commit access to the
repository. If you have some conditions which a potential
co-maintainer has to meet, please say them aloud.
You said your are open to maintainers joining on, but haven't said
nothing about your conditions.
Both Debian and Fedora has not a short list of downstream patches
applied on top of the last Avahi release. Many issues are open and
not being worked on, pull requests are not commented on in months. I
think the offer of *Neustradamus* to move to an organization is
reasonable. Not sure if there is another way to add commit rights to
your personal repository.
We can fork your project and start merging those requests manually.
But it would be much easier if you could transfer existing issues and
pull requests to a common organization and give permissions. If you
want to be organization owner, fine, just say it. Certainly you
should be administrator there, your expertise is vital. It seems a
personal repository still allows some ways to collaborate [2] with
more people.
I think now we are missing mainly two things:
- a person with time to read issues and pull requests and categorize
them. Labels are a good thing and it would be nice to prioritize
bugs, grouping important and unimportant.
- a person with the language understanding and commit access able to
merge
I messaged Adrian some time ago. He mentioned you talked, but no
change is visible to us. Still not a single comment, commit or a
label change. I have talked with Till Kamppeter on Ubuntu Summit in
Prague, he said you are just too busy and likely it would not change
anytime soon.
Would you be able to give some access to other collaborators before
the end of this year? I am willing to maintain a fork and invite more
people after the next year unless something changes. I think the
existing code is fixable, it just needs more eyes and hands. If you
have any vision how to allow that, please share it.
Kind Regards,
Petr
[1] https://github.com/lathiat/avahi/issues/388
[2]
https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository
--
Petr Menšík
Software Engineer, RHEL
Red Hat,https://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
--
Petr Menšík
Software Engineer, RHEL
Red Hat,http://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
--
Petr Menšík
Software Engineer, RHEL
Red Hat,https://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
