-
Notifications
You must be signed in to change notification settings - Fork 668
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 NumFOCUS sponsorship (issue #2460) #2467
Conversation
So on the template for numfocus attribution there's a little thing that they use for automatic audits. This is in markdown, whereas our readme is rst, so it look like a quick rejig into markdown is required... unless anyone objects? |
Not that it adds much to the discussion, it is interesting that a thrawl through github doesn't seem to indicate any cases of this auditing tag being used anywhere (I was having a look through to see if anyone came up with an alternative for Considering this template is new as of last September, I assume this isn't something they have fully implemented yet? |
Codecov Report
@@ Coverage Diff @@
## develop #2467 +/- ##
===========================================
+ Coverage 90.21% 90.34% +0.13%
===========================================
Files 177 179 +2
Lines 22642 23813 +1171
Branches 2933 3010 +77
===========================================
+ Hits 20427 21515 +1088
- Misses 1616 1691 +75
- Partials 599 607 +8
Continue to review full report at Codecov.
|
Could rst comments be of any help? https://docutils.sourceforge.io/docs/user/rst/quickref.html#comments If NumFOCUS just search for the string, then it may be enough to have it appear in the readme somehow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Testing if I can fully review even if I am not a dev.
Raise an issue at https://github.com/numfocus/templates/issues and ask for how to use in rst ? |
we are still missing some affiliation links
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Not sure if they want to see it on the site and then give use the sponsorship link or if we should wait.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wait with merge until we have the sponsorship link
I'll add the link from #2506 |
- moved NumFOCUS to top (as in template https://github.com/numfocus/templates/blob/master/fiscal-sponsor-readme-attribution.md) - add link to Code of Conduct (as in template) - fixed link to governance (use website Governance section instead of repo file) - add NF donation link from #2506 - close #2506 - updated high level description
I added the links and did some general editing. However, two things are still bothering me
|
Maybe we should just ask numfocus? |
- added the audit anchor as a reST link target as suggested by @jbarnoud - added alt tag for NumFOCUS image
Yes, will do. (EDIT) after merging this one. We can fix it up once we know how. I just don't want to wait around. |
Hm, apparently we ought to have a GOVERNANCE.md in the repo, even if it's only a stub, so will add one...
|
This file is required as a NumFOCUS sponsored project.
) Fixes #2647, towards #2553 ## Work done in this PR Elements are now read from PDB files and added to the elements attribute of the universe. This is currently only done in cases where all elements in the PDB file are valid (i.e. match IUPAC naming). In all other cases a user warning is thrown and the elements are not assigned. ## Files changed - MDAnalysis/topology/PDBParser.py - MDAnalysisTests/topology/test_pdb.py - CHANGELOG and AUTHORS (new contributor)
Fixes #2460
Changes made in this Pull Request:
PR Checklist