-
Notifications
You must be signed in to change notification settings - Fork 27
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
repostatus badge #41
Comments
hi @megies !! 👋 Thank you for the package submission AND for the issue here!! can you kindly help me understand:
we have so much content in our dev_guide and it's definitely a work in progress. i'm looking forward to addressing some of the bugs that you have found!! thank you again! we will have a look at your submission soon (maybe after i get back from agu however given how busy this conference has been :) |
1.It's mentioned here and I ended up on that page during filing that "new review" issue. You end up on that page following a link in the "new review issue" template:
2.The below badge is prominently advertized kind of as a requirement almost, but with it's static nature (e.g. hardcoded
No worries, no hurry at all. Just wanted to do it right away, lest I forget. You folks are definitely working on something that is needed and would be a very useful guidance for the hero code zoo out there, so.. happy to advertize your efforts. |
hi @megies my gosh this is a very old issue as well :) i am going to close this issue as we don't require / talk about that badge right now. we do intend to create a page on badges in our newer package guide! but that will be a WIP in the future. i hope you are well!! |
@all-contributors please add @megies for code, review |
I've put up a pull request to add @megies! 🎉 |
Having that repostatus badge is prominently advertized in the packaging guidelines that I got pointed at during the submission of package review "new issue" process. (pyOpenSci/software-submission/issues/16)
I didn't know it but from looking at the docs (their extra light gray text on white background is insanely hard to read) and if I'm not missing anything here (mostly due to skipping the longish text bits due to said tough readability), it seems to be static and not dynamically determined from any introspection on the target repo? If that is accurate, the point of that badge evades me. You can add an "active" badge to a repo and then bury it six feet under the next day and 20 years later people will be staring at an "active" badge in the README of a Python 3 project when Python 5 went EOL two weeks ago? 😜
The text was updated successfully, but these errors were encountered: