Voting starts in March for the Drupal Association Board election.
As a follow up to my patch port here: http://drupal.org/node/1611848 i noticed that in some cases I was still having issues where features were considered "Overriden" after loading them on a different server.
Doing a diff of a feature generated on the "overridden" server versus on my original server reveals that revision_uid and various file field timestamp fields were different. For revision_uid, it obviously makes sense that they would differ, but if I've enabled "Reset value on import' with revision author, then revision_uid should be somehow ignored when doing the feature detection.
Similarly, as part of the patch port - even though created/updated timestamps are cleaned up, it seems like all general timestamps should be cleaned up - these are highly volatile data fields, after all.
I would like to help out more directly, but I'm honestly brand-spanking-new to the Features API. If someone could at least point to me the feasibility of this or where to start looking, I'd be happy to spend some bandwidth producing a patch.