this was discussed at bconf and one of the meetings after, with general approval. We can communicate that they can to log into #blendercoders any time. I'm willing to give this a try, if it doesn't work - so be it.
On Wed, Nov 18, 2009 at 10:21 AM, joe <joe...@gmail.com> wrote: > I dunno. What's wrong with just asking people to pop into IRC and bug > people every couple of hours until someone who knows shows up? :) > > This seems too over-structured to work. Getting people to show up for > the premeeting will be a pain. Personally, I'd prefer people felt > comfortable asking questions in IRC anytime, or emailing the mailing > list. With this, people may get the impression they should only ask > their questions in the once-a-month new-developers meeting. > > Perhaps it'd be better to have a mailing list dedicated to asking > questions about the code? > > Joe > > On Wed, Nov 18, 2009 at 1:17 AM, Campbell Barton <ideasma...@gmail.com> wrote: >> Recently it was suggested that we could have meetings for new >> developers involved, heres some suggestions as to how I think it can >> work. >> >> - not too frequently, this takes energy from developers and time to >> set the topic and communicate whats going on. >> - each meeting have a topic - this can at least be a starting point. >> 2.5/BGE/MeshEditing/Modifiers/Sculpting/Rendering/Sequencer/Physics.... >> etc. >> - Need at least 1 dev experienced in this area to show up. >> - Would be great if blender nation would post a week or so before the >> meeting, can show on blender.org also. >> - Having someone to take notes and post would be good too. >> >> * Who might be interested * >> - technical users who want to know more about blenders internals >> - people who are interested in how blender is developed >> - anyone afraid to ask 'stupid' questions on the ML or normally on IRC. >> >> * Please don't * >> - use this as an excuse to bombard others with feature requests >> - complain about blender only to 'motivate' others to fix ;) >> - expect to learn specific areas eg: OpenGL, Python, C... there are >> plenty of online resources. >> >> (this should be worded more nicely) >> >> ---------------- >> >> Proposal >> - First Sunday of every month, 1 or 2 hr's before the normal developer >> meeting. >> - start the first meeting after beta0 release >> - first topic can be 2.5 - (macro's operators, rna, python etc), >> further topics can be set on the ML. >> - post on b.org, maybe blendernation too. >> >> Who does what? >> - me: arrange to have this posted on b.org assign topic, try make sure >> specific devs can be online. >> - (anyone?): run the meeting, keep on topic. >> - (anyone?): record meeting log. >> >> -- >> - Campbell >> _______________________________________________ >> Bf-committers mailing list >> Bf-committers@blender.org >> http://lists.blender.org/mailman/listinfo/bf-committers >> > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers > -- - Campbell _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers