[Bf-committers] meetings for new developers

[Campbell Barton]

Hi Roger, glad to hear your willing to help out and we are ok for the same time.

If you end up running this then Id still turn up and try help answer
questions etc...

- Id like to post these as "Developer Q&A sessions" - for new devs
since its not like a formal meeting, more an info session.
- Re: Times, I'm sticking to 1hr before the meeting, if this isn't
enough it can be made 2 or so... its convenient for devs in Australia,
Europe and part of America, which covers most core developers AFAIK.
  People came to BConf from other countries in some cases to meet up
with devs, getting up early for an important event is not unheard of,
if I am to give spare time to this it needs to be a reasonable hour
for me.
  First sunday of the month 1 hr before the normal dev meeting is easy
to remember.

...to clarify some things...
- these dev Q&A's would be monthly, so 6am once a month is even less
of a problem :)
- not sure on standing agenda, we may find its best even to have the
agenda set very loosely and play it by ear, see what people want to
ask,
  however its important if a topic is discussed, experienced devs are online.
  Since this is for new devs I don't think there is so much value in
2.49 discussions.


On Thu, Nov 19, 2009 at 11:20 PM, Roger Wickes <rogerwickes at yahoo.com> wrote:
> As Education moderator, I would be happy to moderate/conduct/scribe the
> meeting. However, it will not be a rotating times, because that introduces a
>  decision point into the attendee process. They have to remember where to
>  look in advance in order to determine the time and then mark that once
> and then repeat that...etc. As a professional project manager, one never
> changes the time of a regularly scheduled meeting unless it conflicts with
> another.
>
> Time: I would be happy to conduct the meeting for up to one hour, starting
> one hour before the weekly blender coders call. if a dev in AUS is willing to
> stay up till 2am to attend that meeting, they are up at 1am and perhaps
> would be kind enough to log in. You California types can get up at 6am once
> a week, it won't kill ya :) and an hour before is courteous to the EU time
> zones, and leaves them some personal evening time.
>
>
> Location: I propose we use #blendercoders, because that is familiar to
> every developer. I do not have authority over it now, however.
>
> Topics: A standing agenda can be decided on thru this ml, but i would
> suggest something like:
>
> 2.49 C, 2.49 Python API ( regular/BGE)
> 2.5 C, 2.5 Python API (UI/regular/BGE)
>
> with 15 minutes allotted to each segment.
>
> May not be nirvana, but its a start. Let me know.
>
>  ----------------
> Sent by Roger Wickes for intended recipient. If you are not the intended recipient, please delete this message and contact Mr. Wickes immediately.
>
>
>
>
> ________________________________
> From: Mitchell Stokes <mogurijin at gmail.com>
> To: bf-blender developers <bf-committers at blender.org>
> Sent: Thu, November 19, 2009 12:36:30 PM
> Subject: Re: [Bf-committers] meetings for new developers
>
> I like the idea of rotating times. I could help with meetings that are
> later then the regular meeting times. Earlier just doesn't work for me
> (the regular meetings are already at 7am for me). Although, the only
> part of Blender's code that I know about is the BGE, so I might not be
> too helpful in meetings that aren't in helping people navigate the BGE
> code.
>
> Cheers,
> Mitchell Stokes (Moguri)
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>
>
>
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
- Campbell