[fluid-dev] New development

[Bernat Arlandis i Mañó]

This is concerning ticket #11.

I'm thinking on a lot of changes to take FS forward as I review the 
source code and fix some things, but most of these changes would break 
compatibility backwards. Maybe we should think about making a branch for 
something that could be FS2.0. Fixes that break compatibility could go 
there, what do you think? Or we could take intermediate steps that would 
be 1.1, 1.2,... I think it's better working in gradual steps with public 
releases.

I'm willing to push development for that branch since I'm getting to 
know its internals and I like working with it very much, but it wouldn't 
be good to do it completely on my own without your expertise and the 
users support. I don't want this to start a fork neither, so there has 
to be an initial agreement that we all support this branch while it 
accomplishes some goals or we all forget about it.

I know it's a short time since I'm working with the code, but I'm 
already playing with it and there are simple things that can't be done 
without breaking backwards compatibility since the code exposes a lot of 
internals and there's a highly coupling between some components. These 
are issues that keep FS from evolving.

Opinions, please.

--
Bernat Arlandis i Mañó