Hi everyone,
As some of you know, I've been working on a number of issues across various projects in Drupal. I've released patches ready for review for a bunch of them. But at the same time, its been a little difficult to find folk that could read through it and leave feedback so it can actually be ready to get committed. Along the same lines, I'm sure there are a few others here doing the same and waiting for reviews on their issues (or looking for help on it) and perhaps stuck in the same cycle. I'm wondering if we could (or even should? maybe that's the bigger question?) pool our issues into a wiki so folk in the community know what others are working on and could maybe try and help out with the issue if they get a chance. I know the code sprints can sometimes don't go as planned but until we organize one out fully, this might be a nice way to participate on what's happening (and we would also have a clear list of things people could join in on should we have a code sprint :)
Comments
Great idea!
I think a wiki page for this is a great, great, great idea. Here are some links I'm personally interested in and can copy/paste when there is a wiki page.
The only patch I've authored (or co-authored, I forget) that needs review at this point is:
Token: add timestamp tokens (g, G, h, H, i, s, U) for hours, minutes and seconds
http://drupal.org/node/323441
I would love some help, though, reviewing patches that are in the issue queues of the modules I maintain:
Shared Email: Incompatible with email_registration module
http://drupal.org/node/1025840
Shared Email: Subuser integration
http://drupal.org/node/896520
For groups.drupal.org, I'd like to work on the following issues:
groups.drupal.org: Add a location field to group node
http://drupal.org/node/1074208
groups.drupal.org: Group/content notifications on groups.drupal.org cannot be set up
http://drupal.org/node/962424
For the issue of location fields on groups, I've already contacted Tom to see if he'd like to do a code sprint either virtually or physically or a combination of both.
Thanks!
Your list is a great starting point (I'll try to gather some time to be able to look through and try to review them). I'm hoping a few others will chime in as well. In the meanwhile, I'll post up some of the patches I'm working on as well (most of these are in a 'needs review' state). I'll keep this list down to things in Drupal Core :)
https://drupal.org/node/1015916
RTBC. This is ready to go. I also changed "tool tip" to "tooltip" to bring it in sync with the rest of core.
https://drupal.org/node/1067120
I didn't review the functionality but the patch conforms to coding standards.
https://drupal.org/node/1273478
I'm not an OO-master but I updated the summary of the issue so that it reflects that it's about failing tests that have unmet requirements rather than skipping them.
For anyone who works at more
For anyone who works at more than one company or organization (and would like their names and logos to appear on your Drupal.org profile), this might interest you:
Multiple values for current companies
https://drupal.org/node/968994