From: Man Shankar <man.ee.gen@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] PR Project Activity Issues
Date: Tue, 27 Jan 2009 16:38:49 +0530 [thread overview]
Message-ID: <20090127110849.GB8839@gentoo.mychoice> (raw)
In-Reply-To: <b41005390901262351r135158b1y4f3741f3bca52a88@mail.gmail.com>
On 23:51 Mon 26 Jan , Alec Warner wrote:
---- [snipped] ----
> A long time ago I suggested some sort of pr-onduty role where
> basically for a set period you are the prime pr contact and if someone
> has news it is your job to review and post it or reject it. This was
> never implemented; but may be a good idea if we are limited by commit
> access. One of the main problems with posting to an alias is that you
> can always not reply and it will become someone else's problem(TM)
> until no one replies and the message is ignored.
+1
Recently, i had started a thread here on -dev regarding the newsletter.
I was asked to post to gmn-feedback. Sorry, haven't heard from them as
yet. I wonder a pr-onduty may have worked!
>
> I for one almost never read pr@ because it is mostly spam and it is
> difficult to locate useful requests from crap. It may be useful to
> tag important items with NEWS ITEM or UPDATE or something.
>
> If GuideXML makes it hard to post we can perhaps develop a technical solution.
>
> If there is not enough content I'm sure we can brainstorm ideas on
> what we could do (index2 covers this area pretty well IMHO).
I doubt lack of content to be the real issue. As the OP mentions, if such a
problem exists why not ask for help from the community in a more direct way.
Maybe, something like the monthly reminders we get for the council-meeting.
To back up the fact that lack of content should be a non-issue is the
following excerpt from the thread i mentioned:
Nathan Zachary <kalos@gentoo.org> wrote:
I would be happy to help out with the newsletter, especially
with the "one article."
So, see, people are willing to help with the content. Their prowess needs
to be utilized and channeled, i guess.
> But mostly I want to address concrete problems.
>
> -Alec
>
--
Thanks & Regards,
Man Shankar <man.ee.gen(at)gmail.com>
next prev parent reply other threads:[~2009-01-27 11:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 21:30 [gentoo-dev] PR Project Activity Issues AllenJB
2009-01-27 2:46 ` Jesus Rivero
2009-01-27 4:28 ` Douglas Anderson
2009-01-27 4:47 ` Alec Warner
2009-01-27 5:50 ` [gentoo-dev] " Ryan Hill
2009-01-27 6:21 ` Josh Saddler
2009-01-27 8:17 ` [gentoo-dev] " AllenJB
2009-01-27 9:55 ` Alec Warner
2009-01-27 11:38 ` Tobias Scherbaum
2009-01-31 6:20 ` Donnie Berkholz
2009-02-01 7:35 ` Alec Warner
2009-02-02 4:53 ` Donnie Berkholz
2009-01-27 6:07 ` Donnie Berkholz
2009-01-27 7:17 ` Ben de Groot
2009-01-27 7:51 ` Alec Warner
2009-01-27 11:08 ` Man Shankar [this message]
2009-01-27 16:38 ` Nathan Zachary
2009-01-27 8:42 ` AllenJB
2009-01-31 6:24 ` Donnie Berkholz
2009-01-30 12:02 ` djay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090127110849.GB8839@gentoo.mychoice \
--to=man.ee.gen@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox