I like the format you're suggesting. I've been on the mailing list for at least a year now and have played with Blender's source code a little longer, in-between school and work. It's big and easy to get lost in. So, any guidance on where to start, or some pointers would be helpful. Also, the meeting time being posted is great, too. Especially if the time changes.
George > Date: Wed, 18 Nov 2009 10:17:21 +0100 > From: ideasma...@gmail.com > To: bf-committers@blender.org > Subject: [Bf-committers] meetings for new developers > > 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
