<?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 open source)</title><link>https://sgillies.net/</link><description></description><atom:link href="https://sgillies.net/tags/open-source.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Mon, 18 Nov 2024 02:42:12 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Python typing mulligan</title><link>https://sgillies.net/2024/11/17/python-typing-mulligan.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;This is why I've been hesitant to add type hints to Fiona, Rasterio, and
Shapely. David Lord on &lt;a class="reference external" href="https://mas.to/@davidism/113489750103116039"&gt;missteps and misgivings&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I want a "start over" tool for type annotating a Python library. I started
with Flask as untyped code, then added annotations until mypy stopped
complaining. But this didn't mean the annotations were _correct_. Over time
I've fixed various reported issues. I feel like if I could start from
scratch again, I'd probably get closer to correct with the experience I've
gained. But removing all existing annotations and ignores is too time
consuming on its own. #python&lt;/p&gt;
&lt;/blockquote&gt;</description><category>open source</category><category>python</category><category>typing</category><category>work</category><guid>https://sgillies.net/2024/11/17/python-typing-mulligan.html</guid><pubDate>Mon, 18 Nov 2024 02:16:36 GMT</pubDate></item><item><title>On not using Slack for open source</title><link>https://sgillies.net/2019/02/28/on-not-using-slack-for-open-source.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;I completely agree with Matthew Rocklin about the &lt;a class="reference external" href="https://mrocklin.github.com/blog/2019/02/28/slack-github"&gt;suitability of Slack for open
source projects&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Real-time chat systems make everyone feel productive (it’s fun to have
a face-paced technical conversation with colleagues), but do relatively
little for long-term community consensus building, particularly when the
users and developers of a project span a variety of institutions and a long
range of time.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I created two discussion groups for Rasterio on groups.io because I don't want
real-time support chat to suck up all the community's oxygen and because the
community's collective wisdom is more powerful when it is searchable. I also
don't do live support for my projects on any Slack other than Mapbox's.&lt;/p&gt;</description><category>open source</category><category>slack</category><category>work</category><guid>https://sgillies.net/2019/02/28/on-not-using-slack-for-open-source.html</guid><pubDate>Thu, 28 Feb 2019 17:10:53 GMT</pubDate></item><item><title>Current status</title><link>https://sgillies.net/2017/08/30/current-status.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;I've been neglecting my open source projects this summer due to time
constraints. At Mapbox we've been onboarding a new President and COO and a raft
of new employees, plus a manager for my team at Mapbox. These are hugely
positive developments, but have also been a big lift.  Moving back to Colorado
and bringing our lives here out of suspension has similarly taken all of my
personal time. I've been the blocker for new releases of Fiona, Rasterio, and
Shapely all summer long and have been feeling rather guilty about it.&lt;/p&gt;
&lt;p&gt;Things are looking up now. My kids are back in school and have seen their
doctor and dentist. Their schedule of soccer practices and other activities for
the season is getting settled quickly. I'm resuming weekly yoga and gym
workouts along with my existing running schedule. I like having a weekly
routine; it helps me stay relaxed and gives me time for personal projects like
writing and computering.&lt;/p&gt;
&lt;p&gt;Open source continues to be a big part of my job and as my share of the
onboarding lift eases I've been able to increase my time on Fiona, Rasterio,
and Shapely. I released the long overdue Shapely 1.6.0 and have supported the
GeoPandas team on getting 0.3.0 out. Fiona 1.7.9 was the first bug fix release
of that project since June and I'm happy to have that in user hands. This week
I'm working on coding and writing about the upcoming Rasterio release. I feel
like I'm doing a good job as an open source maintainer and mentor again and am
excited about what I'll be able to do in the next few months.&lt;/p&gt;
&lt;p&gt;None of these projects would be viable without the help of other developers.
To my open source collaborators: thanks for hanging in there and being patient
with me!&lt;/p&gt;</description><category>fiona</category><category>open source</category><category>python</category><category>rasterio</category><category>shapely</category><category>work</category><guid>https://sgillies.net/2017/08/30/current-status.html</guid><pubDate>Wed, 30 Aug 2017 13:29:08 GMT</pubDate></item><item><title>Trying something new</title><link>https://sgillies.net/2013/02/10/trying-something-new.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;I'm working on submissions for the upcoming &lt;a class="reference external" href="http://foss4g-na.org/call-for-presentations/"&gt;FOSS4G-NA&lt;/a&gt; conference (aka MapServer
User Meeting XI) and am experimenting with opening the abstracts up to comments
and forks as I write them at &lt;a class="reference external" href="https://gist.github.com/sgillies/4745903"&gt;https://gist.github.com/sgillies/4745903&lt;/a&gt;. If you
like the direction I'm going with the abstracts, feel free to comment. If it
looks like I'm overlooking something important, please comment. If you're
interested in co-presenting please fork the Gist and we'll talk. The results
will go into the FOSS4G-NA submission spreadsheet on the 14th.&lt;/p&gt;
&lt;section id="comments"&gt;
&lt;h2&gt;Comments&lt;/h2&gt;
&lt;section id="re-trying-something-new"&gt;
&lt;h3&gt;Re: Trying something new&lt;/h3&gt;
&lt;p&gt;Author: Martin Davis&lt;/p&gt;
&lt;p&gt;This looks like a couple of good reasons to try and make it to FOSS4GNA-2013!&lt;/p&gt;&lt;/section&gt;
&lt;/section&gt;</description><category>open source</category><category>work</category><guid>https://sgillies.net/2013/02/10/trying-something-new.html</guid><pubDate>Sun, 10 Feb 2013 07:00:00 GMT</pubDate></item><item><title>Libspatialindex 1.8.0 released</title><link>https://sgillies.net/2012/12/13/libspatialindex-1-8-0-released.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;Good bye, LGPL. Hello, MIT (and iOS). Howard Butler &lt;a class="reference external" href="http://lists.gispython.org/pipermail/spatialindex/2012-December/000341.html"&gt;writes&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I'm pleased to announce the release of libspatialindex 1.8.0. Two significant
changes have been made in this release to necessitate incrementing the
libtool versioning. The first exciting change is the license of
libspatialindex was changed from LGPL 2.1 to MIT. This licensing change is to
support the use of libspatialindex in embedded systems development situations
(such as iOS) where dynamic linking to satisfy the LGPL is not possible for
whatever reason.  The second, more mundane change, is to add a flush() method
to the IStorageManager to support saving the index in situations where you do
not want to completely tear down the object. This is useful in situations
where you are using libspatialindex on top of some other system and are
providing your own index storage implementation.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Howard has also compiled Windows binaries: &lt;a class="reference external" href="http://libspatialindex.github.com/#download"&gt;http://libspatialindex.github.com/#download&lt;/a&gt;.&lt;/p&gt;</description><category>open source</category><category>the lab</category><category>work</category><guid>https://sgillies.net/2012/12/13/libspatialindex-1-8-0-released.html</guid><pubDate>Thu, 13 Dec 2012 07:00:00 GMT</pubDate></item><item><title>Closing down the Lab</title><link>https://sgillies.net/2011/08/19/closing-down-the-lab.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;If you're a suscriber to the GIS-Python projects mailing list, you've seen the
discussion about migrating projects to other hosting services. If you're not
a subscriber your first notice might have been seeing this at the Trac &lt;a class="reference external" href="http://trac.gispython.org/lab/"&gt;site&lt;/a&gt;:&lt;/p&gt;
&lt;img alt="http://sgillies.net/images/closing-lab.jpg" src="http://sgillies.net/images/closing-lab.jpg"&gt;
&lt;p&gt;OWSLib is going to &lt;a class="reference external" href="http://sourceforge.net/apps/trac/owslib/wiki"&gt;Sourceforge&lt;/a&gt;, the zgeo.* projects are being superceded by
the collective.geo suite at &lt;a class="reference external" href="http://www.coactivate.org/projects/collectivegeo/project-home"&gt;CoActivate&lt;/a&gt;, and most everything else has been
moved to GitHub.&lt;/p&gt;
&lt;p&gt;When Kai and I started the GIS-Python effort in 2005, running our own
development site looked like the best option. Today, it's nowhere near the best
option and feels increasingly like a hinderance. I'm looking forward to
spending less time on operations and more time on coding. I hope you'll stick
with the projects through the move and beyond.&lt;/p&gt;</description><category>open source</category><category>programming</category><category>the lab</category><category>work</category><guid>https://sgillies.net/2011/08/19/closing-down-the-lab.html</guid><pubDate>Fri, 19 Aug 2011 06:00:00 GMT</pubDate></item><item><title>That's more like it</title><link>https://sgillies.net/2011/01/12/thats-more-like-it.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;Pulling the unflattering and inaccurate &lt;a class="reference external" href="http://sgillies.net/blog/1059/copywriting-run-amuck"&gt;stereotype&lt;/a&gt; of open source GIS pioneers from the FOSS4G 2011 &lt;a class="reference external" href="http://2011.foss4g.org/"&gt;home page&lt;/a&gt; is the right move.&lt;/p&gt;</description><category>community</category><category>open source</category><category>work</category><guid>https://sgillies.net/2011/01/12/thats-more-like-it.html</guid><pubDate>Wed, 12 Jan 2011 07:00:00 GMT</pubDate></item><item><title>In which I try to help more and complain less</title><link>https://sgillies.net/2010/12/22/in-which-i-try-to-help-more-and-complain-less.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; (2011-01-12): Better: &lt;a class="reference external" href="http://sgillies.net/blog/1065/thats-more-like-it"&gt;http://sgillies.net/blog/1065/thats-more-like-it&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A reader suggested to me in comments that I should approach the words on the
FOSS4G 2011 site (which I quoted &lt;a class="reference external" href="http://sgillies.net/blog/1059/copywriting-run-amuck"&gt;previously&lt;/a&gt;) from a different angle and try to
appreciate that they're aimed at folks outside the FOSS4G community.  Speaking
to them using their own language including, apparently, their own unflattering
stereotypes of open source users in an anything goes effort to lure them in to
the event. I suppose this makes some twisted sense if you ignore an
eventuality: that this corporate audience will at some point discover
themselves fully surrounded by these very same wild-eyed open source hippy
freetard philosophers. But nevermind that for now, I'm fully onboard with the
FOSS4G rhetoric and have some other stereotypes that the marketers are free to
use or repurpose if the original&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Many early adopters of FOSS solutions chose them based on
"philosophical" reasons, but ...&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;starts to wear thin. How about this one, which uses unnecessary quotes to
maintain the right style?&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Many early adopters of FOSS solutions were into GIS as a "fun" hobby, but ...&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;That will have strong appeal for certified professionals.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Many early adopters of FOSS solutions felt "everything" should be free, but
...&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The conference is coming back to the USA, and nothing is more American than
using Communists as bogeymen.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Many early adopters of FOSS ranted about the "difference" between freedom and
free beer, but ...&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Always with the damn philosophizing, those freetards.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Many early adopters of FOSS were from "academic" backgrounds, but ...&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I almost forgot the Ivory Tower! Nobody is less pragmatic than an academic researcher, right? Hope this helps, and
Merry Christmas.&lt;/p&gt;</description><category>community</category><category>ironic</category><category>open source</category><category>work</category><guid>https://sgillies.net/2010/12/22/in-which-i-try-to-help-more-and-complain-less.html</guid><pubDate>Wed, 22 Dec 2010 07:00:00 GMT</pubDate></item><item><title>Copywriting run amuck?</title><link>https://sgillies.net/2010/12/21/copywriting-run-amuck.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;&lt;a class="reference external" href="http://2011.foss4g.org/"&gt;Bullshit&lt;/a&gt;.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Recent years have seen substantial changes in the geospatial industry. One of
those changes has been the growth in maturity and adoption of free and open
source solutions. &lt;strong&gt;Many early adopters of FOSS solutions chose them based on
"philosophical" reasons&lt;/strong&gt;, but increasingly large enterprises and government
organizations are choosing these solutions for pragmatic business reasons. In
many cases organizations are using a mixture of open and closed source
solutions.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Emphasis above is mine. What the hell is up with the scare quotes and the impractical, ideology-driven,
early adopter strawman? If you were there in the early FOSS4G days, you'll
remember that it was in fact about pragmatic solutions: proprietary software
often lacked features that we needed to do our jobs or was riddled with bugs
that we suspected wouldn't be fixed any time soon. The need to get shit done
was the driving force behind GDAL, MapServer, PostGIS, and friends. Driving a stake through the heart of
ArcIMS was just gravy.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; (2011-01-12): Better: &lt;a class="reference external" href="http://sgillies.net/blog/1065/thats-more-like-it"&gt;http://sgillies.net/blog/1065/thats-more-like-it&lt;/a&gt;&lt;/p&gt;
&lt;section id="comments"&gt;
&lt;h2&gt;Comments&lt;/h2&gt;
&lt;section id="re-copywriting-run-amuck"&gt;
&lt;h3&gt;Re: Copywriting run amuck?&lt;/h3&gt;
&lt;p&gt;Author: Karsten Vennemann&lt;/p&gt;
&lt;p&gt;Seems that the quote above is straight from the foss4g 2011 home page...&lt;/p&gt;&lt;p&gt;Certainly a driving force behind the OS GIS solutions was getting things done, but functionality comes, matures and is added on over time as we all know ;) . I can see in the small GIS consulting business that I am running a huge and growing client demand for OS web based solutions unfolding over the last 4 years. I have seen that OS web based solution already where competitive over the last 5 years when I have been using them. However with OS desktop GIS that increasingly became true over the last 2 years when e.g. QGIS and gvSIG became so powerfull that they actually can be used to do most of I was doing in ArcGIS previously (namely fine cartography and labeling).&lt;/p&gt;&lt;p&gt;Also it's not all about the technological solution (and what it can do) but about information about the solution, about spreading the word, and the process that this information finally arrives  (trickles through ) at decision  makers desks (long way) - that is in other words (due successful foss4g) 'marketing' (yuk ?).&lt;/p&gt;&lt;p&gt;On the foss4g web site I see this quote also as a perception described and I don't see anything wrong with that. I think the home page is also largely about spreading the word to non - typical OS GIS users (yes not only geeky OS developer types that come to foss4g anyway thanks god!) to get them and come to the FOSS4G. Personally I would love to see more regular GIS users (vs developer types) to attend foss4g and especially lots of newcomers (yes ESRI type GIS users) to join this event !&lt;/p&gt;&lt;p&gt;Note: I am not involved in creation of the home page at all ;)&lt;/p&gt;&lt;/section&gt;
&lt;section id="re-copywriting-run-amuck-1"&gt;
&lt;h3&gt;Re: Copywriting run amuck?&lt;/h3&gt;
&lt;p&gt;Author: Sean&lt;/p&gt;
&lt;p&gt;Karsten, I am not disputing the undeniable "growth in maturity and adoption". I'm disputing the characterization of early adopters -- the people who put PostGIS (for example) into production long before it hit 1.0, who found and saw closed all the early show-stopping bugs, who supported each other before there were books or adequate documentation, who raised the damn FOSS4G barn -- as unpragmatic has-beens. The mainstream owes the early adopters respect, if not thanks.&lt;/p&gt;&lt;/section&gt;
&lt;section id="re-copywriting-run-amuck-2"&gt;
&lt;h3&gt;Re: Copywriting run amuck?&lt;/h3&gt;
&lt;p&gt;Author: bk&lt;/p&gt;
&lt;p&gt;Tuff in the corners, sweet hands in front of the net.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;a href="http://www.jtbourne.com/clark-gillies-chardonnay-men-apparently/"&gt; Gillies is the Chardonnay of Men..&lt;/a&gt;&lt;/section&gt;
&lt;section id="re-copywriting-run-amuck-3"&gt;
&lt;h3&gt;Re: Copywriting run amuck?&lt;/h3&gt;
&lt;p&gt;Author: Sean&lt;/p&gt;
&lt;p&gt;Sadly, I am not, to my knowledge, related to Clark Gillies.&lt;/p&gt;&lt;/section&gt;
&lt;section id="re-copywriting-run-amuck-4"&gt;
&lt;h3&gt;Re: Copywriting run amuck?&lt;/h3&gt;
&lt;p&gt;Author: Paul Ramsey&lt;/p&gt;
&lt;p&gt;Agreed. Unless "unafraid of change" or "open to new approaches" count as "philosophical" reasons. Sure, it takes a different mindset than your bog standard IT manager might have, but ideology doesn't enter into it.&lt;/p&gt;&lt;/section&gt;
&lt;section id="re-copywriting-run-amuck-5"&gt;
&lt;h3&gt;Re: Copywriting run amuck?&lt;/h3&gt;
&lt;p&gt;Author: Daniel Morissette&lt;/p&gt;
&lt;p&gt;This sentence on the FOSS4G 2011 page also hurt my eye. I consider myself one of those early adopters but as a consultant my motivations have always been and still are mostly pragmatic and not philosophical.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;I don't think this descriptions matches many FOSS4G user organizations either (not our own clients anyway, not even those from the early days). All our clients care about is that the tool gets the job done. Very few care about the "philosophical" reasons and it's actually the contrary: if you want to scare a potential client away then start giving them a "philosophical" lecture.&lt;/p&gt;&lt;/section&gt;
&lt;/section&gt;</description><category>community</category><category>open source</category><category>work</category><guid>https://sgillies.net/2010/12/21/copywriting-run-amuck.html</guid><pubDate>Tue, 21 Dec 2010 07:00:00 GMT</pubDate></item><item><title>An afternoon of hacking before WhereCamp5280</title><link>https://sgillies.net/2010/10/26/an-afternoon-of-hacking-before-wherecamp5280.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;Geospatial programmers inclined toward interpreted languages and open source don't get together enough on the Front Range. Please help Chris Helms, Tyler Erickson, and I correct this unfortunate state of affairs on November 18 at the once Colorado Brewery, now Nationally Registered Historical Place known as CU Denver's Tivoli Student Center. WhereCamp once piggybacked on Where 2.0 and now we're hooky bobbing on &lt;a class="reference external" href="http://www.wherecamp5280.org/"&gt;WhereCamp5280&lt;/a&gt;. See the &lt;a class="reference external" href="http://groups.google.com/group/frugos/browse_frm/thread/f8613ceb342ff4b3?hl=en"&gt;announcement&lt;/a&gt; by Chris on the FRUGOS list for details and spread the word.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt; (2010-10-26): Please &lt;a class="reference external" href="http://wc5280hack.pbworks.com/"&gt;sign up&lt;/a&gt; on the wiki if you're planning to attend.&lt;/p&gt;</description><category>community</category><category>open source</category><category>programming</category><category>work</category><guid>https://sgillies.net/2010/10/26/an-afternoon-of-hacking-before-wherecamp5280.html</guid><pubDate>Tue, 26 Oct 2010 06:00:00 GMT</pubDate></item></channel></rss>