Development plan

Notes:

• Time in [square brackets] is an estimate, (hours in normal brackets) on done items is time actually spent.
• 21.5 hrs - early design meetings and documentation - already done

Alpha (19 September)

Delivers a D7 Panopoly-based site based on TN's own new distribution, with component/plugabble (initiative) widget system, internationalisation capabilities.

Done

1. 26 August 4h: 0.25 Clone winacc_panpoly distribution repo -> rename to transitionnetwork_d7 - Distro here: ​https://github.com/transitionnetwork/transitionnetwork_d7 (1.5 hours)
2. 1.0 Change profile to be TN-focused, include key modules: (0.5 hours)
   • Address
   • Geofield, geocoder, geophp
   • Leaflet
   • dnl, i18n
3. Set up local development site (1.5 hours).
4. 28 August 4h: R&D into
   • various aspects: BOA, Leaflet/OpenLayers?, makefiles etc (0.5 hours)
   • R&D into internationalisation dnl, i18n (0.5 hours)
5. Create Initiative content type with required fields (0.5 hours)
6. Create Base and Initiative feature, push to GitHub? (1.5 hours) - ​Base repo, ​Initiative repo

Development total so far: 8 hours

To Do

1. [4] Decide on User profile-related modules, then create User Profile feature (decide approach Profile2 vs core user fields etc)
2. [4] Change profile and extend Distro to be TN Hub focused.
3. [1] Create 'Transition Network Tweaks' module to put minor overrides in.
4. [4] R&D then add Social media login/integration
5. [2] Add Services related modules as needed
6. [2] Investigate I18n & related language/internationalisation modules & best practice
7. [1] Set up test site on Jim's server
8. [3] Create very simple Bootstrap-based theme (little/no customisations)
9. [8] Begin/convert new Widget modules (core, initiative, registration etc) -- see
10. [8] Enable French language and translate some key bits with Google Translate.
11. [32] Convert D6 widget modules & features to D7 per IIRS/SolutionDesign
12. [8] (Ben?) Update widget HTML/CSS/theme as needed.
13. [8] Update all views, panels, features to handle language context.

Expected total: 12.25 +/- 5 (= 98 - 140 hrs)

Beta (? October)

Delivers a cleaned/tweaked up system and some web services connections back to the D6 site, plus an installed and integrated beta website.

1. [12] Fix bugs/do tweaks
2. [32] Add Services to sync between D6 <--> D7 sites (and future hub sites) with resilient queuing, plugable architecture
3. [12] Test, tweak, prep Beta, install, integrate

Subtotal: 6.5 +/- 3 days (= 52 - 76 hrs)

Total: 18.75 +/- 8 days (= 150 - 216 hrs)

NB: from Ed - Jim - your total time budget is 150 hrs. This gives us 3 days with a second programmer in beta phase (agreed as good idea). Bear this in mind!