New Features List

l10n
#1

Hi,

can somebody explain me how the New Features page[1] has been compiled?

1) Where do the developers list new features?
2) Who does it "translate" into a human readable draft feature list?
   (assumed: Wiki[2])
3) What about this page
   http://wiki.documentfoundation.org/Development/Weekly_Summary ?
4) Who transforms the draft feature list[2] into a user-friendly &
marketing-approved website announcement page[1]?

And finally 5)
Is the above process documented somewhere?

Thanks
Nino

[1] http://www.libreoffice.org/download/new-features-and-fixes/
[2]
http://wiki.documentfoundation.org/Marketing/LibOReleaseEvents/LOPressKit/FeatureList3.3

#2

Hi Nino,

Hi,

can somebody explain me how the New Features page[1] has been compiled?

with a lot of pain this time for sure :wink: I've work on the OOo one for several years without having to dig so much...

1) Where do the developers list new features?

in there commits and there is a weekly summary provided each week on the dev list (my personal thanks go to Kohei commits: clear, shorts and descriptives :slight_smile:

2) Who does it "translate" into a human readable draft feature list?
    (assumed: Wiki[2])

This time it was me, but that was done in emergency for the needs of the different groups (l10n/QA/Doc/Marketing) so it was not really human readable, Marc Paré has help to list it with the OOo features on the wiki, then some others help to complete it.

3) What about this page
    http://wiki.documentfoundation.org/Development/Weekly_Summary ?

this was the basis for the work

4) Who transforms the draft feature list[2] into a user-friendly&
marketing-approved website announcement page[1]?

Michael Meeks because nobody else did the job. I think Thorsten polished it tonight. Mark Morin is working on the screen shots and I'll try to finish screen shots tonight too.

And finally 5)
Is the above process documented somewhere?

Not yet because that was not a good process.

If you can wait a bit until the 3.3 is out, I then have already work on a process with developers (at least Thorsten) to have a much better list (a BZ number for each feature open, managed by QA people and a script to retrieve the list).
Then there should be really less work needed to add details and the list will be ready and useful for all groups at feature freeze.

Well now finally I have a question:
Why all these questions? :slight_smile: Would you like to work on it the next time?

Kind regards
Sophie

#3

Hi Sophie,

thanks for answering,

> 1) Where do the developers list new features?

in there commits and there is a weekly summary provided each week on
the dev list (my personal thanks go to Kohei commits: clear, shorts
and descriptives :slight_smile:

ok

> 2) Who does it "translate" into a human readable draft feature
> list? (assumed: Wiki[2])

This time it was me, but that was done in emergency for the needs of
the different groups (l10n/QA/Doc/Marketing) so it was not really
human readable, Marc Paré has help to list it with the OOo features
on the wiki, then some others help to complete it.

ok

> 3) What about this page
> http://wiki.documentfoundation.org/Development/Weekly_Summary ?

this was the basis for the work

but has not been continued any more since week 44?

> 4) Who transforms the draft feature list[2] into a user-friendly&
> marketing-approved website announcement page[1]?

Michael Meeks because nobody else did the job. I think Thorsten
polished it tonight. Mark Morin is working on the screen shots and
I'll try to finish screen shots tonight too.

Ok, then it is "qa-ed" by the developers, that's fine. (No doubt about
your competence but just wanting to know it)

> And finally 5)
> Is the above process documented somewhere?

Not yet because that was not a good process.

If you can wait a bit until the 3.3 is out, I then have already work
on a process with developers (at least Thorsten) to have a much
better list (a BZ number for each feature open, managed by QA people
and a script to retrieve the list).

Fine.

Then there should be really less work needed to add details and the
list will be ready and useful for all groups at feature freeze.

Well now finally I have a question:

You're wellcome :slight_smile:

Why all these questions?

1) Because I did not find the process documented

:slight_smile: Would you like to work on it the next
time?

2) No. I'm not an english native speaker nor *OfficeSuite specialist :wink:

3) But I love transparent processes, so anybody can reproduce and
understand them (quality by obviousness) and participating is made easy

and finally (the real selfish reason :wink: )
4) We are translating the page (into German) and were asking us, at what
stage the translation makes sense.

Nino

#4

Hi Nino,

Hi Sophie,

thanks for answering,

1) Where do the developers list new features?

in there commits and there is a weekly summary provided each week on
the dev list (my personal thanks go to Kohei commits: clear, shorts
and descriptives :slight_smile:

ok

2) Who does it "translate" into a human readable draft feature
list? (assumed: Wiki[2])

This time it was me, but that was done in emergency for the needs of
the different groups (l10n/QA/Doc/Marketing) so it was not really
human readable, Marc Paré has help to list it with the OOo features
on the wiki, then some others help to complete it.

ok

3) What about this page
     http://wiki.documentfoundation.org/Development/Weekly_Summary ?

this was the basis for the work

but has not been continued any more since week 44?

this was feature freeze. In the dev process, once feature freeze date appears, their is l10n/QA/Doc/Marketing tasks that can be consolidated, because no new features won't be added, only code fixes will appear in the product.

4) Who transforms the draft feature list[2] into a user-friendly&
marketing-approved website announcement page[1]?

Michael Meeks because nobody else did the job. I think Thorsten
polished it tonight. Mark Morin is working on the screen shots and
I'll try to finish screen shots tonight too.

Ok, then it is "qa-ed" by the developers, that's fine. (No doubt about
your competence but just wanting to know it)

oh, it's ok. I've sent the list to the dev@ list to make sure I didn't forget somebody's baby or change it too much :wink:

And finally 5)
Is the above process documented somewhere?

Not yet because that was not a good process.

If you can wait a bit until the 3.3 is out, I then have already work
on a process with developers (at least Thorsten) to have a much
better list (a BZ number for each feature open, managed by QA people
and a script to retrieve the list).

Fine.

Then there should be really less work needed to add details and the
list will be ready and useful for all groups at feature freeze.

Well now finally I have a question:

You're wellcome :slight_smile:

:slight_smile:

Why all these questions?

1) Because I did not find the process documented

:slight_smile: Would you like to work on it the next
time?

2) No. I'm not an english native speaker nor *OfficeSuite specialist :wink:

few of us are here :wink:

3) But I love transparent processes, so anybody can reproduce and
understand them (quality by obviousness) and participating is made easy

yes, that will be, because I don't want to spend my time here too :wink:

and finally (the real selfish reason :wink: )
4) We are translating the page (into German) and were asking us, at what
stage the translation makes sense.

the list as is imho doesn't make much sense. It needs more details/love to transform it on a marketing or documentation tool.

Kind regards
Sophie

#5

Hi Sophie,

> http://wiki.documentfoundation.org/Development/Weekly_Summary
> ... has not been continued any more since week 44?

this was feature freeze.

ok, I see.

In the dev process, once feature freeze date
appears, their is l10n/QA/Doc/Marketing tasks that can be
consolidated, because no new features won't be added, only code fixes
will appear in the product.

It was not that clear to me, but now it is :slight_smile:

>>> 4) Who transforms the draft feature list[2] into a user-friendly&
>>> marketing-approved website announcement page[1]?
>>
>> Michael Meeks because nobody else did the job. I think Thorsten
>> polished it tonight. Mark Morin is working on the screen shots and
>> I'll try to finish screen shots tonight too.
>
> Ok, then it is "qa-ed" by the developers, that's fine. (No doubt
> about your competence but just wanting to know it)

oh, it's ok. I've sent the list to the dev@ list to make sure I
didn't forget somebody's baby or change it too much :wink:

ok :slight_smile:

[...]

>> :slight_smile: Would you like to work on it the next time?
>
> 2) No. I'm not an english native speaker nor *OfficeSuite
> specialist :wink:

few of us are here :wink:

touché :wink:

> 3) But I love transparent processes, so anybody can reproduce and
> understand them (quality by obviousness) and participating is made
> easy

yes, that will be, because I don't want to spend my time here too :wink:

looking foreward to the new process :slight_smile:

> and finally (the real selfish reason :wink: )
> 4) We are translating the page (into German) and were asking us, at
> what stage the translation makes sense.

the list as is imho doesn't make much sense. It needs more
details/love to transform it on a marketing or documentation tool.

That's approximately what we discovered :slight_smile:

Nino