Cycle5: Improving astropy vo and votable capabilities #500
+50
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Member
Author
|
thank you so much @ManonMarchand! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is proposal is very much a draft and will benefit from discussions at the upcoming IVOA interop.
Also, no language tuning was made, sending through the AI machinery could improve the fluff.
@tomdonaldson @andamian -- I mentioned 3 of us in the text as it's clear we cannot take on contracts so at best we can coordinate this project (by definition, if we do it well, it should not add much burden on the existing maintainers team).
Also, cc @ManonMarchand and @msdemlei, I hold on hope that you could take on the contract if it's selected, but either way, let's discuss it in Görlitz