LA Drupal Issues

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!
Posted by frob on January 5, 2012 at 3:52am
Last updated by tmckeown on Fri, 2013-03-29 17:36

The purpose of this page is to have a page that contains all issues that we (in Drupal LA) are working on. These would be any core or contributed module issue.

Here are a set of useful links for contributing back to Drupal.

Issues that we have already tackled as a group

What we're working on

* (thund3rbox) http://drupal.org/node/1306324
* (frob / bvirtual) http://drupal.org/node/1428550
* (mike) http://drupal.org/node/939462#comment-5662130
* http://drupal.org/node/687180 => Deleting a taxonomy vocabulary leaves term reference fields still pointing to it, and a PDO Exception when creating content => Drupal core, taxonomy.module, major, patch (to be ported), 56 comments, 22 IRC mentions
* http://drupal.org/node/1431076 => Overlay does not work with prefixed URL paths => Drupal core, overlay.module, major, needs review, 22 comments, 5 IRC mentions
* http://drupal.org/node/1364798 => Impossible to generate meaningful diffs of upgrade db dumps
* (tmckeown) http://drupal.org/node/1955292 => #1955292: JSHint edit => Drupal core, javascript, normal, needs work, 6 comments, 5 IRC mentions

If you have an issue that near and dear to you; if you are still awaiting rtbc on a patch you submitted please list it below.

Comments

I read

Posted by patrickfgoddard on February 28, 2012 at 5:55am
patrickfgoddard's picture

I read through:
http://drupal.org/node/687180

Last comment (as of typing this) says:

"Should be a straightforward backport, tagging novice."

Has anyone done a backport? Wasn't sure how to do.

I wouldn't put anything with

Posted by frob on February 28, 2012 at 8:50pm
frob's picture

I wouldn't put anything with "PDO Exception" in the title in the novice category.

cTools, Ajax Load, and Quicktabs

Posted by mrjeeves on March 14, 2012 at 9:15pm
mrjeeves's picture

Hey everyone, I loved meeting the group last night at the meetup and am posting my issues (lol) here for everyone to review.

cTools deep copy (merge) settings from ajax (this allows further development on the ajax load model for D7, as well as fixing many other issues):
http://drupal.org/node/999164

Nesting quicktabs needs to use machine name instead of qtid:
http://drupal.org/node/448938

Change order of execution for js settings merge and js behaviors (first step in fixing issues with ajax views inside of ajax quicktabs):
http://drupal.org/node/345525

Some of these may need to be updated to latest release, I haven't had time to check and my dev box is only remote access at the moment.

Thanks again,

Chris.

Thanks Chris and Welcome to Los Angeles!

Posted by bvirtual on March 15, 2012 at 1:25am
bvirtual's picture

Chris attended his first LA Meeting last night, coming from years of Drupal development in Missouri (did I recall that right?). Chris learned about the Long Beach Contrib Wiki, as a place to post Drupal.org issues for fellow LA members' consideration. Thanks Chris for contributing!

CTools and quicktabs issues have few comments, and might be doable in one meeting ... ?

I'm thinking the Long Beach Meetup ought to look at the first two, even if they are not novice, just to start moving towards intermediate level, and see some AJAX/JS code.

While the 3rd issue about execution order has 85 comments, the last being one about part of the issue might be solved in yet another place.

Last meeting I got into reading one issue with 60+ comments, which takes a good part of the meeting time to digest. To not lose my contrib, I did post 3 times, my conclusions of my research over the course of the meeting.

Point is, to get the ROI on attendee time, I might, might, recommend avoiding issues with more than 30 comments. As too time consuming for 2-4 members to read during meeting time. I'm sad to say this about "big" issues.

I'd be 'more' happy to say the meeting time resulted in a commit. Or several commits. The idea is to reward attendees with "success", which I feel encourages continuing attendance. Later this year, dealing with "big" issues can be re-evaluated.

I know the wide variety of knowledge I have gain from my fellow dedicated attendees has been very valuable to my skill base in Drupal. I'm hooked. Being able to talk to Drupal intricacies is an professional enhancement. Learning intricacies in a vacuum is hard, but at this meeting it's a joy.

Peter

LA's Open Source User Group Advocate - Volunteer at DrupalCamp LA and SCALE

The first two are certainly

Posted by mrjeeves on March 15, 2012 at 2:58am
mrjeeves's picture

The first two are certainly due for some serious consideration and testing, I would be thrilled to see some movement on those topics.

Would a summary of current progress on the longer threads be helpful in focusing the workflow? Since many of the comments are from novice site owners, I feel that I can quickly wrap up previous work and get the issues back on track. Another possibility is to branch the issues since I know that some of them deal with multiple use cases that may be more suited to separate queues.

P.S. Yes, Missouri :)

Thanks again for the warm welcome, I can feel the love.

Chris.

Issue 1352000 for me and others

Posted by bvirtual on March 15, 2012 at 1:52am
bvirtual's picture

Today, on IRC, Ashok lead me to look at issue 1352000, "Forward-port upgrade test clean-ups from 7.x to 8.x," which is about simpletest. My posted comment and commitment for some of time on the 28th: http://drupal.org/node/1352000#comment-5734032

I will spend 30 minutes reading this patch, and posting my promised comment to refine the roadmap I already posted.

Peter

LA's Open Source User Group Advocate - Volunteer at DrupalCamp LA and SCALE