public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Roy Bamford <neddyseagoon@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo Bugday
Date: Wed, 27 Feb 2013 19:12:29 +0000	[thread overview]
Message-ID: <1361992349.3007.0@NeddySeagoon> (raw)
In-Reply-To: <CAOgmxWyOg4cERMDoGOWaU=AWkXqf=AEuhF-J+HfAM9sHss52dA@mail.gmail.com> (from dastergon@gentoo.org on Wed Feb 27 00:39:14 2013)

[-- Attachment #1: Type: text/plain, Size: 1925 bytes --]

On 2013.02.27 00:39, Pavlos Ratis wrote:
> Hello everyone,
> 
> I would like to announce you a new try to 'revive' the Bugday event.
> As most of the open source projects have their own bugday, I thought
> it would be great to have this event back.  For those who don't know,
> its a monthly 24h event that takes place in #gentoo-bugs. Its goal is
> to close as many bugs as possible . You don't have to be a Gentoo
> expert to participate. Those days are a great way to start joining 
> the
> Gentoo community, improving Bugzilla's and Wiki's quality and looking
> for a mentor to begin the recruitment process. The upcoming bugday
> event is this Saturday and I hope this event will continue in the 
> next
> months. I have created a wiki page for the event[1] and I added some
> guidelines. I have also created a related blog post about the
> event[2].
> 
> I have listed some maintainer-wanted and maintainer-need bugs and
> Bugzilla admins also re-enabled the bugday flag. I would like to ask
> the Gentoo project teams to start using this flag to their bugs that
> think that are good to start and enable the flag at them. It would be
> great to a have a really big list with 'good to start' bugs.
> 
> It's the first time after a long time that this event will take 
> place,
> so I am looking forward to your participation both users and
> developers and your feedback.
> 
> [1] http://wiki.gentoo.org/wiki/Bugday
> [2] http://blog.dastergon.gr/gentoo-bugday/
> 
> Thanks,
> Pavlos
> 
> 

Pavlos,

I used to do a forums announce for the old bugday.  That can be revived 
too if you want.  The old bugday ran to a calender, so the announces 
went up a week beforehand.

Are you goings to stick to the first Saturday in the month ?

Good luck with the revived bugday.

-- 
Regards,

Roy Bamford
(Neddyseagoon) a member of
elections
gentoo-ops
forum-mods
trustees

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2013-02-27 19:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27  0:39 [gentoo-dev] Gentoo Bugday Pavlos Ratis
2013-02-27  2:01 ` "Paweł Hajdan, Jr."
2013-02-27  3:14 ` [gentoo-dev] " Michael Palimaka
2013-02-27  6:28   ` Alec Warner
2013-02-27 10:19     ` Theo Chatzimichos
2013-02-27 18:57       ` Pavlos Ratis
2013-02-27 19:00         ` Peter Stuge
2013-02-27 19:40           ` Tom Wijsman
2013-02-27 21:30             ` Peter Stuge
2013-02-27 23:04               ` Tom Wijsman
2013-02-28  0:20                 ` Peter Stuge
2013-02-28  1:07                   ` Tom Wijsman
2013-02-28  2:14                     ` Pavlos Ratis
2013-02-28 16:31                       ` Roy Bamford
2013-02-28 11:33               ` Sergey Popov
2013-02-28 15:47                 ` Pavlos Ratis
2013-02-27  9:07 ` [gentoo-dev] " Alexander Berntsen
2013-02-27 15:07   ` Peter Stuge
2013-02-27 19:12 ` Roy Bamford [this message]

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=1361992349.3007.0@NeddySeagoon \
    --to=neddyseagoon@gentoo.org \
    --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