Changes between Version 4 and Version 5 of BluePrint/Mobile/P2PSync


Ignore:
Timestamp:
05/29/17 11:43:23 (7 years ago)
Author:
MichaelRogers
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Mobile/P2PSync

    v4 v5  
    77Peer-to-peer sync capabilities exist in [http://developer.servalproject.org/dokuwiki/doku.php?id=content:servalmesh:main_page Serval Mesh] and a number of messaging apps including [https://briarproject.org/ Briar], [https://github.com/casific/murmur Murmur] and [http://whispercomm.org/shout/ Anonymouse].
    88== Stakeholders ==
    9 <Who will be the users of the solution?>
    10 <Who else will be affected by this solution? eg. Developers, Users of Existing Functionality that may be changed?>
    11 <How will stakeholders be affected?>
    12 Tip: Engage these stakeholders in the development of your !BluePrint.
    13 
     9!EdenMobile users are the primary stakeholders - they will be able to use P2P sync to share data with each other. The data subjects will also be stakeholders, and appropriate data handling controls to protect the confidentiality, integrity and authenticity of data must be built in. If the server needs to be aware of P2P sync, for example in order to deduplicate data received from mobile clients, then the people deploying and operating the server will also be stakeholders.
    1410== User Stories ==
    1511<http://en.wikipedia.org/wiki/User_story>