1 |
The reply appears to have disappeared into a black hole. |
2 |
|
3 |
-------- Forwarded Message -------- |
4 |
> From: Christel Dahlskjaer <christel@g.o> |
5 |
> To: gentoo-dev@l.g.o |
6 |
> Subject: Re: [gentoo-dev] July Council Meeting: Requested Agenda Item |
7 |
> Date: Sat, 10 Jun 2006 13:26:31 +0100 |
8 |
> |
9 |
> On Sat, 2006-06-10 at 10:07 +0200, Lars Weiler wrote: |
10 |
> > Congratulations. I just unsubscribed from the |
11 |
> > gwn-feedback-alias after reading your mail. |
12 |
> > |
13 |
> > * Christel Dahlskjaer <christel@g.o> [06/06/10 04:28 +0100]: |
14 |
> > > 1. Reliability. The GWN claims to be a weekly publication, yet it |
15 |
> > > frequently fails to publish without prior warning. There was no edition |
16 |
> > > this week, and Patrick Lauer says that it is "unknown" whether there |
17 |
> > > will be an edition next week as Ulrich Plate is AWOL. |
18 |
> > |
19 |
> > Several times Kurt or I took over the job of publicing the |
20 |
> > GWN when Ulrich asked us. So, there is a backup, but he |
21 |
> > didn't asked for this week. |
22 |
> |
23 |
> I am glad to hear that backup has been used in the past, and I hope that |
24 |
> it will be again. |
25 |
> |
26 |
> > > 2. Permissions. Although it could be considered flattering that the GWN |
27 |
> > > should choose a developer's blog as inspiration for an article, they |
28 |
> > > should ensure that they have the developer / author's permission before |
29 |
> > > quoting them (see previous complaints by brix, ciaranm and others). |
30 |
> > > |
31 |
> > > I also believe that when posting an article or interview, a copy should |
32 |
> > > be sent to the relevant people to ensure that they are ok with what is |
33 |
> > > being posted (my dev of the week interview, for example, was rather |
34 |
> > > screwed up and misrepresentative). When someone contacts GWN to have |
35 |
> > > something corrected, it would be appreciated were the GWN staff to at |
36 |
> > > least deign to acknowledge receipt, even if for some reason they choose |
37 |
> > > not to honour the corrections or post a retraction (although refusing to |
38 |
> > > publish corrections is extremely insulting to those wronged). |
39 |
> > |
40 |
> > And I expect the same from you. You should ask the affected |
41 |
> > people first before starting a discussion about them on our |
42 |
> > public mailing lists. This is a device I can give you for |
43 |
> > further userrelations-activities. |
44 |
> |
45 |
> I have actually contacted Ulrich on several occasions, he chose not to |
46 |
> get back to me. And I have spoken a fair bit with Patrick, and from |
47 |
> speaking with Patrick it is quite obvious that the GWN could do with |
48 |
> some help, and I am hoping that my addressing the problems we can pool |
49 |
> together and find ways of helping them. |
50 |
> |
51 |
> > > 4. Credit. Care should be taken to ensure that crrect credit is given. |
52 |
> > |
53 |
> > It is. Either as "Author" or "Contributor". |
54 |
> |
55 |
> Or it is totally lacking, like in the above mentioned blog scenario. |
56 |
> |
57 |
> > > Another thing that concerns me is the way the articles are written. It |
58 |
> > > is blatanly obvious that the GWN writers are not native English speakers |
59 |
> > > as both the grammar and the flow of the articles is far from attractive. |
60 |
> > > Having read through the archives, I notice that there was once a time |
61 |
> > > when the GWN was a great publication, and I would like to think that it |
62 |
> > > could become great yet again; in its current state, though, it is doing |
63 |
> > > more harm than good. |
64 |
> > |
65 |
> > It's quite interesting to see, that the GWN and also |
66 |
> > Debian's Weekly Newsletter is run by Germans mostly. Is |
67 |
> > there a problem with native speakers to run a periodically |
68 |
> > newsletter for a long time (> 3 years)? |
69 |
> |
70 |
> No, there isn't a problem with it. However, as I understand it the GWN |
71 |
> is translated into N languages, and I would presume the german version |
72 |
> to be the one which reads better. Could it be an idea to have someone |
73 |
> whos first language is English look over and improve upon the English |
74 |
> version? I know we already dot the i's and cross the t's, maybe it would |
75 |
> be of benefit if someone worked a bit on how it flows. |
76 |
> |
77 |
> > > Lack of content and poorly written or incorrect articles are often |
78 |
> > > justified by the GWN team on grounds of overwork and insufficient |
79 |
> > > manpower. When I asked why they were not recruiting, I was informed that |
80 |
> > > no-one has any interest in contributing. Upon speaking with others, |
81 |
> > > however, I find that this is not the case -- people are interested, but |
82 |
> > > fear (and rightly so) that their work will be edited in such a way that |
83 |
> > > it is no longer something with which they want to be associated. |
84 |
> > |
85 |
> > Subscribe to the gwn-feedback-alias and read or comment the |
86 |
> > submissions to the GWN. Make sure that every user will |
87 |
> > receive and answer. And forward questions to the |
88 |
> > arch-teams. Isn't that userrel's job? I didn't saw your |
89 |
> > contributions there yet. |
90 |
> |
91 |
> I wasn't aware the gwn-feedback alias was public, if it is then I would |
92 |
> be more than happy to subscribe to it and read and comment to every |
93 |
> user. Would I be stepping on anyones toes by doing so? And if the GWN |
94 |
> would like to off-load some stuff onto Userrel, then userrel would be |
95 |
> more than happy to help. We already have a GWN representative and he |
96 |
> knows that several of the userrel team would jump at the chance to help |
97 |
> out with various GWN related bits. |