Contribute & Learn Drupal Together :: Mon Feb 27, 2012

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
mike stewart's picture
Start: 
2012-02-27 19:00 - 22:00 America/Los_Angeles
Organizers: 
Event type: 
User group meeting

Come contribute! The 4th Monday in Long Beach we're holding meetups to coincide with core office hours.

Join us in Long Beach or meet us online in our google+ hangout. The first few meetups have been fantastic! During each we either contributed patches or helped somehow in the process. As a result we've already helped get code committed to Drupal core! Want to help? Can't code? no problem. There truly is something for everyone to do. We'll help teach you.

The agenda is simple. Show up, bring a smile, and be prepared to work. Optionally, post link(s) to issues youd like to work on in the comments below. Otherwise, we'll get started on novice issues together.

We'll try to breakoout into groups. Typically 2-5 people per group working on a single issue. We have three rooms and 1-2 projectors for groups to share. We also use google+ hangouts if you'd prefer to joinn us virtually. We share the hangout room video & audio on even another big-screen display -- and we have at least one high definition camera on the room. If you have a Mac with an Apple proprietary video connector, please bring a dongle so you can share video on a projector.

MEETUP INFORMATION
Monthly muse: Easy peasy things that help.
When: 4th Monday (Feb 27, 2012) :: 7:00pm - 10:00pm
Doors open early (by 6p) and often close late (10p+). Come early to help setup & chat. RSVP below by clicking sign-up
Where: LA NET
4182 N. Viking Way, Suite 214
Long Beach, CA 90808
Online: Unlimited: hangout icon IRC channel: #drupal-la
Up to 10 people: Only local images are allowed. google+ Hangout
Agenda: Find or bring an issue. Preferably before the meetup.
Post issue suggestions in comments below. Or look here: http://drupal.org/project/issues/search?text=&projects=Drupal+core&assigned=&submitted=&participant=&status[]=Open&issue_tags_op=or&issue_tags=Novice
__Free Food & Drink:__ Thanks to our sponsor and local Drupal shop:
Only local images are allowed.  

media done right

Comments

Are we still planning the pre

frob's picture

Are we still planning the pre meetup study group? if so what is the topic?

Yes. I'd like to do this.

mike stewart's picture

Yes. I'd like to do this. Unless someone has another idea on time/place let's plan on meeting up at
cirevello's anytime after 5pm to eat or drink & study? too early? not early enough?

I'd like to dive into the guts of a core module or something similar.

--
mike stewart { twitter: @MediaDoneRight | IRC nick: mike stewart }

With the thought of doing

frob's picture

With the thought of doing something potentially future forward, how about a look at entities? We can use the entity api module as the starting point.

D8 Entity API to core at Denver Sprint

bvirtual's picture

I want to do the module "Entity" http://drupal.org/project/entity also known as Entity API as well. I've been using it. Seems I might be the "leader" for this adhoc meeting?

Core has a part of the CRUD API, and in D8 there is an effort to migrate the module Entity into core. That said, what will we be doing with the entity api module? Work off issues? Or select issues for the meeting?

Or just learn the API, and how to use it? See module "Model" for writing your own custom entity module. It's a good starting point. It includes exposure to Views, and examples of how to create Fields in PHP.

Peter

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

Entity API module is one

BTMash's picture

Entity API module is one approach to writing entities. You can always create entities in core without using entity api (see Relation module) though you've already mentioned part of what is going on. But getting into the pros/cons on both approaches (along with looking at modules which work with creating dynamic entities such as entity construction kit) is a good idea.

Yes, there is a large movement to move a variant of entity api into core. A chunk is already in place but there is a lot more work to do. If you want to segue, we can work on issues highlighted at http://drupal.org/node/1346204.

Not exactly sure what the

frob's picture

Not exactly sure what the Relation module has to do with creating entities.

After reading our link I am a bit confused. The entity api module is in core for D8 isn't it?

Relation module shows how you

BTMash's picture

Relation module shows how you would work with the core entity system for D7 right now to create entities (relation doesn't require entityapi). Its not as simple, but its wholly possible. Something like eck, searchapi, media, etc show how you use entityapi to simplify the entity CRUD process.

As for entityapi in core, its mostly there (or more of the concept is, anyways. The person that wrote entityapi is now going to be the maintainer for entity in core for D8). But a lot of work needs to be done to make the current set of entities that are in core (node, user, etc) conform to working with entityapi instead of how it works for D7.

Core would be good for me at 5 PM

bvirtual's picture

I'll be there before 5 pm. Do they have wifi? http://www.cirivellos.com/ did not say on home page. They do have rooms of any size... call them ahead of time and ask for the cost of small room?

UPDATE:

I viewed a dozen pages at their web site. (562) 420-2113 is their number. I called, bad connection, and learned they have no wifi, before I gave up repeating my questions.

There is no charge for rooms, just book ahead of time as they fill up, or so their web site states.

Their rooms have AV projector and screen, but the small one in the gallery had only one picture and did not show all four walls, so a screen could be there. Do we need a screen and projector?

Peter

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

bvirtual's picture

I'd like to "pre-select" issues, get a list of issue numbers, and "present" them to the attendees, and have them assist in choosing the "top" 3 for that night, and let members break off in the subgroup that will handle their preferred issue.

Start at http://drupal.org/novice and use the direct link to search for novice level issues.

Below are the steps to evaluate an issue for deciding if our meeting will tackle it. This outline will be modified over time, and maintained at our wiki. The outline is what I have found is needed the last three of our meetings. There are additions I have not added, but the below is the minimum needed.

  1. Read the Description
  2. See if anyone has posted on it recently, or has it been assigned.
  3. Read the last few posts to see what the status is.
  4. Read all the posts from the beginning. Yes, it can be dozens of posts.
  5. If you "like" to work the issue, try contacting the assignee or poster(s).
  6. Duplicate the issue by installing D7, install any modules, etc, and find the error.
  7. Look at the code.
  8. Create a fix.
  9. Test the fix and see you can not duplicate the issue anymore.
  10. Repeat the above.
  11. Roll a patch.
  12. Post the patch to the issue.
  13. Wait for for the bot to run the test, every half hour rumor has it.

There can be an exception to the above, the issue not applicable to D7, already fixed in D7, divided into 2 more issues, are some the 'harder' situations I have come across since I started contributing.

I'm thinking a day or two before the meeting, the weekend, I will try my hand at finding 6-8 issues for our pre-meeting. I will do steps 1, 2, 3, and 4, for maybe a dozen issues. More likely only 6 issues, and I'll pick 2-3 of them, and the night of the meeting, I will have my first "choice".

I'll include your additions and corrections to the above, for putting into our wiki.

Peter

Peter

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

sounds like a great way to

mike stewart's picture

sounds like a great way to help!

--
mike stewart { twitter: @MediaDoneRight | IRC nick: mike stewart }

Sounds like a good plan.

BTMash's picture

Sounds like a good plan. There are a bunch of critical issues that need to get through at http://drupal.org/project/issues/search/drupal?status[]=1&status[]=13&status[]=8&status[]=14&status[]=15&priorities[]=1&priorities[]=4&categories[]=bug&version[]=8.x&version[]=7.x if you want suggestions on larger issues to work on.

I will most likely be working on upgrade path stuff (see http://drupal.org/node/1352000, http://drupal.org/node/1263208, and more importantly, http://drupal.org/node/1364798). Personally, I need help with someone running into the issue at http://drupal.org/node/1428550 so it can get fixed up (its a D7 issue).

1428550 is kind of a freak

frob's picture

1428550 is kind of a freak occurrence, though we have (i think) narrowed it down quite a bit.

xosview follow up - Ubuntu system load GUI

bvirtual's picture

During the meeting I indicated I use a light weight Linux tool called xos, really command xosview

Below is my script I use to display a small bar chart in the lower left corner. Modify the network 450000 to match your top speed of your DSL line (that's what I do).

xosview -network 450000 -xrm "xosview*netIface: eth1" -xrm "xosview*cpuPriority: 10" -geometry 135x220+-20--10 +load +mem +disk +gfx +net +cpu -swap -page -int -xrm "xosview*borderwidth: 10" -xrm "xosview*title: xos" &

There are many, many more variables you could display.

Peter

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

LA Drupal [Los Angeles Drupal]

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week