It has been interesting talking with colleagues about how we best record things like meetings in the project I’m now involved in, GovStack.
To encourage contribution, volunteer contributors, especially but not exclusively, need to feel that the decision making in the project is clear and open - there should never be a difficulty in finding how decisions were made.
After years of getting used to how we do things in the large open source project close to my heart, Drupal, I very much see a meeting, like the monthly mentoring coordination meetings, as an activity that people participate in and contribute to. So, to ensure that they are given due recognition for that contribution, we place the agenda for the meeting in an issue in our issue management system, add meeting notes after the meeting, add issues for any actions and finally give contribution recognition for those that participate.
The way a lot of more traditional projects seem to do things is to add meeting agendas and minutes into a wiki, like Confluence. So far as I can figure out, just because that’s the way things are done (and I’ve never been one for doing things because that’s the way they are done, as you know…)
So, the question on my mind is; are the benefits of recording meetings in issues strong enough to outweigh the inertia of recording them in a wiki?