On Thursday 03 February 2005 17:07, Chris Shenton wrote:[...]

I haven't read the archives on the bootcamp, so perhaps this has been 
suggested. The bootcamp seems like a great addition to the Python/Zope 
Sprints at GWU just prior to the PyCon. The sprints are scheduled for March 
19-22. How many people would be interested in doing an bootcamp and then use 
the results of the bootcamp to hold a sprint to create a Zope or Plone or 
possibly Zope3 product? We should have some idea of how many people would 
attend and on which days they would attend prior to adding a session to the 
sprint wiki. Also, how much time can people comit to participating? All four 
days? Just the Weekend? Just one day?

I'd also like to remind ZPUG list participants about PyCon 
(http://pycon.org/). There were people at the
meeting tonight that didn't 
realize there was a Python conference in the DC area in March. This is a 
great event and it's a real bargan. Metro access is very reasonable. The 
meeting is two blocks from the Foggy Bottom Metro stop. If you haven't been 
to PyCon then you're in for a treat. They are great fun.

On Thu, Feb 03, 2005 at 11:43:46PM -0500, Michael McLay wrote:[...]

An alternate possibility, since time for bootcamp planning in time for PyCon
is nearing hard deadlines, is for us to hold a "learning sprint" during the
PyCon pre-period. I'd be happy to coach people over a 2d period on how to
build a good, Archetypes-based product. We could cover the "best practice"
kind of stuff. This isn't training, tho', so it would require people to be
self-motivated about learning Plone basics and some dev stuff beforehand.

This sprint in CA is going great, BTW. Having a blast.

Sorry it appears there was some confusion re: the meeting tonight. I was
in meetings all day and missed all the should-we-meet stuff, but I'm
glad it worked out.

- j.

joel(at)joelburton.com writes:
[...]

Sounds like a good way to dive into it. If you could provide some
pointers to stuff we should get smart on, we can try and get up to
speed before then.

Thanks.

I'm not clear on the suggested redirection.  What is a "learning  
sprint" and how does it differ from training?  What level of  
Plone/Zope/Python skill/experience is assumed?  Is this an event that  
would take place during the day as with the training?   Do we have to  
answer the same questions - location, dates, etc.  And, why are we  
redirecting at all?  What was wrong with the initial training bootcamp  
idea?  It sure appealed to me.  The followon event to build an  
Archetypes product sounds good although I had thought that Archetypes  
would be covered (including some sample development) in the training  
bootcamp.

David

On Feb 4, 2005, at 1:08 AM, joel(at)joelburton.com wrote:
[...][...]
>>> While I'm very interested in the presentation,  the main
>>> time-sensitive issue is the potential bootcamp, especially as
David
>>> Diskin has reserved some rather good sounding space the week of
April
>>> 4th.   (I could be up for that week.)
>>>
>>> Perhaps we can continue discussion of bootcamping via email and
wiki
>>> in the intervening weeks and come to a conclusion.[...][...]
==============================
David Diskin, david.diskin(at)verizon.net

On Fri, Feb 04, 2005 at 12:16:39PM -0500, David Diskin wrote:[...]

Most sprints are for very experienced developers; this could be
one for beginning/intermediate developers, ith the goal of teaching
as much as doing (hence, learning sprint).

It would be for people know many parts of Plone basics, but want to apply
this in the  real world.

It could take place during the day, and, given that it's a different
focus (sprinting) and only 2d, we could just do it without cost
and use the Pycon sprinting space at GWU.
[...]

No, since Pycon already has space and dates for sprinting.
[...]

Besides your work, Davis, there hasn't been much energy into organizing
the bootcamp--and it does take real organizing to pull of a week-long
training. I merely offered the sprint idea as something we don't really
have to plan at all: sprints are just pair programming events coached
by someone, and therefore are much easier to put together.

They meet different audiences, in some ways (the sprint is, by its
nature, for more experienced people, whereas bootcamps are to get you
there), and they feel quite different: during a sprint, the focus is on
getting people to dive into source code, fix bugs, and share
techniques with each other, rather than having a trainer lead people
through learning concepts in a more directed way.

Anyhoo, just offering a simpler path to a different outcome :) Don't
mean to muddy the waters. I'd love it if a bootcamp gets pulled together--
I hpoe that if people want that, they make it happen.

Now, I have to get back to the sprint that's here right now :)

- j.

Isn't there already a Sprint associated with Pycon? 

Yes there is.... March 19-22. I suppose it would be nice for us to 
have our own 2-day thing during that time period.

Another big difference is that you don't charge for coaching a sprint, 
right Joel ? ;-)

I also don't think that this will take any focus away from the bootcamp
planning
which is going to require it's own separate week, no ? 

Alex

On Fri, Feb 04, 2005 at 11:20:15AM -0600, joel(at)joelburton.com wrote:[...]
[...]