Comments (4)
I'm not 100% sure on this but I think maybe it's best for this to be subsumed into #74 ? In my review there I suggested that this guide is better done as a unified "for reviewers and contributors" document, as it's better if everyone's on as equal footing as possible.
But it might be that this contributor guide should have more detail like "here's how to do a rebase", while #74 is more high-level? So then the prerequisite to the guide this is about would be #74, but it would have more detail?
from style-guides.
As a reminder: addressing this should also address #74 (comment) and one of the links in #74. That is, the code review guide should be referenced from any guide that addresses this issue, and the code guide links should also be updated to point to this issue's guide.
from style-guides.
I am not opposed for this issue to be addressed as a follow up of #74 on that same page. @brechmos-stsci , what do you think?
from style-guides.
I, personally, think the style guides should remain "on topic" and "short". That way people (like me) will read them :). So, given that, I think these two should be separate.
from style-guides.
Related Issues (20)
- Web style guide should link to branding page
- Add astroconda to release guide
- Microservices style guide HOT 1
- Testing style guide: Discourage Travis CI, find replacement? HOT 2
- Add information about how to cite software HOT 1
- Notebook style guide: Footer instruction confusing HOT 1
- Review security style guide HOT 2
- Community Name for Zenodo Software DOI? HOT 1
- Detailed Zenodo instructions for new software DOI? HOT 1
- This thing needs to be managed and advertised HOT 2
- Present this in TIPS and EngOps in 2020 HOT 1
- Badge for packages that follow style guide HOT 2
- Distribute flyers around STScI HOT 1
- Update python packaging information
- Organize a hack day in 2020 HOT 1
- Create a ROADMAP
- Ditch Travis CI as a recommended solution HOT 4
- Update Master Branch
- Notebook accessibility from Scipy 2023
- Adopt the Scientific Python Developers Guide
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from style-guides.