<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Boston Ruby Group: Job Posting Policies.</title>
    <link>http://boston.rubygroup.org/articles/2007/06/18/job-posting-policies</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>Job Posting Policies.</title>
      <description>&lt;ul&gt;
	&lt;li&gt;The mailing list will not ban those who post Ruby-related jobs, including
RoR jobs. Such a posting must have a subject line beginning with:
[JOB]&lt;/li&gt;
	&lt;/ul&gt;


	&lt;ul&gt;
	&lt;li&gt;Ideally, the subject line will provide the name of the job, the
location, and the duration. The body would repeat all of that info,
with a longer job description, contact info, compensation if known,
etc., etc.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;ul&gt;
	&lt;li&gt;We would be annoyed if the same job listing is posted and re-posted
on a frequent basis. I.e., post a single job once; if there&amp;#8217;s really
no uptake, you might post it again in six weeks. But the list
shouldn&amp;#8217;t be a broadcast medium for recruiters with generic catch-all
listings.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;ul&gt;
	&lt;li&gt;Abuse of the list for non-Ruby/RoR jobs will be assessed on a
per-case basis; in general, such postings are strongly disapproved.&lt;/li&gt;
	&lt;/ul&gt;</description>
      <pubDate>Mon, 18 Jun 2007 16:58:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:879b16da-e485-4ebf-ac61-68e6a8ad2704</guid>
      <author>Tom Dyer</author>
      <link>http://boston.rubygroup.org/articles/2007/06/18/job-posting-policies</link>
      <category>Jobs</category>
      <category>jobs</category>
      <trackback:ping>http://boston.rubygroup.org/articles/trackback/24690</trackback:ping>
    </item>
  </channel>
</rss>
