Version 22 (modified by jim, 3 years ago) (diff) |
---|
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
- 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) - 1.0
Change profile to be TN-focused, include key modules:(1 hours)AddressGeofield, geocoder, geophpLeafletdnl, i18n
Set up local development site(1.5 hours).- 28 August = 3h:
R&D intovarious aspects: BOA, Leaflet/OpenLayers?, makefiles etc(0.5 hours)R&D into internationalisation dnl, i18n(0.5 hours)
Create Initiative content type with required fields(0.5 hours)Create Base and Initiative feature, push to GitHub?(1.5 hours) - Base repo, Initiative repo- 29 August = 4:
Social login decided, added to makefile: HybridAuth? Social Login(0.5 hours) R&D for user profile modules, added user profile2 module(0.5 hours)Ed Mitchell & Jim Kirkpatrick Skype PM/Design/Progress meeting(1 hour)Looked into: Countries, Location Taxonomize and decided to KISS for now. (0.25 hours)R&D/Decision Made: NO user location-related fields present on basic Drupal account, First, Last & Middle name fields only. ALL location and other features for users will be on Profile2 and defined later.(0.25 hours)Added realname and realname_registration to remove need for username on registration(0.25 hours)- [UNDERWAY .75] Create User Profile feature (decide approach Profile2 vs core user fields etc)
Development total so far: 11 hours
To Do
- [3] R&D Add & set up Social media login/integration, convert basics to feature.
- [8] Begin/convert new Widget modules (core, initiative, registration etc) -- TO BREAK DOWN ONCE UNDEWAY
- [2] Investigate I18n & related language/internationalisation modules & best practice
- [4] Debug & improve Hub install profile.
- [1] Set up test site on Jim's server
- [3] 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
- [4] Create 'Hub Profile' on clone (STG?) of D6 TN.org containins basic text, country, language and widget displays.
- [8] (Ben?) Update widget HTML/CSS/theme as needed.
- [2] Add Services related modules as needed
- [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.
- [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!