Wiki
Partners and their Contact Details:
Project Tools User Guides
[OPENi Redmine guide]
[Gitlab beginners guide]
[Cloudlet Platform Development Setup Guide]
[Cloudlet Platform Vagrant Development Environment Setup Guide]
[CouchDB Setup Guide]
General Conference Call Minutes
Work for Tasks
[WP2 - Use Cases Analysis and Requirements Specification]
- [WP2 Telco Minutes]
- [T2.1 - Cloud-based services analysis]
- [T2.4 - Use Case Analysis]
- [T2.5 - Requirements Specification]
[WP3 - Architectural design and Security frameworks]
Weekly "Stand-up" meeting to occur every Monday at 10am GMT
- [WP3 Telco Minutes]
- [T3.1- OPENi APIs Specification]
- [T3.2- OPENi Cloud Platform Specification]
- [T3.3- OPENi Security and Privacy Specification]
- [OPENi Service Enablers]
- [OPENi Service Enablers as per architecture changes and decisions made in London meeting]
- [CGI's API definitions]
[WP5 - Service and Application Development]
[WP6 - Prototyping and Use Case Evaluation]
[WP7 - Dissemination and Exploitation]
- [WP7 Telco Minutes]
- [Dissemination List]
- [Dissemination Reporting Template]
- [Other Open Projects about Cloud]
Meetings
SOTA
OPENi Open Source License Discussions
http://www.openi-ict.eu/pad/p/Licenses
Value Proposition for OPENi
Positioning statement
Headline. What is the end-benefit you’re offering, in 1 short sentence. Can mention the product and/or the customer. Attention grabber:
Sub-headline or a 2-3 sentence paragraph. A specific explanation of what you do/offer, for whom and why is it useful:
3 bullet points. List the key benefits or features:
Visual. Images communicate much faster than words. Show the product, the hero shot or an image reinforcing your main message:
Explains how your product solves customers’ problems or improves their situation (relevancy)
Delivers specific benefits (quantified value)
Tells the ideal customer why they should buy from you and not from the competition (unique differentiation)
Welcome to your wiki!
This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].
The wiki uses Markdown syntax.