You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: measuring-your-open-source-program.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ Careful (and strategic) measurement also makes great fodder for reports to upper
37
37
38
38
Facebook’s open source program office, for example, periodically posts the month-over-month results from its open source projects internally and sends an executive report to management.
39
39
40
-
> "Reports are just a good way to raise awareness. Even though Facebook does value open source (as an organization), it's still always a good thing to market yourself internally all the time and show your value." - [Christine Abernathy](https://twitter.com/abernathyca), Open Source Developer Advocate at Facebook.
40
+
> "Reports are just a good way to raise awareness. Even though Facebook places a high value open source (as an organization), it's still always a good thing to market yourself internally all the time and show your value." - [Christine Abernathy](https://twitter.com/abernathyca), Open Source Developer Advocate at Facebook.
41
41
42
42
Publishing the results publicly on a regular basis also helps raise awareness of your organization’s open source activities among potential partners, users, and developers.
43
43
@@ -49,7 +49,7 @@ It’s OK to have lofty goals for your open source program, but set reasonable e
Next, get all of the open source program managers and stakeholders together -- at Facebook, that’s about five people -- and decide as a group where you want to go over the next 3-6 months (small, achievable increments). At the end of that time period, look back at how you did and adjust goals and tactics for the next pass, based on the previous pass.
52
+
Next, get all of the open source program managers and stakeholders together -- at Facebook, this includes the engineering leads and project maintainers -- and decide as a group where you want to go over the next 3-6 months (small, achievable increments). At the end of that time period, look back at how you did and adjust goals and tactics for the next pass, based on the previous pass.
53
53
54
54
> "I tend to find metrics based on what the community is feeling as pain, and try to change those metrics for the better to improve the community health." - [Sarah Novotny](https://twitter.com/sarahnovotny), Kubernetes Community Manager at Google.
55
55
@@ -139,7 +139,7 @@ But chances are that you as a program manager will not have a direct role in rec
139
139
* How did that awareness influence their decision to join the company?
140
140
* Does their experience with open source apply to the work that they are doing now?
141
141
142
-
> "We don't have goals around the survey but it's good to know that the numbers are trending upwards. That speaks to the overall effectiveness of how people view our open source projects." - [Christine Abernathy](https://twitter.com/abernathyca), Open Source Developer Advocate at Facebook.
142
+
> "We use the survey to measure the health of our open source culture and it speaks to the overall effectiveness of how people view our open source projects. It's good to know the numbers trend upwards." - [Christine Abernathy](https://twitter.com/abernathyca), Open Source Developer Advocate at Facebook.
143
143
144
144
Other common metrics for developer recruitment include:
0 commit comments