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

[blog] Write a post about Gatsby's mission/values #7761

Closed
jlengstorf opened this issue Aug 30, 2018 · 0 comments · Fixed by #7904
Closed

[blog] Write a post about Gatsby's mission/values #7761

jlengstorf opened this issue Aug 30, 2018 · 0 comments · Fixed by #7904
Assignees

Comments

@jlengstorf
Copy link
Contributor

During the Gatsby Inkteam gathering last week, we spent a lot of time thinking about, talking through, and writing down what kind of company we want to be.

Gatsby values on a whiteboard.

There were several requests in the thread for more details, so we should write up a blog post talking about how we went about this, what our values are, and how they'll influence us as we move forward as a company.

@jlengstorf jlengstorf self-assigned this Aug 30, 2018
jlengstorf added a commit to jlengstorf/gatsby that referenced this issue Sep 5, 2018
jlengstorf added a commit that referenced this issue Sep 7, 2018
This post dives into the process the Gatsby Inkteam followed to discuss and define our core values. It also lists out our core values and talks about how we plan to further embody them as Gatsby Inc continues to grow.

closes #7761
<!--
  Q. Which branch should I use for my pull request?
  A. Use `master` branch (probably).

  Q. Which branch if my change is an update to Gatsby v2?
  A. Definitely use `master` branch :)

  Q. Which branch if my change is an update to documentation or gatsbyjs.org?
  A. Use `master` branch. A Gatsby maintainer will copy your changes over to the `v1` branch for you

  Q. Which branch if my change is a bug fix for Gatsby v1?
  A. In this case, you should use the `v1` branch

  Q. Which branch if I'm still not sure?
  A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :)

  Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2.

  Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/
-->
jlengstorf added a commit that referenced this issue Sep 7, 2018
This post dives into the process the Gatsby Inkteam followed to discuss and define our core values. It also lists out our core values and talks about how we plan to further embody them as Gatsby Inc continues to grow.

closes #7761
<!--
  Q. Which branch should I use for my pull request?
  A. Use `master` branch (probably).

  Q. Which branch if my change is an update to Gatsby v2?
  A. Definitely use `master` branch :)

  Q. Which branch if my change is an update to documentation or gatsbyjs.org?
  A. Use `master` branch. A Gatsby maintainer will copy your changes over to the `v1` branch for you

  Q. Which branch if my change is a bug fix for Gatsby v1?
  A. In this case, you should use the `v1` branch

  Q. Which branch if I'm still not sure?
  A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :)

  Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2.

  Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant