[Openstack] Improving meetbot reports (was Re: Community metrics, developers' engagement)

Josh Kearney josh at jk0.org
Wed Sep 28 01:16:50 UTC 2011


This would make for a perfect pyhole plugin.

https://github.com/jk0/pyhole

</shameless plug>

On Sep 27, 2011, at 7:56 PM, John Dickinson <me at not.mn> wrote:

> Taking a recent example, I think there is a big difference between http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-09-06-20.03.html and http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-09-06-20.03.log.html. The first is too short, and the second is too long.
> 
> The best thing I can come up with to describe what would be better (a midpoint) is a journalistic report of what happened at the meeting. Something with more info than what meetbot provides (3 votes, 2 decisions, jbryce talked 54 times, etc) but more clear than the IRC logs (holy great wall of text, Batman!). Meetbot's summaries are precise, but they have a non-human flavor to them, and they are only as good at the moderator for the meeting. The goal (as I understand it) of having all the meetings in the open is to make the decision-making process transparent and accessible. The current setup meets the letter of the law, but perhaps not the spirit.
> 
> --John
> 
> 
> 
> On Sep 27, 2011, at 7:08 PM, Stefano Maffulli wrote:
> 
>> On Mon, 2011-09-26 at 12:51 -0500, John Dickinson wrote:
>>> I too would like to see official community and PPB meeting summaries.
>>> Ideally, I think it'd be nice for the summaries to be written by
>>> someone not involved in the discussion[1], but that wouldn't be
>>> required. Something between what the meetbot produces and the raw IRC
>>> logs would be nice.
>> 
>> I'm very undecided about this as I don't know how this can be achieved.
>> Nice summaries from IRC discussions are not only very hard to produce
>> but also may introduce mistakes in the reports.
>> 
>> If meetbot reports are not sufficiently intelligible we should think
>> about ways to improve them. Or adopt Apache's policy of "if the
>> discussion was not on the mailing list it didn't happen".
>> 
>> Lets start by clearly identifying the problem: What are the major pain
>> points of meetbot reports?
>> 
>> /stef
>> 
>> 
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack at lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp




More information about the Openstack mailing list