Voting starts in March for the Drupal Association Board election.
Last updated January 23, 2012.
The Field API is major new functionality in Drupal 7 to provide custom data types just like CCK did for previous versions of Drupal. Field API became part of Drupal 7 in CVS in February, 2009, but there is still much to do.
To help you get started:
- There is extensive Field API documentation (though it can always be improved).
- Field API tutorial.
- Examples Project has a Field Example and a Node Example (with fields). You can also see these on api.drupal.org
- We are developing a Field API FAQ/HOWTO. It needs more content.
- If the issue list below isn't enough for you, you can get a complete list of all Field API issues at the d.o issue queue.
- Also see Updating CCK Field Modules from D6 to D7.
Grab a patch, get mentored!
The Field API is a great way to get yourself involved directly in Drupal core development. We realize, however, that Field API is a big, new, scary chunk of code that is not the easiest thing to jump into. The Field API team wants to help you get up to speed, so we've created the Field API mentoring process. Here's our promise: If you assign a Field API issue to yourself and take responsibility for it, the Field API mentors will help you learn what you need by participating in the issue and answering questions on IRC.
Below, I've organized the issues by category and assigned each a difficulty rating. These are very rough estimates and could be significantly inaccurate, but are at least a general guideline for how complex the issue/patch is.
Field API forms
Field API internals
1: Simple. One line changes, etc. A great way to get your feet wet!
2: Very easy. A very localized code change, probably no more than a few lines; a small, straightforward test case; reading a simple function and writing its PHPdoc; reviewing a simple patch.
5: Average. Requires a decent understanding of that component of Field API (e.g. Field Attach), and the code/docs/tests to write span multiple functions, perhaps involve small API changes; reviewing a patch whose issue might have been a 6 or 7 but now that the code is written it isn't that complex.
8: Challenging. Involves significant new design work; inventing or refactoring of significant components of Field API; documenting complex issues; writing subtle and difficult test cases.
10: Hard. No one has any idea what to do. Help!