Skip to content
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

Open
lnvodv opened this issue Nov 5, 2018 · 22 comments
Open

Is LittleProxy not maintained anymore? #424

lnvodv opened this issue Nov 5, 2018 · 22 comments

Comments

@lnvodv
Copy link

lnvodv commented Nov 5, 2018

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?

@marcelobusico
Copy link

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!

@lnvodv
Copy link
Author

lnvodv commented Nov 5, 2018

Hi @marcelobusico,

Thanks for the quick reply.
I was not really asking for someone to do it, I rather wanted to know if there are people who already forked the repository with a view to maintaining their own version. If there are, then I would be glad to join them and possibly try to contribute.

@mrog
Copy link

mrog commented Nov 5, 2018

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.

@michalsvec
Copy link

I have contacted @adamfisk on twitter. Let's hope he's going to find some time to think about future of littleproxy.

@crazymaribell
Copy link

Idk

@patricker
Copy link

@michalsvec Any news?

@michalsvec
Copy link

@patricker nope, unfortunately not.

@caseyoneill
Copy link

I just emailed him to see if we could elect a new maintainer.

@caseyoneill
Copy link

Sadly no. At this point it seems like we may have to fork the project. What does everyone else think?

@mrog
Copy link

mrog commented Feb 5, 2019

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.

@lnvodv
Copy link
Author

lnvodv commented Feb 5, 2019

@mrog I'll gladly follow your fork.

@pietrygamat
Copy link

I just uploaded my fork https://github.com/JockX/LittleProxy to maven central under coordinates:

<dependency>
   <groupId>net.jockx</groupId>
   <artifactId>littleproxy</artifactId>
   <version>1.1.3</version>
</dependency>

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.

@mrog
Copy link

mrog commented Feb 6, 2019

@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.

@caseyoneill
Copy link

@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.

@mrog
Copy link

mrog commented Feb 6, 2019

@caseyoneill I would welcome that. I can add you as a collaborator.

@crazymaribell
Copy link

crazymaribell commented Feb 7, 2019 via email

@mrog
Copy link

mrog commented Feb 11, 2019

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.

@mrog
Copy link

mrog commented Mar 2, 2019

I just completed my first release to Maven Central. I also created a Google Group for discussions and questions.

https://github.com/mrog/LittleProxy

<dependency>
    <groupId>xyz.rogfam</groupId>
    <artifactId>littleproxy</artifactId>
    <version>2.0.0-beta-1</version>
</dependency>

https://groups.google.com/forum/#!forum/littleproxy2

Please join the group and help keep the project alive!

@ericbeland
Copy link

ericbeland commented May 2, 2019

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.

@linking12
Copy link

Any news?

I found some bug in production and want to PR to LittleProxy

@valfirst
Copy link

@linking12 I think it makes sense to switch to the fork and introduce the fix there: https://github.com/mrog/LittleProxy

@asolntsev
Copy link

The latest fork which is currently supported is https://github.com/LittleProxy/LittleProxy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests