Cowboy 2.0.0-rc.1

1 files changed, 66 insertions, 127 deletions

diff --git a/index.xml b/index.xml
index 12948726..d40f9451 100644
--- a/index.xml
+++ b/index.xml
@@ -6,10 +6,75 @@
     <description>Recent content on Nine Nines</description>
     <generator>Hugo -- gohugo.io</generator>
     <language>en-us</language>
-    <lastBuildDate>Sun, 26 Mar 2017 00:00:00 +0100</lastBuildDate>
+    <lastBuildDate>Mon, 24 Jul 2017 18:00:00 +0100</lastBuildDate>
     <atom:link href="https://ninenines.eu/index.xml" rel="self" type="application/rss+xml" />
     
     <item>
+      <title>Cowboy 2.0 release candidate 1</title>
+      <link>https://ninenines.eu/articles/cowboy-2.0.0-rc.1/</link>
+      <pubDate>Mon, 24 Jul 2017 18:00:00 +0100</pubDate>
+      
+      <guid>https://ninenines.eu/articles/cowboy-2.0.0-rc.1/</guid>
+      <description>&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;Cowboy &lt;code&gt;2.0.0-rc.1&lt;/code&gt; has been released!&lt;/p&gt;&lt;/div&gt;

+&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;This is the new recommended version of Cowboy.

+Its API should not change before release. While

+you probably should not use it in production yet,

+many do successfully. Use at your own risk.&lt;/p&gt;&lt;/div&gt;

+&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;The plan is to have a new RC version every couple

+weeks until the summer ends or later if there are

+still blocking issues open. Only issues that can&amp;#8217;t

+be fixed without making breaking changes to the

+interface may block the release.&lt;/p&gt;&lt;/div&gt;

+&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;Numerous changes were made since Cowboy 1.0. The

+one most people care about is probably HTTP/2, but

+it&amp;#8217;s most likely not the only one worthwhile. The

+full list of changes (excluding types) can be found

+in the user guide chapter

+&lt;a href=&#34;https://ninenines.eu/docs/en/cowboy/2.0/guide/migrating_from_1.0/&#34;&gt;Migrating from Cowboy 1.0 to 2.0&lt;/a&gt;.&lt;/p&gt;&lt;/div&gt;

+&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;As this is not the full release just yet, please pay

+extra attention to details and report anything

+suspicious you find.&lt;/p&gt;&lt;/div&gt;

+&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;There are still some tests failing. Most of those are

+related to standards that are not being followed perfectly

+just yet. Some of those will probably not be fixed before

+Cowboy 2.0 is released. They are edge cases and should not

+prevent interoperability.&lt;/p&gt;&lt;/div&gt;

+&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;The manual received a lot of love. It now has one page per

+function with a detailed description, arguments list, return

+value, changelog and examples. It also links to the other

+relevant manual pages: &lt;a href=&#34;https://ninenines.eu/docs/en/cowboy/2.0/manual/&#34;&gt;https://ninenines.eu/docs/en/cowboy/2.0/manual/&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;

+&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;Cowboy is now tested and supported with Erlang/OTP 19.0 or above

+on Arch Linux, FreeBSD, OSX, Ubuntu and Windows 7. Contact me

+if you can provide permanent access to another platform for the

+purposes of testing.&lt;/p&gt;&lt;/div&gt;

+&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;Cowboy is now available from four locations:&lt;/p&gt;&lt;/div&gt;

+&lt;div class=&#34;ulist&#34;&gt;&lt;ul&gt;

+&lt;li&gt;

+&lt;p&gt;

+&lt;a href=&#34;https://git.ninenines.eu/cowboy.git&#34;&gt;https://git.ninenines.eu/cowboy.git&lt;/a&gt;

+&lt;/p&gt;

+&lt;/li&gt;

+&lt;li&gt;

+&lt;p&gt;

+&lt;a href=&#34;https://github.com/ninenines/cowboy.git&#34;&gt;https://github.com/ninenines/cowboy.git&lt;/a&gt;

+&lt;/p&gt;

+&lt;/li&gt;

+&lt;li&gt;

+&lt;p&gt;

+&lt;a href=&#34;https://bitbucket.org/ninenines/cowboy.git&#34;&gt;https://bitbucket.org/ninenines/cowboy.git&lt;/a&gt;

+&lt;/p&gt;

+&lt;/li&gt;

+&lt;li&gt;

+&lt;p&gt;

+&lt;a href=&#34;https://gitlab.com/ninenines/cowboy.git&#34;&gt;https://gitlab.com/ninenines/cowboy.git&lt;/a&gt;

+&lt;/p&gt;

+&lt;/li&gt;

+&lt;/ul&gt;&lt;/div&gt;

+&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;They are updated at the same time so there is no real difference.&lt;/p&gt;&lt;/div&gt;

+</description>
+    </item>
+    
+    <item>
       <title>The elephant in the room</title>
       <link>https://ninenines.eu/articles/the-elephant-in-the-room/</link>
       <pubDate>Sun, 26 Mar 2017 00:00:00 +0100</pubDate>
@@ -1052,131 +1117,5 @@ http://www.gnu.org/software/src-highlite --&gt;
 </description>
     </item>
     
-    <item>
-      <title>On open source</title>
-      <link>https://ninenines.eu/articles/on-open-source/</link>
-      <pubDate>Fri, 05 Sep 2014 00:00:00 +0100</pubDate>
-      
-      <guid>https://ninenines.eu/articles/on-open-source/</guid>
-      <description>&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;Last week I read a great article

-&lt;a href=&#34;http://videlalvaro.github.io/2014/08/on-contributing-to-opensource.html&#34;&gt;on

-contributing to open source&lt;/a&gt; by Alvaro Videla. He makes

-many great points and I am in agreement with most of it.

-This made me want to properly explain my point of view with

-regard to open source and contributions. Unlike most open

-source evangelism articles I will not talk about ideals or

-any of that crap, but rather my personal feelings and

-experience.&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;I have been doing open source work for quite some time.

-My very first open source project was a graphics driver

-for (the very early version of) the PCSX2 emulator. That

-was more than ten years ago, and there

-&lt;a href=&#34;http://ngemu.com/threads/gstaris-0-6.30469/&#34;&gt;isn&amp;#8217;t

-much left to look at today&lt;/a&gt;. This was followed by a

-&lt;a href=&#34;https://github.com/extend/wee&#34;&gt;PHP framework&lt;/a&gt;

-(started long before Zend Framework was even a thing) and

-a few other small projects. None of them really took off.

-It&amp;#8217;s alright, that&amp;#8217;s pretty much the fate of most open

-source projects. You spend a lot of work and sweat and

-get very little in return from others.&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;This sounds harsh but this is the reality of all open

-source projects. If you are thinking of building a project

-and releasing it as open source, you should be prepared

-for that. This is how most of your projects will feel like.

-Don&amp;#8217;t release a project as open source thinking everyone

-will pat you on the back and cheer, this won&amp;#8217;t happen. In

-fact if your project is a too small improvement over existing

-software, what many people will do is say you have NIH

-syndrome, regardless of the improvement you bring. So you

-need not to rely on other people in order to get your

-enjoyment out of building open source software.&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;In my case I get enjoyment from thinking about problems

-that need solving. Often times the problems are already

-solved, but nevermind that, I still think about them and

-sometimes come up with something I feel is better and then

-write code for it. Writing code is also fun, but not as

-fun as using my brain to imagine solutions.&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;You don&amp;#8217;t need thousands of users to do that. So are

-users worthless to me then? No, of course not. In fact

-they are an important component: they bring me problems

-that need solving. So users are very important to me.

-But that&amp;#8217;s not the only reason.&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;I got lucky that the Cowboy project became popular.

-And seeing it be this popular, and some of my other projects

-also do quite well, made me believe I could perhaps work

-full time on open source. If I can work full time then

-I can produce better software. What I had one hour to

-work on before I can now spend a day on, and experiment

-until I am satisfied. This is very useful because that

-means I can get it almost right from the beginning, and

-avoid the million API breaking changes that occured

-before Cowboy 1.0 was released.&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;To be able to work full time on open source however,

-I need money. This is a largely unspoken topic of open

-source work. The work is never free. You can download the

-product for free, but someone has to pay for the work

-itself. Life is unfortunately not free.&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;Large projects and some lucky people have their work

-sponsored by their employers. Everyone else has to deal

-with it differently. In my case I was sponsored for a

-while by the &lt;a href=&#34;http://leo-project.net/leofs/&#34;&gt;LeoFS&lt;/a&gt;

-project, but that ended. I also had the Farwest fundraiser,

-which was a success, although the project stalled after that.

-(Fear not, as Farwest will make a comeback as a conglomerate

-of Web development projects in the future.) After that I set

-up the &lt;a href=&#34;http://ninenines.eu/support/&#34;&gt;sponsoring scheme&lt;/a&gt;,

-which I can proudly say today brings in enough money to

-cover my food and shelter. Great!&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;This is a start, but it&amp;#8217;s of course not enough. Life

-is a little more than food and shelter, and so I am still

-looking for sponsors. This is not a very glorious experience,

-as I am essentially looking for scraps that companies can

-throw away. Still, if a handful more companies were doing

-that, not only would I be able to live comfortably, but I

-would also be able to stop worrying about the future as I

-could put money on the side for when it gets rough.&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;A few companies giving me some scrap money so I could

-live and work independently is by far the most important

-thing anyone can do to help my projects, including Cowboy.

-Yes, they&amp;#8217;re even more important than code contributions,

-bug reports and feedback. Because this money gives me the

-time I need to handle the code contributions, bug reports

-and feedback.&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;If Cowboy or another project is a large part of your

-product or infrastructure, then the best thing you can do

-is become a sponsor. The second best is opening tickets

-and/or providing feedback. The third best is providing

-good code contributions.&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;I will not expand on the feedback part. Feedback is

-very important, and even just a high five or a retweet

-is already good feedback. It&amp;#8217;s not very complicated.&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;I want to expand a little on code contributions

-however. Not long ago I ran across the term &#34;patch bomb&#34;

-which means dropping patches and expecting the project

-maintainers to merge them and maintain them. I receive

-a lot of patches, and often have to refuse them. Causes

-for refusal vary. Some patches only benefit the people

-who submitted them (or a very small number of people).

-Some patches are not refined enough to be included.

-Others are out of scope of the project. These are some

-of the reasons why I refuse patches. Having limited

-time and resources, I have to focus my efforts on the

-code used by the larger number of users. I have to

-prioritize patches from submitters who are reactive

-and address the issues pointed out. And I have to plainly

-refuse other patches.&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;I believe this wraps up my thoughts on open source.

-Overall I had a great experience, the Erlang community

-being nice and understanding of the issues at hand in

-general. And if the money problem could be solved soon,

-then I would be one of the luckiest and happiest open

-source developer on Earth.&lt;/p&gt;&lt;/div&gt;

-&lt;div class=&#34;paragraph&#34;&gt;&lt;p&gt;Think about it the next time you see a donation button

-or a request for funds or sponsoring. You can considerably

-improve an open source developer&amp;#8217;s life with very little

-of your company&amp;#8217;s money.&lt;/p&gt;&lt;/div&gt;

-</description>
-    </item>
-    
   </channel>
 </rss>
\ No newline at end of file