Skip to content

Maintenance status #8

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

Closed
flying-sheep opened this issue Jun 26, 2023 · 19 comments
Closed

Maintenance status #8

flying-sheep opened this issue Jun 26, 2023 · 19 comments

Comments

@flying-sheep
Copy link
Collaborator

flying-sheep commented Jun 26, 2023

Hi, is this still maintained?

We’d be interested to include something like it into scanpy.

In case you’re no longer interested in maintenance, maybe we could transfer this project to scverse and take over, publish it to PyPI, …

@frankier
Copy link
Collaborator

Hi @flying-sheep ! Thanks for getting in contact about this.

It's not currently maintained, no. On the other hand I did start doing the work to try and polish this a bit more. I would therefore like to make a counter-proposal.

My original intention before getting distracted by other work was to include this scikit-learn-contrib. So, what if I try to go ahead with transferring it there? I would then be happy to add you onto the relevant scikit-learn-contrib team. Would this work? From my perspective it could be better to keep this in an org with a general emphasis if possible.

@flying-sheep
Copy link
Collaborator Author

That sounds like a great idea! What would be needed to transfer it there?

@frankier
Copy link
Collaborator

Hi! So I am a bit time poor at the moment -- I'm unplugging for a couple of weeks starting tomorrow. It looks like one of the requirements is to setup CI. I tried this but https://github.com/frankier/sklearn-ann/actions/runs/5412841941 .-- unfortunately FAISS has changed its interface. I will fix this and open an issue to move to sklearn contrib when I get back. I understand this might not fit your own timetable, but maybe we can still make it work? Let me know either way.

@flying-sheep
Copy link
Collaborator Author

We would prefer that to happen faster, but not at the expense of your free time of course.

I’m good at setting up CI and things, maybe I’ll just do that.

@frankier
Copy link
Collaborator

I recognise your handle, so I have added you if you want to fix up the CI to expedite things, I think I can open the issue on sklearn contrib before the 12th, otherwise I will fix ci and do it then. Phone only atm

@flying-sheep
Copy link
Collaborator Author

flying-sheep commented Jun 30, 2023

Thank you! And now I hope you don’t worry and enjoy your away time!

@flying-sheep
Copy link
Collaborator Author

flying-sheep commented Jul 3, 2023

OK, decisions. I like do do things the following way, in increasing order of opinion

  • Ruff instead of flake8 for faster style checks and fixes
  • pre-commit for formatting and style checks (no black or ruff in our dependencies)
    • pre-commit.ci for running those checks (auto-update PRs from pre-commit.ci, and one can quickly see if a PR failure is tests or style because there’s two checks instead of one)
  • Hatch instead of poetry for PEP 621 support (standardized pyproject.toml layout instead of poetry specific)
  • tests outside of the source directory and package in src directory, as recommended by Pytest
  • Squash & merge as only merge option on GitHub, branch protection

So yeah, I think Ruff is just a straight upgrade, so I’m just going to do that one.

@frankier
Copy link
Collaborator

frankier commented Jul 3, 2023

All sounds fine to me!

@flying-sheep
Copy link
Collaborator Author

Great! Since I’m no admin, I can’t turn on pre-commit.ci integration, or “Squash & Merge”, …

Seems like the “don’t commit directly to the main branch” hook fails when run in GH actions. It should also work on pre-commit.ci:

grafik

@flying-sheep
Copy link
Collaborator Author

I also remembered another thing that would be great to enable:

@flying-sheep
Copy link
Collaborator Author

Hi! I hope your time unplugging was nice! Do you think we can proceed with this?

@frankier
Copy link
Collaborator

Just putting the hatch PR together now. Hold on a moment.

@frankier
Copy link
Collaborator

I've tried to get the ball rolling over at scikit-learn-contrib/scikit-learn-contrib#64

I think there might be some stuff to tighten up, but maybe now we can see how receptive the scikit-learn-contrib org is an what they think is most important to target.

@frankier
Copy link
Collaborator

frankier commented Aug 1, 2023

Looks like no response. Would it be useful to upload this package to pypi (under its current name) in the interim?

@flying-sheep
Copy link
Collaborator Author

Maybe we can get in touch with them some other way. It says it’s maintained by one person, @egy1st, who seems to be active on GitHub, but hasn’t merged anything into that repo in 9 months.

@egy1st, is it possible that you ask the scientific python community for some help with reviewing things and getting them in?

@egy1st
Copy link

egy1st commented Aug 1, 2023

@flying-sheep @frankier

When you mentioned receiving a message that the repo is maintained by @egy1st, I needed clarification because I am not a member of the scikit-learn-contrib community. I have contributed an algorithm called denmune to their repo at https://github.com/scikit-learn-contrib/denmune-clustering-algorithm. I am just a contributor, a maintainer but not an admin/member. Since I didn't receive any private messages as egy1st, what message were you referring to, and when you received it? I don't have any inside information beyond the public GitHub thread you shared, so I'm unsure what additional messages you mentioned."

@flying-sheep
Copy link
Collaborator Author

flying-sheep commented Aug 1, 2023

Hmm, maybe I read the wrong readme then, sorry. I now see that you’re simply the maintainer of the last package that got added. Sorry about the ping!

@frankier the people who are actually part of that org are here: https://github.com/orgs/scikit-learn-contrib/people maybe we can get in touch

@frankier
Copy link
Collaborator

frankier commented Aug 1, 2023

@adrinjalali Ping! Any info on what the next steps are to get this package added?

@adrinjalali
Copy link
Member

We'll respond on scikit-learn-contrib/scikit-learn-contrib#64, sorry the backlog is kinda long, but we'll get to it.

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