76 Drupal.org projects match your search

Drupal.org is maintained by volunteers and the Drupal Association. These projects organize work on Drupal.org itself. For more about how Drupal.org works, see the FAQ.

Bluecheese

Bluecheese is Drupal.org’s custom theme. The theme must be implemented in accordance with the Drupal.org style guide.

This theme is only for use on official Drupal.org sites. Do not use this for businesses, local groups and other sites, which should have their own brand and identity. Questions and comments about use of this theme should go to the Drupal Association.

Test driven development infrastructure

NOTE (May 20/2012): Testing infrastructure Issue queue is currently being monitored over at the "Testbot" project page.

A project to manage the infrastructure for test driven development of Drupal core and contributed modules. This project extends work supported by Boris Mann and implemented by Moshe Weitzman.

This project is now live and reporting on automated test results: http://testing.drupal.org/tests

It is based on work funded by the Google summer of code project for test automation. Mentored by Thomas Ilsche and Rok Zlender during 2006, and 2007 respectively. Implementation of automated testing has been led by Rok Zlender, with support from Kieran Lal, and Robin Monks. Robin's work is based on his work with the quality project for Mozilla.

Moshe and Rok's work:
http://drupal.org/project/simpletest
http://drupal.org/project/simpletestauto

Robin's project demo: Drupaltestbed
Components:
freshen.php - Brings drupal source from CSV, runs install of the new drupal checkout.

action/install.php - Simpletest script for running the install script.

The Great Git Migration

This project is purely a container for issues pertaining to Phase 2 of the Git Migration. Mostly, this is here so that issues that don't have a specific home in other modules can avoid squatting in the infrastructure queue.

pifr_setup script: Set up QA testbots

This is the script which was formerly used to deploy testbots on http://qa.drupal.org. It's the pifr_setup script forked from http://github.com/scor/pifr_setup.

Current setup instructions instead: How to deploy a testbot

I don't think we'll end up using this again, but we might, so it's here for reference. But we may revamp this.

Interface improvements for groups.drupal.org

Student proposal for GSoC 2011:

Improvements to groups.drupal.org interface.

Drupal Association

The Drupal Association is an educational non-profit organization that tasks itself with fostering and supporting the Drupal software project, the community and its growth.

This issue queue is deprecated.

For questions, discussions, policy changes, and other items please use Drupal Association Group

Marketing

French Drupal 7 booklet

This is a live version of the original contributions/docs/marketing directory which used to be available in the CVS repository.

It contains marketing collateral, mostly by the EU local associations and for their use, like the source files in various formats:

Drupalcon Testbot Sprint Items

I needed a sandbox issue queue for the testbot sprint ... no other purpose.

DrupalCI: Drupal.org Integration (Modernizing Testbot Initiative)

This sub-project is responsible for integration between drupal.org and the 'Modernizing Testbot' infrastructure. This project will host the repository for any custom drupal code/modules meant for deployment on drupal.org (and specifically related to this initiative).

The 7.x-3.x branch of Project issue file test supports DrupalCI.

Drupal 8 Contrib Porting Tracker

A centralized place for tracking the porting status of contributed projects (modules, themes, distributions). This project consists of issues that show the D8 porting status of other projects. (Inception!)

kick_drupalCI

One-time download link after View and Edit

This project is designed to be used by security team members.

Groups.Drupal.org improve

Drupal Google Summer of Code Proposal

Who:
My name is Gabriel Massaki and I am studying Computer Science at the University of Campinas (Brazil).
My e-mail is "gabrielmwb at gmail.com" and my nickname on IRC "Gabriel_Massaki".

I live in Brazil, so it'll be "Winter of Code" for me, I study at night so during the day I will have time to work on the project.

Have you contributed to a open source project before?
No, but I always wanted to contribute, because I like the philosophy of open source projects.

Why do you want to do a project involving Drupal?
I really like webdevelopment and I’ve already played around with drupal. In the end of this year, I’ll start the development of a project for a biologist that will use drupal as the web platform.
By involving myself in this project, I’ll be able to help the community that [in the future] might help me.

Drupal is a really powerful tool for the web. And I want to make it better for me and everyone that uses it.

Overview:
I intend to improve the Groups.drupal.org UI for a better user-experience so that the drupal community may integrate in a better way. And also propose some fixes to correct the bugs when using the messaging/notification system.

Description:

Drupal.org webmasters

A project with issue tracker that you can use to report spam, request a confirmed account or user account problems on Drupal.org website.

"Webmasters" vs. "Content"

Issues related to non-documentation website content, such as case studies, marketplace listings, Planet Drupal feeds, front page posts etc. belong to the Drupal.org content project.

Issues related to documentation belong in the Documentation project.

"Webmasters" vs. "Infrastructure"

If you want to report a problem with the Apache and MySQL installation on drupal.org, the Mailman mailing lists, the Git repositories, and the various Drupal installations on the drupal.org domain, please use the Drupal.org infrastructure project instead.

What about subsites?

Most subsites have own issue queues:

If a sub-site is not in the list above, you can use the queue here to report problems.

Helping as a webmaster

Documentation

This is the main project for all Drupal documentation. To learn more about helping with documentation efforts, start with the Contribute to documentation section of the handbook.

Drupal.org infrastructure

An issue tracker for everything related to the Drupal.org servers. This includes the Apache and MySQL installation, the Mailman mailing lists, the Git repositories, and the various Drupal installations on the drupal.org domain.

If you want to report spam, broken links, or user account problems, please use the Drupal.org webmaster's issue tracker instead.

Drupal.org security advisory coverage applications

Drupal code review logo

This project is the place to post applications for the ability to opt into security advisory coverage.

For more information, see Applying for permission to opt into security advisory coverage.

Git on Drupal.org

This issue queue began as Git Migration Community Testing to collect and triage issues uncovered during the 'git phase 2' community testing period. Now that the Git migration is live, we will continue to use this queue for support. Issues may be moved to the queue of one of the 12+ modules that comprise the Git system when necessary.

When you report an issue here:

SupportDO

**A place for the Support Team to sync up our work on the initial support.drupal.org build while we sprint.**

DrupalCon Denver 2012 Website

That's right! The official issue queue of the DrupalCon Denver 2012 Website.

Purpose

Our aim is to use a Drupal.org sandbox for this site in an effort to use the ticket tracking system and for maximum visibility to the community, the Association, and for future teams building out DrupalCon websites. We'll be using COD as our base installation and customizing from there. So the first thing to help out doing is upgrading COD to Drupal 7. Go help!

Documentation

We are coordinating our documentation within the Association's Open Atrium website. There you can find any official documentation, high level metta discussions, environment details and credentials. If you need access, please ask in #drupal-colorado

Participation

If you would like to help build out this website, here's how you can become part of our team:

  1. Google volunteer signup http://tinyurl.com/4x8lqjk (if you haven't already)
  2. Open up an issue requesting to be part of the team. Subject: Membership

Prairie Initiative Sandbox - New Project Page Prototyping

http://groups.drupal.org/node/137914

This is a Sandbox project to collaboratively prototype potential directions to take Project pages, just like this one!

Current Version (2)

Version 1

Project Testing Status

Note: I've folded this project up and applied it as a patch against PIFT. Progress can be tracked in http://drupal.org/node/1228462

This module adds an "Automated Testing" tab to module project pages on Drupal.org.

This tab contains a form which can be used to trigger one-time branch tests of project branches via the automated testing infrastructure, and report back the most recent test results for any given branch, if any exist.

Refactor PIFR/PIFT unique branch identifier

Currently, the automated testing infrastructure uses a project's 'Release Nid' as one of the keys for that project ... and as sandbox repositories can not create releases, they can not be supported by the automated testing infrastructure.

Because it's used as a unique identifier in a number of places, this key must be unique across the d.o infrastructure.

Pages