Language Selection

English French German Italian Portuguese Spanish

Use Drupal to empower your OSS project community

Filed under

When I started my tenure as marketing lead for the Haiku project in 2006, my highest priority was to renovate the project's Web site. Haiku had been using a custom-coded site which was showing its shortcomings as the project and the community grew in size. The admins wanted a new site that was easy to add content to and maintain, preferably based on an open source content management system (CMS) with a proven track record. The Web team chose Drupal 4.7 for the task. After working with the web team and a few other contributors for a few months, I built Haiku a new Web site that included not only more content, but most importantly more participation from the community. A few months months ago, when I helped start a Haiku user group in the San Francisco Bay Area started, I set up the NORCAL-HUG Web site using Drupal 5.0. In both cases, I learned how to use Drupal as a tool to empower communities, so that they become more participative and engaged in your project.

Everything that you publish with Drupal is a node. Each node belongs to a content type, and each content type has associated with it a set of fields (e.g., title, body, author, etc.), settings (e.g., menu, path, comments on/off, etc.), and workflow (published, promoted to front page, etc.). The default content types are blog entry, page (for static pages), and story (for articles). You can enable more content types via modules that are installed by default, such as the Forum module for forum topics, or by installing and enabling additional modules (such as the Event module). You can also create your own content types, with custom fields, default settings, and workflow. For instance, you could create a FAQ content type with a Question, Answer field and Category fields to provide a Frequently Asked Questions page in your Web site (there is actually a FAQ module that facilitates this).

More Here

More in Tux Machines

Intel Cache Allocation Technology / RDT Still Baking For Linux

Not mentioned in my earlier features you won't find in the Linux 4.9 mainline kernel is support for Intel's Cache Allocation Technology (CAT) but at least it was revised this weekend in still working towards mainline integration. Read more Also: Intel Sandy Bridge Graphics Haven't Gotten Faster In Recent Years

Distributing encryption software may break the law

Developers, distributors, and users of Free and Open Source Software (FOSS) often face a host of legal issues which they need to keep in mind. Although areas of law such as copyright, trademark, and patents are frequently discussed, these are not the only legal concerns for FOSS. One area that often escapes notice is export controls. It may come as a surprise that sharing software that performs or uses cryptographic functions on a public website could be a violation of U.S. export control law. Export controls is a term for the various legal rules which together have the effect of placing restrictions, conditions, or even wholesale prohibitions on certain types of export as a means to promote national security interests and foreign policy objectives. Export control has a long history in the United States that goes back to the Revolutionary War with an embargo of trade with Great Britain by the First Continental Congress. The modern United States export control regime includes the Department of State's regulations covering export of munitions, the Treasury Department's enforcement of United States' foreign embargoes and sanctions regimes, and the Department of Commerce's regulations applying to exports of "dual-use" items, i.e. items which have civil applications as well as terrorism, military, or weapons of mass destruction-related applications. Read more

Linux Kernel News

Games for GNU/Linux