Large Scale Drupal (LSD) - Projects and Plans

Large Scale Drupal is a program run by Acquia's Office of the CTO. We work with large organizations where Drupal is of high strategic importance. Most of these companies are pushing the limits of Drupal and its capabilities.

It is clear that these organizations have something to contribute to the development of Drupal. Large Scale Drupal is a program dedicated to providing a forum for these organizations to collaborate around major issues they'd like to resolve in Drupal, and then work within the community process to realize these objectives. Through this program, large organizations will be able to contribute both ideas and resources to projects via the community.

Specifically, this group is used to present proposals selected by the group that represent large problems that each organization is willing to put resources toward. We'd like to start a discussion of these issues in the community to find out if the ideas have merit, and how we would approach solutions to these problems (cross posting where necessary).

Original blog post from dries: http://buytaert.net/announcing-acquia-large-scale-drupal-program

The Content Staging Initiative's home page: http://groups.drupal.org/large-scale-drupal-lsd-projects-and-plans/conte...

thamba's picture

Advanced frontpage node adminstration module - a proposal

We at Aller Media in Norway are implementing Drupal7 on some of our high traffic sites and we have the need for an advanced frontpage node administration module.

We have this functionality in our legacy CMS we developed in-house, and we plan to port this functionality to Drupal. I have researched quite a bit on this topic and have not found such existing functionality in Drupal. Although it could be hacked together with existing modules like Nodequeue/Draggable views, Scheduler, Views, Blocks and the Dashboard, it still does not satisfy the requirements.

Here is our requirement:

Read more
c3's picture

Large Scale Drupal Track on DrupalCon Sao Paulo

The first DrupalCon to be held outside the U.S. and Europe will take place in Sao Paulo, Brazil, on December 6-8. I’m excited to be part of the Content Team and the track chair of the large-scale Drupal track for this important event.

It’s the first time this topic has been included in its own track at a DrupalCon. I wrote a blog post with the track description, and an invitation for anyone who is interested to present a session: http://devsu.com/labs/have-experience-large-drupal-projects-submit-session

HJulien's picture

When a large project hits limits

I have a large feature-rich site (I'll call it site 1) that can't handle adding more functionality to it. However I need to find a way to allow 1 type of group on site 1 to have separate instances of ubercart i.e. most members in that group would have a store. approx 200.

I would need the 2 sites to be connected. The admin of the group on site 1 would become the owner of a store on site 2. Users on site 1 can buy on site 2. There would be a few shared tables for roles, content profiles and group node data and members.

Read more
indytechcook's picture

LSD CSI Prototype

The initial Prototype for CSI is live. The demo includes integration between SPS, ERS and collections.

The install is based upon http://drupal.org/project/sps_prototype. Please log any issues at http://drupal.org/project/issues/1701722.

http://prototype.csi.dev3.fayze2.com/
user: demo
pw: lsd-csi

thekellye's picture

LSD CSI Sprint 3 Risks

Risks for Sprint 3 - Risks and Plans

Risk 1: Integration points for Workbench, SPS, ERS and Reactions not identified in Sprint 3 planning could setback completion of working prototype.

Plan: A goal of our in-person sprint on 7/26 is to discuss all integration points to ensure all have been planned for and tasked appropriately for Sprint 3. We will review all the module integration points for workflow (jec006 and fmitchell), front end integrations (jec006), some refactoring of the framework specifically reactions (e2thex) and cleaning up collections (indytechcook).

Read more
indytechcook's picture

LSD CSI Prototype

The prototype for CSI will be hosted here: http://drupal.org/sandbox/indytechcook/1701722

thekellye's picture

LSD CSI Sprint 2 Recap

Sprint 2 wrapped up (7/24), or roughly 1d (8h) behind schedule. Great progress was made during Sprint 2 and the velocity of the project picked up greatly from Sprint 1 http://groups.drupal.org/node/242358.

Sprint 2 deliverables and milestones included building the plugins and modules per http://groups.drupal.org/node/233058 and http://groups.drupal.org/node/233098.

This high-level goal translated into the following tasks http://drupal.org/project/issues/search/1621176?issue_tags=lsd-csi+sprint+3

Read more
indytechcook's picture

Site Preview Module

The Site Preview System Framework has been promoted to a full project on Drupal.org http://drupal.org/project/sps

Development will continue here.

indytechcook's picture

Collections

I'm proud to announce that the collection module has been posted as a contributed project on Drupal.org. http://drupal.org/project/collections

indytechcook's picture

Interactive Information Bar

I'm pleased to announce that the Interactive Information Bar been release as a project on Drupal.org. http://drupal.org/project/iib.

This represents the first official community project to come out of the LSD CSI project.

indytechcook's picture

LSD CSI Weekly Update for 7/23

Here is the weekly development update.

Last week

  • Continued work on Sprint 2.
  • Presentations for LSD members
  • On Board Brade Blake for development Brade will not be joing the project
  • Prep for Sprint 3

This week

  • Begin Sprint 3.
  • Create initial Prototype
  • On site meeting in DC
  • Sprint 2 Review document and Sprint 3 goal documents
indytechcook's picture

LSD CSI Sprint 2 Risks

Risks for Sprint 2 - Risks and Plans

Risk 1: Goal clarity - The high-level schedule states "Build plugins, build modules" but the main goal of this sprint is to finish the core SPS system.

Plan: We originally had some tasks associated with this sprint that didn't directly fall under that goal, so we moved to Sprint 3 and brought some clarity to our current effort. Also defining the goal of Sprint 3 in advance i.e. this week, before next Monday, Sprint 3 kick off.

Read more
indytechcook's picture

LSD CSI Weekly Update for 7/16

Here is the weekly development update.

Last week

This week

  • Continued work on Sprint 2.
  • Presentations for LSD members
  • On Board Brade Blake for development
  • Prep for Sprint 3
indytechcook's picture

LSD CSI Sprint 1 Recap

Sprint 1 ended on 7/6. The following deliverables were part of Sprint 1 per http://groups.drupal.org/node/233058 and http://groups.drupal.org/node/233098.

  • "Build Framework"

This was a very high level and abstract goal. The actually tasks turned out as http://drupal.org/project/issues/search/1621176?issue_tags=lsd-csi+sprint+1.

During this Sprint we also worked out a more detailed view of the different parts of the system. http://groups.drupal.org/node/241743. This page also includes the different parts of the system that will be plugable

Plugable Parts

  • Widgets
  • Conditions
  • Overrides
  • Reactions

The controllers and manager of the system will have the ability to be completely swapped out by changing configuration. This will allow for complete control of the system without having to hack the module.

The sprint lasted 3 weeks rather then 2. This was due to the complexity of the framework design and the initial ramping up of resources. The primary measurement of the success of the sprint is in the quality of the code and the high test coverage.

The code can be access by cloning the git repository: http://drupal.org/node/1621176/git-instructions/7.x-1.

Test can by run by putting the module into your Drupal installation, enabling the "sps" and "testing" modules the running the tests for the sps module from either admin/config/development/testing or via the command line "php scripts/run-tests.sh --color --verbose SPS,SPSInteractive" from the Drupal root.

Sprint 2 will entail creating the plugins for the Framework along with the integration points with Drupal and other modules. Sprint 2 tickets are listed here: http://drupal.org/project/issues/search/1621176?issue_tags=lsd-csi+sprint+2.

Read more
indytechcook's picture

Weekly Update for 7.9

Here is the weekly development update.

Last Week

This week

Read more

System Architecture

Here is the current system architecture. There have been some changes from the original design along with details added. This will be updated with information as the project moves along.

The initial system design

Initial System Design

New System Design (with comments about how it changed)

High Level Diagram

New System Design

Layout Preview

Layout Preview

Read more
indytechcook's picture

CSI Weekly Update for 7.2

Here is the weekly development update.

Last Week

This Week

<

ul>

Read more
indytechcook's picture

CSI Weekly Update for 6/25

Here is the weekly development update.

Last Week

  • finalized meeting schedule
  • Developers are up to speed
  • First version of Plugin Framework was committed
  • Setters designs were flushed out. (The class design was changed a little, see http://drupal.org/node/1623104)

This Week

<

ul>

  • document detailed dev/testing process
  • Document Class design for Setters/Conditions/SiteState changes (http://drupal.org/node/1623104)
  • SiteState Complete
  • Continued work on Overrides/Forms
  • Read more

    CSI Development Process

    Development will follow the Drupal.org process with a few changes

    General Guidelines

    • All tasks will be on Drupal.org
    • All code will be a patch before it's committed
    • All patches must include tests (See testing methodology)
    • Keep issue summary updated to reflect what the code is * really doing
    • Keep related issue links in the issue summary
    • All functions should have document blocks
      • Summary
      • Purpose
      • How to use it
      • @params
      • @return
    • Use Readme files to talk about how the code fits together
    • Create *.api.php files for full code examples
    Read more
    Subscribe with RSS Syndicate content