Project Needs Maintainers #139
Comments
|
I share your point of view. Tho the truth is this project needs to be re-written in a more modern language (such as Python for example that might be great for community contributions). Because today almost nobody knows how to code in Perl. |
|
in my fork i have tried to add all the pull requests into one tree nothing more but i alredy switched to aptly for the mirroring. |
|
@Stifler6996 if you don't believe it, it's fine then ;) ps: inform yourself on Docker |
|
@bholtsclaw are you available to share maintainership with people like geosone or Stifler6969? Re: docker, it seems to me that's a great improvement but should be provided as optional and contributed to the same tree. |
|
🚧 Is this repo looking for support? |
|
? The readme-file was updated 14 months ago with: |
|
I would love to see the official repo back again - there are a lot of working versions out there - in my company I implemented the version from @Stifler6996 (https://github.com/Stifler6996/apt-mirror) which includes all the fixes I needed to fork the repos for our users. Is there a way to get the rights on this project to subscribe a new maintainer or contact the official persons? The problem is that the official package for the ubuntu distribution is also built from this repo - https://packages.ubuntu.com/source/focal/apt-mirror. If we could not get this repo back in activity maybe I could ask the MOTU people to use a different repo with a bug report for the package. |
|
This guy is the current maintainer: https://twitter.com/imbrandon . I pinged him on github up this thread, but no reply. Does anybody have a twitter account to maybe try him on there? |
|
The twitter link looked normal to me. But no updates since 2019. |
So you know, I don't know what you are talking about here at all. |
|
At least, pull requests #120 and #127 should be merged as soon as possible, to keep this repo alive. |
|
Thanks for checking in on this. The way I got in contact with Brandon was at https://www.facebook.com/brandon.holtsclaw/ . He's the only one with access to this repository and says he would like to pass it on.
|
|
Any news about Brandon giving you access to the repo ? |
|
No reply from Brandon since my last comment. Maybe he lost access to his facebook account ?? Could something strange be going on? @Stifler6996, I saw you say "I looked at the twitter link, all I can say is I hope all is well with him and his family.", and the last tweet I'm seeing from Brandon is this one:
which doesn't indicate that anything is wrong, to me. Is that the same tweet you are responding to? He has recent Facebook posts and I sent him a facebook message this morning:
|
|
Is Brandon really the only one who can grant additional people access? I've seen at https://github.com/apt-mirror that also @bdrung and @jbouse are in the apt-mirror group. Maybe one of those has enough power? |
|
What is being asked for? I don't have administrative access to the
repository if that is what you're asking.
…On Fri, Jan 29, 2021 at 11:17 AM Thomas Braun ***@***.***> wrote:
Is Brandon really the only one who can grant additional people access?
I've seen at https://github.com/apt-mirror that also @bdrung
<https://github.com/bdrung> and @jbouse <https://github.com/jbouse> are
in the apt-mirror group. Maybe one of those has enough power?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#139 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAKHHQUJNMDOYADPGRAUCLS4LNRPANCNFSM4QHFHDLA>
.
|
|
@jbouse yes that was the question. Thanks for confirming. |
|
what about creating new repo? I simply merge what I thought would be usefull PRs. |
|
Is the mirror at https://github.com/Stifler6996/apt-mirror a suitable new repo? @Stifler6996 what was your reason for inferring that Brandon was going through some tough times? Anybody else: please feel free to reach out further to Brandon, the maintainer. I haven't heard more myself and have been doing other things. Often maintainers just need some reminders to check in on old projects. |
|
Stifler6996/apt-mirror is indeed the most suitable repo for now |
|
28/8, I sent mail to [email protected], no answer yet. |
|
any update on this matter ? |
|
Any news? Would it maybe be better to move forward with one of the forks, if no-one can get hold of the maintainer of the original repo? |
|
yes, the state of this issue is basically a request from visitors to do one or more of:
I have trouble using the internet and don't understand why I would get confirmation from brandon without followup, or what stifler6969 was responding to when they looked at the twitter link in september 2020. |
|
@xloem IMO it would be better at this point to consider this repo abandoned and move forward with one of the forks (probably @Stifler6996's). |
|
meanwhile, |
|
@steamboatid and @Stifler6996 |
Hello @Palando, |
Definitely let me know if you need help on reviewing PRs. |
|
@steamboatid I have begun reviewing open PRs and should hopefully get through them all in the coming weeks. @jbouse I would need at least write or maintain access in order to begin associating the approved PRs with corresponding issues. In the meantime I will continue to provided feedback on any PRs that request a review from apt-mirror/reviewers. Thanks for your patience! |
|
I just made it back to Vancouver this morning after being at sea for a
week. I won't have a computer until I get home Monday evening, so I'll have
a look at permissions when I'm finally home.
…On Sun, Jul 3, 2022, 13:41 OccamsReiza ***@***.***> wrote:
@steamboatid <https://github.com/steamboatid> I have begun reviewing open
PRs and should hopefully get through them all in the coming weeks. @jbouse
<https://github.com/jbouse> I would need at least write or maintain
access in order to begin associating the approved PRs with corresponding
issues. In the meantime I will continue to provided feedback on any PRs
that request a review from apt-mirror/reviewers. Thanks for your patience!
—
Reply to this email directly, view it on GitHub
<#139 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAKHHTNHTTKRV27KKRDQPDVSH3ITANCNFSM4QHFHDLA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@SupaHiro, I've updated @apt-mirror/reviewers to Again, if people are looking to help and want to aid in reviewing PRs feel free to step up. There is a backlog, and it will significantly help get through it. I would also like to see some ways to have automated testing that could be done on commit that would also aid in speeding up acceptance of PRs while ensuring we don't have any regressions. |
|
Just in case any interested I started I used |
|
@nE0sIghT Perfect. Rewriting the tool in a better language like Python, Go or Rust has been on my wishlist for years. apt-mirror2 is a good name. In case of a feature parity dropping this Perl implementation and renaming your rewrite to apt-mirror would be fine IMO. |
|
@bdrung && @nE0sIghT , I'm definitely open to migrating to a python a implementation. Ideally I would prefer to cut at least one more release after reviewing #184 and #185. @rockyluke maybe we could partner on getting this release out? @chutzimir after we create a final perl release would you be interested in working with me to ensure apt-mirror2 parity? |
I believe that all |
|
I just came across this thread (ironically in the process of fixing some issues with my local apt-mirror usage) I use apt-mirror as my primary method of package access for Debian and would be sad to see the demise of the current version. I'd be happy to get involved with maintenance or take over the Perl version in parallel with apt-mirror2 as required. |
Ready to help! |
|
@jbouse When you get a chance would you be able to add @rockyluke to @apt-mirror/reviewers ? |
Hey @clarkema hoping to understand your use case a bit more. Is your concern that moving to a debian package that would require python3 instead of perl would be incompatible with your current system? |
|
FYI I filled ITP [1] and RFS [2] issues to include apt-mirror2 [3] in the Debian. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080273 |
|
To clarify, @clarkema said they had time and interest in helping maintain the Perl version here. It is also great there is a Python port elsewhere. |
|
Thank you @xloem , I've reached out to @clarkema to confirm interest. If so I will work with @jbouse to get @rockyluke and @clarkema added as additional maintainers! |
|
@SupaHiro I haven't seen any contact other than the above mention, so apologies if I'm missed something. Still happy to be involved though. |
That is because I'm extremely busy with a full-time job, starting two personal businesses, serving on the board of directors for one non-profit, serving on a planning committee for another non-profit, and having had my development PC crash. I have only had a little spare time. So you haven't missed anything; I've just been busy. |
|
@clarkema There's probably someone on linkedin wondering who this crazy person is :P No worries. I've added you to the project. Welcome! |
|
@Stifler6996 seems deleted his account? |
Did anyone fork his fork before it was deleted? Is there a good alternative? |
This fork contains the latest commint of Stifler996's fork. |
and others
I noticed this valuable project is without maintainers.
Is anybody able to step up to this task? Alternatively I propose to either wikify the project so anybody can maintain, or reach out to PR contributors to step up (or both).
I noticed there are a lot of forks with activity, some of the owners are @geosone, @defnn, @bryse-dev, @Stifler6996, @chutzimir, @flavienbwk .
When PRs are no longer merged, projects tend to scatter into diverging forks with none of the bugfixing work consolidated, and a lot of duplicated effort. There are enough contributors here to find suitable maintenance effort somewhere.
The text was updated successfully, but these errors were encountered: