Message from discussion
Job posts and Node.js mailing list guidelines (was: PHP/MongoDB Developer - Pants optional)
Received: by 10.42.145.129 with SMTP id f1mr2805384icv.62.1309129123983;
Sun, 26 Jun 2011 15:58:43 -0700 (PDT)
X-BeenThere: nodejs@googlegroups.com
Received: by 10.231.160.132 with SMTP id n4ls4787349ibx.0.gmail; Sun, 26 Jun
2011 15:58:34 -0700 (PDT)
Received: by 10.42.141.7 with SMTP id m7mr2771781icu.37.1309129114492;
Sun, 26 Jun 2011 15:58:34 -0700 (PDT)
Received: by 10.42.141.7 with SMTP id m7mr2771780icu.37.1309129114481;
Sun, 26 Jun 2011 15:58:34 -0700 (PDT)
Return-Path: <d...@deanlandolt.com>
Received: from mail-iw0-f169.google.com (mail-iw0-f169.google.com [209.85.214.169])
by gmr-mx.google.com with ESMTPS id k1si1939770icn.4.2011.06.26.15.58.33
(version=TLSv1/SSLv3 cipher=OTHER);
Sun, 26 Jun 2011 15:58:33 -0700 (PDT)
Received-SPF: neutral (google.com: 209.85.214.169 is neither permitted nor denied by best guess record for domain of d...@deanlandolt.com) client-ip=209.85.214.169;
Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 209.85.214.169 is neither permitted nor denied by best guess record for domain of d...@deanlandolt.com) smtp.mail=d...@deanlandolt.com
Received: by iwn8 with SMTP id 8so5032182iwn.14
for <nodejs@googlegroups.com>; Sun, 26 Jun 2011 15:58:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.114.79 with SMTP id d15mr5326204ibq.186.1309129112852;
Sun, 26 Jun 2011 15:58:32 -0700 (PDT)
Received: by 10.231.79.203 with HTTP; Sun, 26 Jun 2011 15:58:32 -0700 (PDT)
In-Reply-To: <BANLkTimvJUiuqfnO9WNO8_1di31dkD1XZQ@mail.gmail.com>
References: <BANLkTikwGw+3=XZV2YkHiTZB48Hf_KJz4A@mail.gmail.com>
<BANLkTimZFK+Gpvi75gu5hhC9ovtZtrAuiA@mail.gmail.com>
<BANLkTi=RPbKP8o2k38i-SA2mRKmf6bdgBQ@mail.gmail.com>
<BANLkTikL=kqtQe5HjKm5xs1fExGTKeYaXw@mail.gmail.com>
<BANLkTi=G96pUb68GBUaL_J0HqjQSa+X6tA@mail.gmail.com>
<BANLkTimOWTKnwi_XqsnVL736C2y2qj11Sw@mail.gmail.com>
<BANLkTikPPj9v6hd=zPjpEzChPE3U+yUPXw@mail.gmail.com>
<BANLkTi=gyn6xDKMYu+VvwV-ugkHEbxrXMg@mail.gmail.com>
<BANLkTimAMVsYS5c-y+JVixKAViKNS+kF2Q@mail.gmail.com>
<BANLkTi=v8SVBDUbMw=5iBJOuDU-2Fbm...@mail.gmail.com>
<BANLkTi=_S78bih+JUWgw_NFACg9YFvc...@mail.gmail.com>
<BANLkTik4J3noZ5dSSxSmTBmjFqj=Zg4...@mail.gmail.com>
<BANLkTim6vRWFeCvsY+1jkwQ7o73V48R...@mail.gmail.com>
<BANLkTimgw1TeMGU7ESpxPnF+O3U2sEf...@mail.gmail.com>
<BANLkTi=hHLxMCqfr=8TXxq9GN_9ZNF=...@mail.gmail.com>
<BANLkTinKKTF4uAdEZuYrJz2dDZ6sH3Y...@mail.gmail.com>
<BANLkTik0hnqn_ULQvgvGFd6C17E=RHJ...@mail.gmail.com>
<BANLkTimvJUiuqfnO9WNO8_1di31dkD1...@mail.gmail.com>
Date: Sun, 26 Jun 2011 18:58:32 -0400
Message-ID: <BANLkTikq6no+udBb7mZx4hUTqNxeM2S...@mail.gmail.com>
Subject: Re: [nodejs] Job posts and Node.js mailing list guidelines (was:
PHP/MongoDB Developer - Pants optional)
From: Dean Landolt <d...@deanlandolt.com>
To: nodejs@googlegroups.com
Content-Type: multipart/alternative; boundary=0016e6433954bc995704a6a55fcc
--0016e6433954bc995704a6a55fcc
Content-Type: text/plain; charset=ISO-8859-1
On Sun, Jun 26, 2011 at 1:57 PM, Isaac Schlueter <i...@izs.me> wrote:
> On Sun, Jun 26, 2011 at 01:40, Jacobus brogly.decap
> <jacobusbog...@gmail.com> wrote:
> > I dont think Google groups would allow for people charging money (even
> via a
> > -"second handshake"-site)
> > for jobs to be posted here.
>
> I'm not sure, but that's a good point.
>
They're not posted here -- they're posted on joyent's job board. They'd just
be forwarded here. Anyone have a pointer to any possibly related ToS clause?
I'd be shocked if this were an actual violation.
>
> Quite apart from how Google would feel about it, though, that just
> sounds really complicated. It seems a lot simpler to just say "Post
> jobs at http://jobs.nodejs.org/, and not here. If you want to see job
> posts, that's where they are."
>
> I think "the policy that would be ideal if everyone followed it" is
> probably not as good as "the policy that's easy to follow, easy to
> enforce, and solves most of the problems."
>
Well, the policy that's easy to enforce because it's so easy is probably the
best. And that would be just like you said -- don't post jobs here. And for
the reasons Mikeal pointed out it'd be really nice if jobs posted to
joyent's job board get forwarded here. But that'd just be a convenience. The
more important point was that it would be a nice gesture if joyent made it
known to devs that they could submit node related jobs and have them posted
on the joyent job board for free. After all, if it's not about the money
(and I trust it isn't -- it ain't much money) what's the big deal?
--0016e6433954bc995704a6a55fcc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br><br><div class=3D"gmail_quote">On Sun, Jun 26, 2011 at 1:57 PM, Isaac S=
chlueter <span dir=3D"ltr"><<a href=3D"mailto:i...@izs.me">i...@izs.me</a>>=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">On Sun, Jun 26, 2011 at 01:40, Jacobus brogly.decap<br>
<<a href=3D"mailto:jacobusbog...@gmail.com">jacobusbog...@gmail.com</a>&=
gt; wrote:<br>
> I dont think Google groups would allow for people charging money (even=
via a<br>
> -"second handshake"-site)<br>
> =A0for jobs to be posted here.<br>
<br>
</div>I'm not sure, but that's a good point.<br></blockquote><div><=
br></div><div>They're not posted here -- they're posted on joyent&#=
39;s job board. They'd just be forwarded here. Anyone have a pointer to=
any possibly related ToS clause? I'd be shocked if this were an actual=
violation.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;">
<br>
Quite apart from how Google would feel about it, though, that just<br>
sounds really complicated. =A0It seems a lot simpler to just say "Post=
<br>
jobs at <a href=3D"http://jobs.nodejs.org/" target=3D"_blank">http://jobs.n=
odejs.org/</a>, and not here. =A0If you want to see job<br>
posts, that's where they are."<br>
<br>
I think "the policy that would be ideal if everyone followed it" =
is<br>
probably not as good as "the policy that's easy to follow, easy to=
<br>
enforce, and solves most of the problems."<br></blockquote><div><br></=
div><div>Well, the policy that's easy to enforce because it's so ea=
sy is probably the best. And that would be just like you said -- don't =
post jobs here. And for the reasons Mikeal pointed out it'd be really n=
ice if jobs posted to joyent's job board get forwarded here. But that&#=
39;d just be a convenience. The more important point was that it would be a=
nice gesture if joyent made it known to devs that they could submit node r=
elated jobs and have them posted on the joyent job board for free. After al=
l, if it's not about the money (and I trust it isn't -- it ain'=
t much money) what's the big deal?</div>
</div>
--0016e6433954bc995704a6a55fcc--