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 NumFOCUS sponsorship (issue #2460) #2467

Merged
merged 6 commits into from
Feb 5, 2020
Merged

Conversation

richardjgowers
Copy link
Member

Fixes #2460

Changes made in this Pull Request:

PR Checklist

  • Tests?
  • Docs?
  • CHANGELOG updated?
  • Issue raised/referenced?

@richardjgowers
Copy link
Member Author

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?

@IAlibay
Copy link
Member

IAlibay commented Jan 23, 2020

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 .rst files).

Considering this template is new as of last September, I assume this isn't something they have fully implemented yet?

@codecov
Copy link

codecov bot commented Jan 23, 2020

Codecov Report

Merging #2467 into develop will increase coverage by 0.13%.
The diff coverage is n/a.

Impacted file tree graph

@@             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
Impacted Files Coverage Δ
package/MDAnalysis/core/_get_readers.py 96.29% <0%> (-3.71%) ⬇️
package/MDAnalysis/core/topologyattrs.py 97.4% <0%> (-0.72%) ⬇️
package/MDAnalysis/core/topologyobjects.py 97.87% <0%> (-0.64%) ⬇️
coordinates/base.py 94.74% <0%> (-0.4%) ⬇️
package/MDAnalysis/topology/__init__.py 100% <0%> (ø) ⬆️
package/MDAnalysis/topology/tables.py 100% <0%> (ø) ⬆️
package/MDAnalysis/coordinates/__init__.py 100% <0%> (ø) ⬆️
topology/__init__.py 100% <0%> (ø) ⬆️
coordinates/__init__.py 100% <0%> (ø) ⬆️
package/MDAnalysis/coordinates/ParmEd.py 82.84% <0%> (ø)
... and 8 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 66f3ac8...27e48a7. Read the comment docs.

@jbarnoud
Copy link
Contributor

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?

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.

Copy link

@orbeckstASU orbeckstASU left a 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.

@orbeckst
Copy link
Member

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?

Raise an issue at https://github.com/numfocus/templates/issues and ask for how to use in rst ?

@MDAnalysis MDAnalysis deleted a comment from orbeckstASU Jan 27, 2020
@MDAnalysis MDAnalysis deleted a comment from orbeckstASU Jan 27, 2020
@MDAnalysis MDAnalysis deleted a comment from orbeckstASU Jan 27, 2020
we are still missing some affiliation links
Copy link
Member

@orbeckst orbeckst left a 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.

README.rst Outdated Show resolved Hide resolved
Copy link
Member

@orbeckst orbeckst left a 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

@orbeckst
Copy link
Member

orbeckst commented Feb 5, 2020

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
@orbeckst orbeckst changed the title WIP: issue #2460 add NumFOCUS sponsorship (issue #2460) Feb 5, 2020
@orbeckst
Copy link
Member

orbeckst commented Feb 5, 2020

I added the links and did some general editing. However, two things are still bothering me

  • I am not sure that the resizing of the numfocus image actually works, at least not in the preview. According to the template it should be a height of 60px.
  • I don't know what to do with the magic markdown audit code [//]: # (numfocus-fiscal-sponsor-attribution) from the template.

@jbarnoud
Copy link
Contributor

jbarnoud commented Feb 5, 2020

I don't know what to do with the magic markdown audit code [//]: # (numfocus-fiscal-sponsor-attribution) from the template.

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
@orbeckst
Copy link
Member

orbeckst commented Feb 5, 2020

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.

@orbeckst
Copy link
Member

orbeckst commented Feb 5, 2020

Hm, apparently we ought to have a GOVERNANCE.md in the repo, even if it's only a stub, so will add one...

  • If your project has no GOVERNANCE.md at the root, then create a stub GOVERNANCE.md and include a link to your governance documentation or the appropriate parties to contact for more information.

This file is required as a NumFOCUS sponsored project.
@orbeckst orbeckst merged commit 009ec22 into develop Feb 5, 2020
@orbeckst orbeckst deleted the richardjgowers-patch-1 branch February 5, 2020 23:58
IAlibay pushed a commit that referenced this pull request Mar 30, 2020
)

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)
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.

indicate NF sponsorship
6 participants