rszrama

Great work, Mike, and fun stats. Hope it continues to grow. : )

1. Generous function level and inline comments that explain the rationale behind code organization / approach. Code can be self-documenting, but intentions are not. A great programmer will ensure future maintainers / contributors don't break something for lack of understanding the original context.

2. No magic configurations. No implicit behaviors. Every optional behavior should be explicitly opt-in or opt-out.

3. Treat one as a special case of many. You will thank yourself later when you would otherwise curse the day you were born.

I believe Dries's words in his apology post were sincere, so I do submit that as evidence but understand you may find him untrustworthy. However, the willingness of people who practice BDSM who actually work for him to speak out on that post provides even more compelling evidence that Dries isn't known for discriminating on that basis:

http://buytaert.net/comment/132641#comment-132641

If Preston and other BDSM practitioners like him are fired from Acquia or removed from the Drupal community, I'll eat whatever crow you care to dish up.

Larry also writes,

> Dries, from what I understand, was first informed, without my knowledge, of the matter in early February, by the CWG.

Curious that the CWG referred the matter to him as part of their documented process (i.e. when an issue exceeds the scope of their charter). You may not be inclined to believe a word they say, but at the very least Larry's timeline does not contradict this detail as provided by Megan / Dries:

> The Community Working Group, which is part of Drupal’s governance structure, provided conflict resolution. When it became clear that some of the issues raised went beyond the scope of their charter, they determined that it was appropriate for the matter to be escalated to Dries. This is consistent with their existing policy and process.

The FAQ section on this post provides the clearest timeline from the "other side" that I've seen: https://www.drupal.org/association/blog/working-through-the-...

Regardless, multiple decisions were made before Dries and Larry talked, and it is your characterization of Dries as a meddler who is circumventing a process that I am declaring untrue by anyone's accounting of the facts.

We don't live in a binary world, there are other options here besides Dries abused his power or Dries did everything right... for example, the process itself may be deficient and in need of reform. Before slinging mud, we should at least consider that possibility.

That's not true by anyone's accounting of the events, including the aggrieved's.

Non sequitur, but you might be at least comforted by Drupal 9 abandoning the philosophy of backwards incompatibility. : )

http://buytaert.net/making-drupal-upgrades-easy-forever

Hah, I've only played this once or twice with my young daughter, but she still remembers it - very charming, polished game with a good cause.

Gesture-based movement would be very interesting. Using the app also got me to thinking about common interactions using links - i.e. click a monster's name to attack it, an item's name to pick it up, etc. That could take some doing, though - how could the client distinguish between an object vs. mob, for example.

Might be interesting to be able to hide room descriptions and tap to expand them somehow. I don't typically use them in-game anyways, and on the app it's even more in the way.

Works great! Went ahead and bought it for some MUDding I've been into lately. Turns out I already play AU on the list, too. How 'bout that! : )

Harry Potter? Twilight? Final Destination? (Oh, wait.)