RFC: Sprint summary emails

Jason Guiditta jguiditt at redhat.com
Tue Aug 7 14:43:59 UTC 2012


On 07/08/12 20:41 +1000, Justin Clift wrote:
>On 06/08/2012, at 11:27 PM, Matt Wagner wrote:
><snip>
>> On Friday, I took a stab at writing something like I described above,
>> but for the blog versus email:
>> http://blog.aeolusproject.org/conductor-sprint-2012-8/
>>
>> I personally find it much easier to read / more approachable than
>> viewing the Redmine backlog. I did find that I spent a while rewording
>> things to be more catered to end users.
>>
>> So my question is -- is this useful? Is this something that should
>> become standard practice for each sprint's start?

I am not against this, but not sold on it either.  To me, you should
just be looking at the roadmap page in redmine[1]. Yes, it could be a
tad more readable, but that is mostly our own fault for: 

1) Not grouping things correctly (I see a lot of stuff listed as tasks
there instead of features/scenarios, which is basically what your blog
post lists).  If we group them right, we can provide a link on the
main site (or even embed the content in a blog post if you wanted)
which filtered the list to just show those 2 types (filter is on top
right of page).

2) Writing poor descriptions in the title of the task.  They could
easily be called what you have written in the blog post, but nobody
seems willing to take the time to do it - it really isnt that hard. I
am left wondering why we should spend the extra effort summarizing
instead of just being clear to begin with


However, regardless of these points, your post is nice, I just don't
see the duplicate work being needed.

-j

[1]https://www.aeolusproject.org/redmine/projects/aeolus/roadmap?tracker_ids[]=2&tracker_ids[]=4&tracker_ids[]=5#Conductor%202012.8%20%28Sprint%201%29



More information about the aeolus-devel mailing list