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

Fork of the project #227

Open
SMoraisAnsys opened this issue Feb 25, 2025 · 5 comments
Open

Fork of the project #227

SMoraisAnsys opened this issue Feb 25, 2025 · 5 comments

Comments

@SMoraisAnsys
Copy link

The pip-licenses project hasn't received any commit to the main branch since multiple months and multiple PRs have been opened in the mean time without being reviewed.

For those who would like to continue using this project, we have forked it and are considering integrating some of the already open pull requests. Our goal is to ensure continuity while incorporating relevant contributions.

Here is a link to the fork: https://github.com/ansys/pip-licenses

@stefan6419846
Copy link

Just as a side note: For similar reasons (long announced library functionality) I have been maintaining a fork of this repository for about 1.5 years already as well: https://github.com/stefan6419846/pip-licenses-lib This should include most of the relevant fixes as well, although it completely omits all rendering functionality.

@anmol-aidora
Copy link

We at Aidora have also created a fork: https://github.com/aidora-inc/pip-licenses

@GergelyKalmar
Copy link

Would it perhaps make sense to create a separate fork under a joint organization to which multiple contributors can commit? It seems there is enough interest, but right now the efforts are quite fragmented. Also, many of the forks don't seem to be on pypi, reducing their usefulness.

@stefan6419846
Copy link

In theory, this might be a possible solution, although the preferred solution should still be to keep the original repository alive - maybe by adding a collaborator. Otherwise, everyone has to replace their dependencies. (I am aware that myself having a fork on PyPI for quite some time now contradicts this a bit, but past development has shown that for some features integration into the CLI proved to be challenging.)

@GergelyKalmar
Copy link

Sure, if @raimon49 was kind enough to provide maintainer rights to someone else, I agree that it would be a better option.

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

4 participants