core

Feature Freeze is creeping up on D8 faster than you think, so now's a great time to go check out how to help D8 core development initiatives!

Read all about it here: http://drupal.org/community-initiatives/drupal-core

That page will tell you:
- what D8 Initiative owners and contributors are up to
- the most important places you can help right now
- thank yous to special snowflakes who have helped
- general information and links for each initiative

We're hoping to do some sprints around a potential effort to get parts of Date in core at the DrupalCamp New York July 19-23 (http://www.nyccamp.org/) and Midwest Developer Summit, July 26-28 (http://midwest-developer-summit.com/).

The sprints will involve discussions about which parts should go into core and a strategy for getting them there.

Please join us if you can!!

Though Initiative Owners are doing a fantastic job of keeping up with their individual initiatives, we've recently heard that the community would like more visibility on D8 progress in general. We've been trying to find the right format and we've got something for you to check out! http://drupal.org/community-initiatives/drupal-core

The D8 team of Initiative Owners and its supporters want to make it easier for you to find the most important issues to work on, so we've put together a summary page that we'll be updating it every two weeks, and more frequently on an as-needed basis.

The last entity type just moved to classed objects, so all core entity types are classed objects using a defined interface now! See the change record for details!

I've been asked to edit the Standard Issue Tags for Drupal core page to correct its characterization of accessibility issues, and, as usual, the editorial eye found more needing to be fixed than it was asked to review.

Specifically in this case, there are cases in which two issue tags are difficult to distinguish from each other. "Accessibility" and "needs accessibility review" is one such instance. Another is "usability" and "needs usability review." The definitions given for these terms don't help clear things up, either.

Before I make sweeping changes, I would like to get feedback from folks who are familiar with the issue queue about a role- and intent-based approach for telling who should — or, sometimes, who may — use any particular tag.

[EDIT: This idea is temporarily code-named D.I.A.S., the Duplicate Issue Alert System]

I've been having a lot of conversations about HTML5 and Drupal 8 this week while in Chicago — both with people here and with people back in New York. And the Core Conversation proposal deadline is coming up soon!

This is what I'm thinking. Let's present a real-world "This Is What We Think Should Be Done". As a call-to-action, where people can get involved and there are leaders driving each thing.

I'm thinking of submitting this proposal. And present as a team, team-tag style (one person do each section):

I have just (fairly) successfully installed a Drupal multisite on my host (A2Hosting). The three sites access the core code base and their individual databases brilliantly. One HUGE problem. After I uploaded my standard set of contrib modules and themes to the sites/all/modules and sites/all/themes (respectively), none of the sites recognize them. The admin/modules only shows the core modules on all three of the sites.

På sajten jag jobbar på nu så ska det finnas en sökfunktion inbyggd i headern. Det finns ett form-fält klart men det är inte kopplat till något. Nu undrar jag hur jag går tillväga för att sätta ihop allt så att det fungerar såhär:

1) Användaren matar in valfritt ord i fältet
2) Användaren trycker "sök" eller trycker på enter
3) Formuläret postas till en view (/search/node)
4) Views letar efter ordet i flera fält (brödtext,ingress,rubrik,bildmetadata etc)
5) Views visar en lista med fields (sökresultatet)

If anyone from LA Drupal, or our neighboring groups, has submitted a Core Developer Summit presentation then please comment here. I'd like to get a sense of who else made a submission. Maybe we can sit together and represent L.A. Drupal Devs some.

My submission is titled "Encourage more usage of PHP Interfaces In Drupal" and the slides are available at: http://www.slideshare.net/ccharlton/drupalcon-developer-summit-2010-ligh...