Download
1 / 3
30 likes | 43 Views
One month in, and records have already been broken. And there has even been a new release! All this thanks to the work of both the active Umbraco community and the new PR team. With a new process in place including the goal of getting a reply within 48 hours, it has clearly already become more fun and rewarding to contribute to Umbraco. Sebastiaan will let you in on how things are going (including those records 😉) and what the plan is going forward: For more details please visit at https://umbraco.com/blog/the-pr-team-chronicles-month-one/
E N D
The PR team chronicles: month one One month in, and records have already been broken. And there has even been a new release! All this thanks to the work of both the active Umbraco community and the new PR team. With a new process in place including the goal of getting a reply within 48 hours, it has clearly already become more fun and rewarding to contribute to Umbraco. Sebastiaan will let you in on how things are going (including those records 😉) and what the plan is going forward: https://umbraco.com/blog/the-pr-team-chronicles-month-one/
Remind me again, what is the purpose of the PR team again? For the first few months of its existence, the purpose of the PR team is to make sure that new contributions (so anything new after Codegarden 18, more on this later in "Future plans") to Umbraco get all the attention they deserve. This means they'll get a prompt reply that we have seen and appreciate their contribution and that we'll check it out soon. This alone helps contributors feel like they have sent their PR correctly and that they can expect a more substantive reply in the next few days. After that initial reply, a PR team members will: Evaluate the code, to see if it makes sense and is roughly in line with the coding style that Umbraco uses already If there's any concerns or questions, we'll raise them as soon as possible - examples of questions might be: "what exactly does this solve?", "how do I reproduce the problem?", "why is there a picture of a banana added?", etc. Clone the PR locally, build the code and test it out to see if it works as expected and to make sure it doesn't break anything - this results in either a positive review or a request for some more changes as required At this point HQ can pick up the PR if they had not already and feel fairly confident that it does what is described. Usually we'll do another quick test and we'll do another code review as well. Of course if there's any questions or changes are needed, the PR will get updated accordingly so the submitter knows what's going on and can help further the PR
Results for the first month Currently with the PR team we're still learning how to handle the flow of new contributions and we're not quite on top of absolutely everything yet. However, we are already breaking records! I've been so jealous of Sofie's beautiful stats based on the Documentation Curators development over the past year, so I had to follow up with some stats of our own! Below we're showing pull requests created (blue) and merged (red) per month for the last year. For the month of June 2018 (stats are from the 21st of June) we have managed to merge a record number of 40 PRs from just community members, this does not include pull requests made by Umbraco HQ, so only community contributors. https://umbraco.com/blog/the-pr-team-chronicles-month-one/
