Entries feed - Comments feed

Friday, 28 July 2017

Processeer.io - a Powerful and Flexible Report Builder for JSON APIs

More than 2 years ago, I wrote about a prototype I built, called Spectateur, that allowed users of Socorro to create custom reports for their needs. The idea was to make it easy to write a script that pulls data from a public API, transforms it and then displays it as a nice table or chart. I strongly believe in this idea, and have been making various progress on the concept over the last 2 years, until I finally put together a nicer, more complete prototype at the end of 2016. I called it Processeer, and it's available at processeer.io.

Continue reading...

Monday, 20 June 2016

Game Dev Party Jam #10: Llamazord

Two weekends ago was the 10th Game Jam of the Game Dev Party association, where I was once again both participating and helping with the organization. And once again I proposed a game idea and I was lucky enough that people liked it and voted for it! So I gathered a team of 6 awesome people, 3 developers and 3 designers, plus myself as a part-time coder part-time manager, and we made a game.

Continue reading...

Friday, 25 December 2015

How to include HTML in your React app with webpack

One of the few things that I find unpleasant with React and JSX is that it's not great for writing long static HTML content. Up to now I never encountered that problem, but I heard some colleagues complain about it and knew that it was indeed a negative point.

Continue reading...

Monday, 6 July 2015

ensy — Entity System Reloaded


During the last Game Dev Party Jam in Lyon, I pitched a game idea with the intention of building that game with Web technologies and my Entity System library. I had been waiting for an occasion to use that lib in a "real" game, and knew that would be the perfect moment: the 8th Jam happened over 3 days (when it usually is only 2) and was thus ideal for trying out risky things.

Continue reading...

Wednesday, 10 June 2015

Rethinking Socorro's Web App

Credits @lxt

I have been thinking a lot about what we could do better with Socorro's webapp in the last months (and even more, the first discussions I had about this with phrawzty date from Spring last year). Recently, in a meeting with Lonnen (my manager), I said "this is what I would do if I were to rebuild Socorro's webapp from scratch today". In this post I want to write down what I said and elaborate it, in the hope that it will serve as a starting point for upcoming discussions with my colleagues.

Continue reading...

Wednesday, 3 June 2015

[Snippet] Django Shell: making a user a superuser

I can never remember this snippet and I found myself duckduckgoing for it a few times, so I wanted to write it down somewhere where I can easily find it (and maybe it will help people looking for it, since I can never reliably find it in search engines).

To start Django's shell:

./manage.py shell

And to make a user a superuser:

from django.contrib.auth.models import User
user = User.objects.get(email='me@example.org')
user.is_superuser = True

Thursday, 26 February 2015

Spectateur, custom reports for crash-stats

The users of Socorro at Mozilla, the Stability team, have very specific needs that vary over time. They need specific reports for the data we have, new aggregations or views with some special set of parameters. What we developers of Socorro used to do was to build those reports for them. It's a long process that usually requires adding something to our database's schema, adding a middleware endpoint and creating a new page in our webapp. All those steps take a long time, and sometimes we understand the needs incorrectly, so it takes even longer. Not the best way to invest our time.

Continue reading...

Tuesday, 2 December 2014

Socorro: the Super Search Fields guide

Socorro has a master list of fields, called the Super Search Fields, that controls several parts of the application: Super Search and its derivatives (Signature report, Your crash reports... ), available columns in report/list/, and exposed fields in the public API. Fields contained in that list are known to the application, and have a set of attributes that define the behavior of the app regarding each of those fields. An explanation of those attributes can be found in our documentation.

Continue reading...

- page 1 of 5