Excerpts from Doug Hellmann's message of 2018-01-12 15:37:42 -0500:
> Since we are discussing goals for the Rocky cycle, I would like to
> propose a change to the way we track progress on the goals.
>
> We've started to see lots and lots of changes to the goal documents,
> more than anticipated
Emilien Macchi wrote:
> On Fri, Jan 12, 2018 at 12:37 PM, Doug Hellmann wrote:
>> [...]
>> How does this sound as an approach? Does anyone have any reservations
>> about using storyboard this way?
>
> Sounds like a good idea, and will help to "Eat Our Own Dog Food" (if
>
I think this is a great idea!
This would really help with getting more eyes on StoryBoard. I think a lot
of people haven't touched it much in the last year or two and aren't aware
of all of its capabilities at this point and this would be a great way to
get people up to speed.
This use case
> >
> > How does this sound as an approach? Does anyone have any reservations
> > about using storyboard this way?
>
> Sounds like a good idea, and will help to "Eat Our Own Dog Food" (if
> we want Storyboard adopted at some point).
My thoughts as well. This would be a good way to get more
On Fri, Jan 12, 2018 at 01:11:40PM -0800, Emilien Macchi wrote:
> On Fri, Jan 12, 2018 at 12:37 PM, Doug Hellmann wrote:
> > Since we are discussing goals for the Rocky cycle, I would like to
> > propose a change to the way we track progress on the goals.
> >
> > We've
On Fri, Jan 12, 2018 at 12:37 PM, Doug Hellmann wrote:
> Since we are discussing goals for the Rocky cycle, I would like to
> propose a change to the way we track progress on the goals.
>
> We've started to see lots and lots of changes to the goal documents,
> more than
Since we are discussing goals for the Rocky cycle, I would like to
propose a change to the way we track progress on the goals.
We've started to see lots and lots of changes to the goal documents,
more than anticipated when we designed the system originally. That
leads to code review churn within