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

Add PyAutoGalaxy as AstroPy Affiliated Package #491

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

Jammy2211
Copy link

We are requesting affiliated status for our package PyAutoGalaxy :).

Copy link
Contributor

@dhomeier dhomeier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for proposing this package as an affiliated package to the Astropy project. I am presently searching for a reviewer to provide a detailed review; at this point I am only asking to make the suggested formal/formatting adjustments to the registry.

affiliated/registry.json Outdated Show resolved Hide resolved
@pllim pllim self-assigned this May 18, 2022
@pllim
Copy link
Member

pllim commented Jun 2, 2022

Thank you for proposing this package as an affiliated package! I'm happy to confirm that your package is now under review and we'll post the results of the review here and on the mailing list.

@pllim
Copy link
Member

pllim commented Aug 15, 2022

Hello and thanks for your patience! As part of the review process, I am opening some issues and PRs to your repository. Let's discuss some specific stuff over there.

@pllim
Copy link
Member

pllim commented Aug 15, 2022

Hello again! Please look at the PyAutoGalaxy issues/PRs (also linked to this issue here). I feel like we should discuss and hopefully resolve most of them before we move the process forward. Thank you for your cooperation.

@Jammy2211
Copy link
Author

Thanks for the review so far!

I have fellowship deadlines due mid-Sept so am taking a step away from development for most of the next month, but will try and respond to things when I have a spare moment. However, you can probably expect me to respond in full after September 13!

@pllim
Copy link
Member

pllim commented Aug 18, 2022

Thanks for the update, @Jammy2211 . No rush on my end. Good luck with your application!

@pllim
Copy link
Member

pllim commented Feb 7, 2024

Hello, @Jammy2211 . It has been over a year, so I am trying to follow-up and see how we can push this forward.

As @dhomeier put it: As outlined below, we have been in the middle of migrating our Affiliated Package review process to a new system in partnership with pyOpenSci now described in APE 22, and experienced some unexpected delays in that transition.

What this means for all packages that have applied for Affiliated status before APE 22 was passed is, that we still offer you to continue the package review in the previous mode, but also want to give you the option (and encourage you) to apply through the pyOpenSci page instead.
Some key differences this would bring about are

Please comment here on your preferences, or if you need additional information on this process.
Thanks!

@Jammy2211
Copy link
Author

Hi,

My apologies for how long this has taken!

Other work projects pretty much took over my life, but from March 1sr I start a new position where I'll actually have the time to work on the software again.

So, I'll get the process moving from March, and would be happy to go via the new process :). If getting that started now means the feedback will be in place for March, even better :)

@pllim
Copy link
Member

pllim commented Feb 8, 2024

@Jammy2211 , congrats on your new job! We are currently collecting interest and have no formal timeline. But thanks for your response. I do think the process would be faster this time under the partnership with pyOpenSci. I will update you when we are ready to move forward. Thank you for your patience!

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

Successfully merging this pull request may close these issues.

3 participants