Buddy System #45
Replies: 2 comments 6 replies
-
@glennawatson I love the idea! Having projects help each other “scales” better than individual board members helping out. I say this because the board will change every two years as elections and positions end. |
Beta Was this translation helpful? Give feedback.
-
If this "buddy system" is the same that I proposed elsewhere, the goal was actually to: Buddy up every .NET Foundation project with a .NET Foundation board member (all decision-makers, really). As I've reflected on the past week, I believe that a lot of issues could have been resolved better if there was someone at the .NET Foundation that each project trusted. Project maintainers wouldn't have felt so isolated and (ideally) a board member for each of the struggling project maintainers would jump in to ensure the communication was flowing. Additionally, when new board members are elected, their buddy project maintainer will bring them up to speed how OSS projects work simply by communicating. Ideally, this will enable a "continuity of norms" to flow from election to election as the .NET Foundation's leadership changes. I originally called it "adopt a project" but I thought "buddy" was a better term since I hope there is a benefit for both the project maintainer and the board member. |
Beta Was this translation helpful? Give feedback.
-
Based on discussions from other threads, there seems to be an appeal of a buddy system.
Where a project is struggling, a buddy could help out with the project.
The buddy could be another project which has done a particular process before or helping a project set up a CI-based system for example
Beta Was this translation helpful? Give feedback.
All reactions