{"id":18936,"date":"2022-04-30T12:18:05","date_gmt":"2022-04-30T10:18:05","guid":{"rendered":"https:\/\/daniel.haxx.se\/blog\/?p=18936"},"modified":"2022-06-27T08:13:08","modified_gmt":"2022-06-27T06:13:08","slug":"uncurled","status":"publish","type":"post","link":"https:\/\/daniel.haxx.se\/blog\/2022\/04\/30\/uncurled\/","title":{"rendered":"Uncurled"},"content":{"rendered":"\n

– Everything I know and learned about running and maintaining Open Source projects for three decades.<\/p>\n\n\n\n

For several years now, I have had a blog post series in mind to describe something about what people could expect to happen in Open Source projects. I had a few already half-started blog post drafts for some sub topics.<\/p>\n\n\n\n

I couldn’t really make up my mind how to craft a series of blog posts about this wide topic in a sensible way so I kept postponing it for later. I did this for years.<\/p>\n\n\n\n

A book, it has to be a book<\/h2>\n\n\n\n

It just dawned on my one day: the only way to get all this into a comprehensible way that also can hold all the thoughts I would like it to have, is to put it into a book. By book, I mean a document. An essay. A collection of pages. A booklet maybe. I don’t know how many words it might end up to become and I have no illusions of it ever ending up in print.<\/p>\n\n\n\n

I mean to write the document in the open and provide it for free, online. Open Source style.<\/p>\n\n\n\n

Day one<\/h2>\n\n\n\n

I grabbed my original draft for my blog series “You can expect this in your Open Source project”. I had worked on that document in the background for a long time, adding some little thing here and there over years – and it now had maybe twenty-five “lessons” listed with a short paragraph of text next to each.<\/p>\n\n\n\n

I also had started three blog posts based on such lessons that were in pending state here on daniel.haxx.se in my queue of drafts.<\/p>\n\n\n\n

I first copied the blog post content back into the text file from those potential blog posts, before I deleted them, and converted the entire file to markdown.<\/p>\n\n\n\n

I then grouped the “lessons” I had listed in the markdown file and moved them into a few different sections. Like what to expect, code, money, people and project. I put subtitles into separate files for those five main areas.<\/p>\n\n\n\n

How hard can it be?<\/h2>\n\n\n\n

I didn’t want to do a lot of work before I put the thing into git, and I didn’t want to run any private git repository so I had to make a new repo with a name. I went with “How hard can it be” as a working title and created the repo on GitHub. On April 6 I made the first git push with initial contents to that repository<\/a>.<\/p>\n\n\n\n

The first external contributor appeared after just a few minutes with the first pull-request fixing typos. Clearly people are following me on GitHub and spotted the creating of the repository and checked out what it was. I hadn’t told anyone or given any pointers.<\/p>\n\n\n\n

I started expanding on subjects in the book.<\/p>\n\n\n\n

Let’s get a real title<\/h2>\n\n\n\n

In the evening of April 7 I posted this question on Twitter: <\/p>\n\n\n

\n
\""If<\/a><\/figure>\n<\/div>\n\n\n

I got a flood of replies. Lots of good ones and also lots of fun and sarcastic ones. The one that I think really talked to me the best was also the shortest: Uncurled<\/strong>.<\/p>\n\n\n\n