[Soc-2007-dev] Project specifications

[Ton Roosendaal]

Hi Levi,

We don't have formal procedures for it. But we also should try to be as  
clear as possible in advance what we expect from students. You have the  
right to know in advance how to be successful!

The purpose of putting your design proposal in wiki is to get it  
approved on too. And, such a design doc is not only about technology  
(like APIs) but also about usability (i.e. how the user will access it,  
use it).

About your questions below; I think it's correct to assume the mentor  
to approve. But give everyone some time to look at it and review too.
We can do that here, or on the SoC mailing list. No preference.

-Ton-


On 10 Jun, 2007, at 22:23, Levi Schooley wrote:

> Hello,
>
> I read the Sunday meeting minutes at
> http://wiki.blender.org/index.php/BlenderDev/SundayMeetingAgenda/ 
> June_10th_2007
> and noticed the note, "Ton said all SoC projects should get
> project specifications written to wiki and formally agreed on."
>
> 1. Who?
> Which individuals should be involved in this process?
>
> 2. What?
> What is the process for specification approval?
>
> 3. Where?
> Should this process be done publicly via mailing lists (and is
> bf-committers preferred?), or should it be initiated privately
> with my mentor?
>
> 4. How?
> Are there any preferences, guidelines, or examples for how the
> specifications are to be listed and presented?
>
> Thanks!
> Levi
>
> _______________________________________________
> Soc-2007-dev mailing list
> Soc-2007-dev at blender.org
> http://lists.blender.org/mailman/listinfo/soc-2007-dev
>
>
------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton at blender.org  
http://www.blender.org