Re: [Swig-devel] Re: Swig-2.0 communication

[David B. <dav...@da...>]

On Mar 1, 2006, at 11:33 PM, Jason Stewart wrote:
>
> Yes, please.
>
> Before any of us start really making changes - especially those that
> cross modules, it is great to communicate:
> 1) what the problem is
> 2) whose problem it is (one lang, all langs, users, SWIG developers)
> 3) how you think you will implement the fix
> 4) what it is likely to change
>
> So much awesome work has been done lately, but it has been done in
> such a way that leaves me mostly in the dark. I would like to feel
> 'part of the team'. Just by getting the planning emails, it will be a
> great positive change - even if I don't have any say in what happens,
> it will give me that 'warm fuzzy feeling' as if I really did have some
> say.

I've sometimes wondered if we ought to go to a system similar to the  
Python PEPs.  In this case, modifications would be written up and  
described before any kind of implementation.   I agree that it's been  
pretty hard to follow everything that's been changed recently.

I definitely think that some kind of plan/proposal needs to be  
written for major changes such as nested classes.

Cheers,
Dave