Update + status on repository

[chendaniely]

Hi everyone:

I'm going to try to consolidate the messages from a bunch of github issues into this one issue + response.
So far the ones i've seen are:

• #27 - mypy fixup, adds to #24 - unblocks #31 #32
• New Release? #31 (comment)
• PEP 541 Request: pyprojroot pypi/support#2610

First, applogies 🙇 , I actually didn't realize how much potential traction this project may have started, and is my fault for dropping the ball on that. I'm just able to catch up on on a bunch of things from the last 2 years since I've defended my dissertation, started 2 jobs, and moved countries.

GitHub pings are something I don't really see becuase all my important github work and communications happen over slack channels, or even emails. Also, a lot of github pings come from my own students, and are mostly from teaching examples that usually don't prompt me to anything urgent.

What I'm goign to be doing the next few week is merge in all the PRs that don't have any major merge conflicts working. What ended up happening in the past was I accepcted a good feature into the project that worked with a bunch of type hints and unit tests that I don't really know how to work with, and it really broke a lot of my own maintence of the project. I think #32 just fixed that so thank you.

Moving forward, I might need to just work on getting all the incoming featured merged in without worrying about the unit tests, and slowly work on figuring that part out on my own. There are a few things that I would like to do with this project.

There are a few conferences I'm planning to attend with sprints that this project seems good for (PyCascades, PyCon, SciPy). And also it would be really nice to revisit #14 and actually get this project published through PyOpenSci, now that Leah is full time on the organization.
I'll try to track down all the people with forks and imprrovements over the the next few weeks and invite them to PR back up stream so we can all be on the authorship when the proposal to PyOpenSci goes in.

I'll post more in this issue as things progress along.
If you need to reach out to me my gmail account is the same as this username (and should be able to be tracked in the commit history?)

• Triage Issues + Current PRs

• See what state would the repostiory need to be in for PyCascades Sprint March 20th.

• Dan

[chendaniely]

@achimgaedke @jamesmyatt: if you would like to be added as a maintiner to the project please let me know. I'll try to see if there's a way to get more synchronous communication channel going as well.

[achimgaedke]

Thanks, @chendaniely and much appreciated. - I will close pypi/support#2610 - no longer required.

Yeah, it would be good to work out how - how far - we want to push the project forward.

• What are the short-term issues we'd like to fix for a version 0.3.0... (e.g next month)?
• What could be a longer-term future for this package (over several months)?

[achimgaedke]

I've worked on extending this project quite a bit more, ending up rewriting it totally - taking a lot of ideas from the issue tracker and inspiration from the TODOs in the source code. - Also trying to organise the code such that it meets different expectations:

• the users just using the here function
• the users expecting the interface of the R packages rprojroot, and here
• the users wanting to define/customise the criteria

A longer-term state of the project could be like this - https://github.com/achimgaedke/pyprojroot2/tree/pyprojroot2-rewrite

Read the code or just the README.

If anything of this is liked, I would find a way to migrate this into this repository in digestible steps.

[jamesmyatt]

HI @chendaniely . Thanks for following this up. I'm happy to be added as a maintainer. I don't expect to be as active as @achimgaedke , but I'll help out where I can.

I'm keen to see a v0.3.0 go out as soon as possible.

After that I'd like to see whatever updates/rewrites that are necessary to reach what I'll call "basic user experience equivalence" in the Python ecosystem compared with the rprojroot and here projects. As @achimgaedke says, users of the here function and the rprojroot functions have different expectations.

[chendaniely]

Thanks yall! Give me a day to look over stuff in the forked repos and get you all added.

I'm not personally attached to any of the code already in here. So even if a PR that re does everything is something that I'll consider.

I'll be able to circle back to this later tonight for me.

[achimgaedke]

For the short term:

• I've created consolidate dev #34 - containing code changes needed in my opinion for releasing 0.3.0, merging it into the dev branch
• that doesn't contain any changelog / README updates

[jamesmyatt]

@chendaniely , can you add @achimgaedke and me (@jamesmyatt) as maintainers of this repo, please?

[jamesmyatt]

@chendaniely , ping! It's been over a year now.