<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> 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. <a class="moz-txt-link-freetext" href="https://src.fedoraproject.org/rpms/avahi">https://src.fedoraproject.org/rpms/avahi</a> <div class="moz-cite-prefix">On 21. 11. 22 3:22, Adrian Cable wrote: </div> <blockquote type="cite" cite="mid:SJ0PR22MB252613E0FAB49B1F968A4B0CF40A9@SJ0PR22MB2526.namprd22.prod.outlook.com"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style>@font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:11.0pt; font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;}pre {mso-style-priority:99; mso-style-link:"HTML Preformatted Char"; margin:0in; font-size:10.0pt; font-family:"Courier New";}span.HTMLPreformattedChar {mso-style-name:"HTML Preformatted Char"; mso-style-priority:99; mso-style-link:"HTML Preformatted"; font-family:"Consolas",serif;}span.EmailStyle22 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext;}.MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;}div.WordSection1 {page:WordSection1;}</style> <div class="WordSection1"> Hi Petr – thanks for reaching out.<o:p></o:p> <o:p> </o:p> 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.<o:p></o:p> <o:p> </o:p> -Adrian<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"> From: Petr Menšík <a class="moz-txt-link-rfc2396E" href="mailto:pemensik@redhat.com"><pemensik@redhat.com></a> Date: Sunday, November 20, 2022 at 4:41 PM To: Trent Lloyd <a class="moz-txt-link-rfc2396E" href="mailto:trent@lloyd.id.au"><trent@lloyd.id.au></a> Cc: Avahi ML <a class="moz-txt-link-rfc2396E" href="mailto:avahi@lists.freedesktop.org"><avahi@lists.freedesktop.org></a>, Adrian Cable <a class="moz-txt-link-rfc2396E" href="mailto:adrian.cable@gmail.com"><adrian.cable@gmail.com></a> Subject: Commit and issue editing rights to Avahi repositories<o:p></o:p> </div> Hello Trent, Hi Adrian.<o:p></o:p> 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.<o:p></o:p> You said your are open to maintainers joining on, but haven't said nothing about your conditions.<o:p></o:p> 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.<o:p></o:p> 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.<o:p></o:p> I think now we are missing mainly two things:<o:p></o:p> - 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<o:p></o:p> 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.<o:p></o:p> 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.<o:p></o:p> Kind Regards, Petr<o:p></o:p> [1] <a href="https://github.com/lathiat/avahi/issues/388" moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/lathiat/avahi/issues/388</a> [2] <a href="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" moz-do-not-send="true" class="moz-txt-link-freetext"> 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</a><o:p></o:p> <pre>-- <o:p></o:p></pre> <pre>Petr Menšík<o:p></o:p></pre> <pre>Software Engineer, RHEL<o:p></o:p></pre> <pre>Red Hat, <a href="https://www.redhat.com/" moz-do-not-send="true" class="moz-txt-link-freetext">https://www.redhat.com/</a><o:p></o:p></pre> <pre>PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB<o:p></o:p></pre> </div> </blockquote> <pre class="moz-signature" cols="72">-- Petr Menšík Software Engineer, RHEL Red Hat, <a class="moz-txt-link-freetext" href="http://www.redhat.com/">http://www.redhat.com/</a> PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB</pre> </body> </html>