----- "Nigel Kersten" <[email protected]> wrote:

> ----- "Teyo Tyree" < [email protected] > wrote:
> 
> > Would you all be interested knowing what we are working on each
> week?
> > Our iterations will tend to have a theme. This week we are working
> > on building out an inventory service. A high level design document
> is
> > available in Redmine:
> >
> >
> http://projects.puppetlabs.com/projects/1/wiki/InventoryServiceArchitecture
> >
> > We have also thought about the following measures to keep you all
> > involved:
> >
> > Broadcast our daily stand-ups... IRC/Mailing-list
> > Provide weekly snapshots of our work plan for each iteration.
> 
> > Build a Markus effigy with a built in web-cam, point him at our
> > planning board, and broadcast the stream. (Markus is working
> remotely
> > at the moment.)
> >
> 
> > Your thoughts are, as always, welcomed. We have a lot to learn.
> 
> 
> Mostly I am fine with this, except for the lack of discussion around
> the
> inventory service that is the focus of the current sprint.
> 
> I know there was at least some discussions and with this kind of
> thing a lot of it is prototype various ways what works as a means of
> firming
> up the specs and so forth and so on.
> 
> But I get the impression there might have been a RFC covering it? I
> recall
> lots of talk for example around the catalog service but it seems this
> is
> something else and havnt had quite the community opinion involvement
> that
> would be ideal.
> 
> 
> 
> 
> I'm pretty sure Luke sent this out a while ago and asked for input.
> 
> 
> http://projects.puppetlabs.com/projects/1/wiki/InventoryServiceArchitecture

would be very happy to find I just missed it, or forgot about it in old age :P

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-dev?hl=en.

Reply via email to