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

[Brian Moseley]

On 8/1/06, Priscilla Chung <priscilla at osafoundation.org> wrote:

> 1. Name of the project?
>     + Outside of the branding project Pieter is driving, this is just
> an internal project name we can refer to.
>     + There has been a suggestion of dropping the Scooby name and
> just referring the project to be named Cosmo.

that's my vote. it's just the easiest thing to do.

> 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.

if you feel the need. i don't think it's a convention i'll ever adopt.
i just don't think about communications in that way.

> 3. IRC channels?
>     + Are we going to merge the IRC channels?

i don't see why we shouldn't.

> 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?

yes, i think we should merge the scooby docs into the cosmo ones,
rewriting as necessary, and leaving the existing ones for historical
purposes.

>     + There will probably be further discussion about where the
> schedule, features list, road map, documentation and coding standards
> etc. is found on the wiki.

what further discussion is required? let's just do it.

> 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?

it's been suggested before that we have a single meeting with half
focused on front end issues and half focused on back end. that may be
a naive way to divide the agenda of a unified product, but we won't
know until we try. i know that my eyes glaze over when matt and bobby
discuss javascript stuff, and i think the same happens to matt when we
talk about certain back end topics. if we structure so that people can
leave once their individual areas of interest have been covered (or
enter when they are about to begin), i think everybody will be happy.
it might take a few tries to get that structure right.