Re: DPN 02/2013 frozen. Please review and translate.

[Filipus Klutiero]

On 2013-01-18 18:59, Francesca Ciceri wrote:

Hi all,

we just finished the last bits of the new issue of DPN to be released
Monday. We would appreciate reviews and translations.

Instructions are available on the wiki:
http://wiki.debian.org/ProjectNews

As usual, the last updated version is available on the publicity
Subversion repository, even via HTTP:
http://anonscm.debian.org/viewvc/publicity/dpn/en/current/index.wml?view=co


Cheers,
Francesca



Thank you Francesca and everyone. Here are my remarks:


Ben Hutchings, member of the Debian Kernel team and maintainer of the
3.2.y stable series at kernel.org, wrote a series of three blogposts (http://womble.decadent.org.uk/blog/whats-in-the-linux-kernel-for-debian-70-wheezy-part-1.html";>part
1,
http://womble.decadent.org.uk/blog/whats-in-the-linux-kernel-for-debian-70-wheezy-part-2.html";>part
2,
http://womble.decadent.org.uk/blog/whats-in-the-linux-kernel-for-debian-70-wheezy-part-3.html";>part
3) about the additional features of the Debian Linux kernel that will be
shipped with the next Debian stable.


There are now several kernels in Debian; s/"Debian Kernel"/"Debian's Linux".
"3.2.y" is unclear. Just "3.2" will do.
"the additional features of the Debian Linux kernel that will be shipped 
with the next Debian stable" is unclear. We should explain that wheezy 
will ship a modified version of Linux 3.2 with features not present in 
vanilla Linux 3.2.



http://richardhartmann.de/blog/posts/2013/01/18-Debian_Release_Critical_Bug_report_for_Week_03/";
testing="249"
tobefixed="84" />


According to the source, there are actually 165 RC bugs to be fixed :-(


--
To UNSUBSCRIBE, email to debian-i18n-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50fc1e04.2070...@gmail.com

Re: DPN 02/2013 frozen. Please review and translate.

[Justin B Rye]

Filipus Klutiero wrote:
> Thank you Francesca and everyone. Here are my remarks:
> 
>> Ben Hutchings, member of the Debian Kernel team and maintainer of the
>> 3.2.y stable series at kernel.org, wrote a series of three blogposts (> href="http://womble.decadent.org.uk/blog/whats-in-the-linux-kernel-for-debian-70-wheezy-part-1.html";>part
>> 1,
>> > href="http://womble.decadent.org.uk/blog/whats-in-the-linux-kernel-for-debian-70-wheezy-part-2.html";>part
>> 2,
>> > href="http://womble.decadent.org.uk/blog/whats-in-the-linux-kernel-for-debian-70-wheezy-part-3.html";>part
>> 3) about the additional features of the Debian Linux kernel that will be
>> shipped with the next Debian stable.
> 
> There are now several kernels in Debian; s/"Debian Kernel"/"Debian's Linux".

In fact my last edit was adding the "Linux" lower down - partly just
to dilute the concentration of references to Debian.  I didn't add it
in the first line because the team really is called the "Debian
Kernel" team.

> "3.2.y" is unclear. Just "3.2" will do.

"3.2.y" is strange, I'll agree, but it's the name of the git tree as
mentioned in the postings... 3.2 would certainly be clearer if it's
true, but I've been treading carefully.

> "the additional features of the Debian Linux kernel that will be
> shipped with the next Debian stable" is unclear. We should explain
> that wheezy will ship a modified version of Linux 3.2 with features
> not present in vanilla Linux 3.2.

It doesn't need to explain *everything*, because after all it's
pointing at a source that does that, but I suppose we could insert
some extra hint in that direction.  I'll try:

 [...] about the additional features not featured in mainline 3.2 that will
 be included in the Linux kernel to be shipped with the next Debian stable.

-- 
JBR   A long time ago this practice was followed, especially in the
  upper classes, but today even the children of the lower classes
  perform no executions, and this is extreme negligence.
  - "Hagakure", Yamamoto Tsunetomo (1716)


-- 
To UNSUBSCRIBE, email to debian-i18n-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130120180309.ga7...@xibalba.demon.co.uk

Re: DPN 02/2013 frozen. Please review and translate.

[Filipus Klutiero]

Hi Justin,

On 2013-01-20 13:03, Justin B Rye wrote:

Filipus Klutiero wrote:

Thank you Francesca and everyone. Here are my remarks:


Ben Hutchings, member of the Debian Kernel team and maintainer of the
3.2.y stable series at kernel.org, wrote a series of three blogposts (http://womble.decadent.org.uk/blog/whats-in-the-linux-kernel-for-debian-70-wheezy-part-1.html";>part
1,
http://womble.decadent.org.uk/blog/whats-in-the-linux-kernel-for-debian-70-wheezy-part-2.html";>part
2,
http://womble.decadent.org.uk/blog/whats-in-the-linux-kernel-for-debian-70-wheezy-part-3.html";>part
3) about the additional features of the Debian Linux kernel that will be
shipped with the next Debian stable.

There are now several kernels in Debian; s/"Debian Kernel"/"Debian's Linux".

In fact my last edit was adding the "Linux" lower down - partly just
to dilute the concentration of references to Debian.  I didn't add it
in the first line because the team really is called the "Debian
Kernel" team.


If we want to call the team as it calls itself, I'd suggest using the 
official capitalization ("Debian Kernel Team"), using quotes or using 
italics.



"3.2.y" is unclear. Just "3.2" will do.

"3.2.y" is strange, I'll agree, but it's the name of the git tree as
mentioned in the postings... 3.2 would certainly be clearer if it's
true, but I've been treading carefully.


Hum, I didn't know upstream used "3.2.y", and I don't know if that's an 
official name, but I think anyway it would be best to stay as simple as 
possible - as long as it's equally precise.



"the additional features of the Debian Linux kernel that will be
shipped with the next Debian stable" is unclear. We should explain
that wheezy will ship a modified version of Linux 3.2 with features
not present in vanilla Linux 3.2.

It doesn't need to explain *everything*, because after all it's
pointing at a source that does that, but I suppose we could insert
some extra hint in that direction.  I'll try:

  [...] about the additional features not featured in mainline 3.2 that will
  be included in the Linux kernel to be shipped with the next Debian stable.



I agree. Great (except maybe "features not featured"? "features missing 
from" instead?).


Thank you


--
To UNSUBSCRIBE, email to debian-i18n-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50fc56b9@gmail.com

Re: DPN 02/2013 frozen. Please review and translate.

[Justin B Rye]

Filipus Klutiero wrote:
> If we want to call the team as it calls itself, I'd suggest using
> the official capitalization ("Debian Kernel Team"), using quotes or
> using italics.

The wiki page and so on are "Debian Kernel", so I'm not convinced it
needs caps on Team.  Note also the reference in the previous para to
"the Debian Med team" (and to Debian Med).

>> "3.2.y" is strange, I'll agree, but it's the name of the git tree as
>> mentioned in the postings... 3.2 would certainly be clearer if it's
>> true, but I've been treading carefully.
> 
> Hum, I didn't know upstream used "3.2.y", and I don't know if that's
> an official name, but I think anyway it would be best to stay as
> simple as possible - as long as it's equally precise.

If I could be confident it was equally precise I wouldn't need to be
careful.  Besides, we go on to draw a distinction between this and
"mainline" 3.2.

>>  [...] about the additional features not featured in mainline 3.2 that will
>>  be included in the Linux kernel to be shipped with the next Debian stable.
>>
> 
> I agree. Great (except maybe "features not featured"? "features
> missing from" instead?).

Oh, yes, thanks.  And I'll parenthesise it.
-- 
JBR For trifling occasions it is better to accomplish things
simply by yelling - "Hagakure", Yamamoto Tsunetomo (1716)


-- 
To UNSUBSCRIBE, email to debian-i18n-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130120205424.ga11...@xibalba.demon.co.uk

"Debian Kernel team" (Re: DPN 02/2013 frozen. Please review and translate.)

[Filipus Klutiero]

On 2013-01-20 15:54, Justin B Rye wrote:

Filipus Klutiero wrote:

If we want to call the team as it calls itself, I'd suggest using
the official capitalization ("Debian Kernel Team"), using quotes or
using italics.

The wiki page and so on are "Debian Kernel", so I'm not convinced it
needs caps on Team.


I'm not sure what you mean, but the DebianKernel page is at 
/Teams/DebianKernel. Calling it "DebianKernelTeam" would have put it at 
/Teams/DebianKernelTeam. Anyway, many pages on the wiki have a wiki 
style and shouldn't be taken too seriously.

   Note also the reference in the previous para to
"the Debian Med team" (and to Debian Med).



The Debian Med team is the team working on Debian Med (which is the 
official name of... Debian Med). If we refer to "the Debian Kernel team" 
in the same fashion, that implies we're referring to the team working on 
"Debian Kernel". But there's no such thing as "Debian Kernel".


[...]


--
To UNSUBSCRIBE, email to debian-i18n-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50fc64b6.3090...@gmail.com

Re: "Debian Kernel team" (Re: DPN 02/2013 frozen. Please review and translate.)

[Justin B Rye]

Filipus Klutiero wrote:
>> The wiki page and so on are "Debian Kernel", so I'm not convinced it
>> needs caps on Team.
> 
> I'm not sure what you mean, but the DebianKernel page is at
> /Teams/DebianKernel. Calling it "DebianKernelTeam" would have put it
> at /Teams/DebianKernelTeam. Anyway, many pages on the wiki have a
> wiki style and shouldn't be taken too seriously.
>
>>   Note also the reference in the previous para to
>> "the Debian Med team" (and to Debian Med).
> 
> The Debian Med team is the team working on Debian Med (which is the
> official name of... Debian Med). If we refer to "the Debian Kernel
> team" in the same fashion, that implies we're referring to the team
> working on "Debian Kernel". But there's no such thing as "Debian
> Kernel".

There's also a http://wiki.debian.org/DebianKernel pointing at
https://lists.debian.org/debian-kernel/, #debian-kernel on
irc.debian.org, and so on.

"Debian Kernel" is a bad name in at least two ways (it also
contributes to the DPN's annoying tendency to mention Debian several
times per sentence), but people do treat it more or less as a name for
the thing that particular team is concerned with, in the same way as
the QA team, the D-I team, and other lower-case-tee teams.

Next time if there happen to be several Upper-Case-Tee Teams in the
news it might look more sensible to standardise in that direction, but
for now I'm happy with how it is.
-- 
JBR Even if it seems certain that you will lose, retaliate.
Neither wisdom nor technique has a place in this.
  - "Hagakure", Yamamoto Tsunetomo (1716)


-- 
To UNSUBSCRIBE, email to debian-i18n-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130120223815.ga13...@xibalba.demon.co.uk

Re: DPN 02/2013 frozen. Please review and translate.

[Richard Hartmann]

On Sun, Jan 20, 2013 at 5:40 PM, Filipus Klutiero  wrote:


> According to the source, there are actually 165 RC bugs to be fixed :-(


(I am that source)

249 need to be fixed in total.

165 of those affect testing and unstable; 84 affect testing only.


Either way, it's too many and we are lagging behind the last cycle :/


Richard

Re: "Debian Kernel team" (Re: DPN 02/2013 frozen. Please review and translate.)

[Filipus Klutiero]

On 2013-01-20 17:38, Justin B Rye wrote:

Filipus Klutiero wrote:

The wiki page and so on are "Debian Kernel", so I'm not convinced it
needs caps on Team.

I'm not sure what you mean, but the DebianKernel page is at
/Teams/DebianKernel. Calling it "DebianKernelTeam" would have put it
at /Teams/DebianKernelTeam. Anyway, many pages on the wiki have a
wiki style and shouldn't be taken too seriously.


   Note also the reference in the previous para to
"the Debian Med team" (and to Debian Med).

The Debian Med team is the team working on Debian Med (which is the
official name of... Debian Med). If we refer to "the Debian Kernel
team" in the same fashion, that implies we're referring to the team
working on "Debian Kernel". But there's no such thing as "Debian
Kernel".

There's also a http://wiki.debian.org/DebianKernel pointing at
https://lists.debian.org/debian-kernel/, #debian-kernel on
irc.debian.org, and so on.
The debian-kernel mailing list follows our mailing list naming 
conventions, i.e. debian-foo, which go back to when these were hosted by 
Pixar. Similarly, our IRC channels generally start with "debian-" so 
they're in a pseudo-namespace (which used to be particularly useful 
before irc.debian.org became OFTC). That doesn't mean "Debian French", 
for example, means something.


[...]


--
To UNSUBSCRIBE, email to debian-i18n-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50fcac25.50...@gmail.com

"tobefixed" wrong (Re: DPN 02/2013 frozen. Please review and translate.)

[Filipus Klutiero]

Hi Richard,

On 2013-01-20 18:19, Richard Hartmann wrote:
On Sun, Jan 20, 2013 at 5:40 PM, Filipus Klutiero > wrote:


According to the source, there are actually 165 RC bugs to be
fixed :-(


(I am that source)

249 need to be fixed in total.


According to the post quoted:

*Affecting wheezy and unstable: 165 
* 
Those need someone to find a fix, or to finish the work to upload a 
fix to unstable: 


249 is our best approximation of the number of RC bugs in wheezy - 
whether or not they're already fixed and just waiting for testing 
migration. That's the value we call "testing".


[...]