Re: R: [Rainbowportal-devel] Re: Enhancing navigation options...

[Emmanuele De A. <ma...@gm...>]

Hi all,
I see how rainbow is becoming a big all purpose platform and that out
there there are a lot of different requirements that some time does
not overlap completely.
Even if you can fork rainbow I really suggest to think about this.
Forking means that all you do is not compatible anymore with new
versions. We did a lot of work to keep backward compatibility and to
update all modules to fully use new core changes, on the fork you will
be on your own.
There is a new open track that will target net 2.0 and is almost open
to any suggestion at present. We plan to reuse most of old things
together new whidbey features.
What that would be great would be to share the resources you have for
your single project in a bigger project that has 100 times the
features you have planned at same cost.
This is only a suggestion:
http://support.rainbowportal.net/confluence/display/DOX/Rainbow+on+Asp+2.0

Starting next week at least 3 members of core will be on this, so now
is the right time to be involved. we have a privileged channel with
Microsoft until RTM so it is something to think about.
A lot of time will be devoted to the management so we will have a
smoother process that will include testing and fxcop since the
beginning. A separate track that will match jira issues and history
will be made so that are in sync. We will have better process also for
documentation and continuous integration between different parts.

Interested?

Manu





On Tue, 11 Jan 2005 12:04:24 +0100, matro <ma...@re...> wrote:
> hi James,
> 
> > I'm really in a bind on this. If it doesn't get added to the
> > core (or another solution is found), We're either going to
> > have to look for another CMS or fork from Rainbow and
> > continue developing on our own.
> > Neither of these appeal to me. I know we're new and haven't
> > contributed to the community yet, mostly due to just getting
> > our implementation spec'd out, but we have plans of doing a
> > fair amount of work on Rainbow in the coming months as we are
> > planning to use it as a core of our business.
> 
> I'm interested in your decision about this, as I'm in a similar position:
> we're quite new and have plans of doing lots of work.
> 
> why you're already considering a fork or the usage of another CMS? if you
> implement appropriate standards when modifying the core, you should be able
> to keep it updated with small efforts.
> 
> they're working on a project refactoring which will simplify the internal
> structure, so such stuff should be easier.
> matro