> > 1. Hard cut: make SF official and only "innovate" on that version. This > > would mean that any new functionality would only be developed by us ion > > that code base > > My choice is this one.d
I agree. Don't spread your resources thin (but do continue to support the old codebase). However, I think that there *might* be some issues between the SF developers and some RSP developers who contribute patches back to OpenSRS (just read the archives for email from Joe Rhett for examples). I have no idea what the situation is, nor do I really care too much. But if OpenSRS is going to move into a more transparent development system like SourceForge, you will need to be prepared for Joe Public offering patches/suggestions/etc.. Not all developers work well in this environment. I hope the people working on the SF client are ready to deal with this input, both technically and personally. - Colin
