Difference between revisions of "Wishlist for architecture"

From wiki.gpii
Jump to: navigation, search
(What would you like to see the architecture working on)
(New Features: relevant JIRA issues)
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
== What would you like to see the architecture working on ==
 
== What would you like to see the architecture working on ==
  
* Listening to device reporter - 0.2 / 0.3 (Android)
+
* Listening to device reporter - 0.2 / 0.3 (Android) ('''No JIRA''')
* Lifecycle manager and its relation to the service synthesizer tool.
+
* Lifecycle manager and its relation to the service synthesizer tool. ('''No JIRA''')
* Connecting semantic framework with the solution registry.
+
* Connecting semantic framework with the solution registry. ('''No JIRA''')
* Mapping internal application users to GPII users. (Single sign on) - 0.3
+
* Mapping internal application users to GPII users. (Single sign on) - 0.3. ('''No JIRA''')
 
* Document directory structure on the wiki - 0.2
 
* Document directory structure on the wiki - 0.2
 
* Document directory structure of the code
 
* Document directory structure of the code
* Conditional preferences (example omnitor; change settings depending on which person you’re calling) - after actual device/environment reporter - 0.2/0.3
+
* Conditional preferences (example Omnitor; change settings depending on which person you’re calling) - after actual device/environment reporter - 0.2/0.3 ('''No JIRA''')
* Supporting binary data
+
** latest proposal = [[Proposal for Declarative Preference Conditions]]? The format has also been worked on by the Context team (Andres et al.).
* Proper device reporting - 0.2 / 0.3 (Android)
+
* Supporting binary data. ('''No JIRA''')
* Common terms registry / listing
+
* Proper device reporting - 0.2 / 0.3 (Android). ('''No JIRA''')
* Snapshotting tool - 0.4 (start planning soon)
+
* Common terms registry / listing. Relevant JIRAs:
* Security - 0.3 (or at least have a plan!)
+
** [http://issues.gpii.net/browse/GPII-230 GPII-230: Define common terms to be used by in the second round of pilots] (work in progress; Claudia & Christophe)
 +
* Snapshotting tool - 0.4 (start planning soon). Relevant JIRAs:
 +
** [http://issues.gpii.net/browse/GPII-228 JIRA: GPII-228: Implement snapshotter].
 +
* Security - 0.3 (or at least have a plan!). Relevant JIRAs:
 +
** [http://issues.gpii.net/browse/GPII-45 GPII-45: Component for user-selected privacy and security settings]: also covers trusted components like matchmakers.
 +
** [http://issues.gpii.net/browse/GPII-33 GPII-33: Use an anonymous token for user identification instead of their name]
 
* Thin matchmaker (and transformer) / allowing web based applications and other apps more to use the common setting - 0.2
 
* Thin matchmaker (and transformer) / allowing web based applications and other apps more to use the common setting - 0.2
* .INI settings handler 0.2 (needed for pilots)
+
* .INI settings handler 0.2 (needed for pilots). Relevant JIRAs:
 +
** [http://issues.gpii.net/browse/GPII-73 GPII-73: Implement .ini settings handler].
 +
** [http://issues.gpii.net/browse/GPII-93 GPII-93: Fix INI library to support #comments and nested categories].
 +
 
 +
==Update June 2013==
 +
 
 +
===Short Term===
 +
* Continue the model transformation work. Relevant JIRAs:
 +
** [http://issues.gpii.net/browse/GPII-166 GPII-166: Replace the gpii.discoveryTool.modelTransformer with use of Infusion's model transformation functions].
 +
* Get the pilots branch merged into master.
 +
** Need to document clear JIRAs and wiki pages explaining each feature and the steps to test them.
 +
** Relevant JIRAs: [http://issues.gpii.net/browse/GPII-177 GPII-177: Move relevant parts of the pilot branch (excl. matchmakers) to master].
 +
* Automated integration testing (building on [[Cloud4all Integration Tests]] and [[Cloud4all Pilot Scenario Tests]]). Relevant JIRAs (in random order):
 +
** [http://issues.gpii.net/browse/SP-36 SP-36: Create instructions for Integration Testing and Pre-Pilot testing on the wiki].
 +
** [http://issues.gpii.net/browse/GPII-20 GPII-20: Write Integration tests for GPII/Cloud4All autopersonalization].
 +
** [http://issues.gpii.net/browse/GPII-237 GPII-237: For each SP3 application: Write integration tests].
 +
** [http://issues.gpii.net/browse/GPII-77 GPII-77: Synchronise GPII's jqUnit with the one that is held in latest Infusion with FLUID-4886].
 +
** [http://issues.gpii.net/browse/GPII-2 GPII-2: TestDriver for gpii modules fails on run].
 +
* Release GPII/Cloud4all v0.2:
 +
** Check [http://issues.gpii.net/browse/GPII/fixforversion/10001#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel Issues for V0.2].
 +
 
 +
===New Features===
 +
* Android convergence. Relevant JIRAs:
 +
** [http://issues.gpii.net/browse/GPII-98 GPII-98: Android dev json config stubs ].
 +
** [http://issues.gpii.net/browse/GPII-120 GPII-120: Refactor Android java modules].
 +
** [http://issues.gpii.net/browse/GPII-241 GPII-241: Ensure that PCP works under Android].
 +
** [http://issues.gpii.net/browse/GPII-233 GPII-233: Update build scripts for v0.2 tag] (not only for Android but also Windows and Linux).
 +
* A re-envisioned Security Gateway (Oauth 2.0 & UMA). Relevant JIRAs:
 +
** [http://issues.gpii.net/browse/GPII-238 GPII-238: Integrate with current security gateway].
 +
** See also: [http://issues.gpii.net/browse/GPII-17 GPII-17:  Implement OAuth for a number of GPII components such as Preferences Server and Solutions Registry] (not a feature request for the Security Gateway as such).
 +
* Web-based Flow Manager for web personalization. Relevant JIRAs:
 +
** [http://issues.gpii.net/browse/GPII-190 GPII-190: Convert Flow Manager to be deployable in the cloud].
 +
** [http://issues.gpii.net/browse/GPII-217 GPII-217: CORS Support Required for Online Flow Manager].
 +
* Error handling and logging improvements. (See [http://lists.gpii.net/pipermail/architecture/2013-June/001052.html the thread from June 2013], [http://lists.gpii.net/pipermail/architecture/2013-July/001144.html the message from July] and [http://issues.gpii.net/browse/GPII-139 JIRA issue GPII-139].) The logs should make '''benchmarking of the matchmakers''' easier.
 +
** [http://issues.gpii.net/browse/GPII-139 GPII-139: Improve logging functionality of the framework].
 +
* Preference editors (see [[User Preferences UX]]). Relevant JIRAs:
 +
** [http://issues.gpii.net/browse/GPII-229 GPII-229: Integrate PCP with snapshotter].
 +
** [http://issues.gpii.net/browse/GPII-231 GPII-231: Define presets for PCP for all pilot 2 common terms].
 +
** [http://issues.gpii.net/browse/GPII-232 GPII-232: Define and implement remaining adjusters for PCP/PMT for pilot 2 terms] (requires subtasks/subissues!).
 +
** [http://issues.gpii.net/browse/GPII-235 GPII-235: Implement feedback mechanism from matchmakers to PCP/PMTs].
 +
** [http://issues.gpii.net/browse/GPII-241 GPII-241:  Ensure that PCP works under Android].
 +
* Settings snapshotter.
 +
** [http://issues.gpii.net/browse/GPII-228 JIRA: GPII-228: Implement snapshotter].
 +
* Conditions in preferences set (see [[Proposal for Declarative Preference Conditions]]). ('''No JIRA'''; see above.)
 +
* Next generation Ontology Service. ('''No JIRA''')
 +
* Separate ‘GPII framework’ from universal repository and offer it as a reusable framework for building apps (‘Kettle’). JIRA:
 +
** [http://issues.gpii.net/browse/GPII-116 GPII-116: Separate gpiiFramework into separate kettle repository].
 +
* [[Unified Listing]]. ('''No JIRA''')
 +
* [[Common Terms Registry]] (see [[Registry - database planning]] and [[Registry - choice of database]]). ('''No JIRA''')
 +
 
 +
 
 +
[[Category:GPII Architecture]]

Latest revision as of 18:19, 9 October 2013

What would you like to see the architecture working on

Update June 2013

Short Term

New Features