Handling of remaining issues from python-acoustics

[roteiro]

Hi!
I'm a regular and happy user of python-acoustics. Thank you for continuing the work of python-acoustics and the modernization with uv and mkdocs.

There a some open issues on the original repo (e.g. python-acoustics#210 python-acoustics#248) which have not been solved yet. I would you like to discuss them and work on them. Would you like me to create new issues for them on this repo as a fresh start and just link to the original discussion or can they be transferred to this fork and continued?

Your fork seems to be the most (and maybe only) active one. I had a quick look at the download stats of the acoustics package and the acoustic-toolbox package, the recent download count for the original package is still an order of magnitude higher. In my opinion it could be beneficial if there was a note on the original and now archived repo that development continues here to attract new users and especially contributors. Are you in contact with its maintainer https://github.com/FRidh?

[Nitnelav]

Hello !

Yes , we should look at the issues opened in python-acoustics at some point, and cherry pick what we think is still relevant. I think opening new issues here, linking back to the original issues, is the best approach. You are of course welcome to contribute through pull requests as well.

We got in touch with @FRidh to discuss forking vs. continuing python-acoustics. Indeed, it would be nice to have a link to our fork from python-acoustics for visibility, especially if we're the only ones working on it. but it's ok either way.

[MitchellAcoustics]

I agree with @Nitnelav about the issues, would be good to pull over any relevant open ones to start tracking.

Personally I was waiting until we got all set up and had pushed a meaningful update before trying to publicise or say this is the recommended fork. I thought we should give people a reason to believe we're actually serious about maintaining it. For my own use, resolving the documentation and deprecation warnings was important before switching over to acoustic toolbox.

I think now we've taken care of the initial setup so I'm happy to start putting it up as the continuation! We should reach out again to fridh to ask if he'll add a note to the python acoustics readme.