Oops … fixed the permissions now.
“I originally wanted to post this comment within a dev group, but I didn’t have default permissions to do that,”
Congrats, you had found a bug in our site 
That’s indeed a good thing that you found it so early. I have fixed that issue now and you will hopefully find that Edgeryders Dev & Testing is a very open developer group. Apart from server passwords, everything is shared with the public. So, welcome to discuss site issues there. The permissions issue that you found was introduced by a change of the widget that governs group visibility in Drupal 7, when two days ago I added the Task feature. I guess I inadvertedly did that change when looking up the group fields, though I don’t remember.
This shows the downside of Drupal’s gazillion options: you can’t remember them all 
A similar funny story happened a few days ago: the main body field on edgeryders.eu was not showing any more, and I had no idea why. So I even had to create a script that overwrites the Drupal database (of a testing site) with values from a backup, table by table and then record by record, until I found the single “1” where a “0” was needed to display the body field again. Turns out I had forgotten about enabling a certain module, and the default permissions of that module where such that they broke the site (see my bug report about it).