LSD CSI Sprint Recap

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
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 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
Subscribe with RSS Syndicate content