trivelop   home of @rrrene   –  

Announcing elixirstatus

TL;DR I think we need a site where people can post what they made in Elixir, simliar to RubyFlow for Ruby. A service that is build in Elixir, that is Open Source and integrates nicely with the existing ecosystem. I want to build this.

Open letter version:

Hello folks,

some of you may know me because I maintain inch-ci.org and was fortunate enough to be featured on Elixir Radar twice (Issues #10 and #11). Today I want to propose an addition to the Elixir community: a community-driven site to post your new projects, blog posts and version updates.

But wait, you will say, we already have something like this, blog aggregators and twitter accounts retweeting interesting stuff - the community is fine. Well, it is, but I think we are still missing a piece of the puzzle.

I am thinking of a service to post stuff you made or improved or wrote. Ruby has RubyFlow for this and I know that I owe many of my early adopters to that venue (incidentally, it was because of José that I decided to put my stuff on RubyFlow, but that is another story).

To give you an idea what this could look like, here is a rough draft:

This should be for the little coder who wrote his or her first package or blog post. It should be a public utility, think of it as infrastructure. A service that is build in Elixir, that is Open Source and integrates nicely with the existing ecosystem. Individual coders can go there to discover interesting stuff others made as can curators of podcasts and newsletters and bloggers. And people who released a version update or wrote a blog post can share their news without the announcement being drowned by all the Twitter noise (seriously, there is just too much to follow on there).

This does not take away anything from existing trends like the #elixirlang and #myelixirstatus hashtags, Elixir Radar or existing, curated newsletters and blogs, but it builds upon existing trends to add a new venue to the brimming Elixir community:

  • This is about broadcasting, but not so much about dialog.
  • This is about empowering individuals, but not about aggregation.
  • This is about easier on-boarding of new Elixir enthusiasts who are eager to share, but not so much about coders who are already known.
  • This is about the coder/blogger who wants to shout "look what I've done".

This project will rise and fall with the participation of the community, I am well aware of that. And as the maintainer of Inch I am also aware how hard it can be to convince people to try something with a different approach.

But I am optimistic for this one.

Best,
René


Inch CI outage / post mortem

On June 22nd, the Inch CI site and services were not available for ~ 18 hours, as you may have witnessed.

This is what happened to the best of my knowledge:

An attacker gained access to a none-Inch-CI related user account on the server, which was then disconnected. I can not know whether the Inch CI user account, Inch CI database, GitHub tokens or any other security/system-related material has been compromised. To be sure, the server was wiped clean and I installed everything afresh, including a 12h old database backup. I have also resetted the GitHub-App credentials and invalidated all existing user tokens (when you login via Github the next time, you will have to re-authenticate).

All in all this has been a wild day. I am truly sorry for any inconvience this caused you and super greatful for your patience and support via Twitter.

I am very much looking forward to seeing some of you in Salzburg and to buy you a beverage of your choice.


Inch CI: Year One

It's actually been a year since I posted the official annoucement post. Wow. One year of Inch CI. One Year and two weeks that is, actually.

Erik found Inch CI before I had the courage to tell the world and tweeted this:

I was always (secretly) hoping for a known Rubyist like @sferik to talk about my little side project and help me spread the word. But always be carful what you wish for ... Early adopters where flowing in over the next couple of days, and I was forced to jump in at the deep end, so to speak, to iron out the most obvious glitches.

Everything panned out. One year ago, the idea of "yet another badge" seemed bold, at best, and yet today this little fella can be found all over GitHub:

Inline docs

It has been an amazing experience so far.

Inch CI serves badges for over 1,100 open source projects. It finally supports HTTPS, got a redesign and saw the introduction of Elixir and JavaScript support.

The first big "Thank you" goes out to the really early supporters of Inch, namely @splattael, @solnic, and @jodosha.


A special thanks to Brandon, for this tremendously motivational reply:

"Inch pushed me to write inline docs for the first time." - now that's street cred.


To the community and the early adopters of Inch: I can't thank you enough for all the encouragement, constructive feedback, tweets and PRs!

What an amazing journey.


Fork me on GitHub