[Fiware-miwi] Setting up the "Materializing Advanced Middleware and Web User Interfaces in FI-WARE" page

[Jarkko Vatjus-Anttila]

Thanks for the instructions Christof. I think we (Cyber at least) managed
to do pretty much all of those almost, some small things still need to be
polished, but will be done by Monday.

One clarification: I take we do not add yet the links to the documents
(user guide, install guide, unittest plan) yet, since they are in private
wiki. I left those blank, but should we still put something there at this
point?


On Fri, Mar 14, 2014 at 5:50 PM, Marti Christof (mach) <mach at zhaw.ch> wrote:

>  Dear WP13 GEi owners
>
>  As discussed in todays meeting, following the instructions to setup your
> GEi infos on the "Materializing Advanced Middleware and Web User Interfaces
> in FI-WARE" page.
> You can find the page here:
> https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE
> (it is also linked from the WP13 Dashboard [GE/GEI Infos] and the MiWi
> integration page)
>
>  Please go to this page and edit for your GEi the following information:
>
>    - Information about your *Baseline Assets*. This is general Infos of
>    the Software/Packages your GE implementation is based on. Please add a
>    separate page for each product you describe here. (see also the entries on
>    the example page below)
>    - Links to *Epics* your GEi is implementing. Attention: The name of
>    the Epics have to start with "*FIWARE.Epic.MiWi.*" So you may have to
>    copy the Epics from "*FIWARE.Epic.WebUI.*" If you do so, please also
>    change the chapter field to."*Advanced Middleware and Web UI*".
>    - Links to *Features* your GEi is implementing.
>    - The Unit Testing Plan and Product Guides have to added later, as
>    soon they are published in the public wiki.
>
> If you have done this.* Please also update the links for your GEi on the
> roadmap page*:
>
> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI<https://www.google.com/url?q=https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI&usd=2&usg=ALhdy2-N5YmwjvviNBE-Xy8F1MwweUMu_Q>
>  There are two links on the roadmap page, which need to be updated:
>
>    - In the textual overview part (1st half of the page) below the title
>    of your GEi
>    - In the table part (2nd half of the page) in the first column of your
>    GEi's row
>
> Point the link directly to the section for your GEi in the Materializing
> page: e.g. like for the Middleware :
> https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE
> *#Advanced_Middleware_-_KIARA*
>  (simply take the link from the Materializing pages TOC entry)
>
>
>  As an example for the entries on the Materializing page (Baseline
> Assets, Epics, Features, ...) have a look at the Cloud Chapter page:
>
> https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE
>
>  This should be done *ASAP [latest by Monday March 17th evening]*, so we
> can add the link to the WP13 materializing page to the public wiki and fix
> the remaining tracker issues.
>
>  Best regards
> Christof
>  ----
> InIT Cloud Computing Lab - ICCLab
> Institut of Applied Information Technology - InIT
> Zurich University of Applied Sciences - ZHAW
> School of Engineering
> Phone: +41 58 934 70 63
> Skype: christof-marti
>
>
>
>
>
> _______________________________________________
> Fiware-miwi mailing list
> Fiware-miwi at lists.fi-ware.eu
> https://lists.fi-ware.eu/listinfo/fiware-miwi
>
>


-- 
Jarkko Vatjus-Anttila
VP, Technology
Cyberlightning Ltd.

mobile. +358 405245142
email. jarkko at cyberlightning.com

Go to www.cybersli.de and enrich your presentations!

www.cyberlightning.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20140315/5f2c46ec/attachment.html>