Add PyPI deploy and metadata #46
Conversation
Codecov Report
@@ Coverage Diff @@
## master #46 +/- ##
=======================================
Coverage 72.12% 72.12%
=======================================
Files 29 29
Lines 696 696
=======================================
Hits 502 502
Misses 194 194 Continue to review full report at Codecov.
|
HealthyPear
moved this from In progress
to Review in progress
in Maintenance and computing performance
HealthyPear
moved this from Review in progress
to Reviewer approved
in Maintenance and computing performance
setup.cfg
Outdated
| @@ -1,12 +1,30 @@ | |||
| [metadata] | |||
| name = pyirf | |||
| description = Python IACT IRF builder, | |||
| description = A python library to calculate IACT IRFs and Sensitivities | |||
| url = https://github.com/cta-observatory/pyirf | |||
| author = CTA Consortium, Analysis and Simulation Working Group | |||
| author_email = thomas.vuillaume@lapp.in2p3.fr | |||
There was a problem hiding this comment.
I can sure be the contact person if there is no other email but I think we may change that as well 😅
aswg email?
There was a problem hiding this comment.
ups! I didn't see that...as far as I know we are allowed only 1 email here, right?
In that case the aswg one could be a good choice
though, I don't think I would ever email the author for a problem, I would go to the repo...
There was a problem hiding this comment.
Is the aswg mailing list writable to for non-members? If yes, It would probably be a good choice.
There was a problem hiding this comment.
No idea...perhaps @bregeon knows
There was a problem hiding this comment.
For non-members, emails are forwarded to the list moderators, i.e. the list owners, i.e. the ASWG coordinators.
Eventually, this package will be owned and maintained by CTAO (or related to), so the contact person shall be either CTAO User Support or the "official" contact working as IkC for CTAO.
I am not sure what the best temporary solution is, we shall discuss with CTAO Computing if they have a preference.
Let see if we can come up with some agreement today.
There was a problem hiding this comment.
Let's just add me or michele for now until there is a more official one
There was a problem hiding this comment.
For information, I have opened the issue with official instances, not only for pyIRF.
No description provided.