Community Ideas

• Use-case focused profile for D8 core - right now contrib D7 http://groups.drupal.org/snowman
• UUID
• Pathauto in core

Drupal Commerce (find me in #drupalcommerce to talk these over):

1. Simplify the relationship between nodes and products; focus is on usability for simple product / node creation (i.e. through the use of an inline product add / edit form as a product reference field widget), bulk product creation / import and update, and product sibling groups (i.e. all the sizes of a particular style of t-shirt).
2. Coupon system interacting with Rules to apply discounts to products; will require a checkout pane, a Rules condition, and likely a simplified user interface that can translate a table of coupon settings into a default Rule so the store administrator does not have to actually configure Rules if the don't need anything complex.
3. Simplified tax UI and/or simplified discount UI: again, as with the last item, we're exploring ways to hide the Rules UI from casual store administrators. Both taxes and discounts right now are only possible through configuring product pricing rules, and Rules 2 is quite complex if you aren't a developer. I'm interested in seeing projects collect a basic set of parameters and translating these into default Rules on the back end so store administrators can do things like specify a country or state for a tax rate or choose a role to get a % discount without actually having to configure Rules for these. The parameters will be necessarily limited, and exploring the best set of simplified parameters will be part of the scope of the project, determined in conjunction with Ryan and Bojhan.

Generic Drupal projects (that help Commerce as well):

1. Unified entity access control / revision support / view API. Basically, a project focused on core improvements for D8 and/or extending the Entity API such that we have centralized systems for managing entity access, adding save support for revisions (probably harder than I think), and / or having a "view" API so we have a hook_entity_view() like we do for loading / saving / deleting. This last one actually ties into the next idea and should be developed in conjunction with it or as part of it...
2. Comments on any entity. Right now they're still tied to nodes - for no good reason other than the Comment schema and the fact that there isn't a generic hook_entity_view() that Comment can plug into to add comment data to an entity's renderable array.

I'm happy to mentor along with a couple other developers at Commerce Guys. One of our past students, bojanz, is currently interning for us and is eager to give back as a mentor as well. It would be nice for candidates to be able to maintain their work going forward, but if not, we need to ensure that someone in the Drupal core or Drupal Commerce development community is able to carry the work forward.

• Exposing translation activity in Drupal project, to increase participation
• Gettext API for Drupal contrib and core; work on generalizing an outdated part of core, prove it in contrib and get it into Drupal 8!

1. Search on administrative pages: Create a module to add in-page search to important administrative pages such as /admin/permissions, admin/modules, admin/content, admin/config and more. There are currently a few working modules, but no module that captures all the different pages and provides a complete user experience. This project will require jQuery knowledge and interest in creating a usable search interaction for the different pages.

• Geospatial Data and Mapping: This could include geo support in core, working on the OpenLayers module, or working on new Mapping abstraction module.
• Encryption: Help build a solid encryption solution either as contrib module or as core API.

• Help updater client/server
• Conditional text (probably taken by yorirou)
• Outlines/maps (being worked on by Itangalo)
• Main help module (defining entities and fields, contextual linking)
• Glossary

• previous discussion
• previous GSoC project (switched to server-only validation, later abandoned)
• recent discussion about potential solution (combining Clientside Validation and Form API Validation modules)