On this page

  1. The relationship between Managing News and Drupal
  2. How to contribute a code improvement or bug fix
  3. How to share new features or modules
  4. See also

The relationship between Managing News and Drupal

Managing News is built on a Drupal infrastructure, and much of its functionality comes from Drupal modules distributed on Drupal.org. Because of this, a lot of the community development work for Managing News actually happens on Drupal.org, through module issue queues.

There are some modules in Managing News that are not part of Drupal.org, but the general pattern for community development is the same. This document will help point you to the right resources to determine how and where you can make code contributions.

How to contribute a code improvement or bug fix

First of all, were your improvements made? Use the table below to determine where where the code came from.

Folder Hosting site Notes
/profiles/managingnews/modules/features code.developmentseed.org This folder contains modules generated by the Feature module. This entire folder is part of a single GIT repository.
/profiles/managingnews/modules/contrib Drupal.org This folder includes contributed Drupal modules found on Drupal.org
/profiles/managingnews/modules/custom code.developmentseed.org This folder contains modules that are hosted on developmentseed.org. Each module has its own GIT repository.
/profiles/managingnews/modules/developer Drupal.org This folder includes contributed Drupal modules that are useful specifically for development purposes
/profiles/managingnews/themes code.developmentseed.org This folder contains themes distributed by Development Seed.
/sites/* ?? Most files in the /sites folder will have been added after the initial install of Managing News. These files can be contributed or custom modules, contributed or custom themes, or uploaded resource files.
Most other folders Drupal.org Nearly everything else is part of core Drupal

Now that you know where the code came from, you should a better idea of where to contribute your changes.

For modules distributed on Drupal.org:

  1. Find the respective module page (http://drupal.org/project/your-module-name)
  2. Review that module's issue queue to find out if discussion around the issue you're having is already happening (drupal.org/project/issues/your-module-name)
  3. If an issue does not exist already, create a new issue that contains a description of your problem and your fix with line numbers, either in code tags, or as an attached patch (see here for more information about patches)

For modules or themes distributed on code.developmentseed.org:

The simplest method is to post an issue in the Managing News issue tracker with the solution in code tags or a patch (see here for an example of creating a patch with GIT).

Alternately, you can fork Development Seed's module or theme repository on GITHub, and make a pull request to alert the maintainer that you have made a code improvement you would like to see integrated.

How to share new features or modules

Features can be shared through a Features server. See here for information on what a Features server is and how to set one up.

Drupal modules are shared through a combination of git and project pages on Drupal.org. To learn more about getting a developer account, read [the guide to contributed code maintenance on Drupal.org].

See also

Related pages

External resources