From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Attracting developers (Re: Packages up for grabs...)
Date: Tue, 18 Dec 2012 08:44:23 +0000 [thread overview]
Message-ID: <CAG2jQ8i_dO1YEHj-LnB=EW8zE_Mza4rERNxK+=3UrP2M73jxog@mail.gmail.com> (raw)
In-Reply-To: <20121217221326.23040.qmail@stuge.se>
On 17 December 2012 22:13, Peter Stuge <peter@stuge.se> wrote:
> Duncan wrote:
>> Apparently, IRC is a hard requirement. At least the one final
>> evaluation must be done on IRC.
>
> I understand why online communication is not everyone's prefered format.
>
> I guess that the IRC part of the recruitment is not very formal, I
> don't know as I haven't seen one, but in general I would expect that
> it is simply a lightweight substitute for going to the pub and having
> a chat in person, or talking on the phone to a friend.
>
> I further guess that if you would prefer a chat with someone over the
> phone then that could work just as well.
>
> That said, I find that IRC is a useful tool for developers sometimes.
> It's not mandatory by any means, and sometimes it's just a huge time
> sink, and a little bit like filing bugs it isn't mandatory, but it
> *can* be useful.
>
>
> //Peter
>
Nowadays, I use google docs ( and I am also open to g+ and skype
interviews as well ). So IRC is not an absolute requirement.
--
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
next prev parent reply other threads:[~2012-12-18 8:45 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 16:57 [gentoo-dev] Attracting developers (Re: Packages up for grabs...) Michael Orlitzky
2012-12-16 17:02 ` Fabian Groffen
2012-12-16 17:20 ` Michael Orlitzky
2012-12-16 17:23 ` Fabian Groffen
2012-12-16 17:40 ` Michael Orlitzky
2012-12-16 17:54 ` Fabian Groffen
2012-12-16 18:27 ` [gentoo-dev] " Duncan
2012-12-16 23:40 ` Michael Orlitzky
2012-12-16 18:43 ` [gentoo-dev] " Kacper Kowalik
2012-12-16 21:30 ` Michał Górny
2012-12-16 21:32 ` Michał Górny
2012-12-16 23:43 ` Michael Orlitzky
2012-12-16 22:16 ` Richard Yao
2012-12-16 17:33 ` Samuli Suominen
2012-12-16 17:49 ` Damien Levac
2012-12-16 19:28 ` [gentoo-dev] " Duncan
2012-12-17 22:13 ` Peter Stuge
2012-12-18 8:44 ` Markos Chandras [this message]
2012-12-18 9:26 ` Duncan
2012-12-16 22:34 ` [gentoo-dev] " Pacho Ramos
2012-12-16 22:44 ` Damien Levac
2012-12-16 18:53 ` Andreas K. Huettel
2012-12-16 23:47 ` Michael Orlitzky
2012-12-17 10:43 ` Markos Chandras
2012-12-17 12:31 ` Dirkjan Ochtman
2012-12-17 15:15 ` Markos Chandras
2012-12-17 18:32 ` Roy Bamford
2012-12-17 21:35 ` Dirkjan Ochtman
2012-12-17 22:34 ` Rich Freeman
2012-12-17 14:08 ` Rich Freeman
2012-12-17 15:35 ` Markos Chandras
2013-01-05 5:47 ` Donnie Berkholz
2013-01-05 16:46 ` Roy Bamford
2013-01-05 17:03 ` Andreas K. Huettel
2013-01-05 18:55 ` Alec Warner
2013-01-05 20:29 ` Rich Freeman
2013-01-06 8:14 ` Aaron Bauman
2013-01-06 4:14 ` Donnie Berkholz
2013-01-06 20:49 ` Michael Orlitzky
2013-01-06 21:54 ` "Paweł Hajdan, Jr."
2012-12-16 19:04 ` Markos Chandras
2012-12-16 19:14 ` Michael Mol
2012-12-16 19:28 ` Alec Warner
2012-12-17 9:43 ` Markos Chandras
2012-12-17 20:11 ` Jeroen Roovers
2012-12-17 0:10 ` Michael Orlitzky
2012-12-17 1:20 ` Patrick Lauer
2012-12-17 5:07 ` Brian Dolbec
2012-12-17 9:33 ` Markos Chandras
2012-12-17 9:40 ` Michał Górny
2012-12-17 12:17 ` Markos Chandras
2012-12-19 6:56 ` Jeroen Roovers
2012-12-19 9:03 ` Michał Górny
2012-12-19 12:08 ` Markos Chandras
2012-12-26 16:39 ` Kent Fredric
2012-12-27 0:32 ` Jeroen Roovers
2012-12-27 1:49 ` Peter Stuge
2012-12-27 6:30 ` Kent Fredric
2012-12-27 13:05 ` Rich Freeman
2012-12-28 11:00 ` Patrick Lauer
2012-12-29 8:42 ` Ben de Groot
2012-12-29 16:13 ` Brian Dolbec
2012-12-29 16:22 ` Rich Freeman
2012-12-31 8:46 ` Ben de Groot
2012-12-31 11:43 ` Theo Chatzimichos
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='CAG2jQ8i_dO1YEHj-LnB=EW8zE_Mza4rERNxK+=3UrP2M73jxog@mail.gmail.com' \
--to=hwoarang@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