<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sean Gillies (Posts about conduct)</title><link>https://sgillies.net/</link><description></description><atom:link href="https://sgillies.net/tags/conduct.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sun, 31 Dec 2023 01:26:19 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>SciPy at 1.0</title><link>https://sgillies.net/2017/10/25/scipy-at-1-0.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;SciPy 1.0 was &lt;a class="reference external" href="https://mail.python.org/pipermail/scipy-dev/2017-October/022235.html"&gt;announced this morning&lt;/a&gt;. Ralf
Gommers wrote:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;A version number should reflect the maturity of a project - and SciPy was
a mature and stable library that is heavily used in production settings for
a long time already.  From that perspective, the 1.0 version number is long
overdue.&lt;/p&gt;
&lt;p&gt;Some key project goals, both technical (e.g. Windows wheels and continuous
integration) and organisational (a governance structure, code of conduct
and a roadmap), have been achieved recently.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The code of conduct he mentions is here:
&lt;a class="reference external" href="https://github.com/scipy/scipy/blob/master/doc/source/dev/conduct/code_of_conduct.rst"&gt;https://github.com/scipy/scipy/blob/master/doc/source/dev/conduct/code_of_conduct.rst&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;It's been interesting lurking in the code of conduct discussions on scipy-dev
and on GitHub. The project used a few existing CoCs as starting points
(including the Contributor Covenant used at Mapbox) and ended up with something
they felt more suited to their community.&lt;/p&gt;</description><category>community</category><category>conduct</category><category>numpy</category><category>scipy</category><category>work</category><guid>https://sgillies.net/2017/10/25/scipy-at-1-0.html</guid><pubDate>Wed, 25 Oct 2017 15:14:22 GMT</pubDate></item><item><title>Back from FOSS4G</title><link>https://sgillies.net/2014/09/14/back-from-foss4g.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;In my experience, FOSS4G was tons of fun and very well run. Chapeau to the
organizing team! I hope other attendees got as much out of the conference as
I did. Not only did I get to catch up with people I met at the dawn of FOSS4G,
I met great people I'd only known from Twitter and made entirely new
acquaintances. I even got to speak a bit of French.&lt;/p&gt;
&lt;p&gt;My talk was one of the first in the general sessions. I had fun presenting and
am told that I did a good job. My slides are published at
&lt;a class="reference external" href="http://sgillies.github.io/foss4g-2014-fiona-rasterio/"&gt;http://sgillies.github.io/foss4g-2014-fiona-rasterio/&lt;/a&gt; and you can fork them
from &lt;a class="reference external" href="https://github.com/sgillies/foss4g-2014-fiona-rasterio"&gt;GitHub&lt;/a&gt;.
According to the information at the &lt;a class="reference external" href="https://2014.foss4g.org/live/"&gt;FOSS4G Live Stream page&lt;/a&gt; all the talks will be available online soon.
I missed plenty that I'm looking forward to seeing on my computer. Out of the ones
I attended, I particularly recommend seeing the following:&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;&lt;p&gt;"Using OpenStreetMap Infrastructure to Collect Data for our National Parks"
by James McAndrew, National Park Service&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;"Managing public data on GitHub: Pay no attention to that git behind the
curtain" by Landon Reed, Atlanta Regional Commission&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;"Big (enough) data and strategies for distributed geoprocessing" by Robin
Kraft, World Resources Institute&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;"An Automated, Open Source Pipeline for Mass Production of 2 m/px DEMs from
Commercial Stereo Imagery" by David Shean, University of Washington&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Did the &lt;a class="reference external" href="https://2014.foss4g.org/attending/code-of-conduct/"&gt;code of conduct&lt;/a&gt; work? I heard one
speaker invoke images of barely competent moms – "so easy your mother can do
it" – and was present for a unfortunate reference to hacking private photos at
lunch time. I hope that was all of it.&lt;/p&gt;
&lt;p&gt;If you attended FOSS4G or watched the live feed I encourage you to write about your
experience and impressions. Come on, do it. It doesn't have to be long or
comprehensive. Here are a few blog posts I've seen already:&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;&lt;p&gt;&lt;a class="reference external" href="http://www.atlefren.net/post/2014/09/foss4g-2014-the-good-the-bad-and-the-beers/"&gt;Foss4g 2014: The good, the bad and the beers&lt;/a&gt;   by Atle Frenvik Sveen&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;</description><category>conduct</category><category>conference</category><category>fiona</category><category>foss4g</category><category>portland</category><category>rasterio</category><category>video</category><category>work</category><guid>https://sgillies.net/2014/09/14/back-from-foss4g.html</guid><pubDate>Sun, 14 Sep 2014 06:00:00 GMT</pubDate></item></channel></rss>