3 | | * This work is the beginning of phase 3 of TN.org |
4 | | * Drupal 7 (still a bit early for 8) |
5 | | * Requires a vision of how TN sees the international picture |
6 | | * New roles and responsibilities for people outside tech/support/staff team - in other countries |
7 | | * Opportunity - and decision point- to see this as a really international web project for different countries sharing services |
8 | | * If we go down a federated route, we will be introducing a new technical and financial decision making body with national hubs |
9 | | * Each language will require people to take responsibility for the roles |
10 | | * We think that doing one language first is do-able for September |
11 | | |
12 | | |
13 | | == Immediate things to do == |
14 | | |
15 | | * Describe options and issues succinctly: Jim and Ed |
16 | | * Get decision about strategic options from TN: Ed |
17 | | * Explain TN's strategic goals for International project for options elucidation: Ed/TN |
18 | | * Create working plan in excel: Ed |
19 | | * Create working budget in excel: Ed |
20 | | |
21 | | == Money == |
22 | | |
23 | | * £7,000 set aside for this work |
24 | | * £6,000 at £40 p/h is 18.75 days |
25 | | * £250 for 1 day theming |
26 | | * £750 for another developer to 'on ramp' |
27 | | * Jim at £40 p/h |
28 | | * Ben at £31.25 p/h |
29 | | |
30 | | == Dates == |
31 | | |
32 | | * First meet: 15/7 |
33 | | * Outline proposal to Ben for sharing with hubs: 19/7 |
34 | | * Outline documentation: week commencing 22/7 |
35 | | * Jim holiday: 24/7 - 28/7 |
36 | | * Second meet: 31/7 or 01/8 |
37 | | * Build begin: week commencing 5/8 |
38 | | * Option 2/3 decision point: mid-August |
39 | | * Build to product before hub meet: August/September |
40 | | * Hubs meeting: mid-September |
41 | | |
42 | | == People == |
43 | | |
44 | | * Lead developer: Jim |
45 | | * Design/theme: Ben? |
46 | | * Learning developer/EC friendly: another |
47 | | |
48 | | == Jim availability and meeting days == |
49 | | |
50 | | * July: Monday and Friday |
51 | | * August: Monday, Tuesday, Friday |
52 | | * Monday or Tuesday meetings |
53 | | * NB: Ed not work on Fridays |
54 | | |
55 | | == IIRS walkthrough == |
56 | | |
57 | | * Registration service for initiatives in local language: |
58 | | 1. Local language user and initiative registration functionality on TN.org |
59 | | 2. #1 as embeddable 'widget' functionality on National Hub website |
60 | | * Also discussed |
61 | | 1. CRM features for 'National Hub Profile Administrator'? |
62 | | |
63 | | |
64 | | |
65 | | == Roles required per country == |
66 | | |
67 | | * Administrator |
68 | | 1. to provide user support and manage the service and data per country |
69 | | 2. exists currently as the 'National Hub profile administrator' - might be an extension of that role |
70 | | * Translator |
71 | | 1. a dedicated service administrator per country to translate content that drupal doesn't do automatically |
72 | | |
73 | | |
74 | | == Issues == |
75 | | |
76 | | * Need clear boundaries around what is translated - e.g. having the main navigation in English (non-negotiable) will confuse |
77 | | * Translating core functionality (user acct and initiative profile) vital - no point making them register user acct in English |
78 | | * BIG question: Is this a small section of a UK hub site, or the beginning of a range of international sites sharing a service? |
79 | | |
80 | | == Options == |
81 | | |
82 | | === 1: Multi-lingual capable widget-friendly service on existing drupal 6 platform === |
83 | | * Will meet basic requirement in existing framework |
84 | | * Most easily achievable but not future proofed |
85 | | * Exists in current 'UK as centre' model |
86 | | * No integration required (i.e. less backend work) |
87 | | * Drupal 6 very weak on international/translation/location |
88 | | |
89 | | === 2: Build new initiative feature in new Drupal 7 platform === |
90 | | * Will meet basic requirement on new framework |
91 | | * Assumes existing 'model' - i.e. monolithic UK site is the centre, Int'l as subsections |
92 | | * Integration required (ie. more backend work to port new platform back to old platform with existing directories) |
93 | | * Could be some overlaps in language (e.g. between menus) and administration (e.g. country admin sends msg to other country initiative ppocs) |
94 | | * Could well lead to an international landing page pointing to different country areas with related features |
95 | | |
96 | | === 3: Build new initiative feature in new Drupal 7 platform with new 'distributed' international architecture === |
97 | | * Will meet basic requirement on new framework |
98 | | * Assumes new 'distributed' model - i.e. de-centralised approach enabling separate country-specific features using a shared services platform - and UK is not the 'centre' site |
99 | | * Assumes a view where hubs can and will take responsibility for their own inter-dependent country service which shares the core data and services but not necessarily any/all of the features |
100 | | * Shares much of the earlier development work of option #2 - there will be a fork in the development path when we reach user administration |
101 | | * Could well lead to an international landing page pointing to different country areas with related features |
102 | | |
103 | | == First draft of tech tasks == |
104 | | |
105 | | * NB: this doesn't cover management time for meetings, documentation etc. |
106 | | * Core stuff: |
107 | | * New site - Panopoly and D7: 1 day |
108 | | * Add initiatives and views: 1 day |
109 | | * Rebuild widget in D7: 2 days |
110 | | * Synch for 2 way services: 5 days |
111 | | * New service theme: 2 days |
112 | | * Editorial and other workflow: 1 day |
113 | | * Import data into D7: 2 days |
114 | | * User authentication/SSO: 2 days |
115 | | |
116 | | * Internationalised stuff: |
117 | | * 118a and views work etc.: 3 days |
118 | | * Build country home pages etc.: 1 day |
| 3 | InternationalInitiativeRegistrationService/FirstPosition First position page - outline following Jim an Ed's meet 15/07/13 |