Transparency and keeping everybody on the same page
The Ubuntu development landscape and the whole project has grown so much that it gets harder and harder for everybody to follow what’s going on in each and every team and across the board every day. There’s a lot of different cases where this becomes obvious:
- An announce sent to a team list might be missed by others who it might concern as well.
- A conversation in a bug report might not get the exposure it actually deserves.
- An announce didn’t hit the mailing list, but was in a couple of blog posts.
- Procedure changes, effects and handling of a package transition, etc. etc.
In the vast majority of cases there is no intended active secrecy, but more of an oversight that causes others to be out of the loop, which might result in duplicated work, wasted efforts and frustration.
To help to solve the problem a number of us sat down at UDS and tried to figure out common cases where slips like the ones above might happen and have happened and how to avoid them. The outcome of this is an updated https://wiki.ubuntu.com/DeveloperCommunication
This page tries to help identify information that is worth announcing and documenting and how to best do that.
Please share the page with others that might benefit from it and please feel free to improve the page with more information to avoid misinformation and lack of information on the general team.
Thanks in advance and ROCK ON! :-)