[Scooby-dev] Re: [Cosmo-dev] Scooby/Cosmo Merge approved.

[Matthew Eernisse]

>    + There has been a suggestion of dropping the Scooby name and just 
> referring the project to be named Cosmo.

+1 for 'Cosmo' (no Jell-O Pudding Pops!)

> 2. Mailing lists?
>    + There has been talk about merging the lists. We could potentially 
> place a tag in the subject line referring to [F] - Front end and [B] - 
> Back end/server side conversation.

Yay, merging the lists! The best part will be not having to sort out all 
the cross-posts anymore! Woohoo! :)

My suspicion here is that the Subject line of the e-mail will mostly 
clue you in you whether it's a message about the front-end or back-end 
of the app (e.g., "IE6 is broken on thingie again" or "Content-type 
isn't getting set properly for doohickey").

> 4. Wiki pages?
>    + Are we planning to merge all the information on the wiki pages? Do 
> we want to bother merging all the pages or the upcoming release pages?
>    + There will probably be further discussion about where the schedule, 
> features list, road map, documentation and coding standards etc. is 
> found on the wiki.

This will indeed take awhile, but I also think that we ought to just 
start moving stuff where it needs to go, and archive old stuff. I much 
prefer ripping the band-aid off to sitting around thinking about what it 
will feel like.

> 
> 5. Merging the status meetings?
>    + Currently the meetings are back to back. Most people in the Cosmo 
> meeting are attending the Scooby meeting. Is there a need to merge the 
> meeting so everyone is attending and listening to both sides of the 
> product? Could we possibly make the meetings more efficient?

I like the idea of designating one half of the meeting the "Web UI 
side," and one the "backend side," and let the appropriate people decide 
which bits they should stick around for. I agree with Brian that it'll 
likely take some time to shake out what is the actual best way to handle it.


Matthew