headers
Roberto C. Sánchez | 2 May 2007 01:03
Favicon

Proposed name change for DWN

Hello,

I notice that Debian Weekly News is still called Debian Weekly News,
even though it is not published weekly.  Perhaps we should consider
changing the name to something like the Debian Newsletter?

Regards,

-Roberto

--

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com
Permalink | Reply | 4 comments |
headers
Alexander Schmehl | 2 May 2007 12:16

Re: Proposed name change for DWN

Hi!

* Roberto C. Sánchez <roberto <at> connexer.com> [070502 01:03]:

> I notice that Debian Weekly News is still called Debian Weekly News,
> even though it is not published weekly.  Perhaps we should consider
> changing the name to something like the Debian Newsletter?

Or find more volunteers to contribute to it, so it can be send out on a
weekly basis again?

Yours sincerely,
  Alexander
Permalink | Reply | 3 comments |
headers
Loïc Minier | 2 May 2007 12:25
Picon
Picon

Re: Proposed name change for DWN

On Wed, May 02, 2007, Alexander Schmehl wrote:
> > I notice that Debian Weekly News is still called Debian Weekly News,
> > even though it is not published weekly.  Perhaps we should consider
> > changing the name to something like the Debian Newsletter?
> Or find more volunteers to contribute to it, so it can be send out on a
> weekly basis again?

 Which obviously didn't happen in the last 6 months?  Plus, whatever the
 amount of contributions, DWN doesn't seem to go out when it reached n
 items, but simply at random, so why call it "weekly" indeed?

-- 
Loïc Minier

--

-- 
To UNSUBSCRIBE, email to debian-project-REQUEST <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org
Permalink | Reply | 2 comments |
headers
Felipe Augusto van de Wiel (faw | 2 May 2007 16:56

Re: Proposed name change for DWN


On 05/02/2007 07:25 AM, Loïc Minier wrote:
> On Wed, May 02, 2007, Alexander Schmehl wrote:
>>> I notice that Debian Weekly News is still called Debian Weekly News,
>>> even though it is not published weekly.  Perhaps we should consider
>>> changing the name to something like the Debian Newsletter?
>> Or find more volunteers to contribute to it, so it can be send out on a
>> weekly basis again?
> 
>  Which obviously didn't happen in the last 6 months?  Plus, whatever the
>  amount of contributions, DWN doesn't seem to go out when it reached n
>  items, but simply at random, so why call it "weekly" indeed?

	Is not that simple. It need to hit "n" items on a pre-defined
date to allow peer-review and preparation.

	Joey keeps a very high standard for DWN and it requires some
time to learn how to work on it. Also, for years we had almost only
one DWN editor, the process to split the load and share the tasks
took some time and there are some definitions that were not clear
and, IMHO, we helped to improve that (but better listen from Joey).

	Learn the timelines, quality control, how to contribute, what
to contribute, the ideal DWN, number of paragraphs, size of it and
so on, takes more then two weeks. I got really sad when after a lot
of contributions Joey disappeared for a while without notice. That
makes me stop contributing for a while, yesterday when I saw a new
DWN, I start collecting items that I missed and I'm preparing them
again to submit. Hopefully, I think we can start having DWN weekly
again, so let's try. :-)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Anthony Towns | 2 May 2007 17:36
Picon

Re: Proposed name change for DWN

On Wed, May 02, 2007 at 11:56:02AM -0300, Felipe Augusto van de Wiel (faw) wrote:
> Hopefully, I think we can start having DWN weekly
> again, so let's try. :-)

The DWN contribution howto is at:

    http://www.debian.org/News/weekly/contributing

The most relevant points are probably:

    Right after an issue of DWN is released, Joey will start with an
    empty new issue. The issue is online at Joey's private website which
    is available using anonymous CVS as well. Check it out using  

	cvs -d :pserver:anonymous <at> cvs.infodrom.org:/var/cvs/infodrom.org \
          co -d dwn public_html/src/Writing/DWN
        (empty password for cvs login)

and

    Anybody, who would like to add an item to DWN or who has an issue
    that should be mentioned in the next DWN, should contact us* at any
    time with enough information.

     * mailto:dwn <at> debian.org

Cheers,
aj
(Continue reading)

Permalink | Reply | 0 comments |
headers
Adrian von Bidder | 4 May 2007 07:54
X-Face
Picon

Re: looking to buy an ad on packages.debian.org

Hi Megan,

On Tuesday 24 April 2007 16.17:52 Megan Farnum wrote:
> id like to buy an ad for a company that sells barcode scanners. i was
> thinking about placing the ad on your barcode package page:

As David already said: the debian.org web pages are not for sale.

But here's a deal for you: You check that your barcode scanners work with 
Linux (shouldn't be too hard - most barcode scanners behave just like 
keyboards.  Should take a Linux software engineer not more than a day to 
check and also write a very short example code).  Then you take the Debian 
logo from <http://www.debian.org/logos/> (the swirl, without the bottle) 
and place it on your web site, and you can put out a press release that 
your Devices support Debian GNU/Linux.  As you can see on your logos web 
page, you can freely use our Logo to refer to the Debian project.

There are some lists of Linux compatible hardware on the web, I guess you 
can add your device to those lists, too (always provided that they work.) 
(One such list is <http://www.linuxcompatible.org/>, haven't looked but I 
assume there are some others.)

greetings
-- vbi

--

-- 
Wie man sein Kind nicht nennen sollte:
  Rod Kraut
Permalink | Reply | 0 comments |
headers
Aurelien Jarno | 8 May 2007 12:05

Some thoughts on the ARM build daemons

Hi all,

The ARM port is getting bad [1], the percentage of packages built
staying a bit more than 90% for 2 weeks. Also this is confirmed by a
message on #debian-arm this morning:

09:30 < doko> please could somebody care about the python2.4, python2.5,
binutils, gcc-4.1 and gcj-4.1 builds for arm? for gcj-4.1, please see
the instructions posted on debian-ports/debian-gcc

gcj-4.1 has to be bootstrapped manually (after python is installable
again), but all other packages have not been built on ARM. They are
blocked by python being uninstallable, but python2.4 is on position 115!
in the list of packages to build.

The problems mainly comes from the build daemons. Only *3 out of 7* are
building packages, and one of the three is also building stable-security
from time to time.

Here are the states and reasons I have been able to found on the web and
on IRC:
- grieg: up, building packages
- cats: up, building packages
- tofee: up, building packages, sometimes stable-security.
- smackdown: down, waiting for a 2.6 kernel
- elara: down, waiting for bug#421037
- europa: down, waiting for bug#421037
- netwinder: down, waiting for bug#421037, but seems to be unaffected
  by this bug
(Continue reading)

Permalink | Reply | 36 comments |
headers
Wookey | 8 May 2007 13:02
Picon
Favicon

Re: Some thoughts on the ARM build daemons

On 2007-05-08 12:05 +0200, Aurelien Jarno wrote:
> Hi all,
> 
> The ARM port is getting bad [1], the percentage of packages built
> staying a bit more than 90% for 2 weeks. Also this is confirmed by a
> message on #debian-arm this morning:
> 
> 09:30 < doko> please could somebody care about the python2.4, python2.5,
> binutils, gcc-4.1 and gcj-4.1 builds for arm? for gcj-4.1, please see
> the instructions posted on debian-ports/debian-gcc
> 
> gcj-4.1 has to be bootstrapped manually (after python is installable
> again), but all other packages have not been built on ARM. They are
> blocked by python being uninstallable, but python2.4 is on position 115!
> in the list of packages to build.
> 
> The problems mainly comes from the build daemons. Only *3 out of 7* are
> building packages, and one of the three is also building stable-security
> from time to time.
> 
> Here are the states and reasons I have been able to found on the web and
> on IRC:
> - grieg: up, building packages
> - cats: up, building packages
> - tofee: up, building packages, sometimes stable-security.
> - smackdown: down, waiting for a 2.6 kernel
> - elara: down, waiting for bug#421037
> - europa: down, waiting for bug#421037
> - netwinder: down, waiting for bug#421037, but seems to be unaffected
>   by this bug
(Continue reading)

Permalink | Reply | 7 comments |
headers
Lennert Buytenhek | 8 May 2007 13:21

Re: Some thoughts on the ARM build daemons

On Tue, May 08, 2007 at 12:05:01PM +0200, Aurelien Jarno wrote:

> The ARM port is getting bad [1], the percentage of packages built
> staying a bit more than 90% for 2 weeks.

As to my thoughts about the Debian ARM port: I think there are more
than enough people who care about the ARM port and want to help, but
there doesn't seem to be a way for those people to do the work that
needs doing.

I.e. submitting bugs and providing patches aren't going to fix the
issues that the Debian ARM port currently has.
Permalink | Reply | 0 comments |
headers
Aurelien Jarno | 8 May 2007 15:09

Re: Some thoughts on the ARM build daemons

Wookey a écrit :
> On 2007-05-08 12:05 +0200, Aurelien Jarno wrote:
>> Hi all,
>>
>> The ARM port is getting bad [1], the percentage of packages built
>> staying a bit more than 90% for 2 weeks. Also this is confirmed by a
>> message on #debian-arm this morning:
>>
>> 09:30 < doko> please could somebody care about the python2.4, python2.5,
>> binutils, gcc-4.1 and gcj-4.1 builds for arm? for gcj-4.1, please see
>> the instructions posted on debian-ports/debian-gcc
>>
>> gcj-4.1 has to be bootstrapped manually (after python is installable
>> again), but all other packages have not been built on ARM. They are
>> blocked by python being uninstallable, but python2.4 is on position 115!
>> in the list of packages to build.
>>
>> The problems mainly comes from the build daemons. Only *3 out of 7* are
>> building packages, and one of the three is also building stable-security
>> from time to time.
>>
>> Here are the states and reasons I have been able to found on the web and
>> on IRC:
>> - grieg: up, building packages
>> - cats: up, building packages
>> - tofee: up, building packages, sometimes stable-security.
>> - smackdown: down, waiting for a 2.6 kernel
>> - elara: down, waiting for bug#421037
>> - europa: down, waiting for bug#421037
>> - netwinder: down, waiting for bug#421037, but seems to be unaffected
(Continue reading)

Permalink | Reply | 2 comments |

Gmane