-
Notifications
You must be signed in to change notification settings - Fork 243
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
As a Blockstack team member, I’d like to see a process around code changes and deployment #383
Comments
Larry: "Make a list of things that team members expect of each other." |
We're going to make a series of checklists for PRs, etc. |
I started work on a sort of "Engineering Handbook" that includes some of the process things we've discussed over the past couple weeks along with some other thoughts. There's more that could go into this, but wanted to first get some early feedback. I'd imagine this will live as a markdown file in this repo that we can parse and display on our website. In the meantime, for comments, I've put it in paper: https://paper.dropbox.com/doc/Blockstack-Engineering-Handbook-iBF4toNn3vJLdmhON8fEp (anyone should be able to view this like - let me know if you have trouble) Would love your comments on what's there already and anything else that should be: @kantai @yknl @jackzampolin @guylepage3 @jcnelson |
Kicking this issue. I think everyone has liked the Engineering Handbook. Maybe we want to post this publicly and edit that copy as things change in the future. This repo could be a good home for that. What do you think @larrysalibra? |
As a Blockstack team member, I’d like to see a process around code changes and deployment.
The text was updated successfully, but these errors were encountered: