MC IDE's home

[Robert Brenstein]

>Next Steps
>----------
>I've acting as a sort of interim coordinator simply because some ongoing
>discussions of bugs and related issues with Scott made it convenient to ask
>him for these details to get the thing rolling.  We should probably decide
>how and by whom changes will be made going forward.
>
>As a starting point I'm inclined to suggest that a project leader be
>selected by vote and that person be responsible for changes.  Any work could
>be done by others, but the leader would be reponsible for reviewing and
>posting changes.
>
>The thread on Message Box positioning seems a good model:  a change is
>proposed here, views heard, a summary posted and if there is no strong
>opposition to that summary the majority's preference would be implemented.
>Does that seem desirable?  If not, by what other process should changes be
>approved?
>
>In summary our two immediate questions are:
>
>- Who wants to act as project leader for the next six months?

Richard, since you have started the ball rolling and have been 
already involved dealing with Scott and Rev folks on this issue, I'd 
vote for you to continue for now unless you really do not want to do 
it. A few people have already suggested your name but you do not seem 
to take a clear position. Don't be shy. Most of us are too busy to 
volunteer and getting this off the ground requires some extra effort. 
And you already have your feet wet, so do speak. Many open source 
project are successful on the long term only because of the drive of 
a few dedicated individuals.

I would also not limit the term artificially to six months. I think 
the rotation on the post will work out naturally and we see how the 
group dynamics works over time.

>- By what process should changes be decided on?

What you suggested sounds fine to me. The only thing that might be 
considered is timing: a) not everyone is online daily and/or read all 
posts right away, so some time span is needed, but at the same time 
b) there must be some deadline set, so the issue does not drag for 
too long.

And for other issues:

SourceForge is a good and neutral place for the project. It also 
provides a number of tools that might be handy for us. I agree that 
project should be kept with few limitations there but posting final 
files should be restricted.

Shorter scripts (like solutions for the msg window positioning) can 
be simply posted to the list for testing and improvements by the 
group, as it has been often done, whereas longer scripts or stacks 
can be posted on sourceforge.

Robert Brenstein