-
Notifications
You must be signed in to change notification settings - Fork 780
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is LittleProxy not maintained anymore? #424
Comments
Hi @Invodv, I think it would be a great idea if you can do it, better than asking to do this to anyone else :) All the best! |
Hi @marcelobusico, Thanks for the quick reply. |
I can step up as a fork maintainer if nobody else wants the job. I'm very comfortable with Java, but my HTTP expertise is limited and I don't have a lot of free time. So I'd really like to give other people the chance to go first. |
I have contacted @adamfisk on twitter. Let's hope he's going to find some time to think about future of littleproxy. |
Idk |
@michalsvec Any news? |
@patricker nope, unfortunately not. |
I just emailed him to see if we could elect a new maintainer. |
Sadly no. At this point it seems like we may have to fork the project. What does everyone else think? |
Let's fork the project then. Who will maintain it? I'm available if nobody else wants the job. If anyone else is interested in doing it, please speak up. |
@mrog I'll gladly follow your fork. |
I just uploaded my fork https://github.com/JockX/LittleProxy to maven central under coordinates:
It's not that I feel like taking over the project and become a new maintainer, but since I really needed that guava update, here it is. Maybe someone will benefit. |
@JockX Those look like good changes. This is the last call for volunteer maintainers before I take the job myself. If nobody speaks up in the next couple of days, I'll begin preparations to maintain my own fork. |
@mrog If don't know if you can add a second maintainer to the project but I would be happy to help out. I manage a fairly large installation of LittleProxy and I would love to see the project move forward. |
@caseyoneill I would welcome that. I can add you as a collaborator. |
Some one robbed me of my original account.the cloned account cant do
anything. I fought like you don't wAnna know to get back my 1st grandsons
birth video. I am alive and been violated and I can't seam to get anyone
to believe I'm alive. Email again ill send cell phone # live chat show all
proof evidence and lot lots more. Because I will not be told im dead while
I'm truly alive . ill fight to the end. Or until whoever stole that
account. Had more than ever anyone could imagine.
Meredith Ann Little.
…On Mon, Feb 4, 2019, 6:53 PM mrog ***@***.*** wrote:
Any updates?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#424 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ab8OFP-S63bjWMNFQNT78u6Cm1QYIid9ks5vKMftgaJpZM4YOLK2>
.
|
My fork is at https://github.com/mrog/LittleProxy. @JockX I incorporated your library version changes. @caseyoneill I made you a collaborator. I bumped the version to 2.0.0. This seems fitting for a couple of reasons. First, it will make it easy for people to distinguish between my fork and the original version. Second, I made a breaking change. I updated the ChainedProxyManager class so it can use information about the clients when deciding how to handle requests. New issues can be viewed/filed at https://github.com/mrog/LittleProxy/issues. |
I just completed my first release to Maven Central. I also created a Google Group for discussions and questions. https://github.com/mrog/LittleProxy
https://groups.google.com/forum/#!forum/littleproxy2 Please join the group and help keep the project alive! |
We have joined mrog on his LittleProxy fork and also moved our active fork of the BrowserMob Proxy, which we renamed to the BrowserUp Proxy to point to that LittleProxy fork. |
Any news? I found some bug in production and want to PR to LittleProxy |
@linking12 I think it makes sense to switch to the fork and introduce the fix there: https://github.com/mrog/LittleProxy |
The latest fork which is currently supported is https://github.com/LittleProxy/LittleProxy |
The last contributions from the repository owner @adamfisk go back to Sep 25, 2017. Since then, no change has been committed to master, no pull request has been merged.
Does someone have a fork that they plan to maintain?
The text was updated successfully, but these errors were encountered: