String freeze date

Hello,

I wish to set the date for "string freeze" (aka the date after which strings 
can't be changed anymore), since it is important to give time to the 
translation teams, I would like to set the date slightly after beta2, 
something like October, 22th. Unless there are objections ?

--

-- 
Cyrille Berger

Re: String freeze date

On Wed, 1 Oct 2008, Cyrille Berger wrote:

> Hello,
> 
> I wish to set the date for "string freeze" (aka the date after which strings 
> can't be changed anymore), since it is important to give time to the 
> translation teams, I would like to set the date slightly after beta2, 
> something like October, 22th. Unless there are objections ?
> 

I think that, at least for Krita, that's too early: I am fairly sure that there
are still quite a number of mistakes and missing strings. I also want to go through
Krita and add tooltips.

Boudewijn

Re: String freeze date

On Wednesday 01 October 2008, Boudewijn Rempt wrote:
> I think that, at least for Krita, that's too early: I am fairly sure that
> there are still quite a number of mistakes and missing strings. I also want
> to go through Krita and add tooltips.

What would be a better date for Krita ? Freeze by the end of October allready 
leave a very short time for translations team (if we still hope for a release 
this year).

--

-- 
Cyrille Berger

ODF Interoperability and Conformance TC

Hi,

Reading [1], I was wondering if someone has allready volunteered to 
participate to that TC, and/or if someone intented to do so ?

[1] 
http://www.robweir.com/blog/2008/09/introducing-odf-interoperability-and.html
--

-- 
Cyrille Berger

Re: ODF Interoperability and Conformance TC

_______________________________________________
koffice-devel mailing list
koffice-devel <at> kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

Creating a buzz for KO2

Hey!

I seem to get creative over cups of red tea. So I thought I'd share my
thoughts with you. :)

I would like to raise attention dramatically for the new KOffice
version among our targeted audience of early-adopters/developers and
for that reason want to use the nice and easy so called web2.0
platforms.

o Twitter.com
Everybody could set up her or his own account, but maybe that's not
for everyone. So I suggest setting up an account for KOffice and sync
all of your blogs into it via twitterfeed. That doesn't cause more
work but makes your blogs more visible, at least to those who only
occasionally drop by the planet for example.

o Flickr.com
This would give us a central place to collect screenshots easy to
embed by everyone.

o Vimeo.com
This is a video platform similar to YouTube.com. It provides the
possibility to upload HD content though which adds a lot to the
quality. ;) It is not yet as widely spread as YouTube, but I think the
better quality makes up for that. Additional to that we could put up
screencasts in different formats on the wiki/website for download to
serve those who don't want to rely on flash installs.

The idea behind all this is to have material about KOffice2 in every
possible format which is available on the social web to have people
look at it and comment on it (aka community building). I will use my
personal accounts to spread it and hope some of you will do too.

Bottom line to this is: I can't do this all on my own. I will gladly
set up all those accounts and manage them but I need material. This is
where *you* come in. ;)

I need your blog URLs for the twitterfeed and any screenshot/-cast you
have for a start. I'd be happy with an occasional email saying 'see
attached' with new material. I think you all know your work best and
which features to present. Note that I don't want anybody to spend
hours on this but I think a quick screenshot of a polished feature
should be possible.

Thoughts? Questions?

And thanks for reading to the bottom. ;)
Alexandra

Re: Creating a buzz for KO2

On Wed, 1 Oct 2008, Alexandra Leisse wrote:

> I need your blog URLs for the twitterfeed and any screenshot/-cast you
> have for a start. 

feed://www.valdyas.org/fading/index.cgi/index.rss

> I'd be happy with an occasional email saying 'see
> attached' with new material. I think you all know your work best and
> which features to present. Note that I don't want anybody to spend
> hours on this but I think a quick screenshot of a polished feature
> should be possible.

KOffice Sprint Food for Thought 1: Graphics

Hi there,

In preparation for the KOffice release sprint I have a number of things that I 
think need discussion before the sprint. This mail is the first in a short 
series of emails that will talk about these things.  In this one I want to 
discuss Graphics.

We have a problems with the graphics in KOffice in several ways:
1. Icons
2. New logos that aren't used anywhere.
3. Still the old outdated website.

I want to discuss 1. and 2. above.  3 is more of a marketing question and will 
be dealt with separately.

We used to have a person who was responsible for the graphics elements, but he 
resigned due to too little time. Since then nobody has felt any 
responsibility for the graphics in KOffice, and the result is that we 
currently have a lot of missing icons. Also, I am not sure that the icons 
that we do have are neither well integrated with each other nor in Oxygen, 
even if I'm not sure that they are not either.

Anyway, it would be very good if somebody could step up to coordinate this 
again within KOffice.  

The missing icons is not such a big problem given that we have repeated offers 
by pinheiro and other artists to create KOffice graphics.  What worries me a 
little is the lack of coordination and that the time is getting short.  We 
should start to take care of this problem before the sprint, and it would be 
great if somebody would step up as the coordinator.  Given that we are all 
hackers perhaps we should announce a vacancy on blogs and the dot?

The second problem is the logos.  When they arrived, we all(?) agreed that 
they were good and we should start using them.  However I don't see much of 
that, and that's another thing that we should start doing.  The question is 
how. This problem is probably smaller than the first, but also need to be 
dealt with.

	-Inge

Re: KOffice Sprint Food for Thought 1: Graphics

> We used to have a person who was responsible for the graphics elements, 
but
> he resigned due to too little time. Since then nobody has felt any
> responsibility for the graphics in KOffice, and the result is that we
> currently have a lot of missing icons. Also, I am not sure that the icons
> that we do have are neither well integrated with each other nor in Oxygen,
> even if I'm not sure that they are not either.
>
> Anyway, it would be very good if somebody could step up to coordinate this
> again within KOffice.
I'm already working with pinheiro, and some icons have even been commited 
already, so I have stepped up, and more will happen in the time until the 
release.

regarding the logos, I'm not liking that we we have seperatee app logos and I 
think we should push for the single KOffice logo to be used everywhere.

Re: Creating a buzz for KO2

On Wednesday 01 October 2008, Alexandra Leisse wrote:

> o Vimeo.com
> This is a video platform similar to YouTube.com. It provides the
> possibility to upload HD content though which adds a lot to the
> quality. ;) It is not yet as widely spread as YouTube, but I think the
> better quality makes up for that. Additional to that we could put up
> screencasts in different formats on the wiki/website for download to
> serve those who don't want to rely on flash installs.

Just as a side note on that topic.

About a week ago I did a screencast for Akonadi and uploaded the original OGG 
Vorbis to blip.tv
The site will host the original format as well as automatically convert it to 
Flash and offer both to its users, streaming and downloadable.

Cheers,
Kevin

--

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

_______________________________________________
koffice-devel mailing list
koffice-devel <at> kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel