| 1 |
Man Shankar wrote: |
| 2 |
> On 23:51 Mon 26 Jan , Alec Warner wrote: |
| 3 |
> ---- [snipped] ---- |
| 4 |
> |
| 5 |
> |
| 6 |
>> A long time ago I suggested some sort of pr-onduty role where |
| 7 |
>> basically for a set period you are the prime pr contact and if someone |
| 8 |
>> has news it is your job to review and post it or reject it. This was |
| 9 |
>> never implemented; but may be a good idea if we are limited by commit |
| 10 |
>> access. One of the main problems with posting to an alias is that you |
| 11 |
>> can always not reply and it will become someone else's problem(TM) |
| 12 |
>> until no one replies and the message is ignored. |
| 13 |
>> |
| 14 |
> +1 |
| 15 |
> Recently, i had started a thread here on -dev regarding the newsletter. |
| 16 |
> I was asked to post to gmn-feedback. Sorry, haven't heard from them as |
| 17 |
> yet. I wonder a pr-onduty may have worked! |
| 18 |
> |
| 19 |
> |
| 20 |
>> I for one almost never read pr@ because it is mostly spam and it is |
| 21 |
>> difficult to locate useful requests from crap. It may be useful to |
| 22 |
>> tag important items with NEWS ITEM or UPDATE or something. |
| 23 |
>> |
| 24 |
>> If GuideXML makes it hard to post we can perhaps develop a technical solution. |
| 25 |
>> |
| 26 |
>> If there is not enough content I'm sure we can brainstorm ideas on |
| 27 |
>> what we could do (index2 covers this area pretty well IMHO). |
| 28 |
>> |
| 29 |
> |
| 30 |
> I doubt lack of content to be the real issue. As the OP mentions, if such a |
| 31 |
> problem exists why not ask for help from the community in a more direct way. |
| 32 |
> Maybe, something like the monthly reminders we get for the council-meeting. |
| 33 |
> To back up the fact that lack of content should be a non-issue is the |
| 34 |
> following excerpt from the thread i mentioned: |
| 35 |
> |
| 36 |
> Nathan Zachary <kalos@g.o> wrote: |
| 37 |
> I would be happy to help out with the newsletter, especially |
| 38 |
> with the "one article." |
| 39 |
> |
| 40 |
> So, see, people are willing to help with the content. Their prowess needs |
| 41 |
> to be utilized and channeled, i guess. |
| 42 |
> |
| 43 |
>> But mostly I want to address concrete problems. |
| 44 |
>> |
| 45 |
>> -Alec |
| 46 |
>> |
| 47 |
>> |
| 48 |
> |
| 49 |
> |
| 50 |
The more I look at the discussion lists, the less I want to contribute. |
| 51 |
I understand that correcting someone for posting to the wrong list is |
| 52 |
expected, but the way that it is done is equally as important. For |
| 53 |
instance, saying "Firstly, it's wonderful that you'd like to help with |
| 54 |
project X. You might get a better response if you offer a submission to |
| 55 |
such and such list instead." is radically more beneficial than "Wrong |
| 56 |
list; check the website before cluttering the discussion lists." |
| 57 |
|
| 58 |
I joined the forum staff because I had not witnessed that type of |
| 59 |
superiority there. Rather, I had seen a willingness for users and |
| 60 |
developers to help each other out with questions, comments, or concerns. |
| 61 |
I'm hoping that this trend doesn't continue. |
| 62 |
|
| 63 |
Regarding the original topic, I think a reminder on the forum and on the |
| 64 |
mailing lists would be great for the newsletter. At my place of |
| 65 |
employment, there is an email sent out to everyone saying something |
| 66 |
along the lines of "don't forget to submit your ideas for the January |
| 67 |
newsletter," and so on. If such a reminder is sent out a few days |
| 68 |
beforehand, there might be a better response to submission requests. |
| 69 |
|
| 70 |
--Zach |
Archives