Name announcement planning

[Alfredo Beaumont]

2010/11/27 C. Boemann <cbo at boemann.dk>:
> On Saturday 27 November 2010 14:23:02 Boudewijn Rempt wrote:
>> On Saturday 27 November 2010, Cyrille Berger Skott wrote:
>> > Hi,
>> >
>> > At some point we will need to make a public announcement on the new name.
>> > Inge is going to take care of the actual announcement.
>> >
>> > But we need to have a few things ready:
>> >
>> > * website
>> > * applications name
>> > * logo ?
>> >
>> > The website is almost ready, while application names are in progress.
>> > Personnally I don't think the logo is mandatory, it can be announced
>> > later.
>>
>> The only thing we're really waiting for is the board's answer about koffice
>> and koffice.org, right? The individual application names can wait, except
>> for kword, if needed, even until the next release.
> I must disagree. I think it would be very wrong to announce this split with
> old names no logo etc. It just oozes of something done in a hurry and seems
> very unprofessional.
>
>> > However we have a deadline next week with the switch to git. We will need
>> > to announce the location of the new repository. Personnaly, I had like
>> > everything to be ready at that point, and we will need to minimize the
>> > delay as much as possible.
>>
>> Yes, indeed.
>>
>> > And if we have to push the name announcement after the transition to
>> > git, someone will have to deal with the mess of people still looking at
>> > the svn repository
>>
>> That would be very unfortunate.
> Yes, but really, how many besides ourselves really need to know on the very
> first day. How many strangers do you see committing on an average week. One
> maybe. I think we can handle that manually if needed. It's not like the delay
> in announcing will be weeks long. but maybe a few days.
>
> Let's not rush now. Well let's rush getting ready, but not announce before we
> are ready.

+1

I'd also try to rush e.V. (if possible). We don't want to give the
sensation of we forking just because we're the only ones actually
moving... Current koffice infrastructure should be prepared to
announce the new status too and we need to know how we need to handle
this before actually handling it