Contributing to Drupal by helping module / core developers.
Doing a triage on a particular issue queue relieves the developer(s) from tracking all issues in their queue. Others have checked the issues for validity and completeness. This would mean a bug is a bug.
Here at Istos we would love to see a set of Drupal 7 modules that provide support for the complete OStatus stack and see where FOAF ssl could fit into that. The first step we are working towards at is to provide support for Activity Streams for the Drupal 7 port of the Activity module (thanks Scott!). Then we would like to combine these with the PubSubHubbub work to have a working example of Drupal users across Drupal sites subscribing to each other's activity streams.
The Display suite module is an API which other modules can use to store and manipulate display data for objects (nodes, users, comments etc). Modules implementing this API automatically get an interface for adding build modes, fields and plugins either through code or via the UI
One of the things that a default Drupal installation does is that it handles 404s for static files within Drupal itself. In other words, a 404 for a .css or .jpg file causes a full Drupal bootstrap. This is not necessary, and wastes resources on a site that gets lots of 404s: lots of code is executed, many database queries are performed, only to return a 404 for a static file.
Drupal 7 and Drupal community features of importance.
it's getting better and more fun and more interesting with every passing moment. And that's because of the stellar contributions of the dozens of core developers on Drupal 7 (and 6 and 5 and 4.7 and 4.6 and 4.5), the leadership of people and companies in the Drupal community, and all the people who contribute back %u2014 whether it's out of the notion of "giving back" or out of the self-interest of inviting the rest of the community to help them on their project.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution 3.0 Unported License.
