Request for comments for future-proofing Umbraco’s backoffice
As mentioned in the last product update, we’ve set a deadline for the first RFC in the backoffice project for today, January 29th, 2021. We’re thankful for all the great input and discussion, it has definitely helped form this RFC as well as the roadmap for the rest of the project. If you have any additional comments, you can still add them today and we will not close the comment section when the RFC is accepted.
We’re currently working on the next RFC for building a UI Library based on web components (as detailed in the first RFC) and will let you know as soon as it is ready.
That’s all folks
Just a couple of things to update you on before I go:
Updated Umbraco Code of Conduct
We have just published a new and updated version of the Umbraco Code of Conduct. It’s been revised with the help of our lovely Umbraco MVPs over the last several months. It now contains more details on what is not acceptable behaviour and, importantly, who to contact if you encounter anything that does not live up to the CoC.
It’s an important thing to have in place for newcomers to the community (new contributors, event speakers etc.) to let them know this is a safe and friendly corner of the broader tech community.
If you’re an Umbraco event or meetup organiser, you’re of course more than welcome to use and refer to this as the code of conduct for your event/meetup.
The CoC is open source, so if you have comments or suggestions you can find it here on Github. We’ll have more details on the new CoC in an upcoming blog post.
… Until next time
A large part of the work we do is inspired by the feedback we get from you. For issues and specific feature requests, you can find the issue trackers for our products on the Umbraco Github account.
If you have product feedback, you’re welcome to reach out to us on product@umbraco.com.