All the stewards (or team leads) are currently HQ staff, but it could as well be a community member who has that role.
As per the discussion at the Round Table, we have implemented the model of concentric circles. We will continue using this model of concentric circles trying to identify “personas” in the circles.
Furthermore, we will increase communication and communicate more about team activities, thus becoming more visible and accessible to the outside world. This should help us move away from a “who you know” access towards more accessibility to the outside world.
A fourth team has just been announced, the “Unicore Team”, who will work on moving Umbraco version 8 to .NET Core. This team will use the same methods as described above regarding communication and visibility.
A final comment on this topic is that contribution comes in many different flavours and we do recognize that there are several ways of getting involved.
If submitting a pull request is not your cup of tea or you enjoy speaking at events or organizing meetups, for example, we would love to hear from you.
One of the initiatives we are currently working on is “Speakers Academy”. The purpose is to give future speakers in the community an opportunity to test and hone their skills.
We have not finalized the concept yet, and we are open to comments and suggestions, so please reach out to Ilham ilham@umbraco.com or me on sneum@umbtraco.com
The chasm between stability/spontaneity and less big PR
At the Round Table Discussion, we discussed that in the “olden days” things like pull requests were bigger, they got implemented faster and Umbraco was more open and with fewer rules and processes.
It was also recognised that along with the increased reach of the software and growth in both the community and the company, the need for stability, predictability and reliability was demanded and has subsequently risen significantly.
We can’t change that.
Obviously, we don’t want to be less spontaneous than called for, nor do we want to be rigid and closed.
We have neither a limit on the size of any given PR. Big and small are welcome.
We recognise that it might not be (perceived) as being as easy as it previously was, but we still strive to make it as simple and transparent as possible. Furthermore, it requires a coordinated effort ensuring predictability.
Down below, you can find some of our thoughts on how we want to accommodate this:
- As for “smaller contributions” much work is done through “The Core Collaborators” including discussion of “feature like” PRs.
- Contributions which are more relevant for packages will be handled by the Package Team which has the goal of making packages a first class citizen.
- In regards to topics outside the above two categories, please reach out to our product owner Mr Rune Hem Strand (product@umbraco.com) to suggest, comment or discuss product related areas. I would like to mention two examples:
- Our Gold Partner Perplex is working on segmentation. They reached out, and through several PRs, we are assisting them with reviews and sparring on implementing this feature.
- The Accessibility Team have raised the standard of the Umbraco CMS significantly over the many past releases. This is a coordinated community effort and has resulted in many small(er) PRs that get handled through the Core Collaborators team in our standard PR process. This makes it possible to continually improve accessibility in the back office as opposed to making a few huge PRs that would be much more difficult and time-consuming to review and merge.