Hi Graham, Daniel,
Thank ou for your input. This is exacctly what I am aiming for.
Information that can help me to define a possibility.
In reply:
- If the 3.0 release is so far away, it is to far :)
-Not using version figures 5.2.6.458 is a much better for marketing then
stressing with a new version. I believe the version thing should be kept
as to define what version people are working with, but should be dropped
in marketing actions. Using 'flaming flamingo' as a version definer (or
any other) is fun, but leads me to the EE discussion we are still having.
We could handle this in a pro way by doing:
- about spash screen with 'special thanks to developping team' with a
link to a webpage with their foto's and names. (I will be happy to make
such a page for each component)
- removing the EEs (a compromise is a good start, we could ask the
installing administrator to give us his oppinion on if they should stay
in or not and why when he is installing and base a future release EE
situation on that information, as it is the most correct information we
can get)
- defining a moment when to release a version with an event (IMHO it
would take about 6 months to prep a release 'event', depending on the
help and coöp we get)
- When discussing release 'names', ccan we include the change af the OOo
name as is? I think forking OOo is not a good idea. Using a new name as
a marketing message howover works fine. Can we codename this for
discussions sake? (releasing 'Breezy Badger' or any other suggestion)
Thanks again!
Steven P
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
