Version 9 (modified by jim, 3 years ago) (diff) |
---|
Development plan
Note time in [square brackets] is an estimate, (hours in normal brackets) on done items is time actually spent.
- 17.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
0.25 Clone winacc_panpoly distribution repo -> rename to transitionnetwork_d7(1.5 hours) - Distro here: https://github.com/transitionnetwork/transitionnetwork_d7- 1.0
Change profile to be TN-focused, include key modules:(0.5 hours)AddressGeofield, geocoder, geophpLeaflet
Set up local development site(1.5 hours).R&D into various aspects: BOA, Leaflet/OpenLayers?, makefiles etc(0.5 hours)
Development total so far: 4 hours
To Do
- [1] Set up test site on Jim's server
- [12] Change profile and extend Distro to be TN Hub focused, needs extra key modules including:
- User profile-related modules
- Social media login/integration
- Services modules
- [0]
Look at Debut feature and include where sensibleNot needed at present - [4] Create Initiative feature
- [2] Investigate I18n & related language/internationalisation modules & best practice
- [4] Create User Profile feature (decide approach Profile2 vs core)
- [4] Create very simple Bootstrap-based theme (little/no customisations)
- [8] Begin/convert new Widget modules (core, initiative, registration etc) -- see
- [8] Enable French language and translate some key bits with Google Translate.
- [32] Convert D6 widget modules & features to D7 per IIRS/SolutionDesign
- [8] (Ben?) Update widget HTML/CSS/theme as needed.
- [8] Update all views, panels, features to handle language context.
Expected total: 12.25 +/- 5 (= 98 - 140 hrs)
Beta (? October)
- [12] Fix bugs/do tweaks
- [32] Add Services to sync between D6 <--> D7 sites (and future hub sites) with resilient queuing, plugable architecture
- [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!