Hello Technical Board and Council,
continuing efforts to lower the barrier of entry and making contribution
opportunities more meaningful I'd like us to consider reviving and
iterating on the patch pilot program. I've put together an initial brief
here for your reading leisure:
https://docs.google.com/document/d/e/2PACX-1vSgn4ln01g7qoFSI-xStQvki8yRn83wF4-rNW5zZxMHm-VhqMhl3SIAhMzHwtB8cAVhHiBOXMKXReGz/pub
I'd love to have the discussions around this in the open as much as is
feasible. Before I make a discourse post I wanted to get some initial
feedback from managers internally, as well as you all. Let me know if
there are aspects of the proposal that are off or if there are other
points that should change before I post this more broadly.
I'd also appreciate if we could identify at 1–2 point people from each
group that would be involved as stakeholders and help drive the proposal
forward.
Philipp
PS: As a quick aside mostly for the CC: I'm looking for ways to get the
community involved much earlier while also making it simple for
Canonical staff to participate. I'd like to have a synchronous
communication channel where I can easily pull in people from both sides
and coordinate ongoing discussion. Creating a temporary IRC channel for
this project specifically makes it easy to rope in community folks, but
might have a higher barrier of entry for staff. Using a Mattermost
channel makes it fairly difficult to pull in community members. Using
email or discourse completely might delay communications. Though, maybe
I am overthinking it though and it turns out to be feasible to just get
Canonical staff onto IRC? Let me know if you have thoughts or past
experience on this.
--
Philipp Kewisch
Community Engineering Manager
Canonical <https://www.canonical.com>
--
technical-board mailing list
technical-board@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/technical-board
