Contributing Hurts

Well, I'm in the throes of trying to contribute to core for the first time, and I have to say, it's a painful experience. Your concepts and code are suddenly thrown open to pretty fierce scrutiny by the community at large.

When you're making your own module no one really cares what you do, as long as it doesn't compromise the security or operation of other modules. Not so with core. There can be some pretty harsh debate around what can and cannot go in to the framework.

I am currently trying to convince folk that it is a good idea to be able to group system messages by module. There's at least one guy who vehomently disagrees with me, though I'm not entirely sure why... Ho hum.

Anyway, solid scrunity is absolutely fair enough, given the consequence of doing something bad. For my part, I have to resist the urge to take things personally and keep calmly and politely plugging my point. As well as making sure I'm not plugging something stupid.

We’re Code Enigma

We’re one of the most experienced Drupal teams in Europe, best known for our work on large, technically challenging projects for all kinds of clients.

Our team is passionate about Drupal and open source software. Our whole company spends at least four weeks per year working on Drupal modules or other open source projects. We’re also strongly committed to putting design first, taking a mobile-first, content-out approach to creating websites. This ensures that the sites we build combine the power of Drupal with best practice design and development.