Dear Yosu, that's the right wiki but you can't access it directly, you have to log-in into the forge first, and than go to the wiki ... I haven't set up the ToC yet ... yes, we will use same templates of the FI-WARE wiki I agree with you that our Use Cases will be translated into the backlog as Epics, the reason I see is that they are not detailed enough and it's not possible to complete them in a sprint (one sprint = one month) regards, Davide On 10/20/2011 05:08 PM, Yosu Gorroñogoitia wrote: > Dear Davide, > > do we already have the private wiki to start working on the backlog? > > I assume it is another one, but not this one: > https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php > Indeed, in this one, i cannot register myself to get login access. > > Concerning the backlog entries, I assume we should use the EPICS/User > Stories templates provided in the FIWARE wiki. > > When translating our specification document use cases into backlog > entries, what is the most appropriate granularity: EPICS or > UserStories?. IMHO, I think they are directly translated into EPICS. > > I will contact you tomorrow by skype. > > Kind regards > Yosu > > On Thu, 2011-10-20 at 11:16 +0200, Davide Dalle Carbonare wrote: >> Dear Partners, >> please find attached the last meeting minutes, >> and let me know if I forgot or misinterpreted something. >> >> here is the doodle for the f2f meeting in November, in Rome >> http://www.doodle.com/pwgunpf29ie2wmud >> I ask you set your preference before the next phone conference. >> >> We have a private wiki linked to the forge project, it's a private >> wiki and you can access after the login into the forge ... >> once you're into the Tools project you can see the "Mediawiki" >> as last button (right) of the top grey bar. >> >> I'll set up the table of contents into the wiki as soon as possible, >> and once it is ready I ask you to contribute to move the contents >> there: >> ENG: ToC, structure, templates, Introduction, IDE, Forge and related Use >> Cases >> EAB: Catalogue chapters and related Use Cases >> UDE: Test, Validation and Deploy chapters and Use Cases >> >> cheers, >> Davide >> _______________________________________________ >> Fiware-tools mailing list >> Fiware-tools at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-tools > > ------------------------------------------------------------------ > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive > this e-mail in error, please notify the sender immediately and destroy it. > As its integrity cannot be secured on the Internet, the Atos > group liability cannot be triggered for the message content. Although > the sender endeavours to maintain a computer virus-free network, > the sender does not warrant that this transmission is virus-free and > will not be liable for any damages resulting from any virus transmitted. > > Este mensaje y los ficheros adjuntos pueden contener informacion confidencial > destinada solamente a la(s) persona(s) mencionadas anteriormente > pueden estar protegidos por secreto profesional. > Si usted recibe este correo electronico por error, gracias por informar > inmediatamente al remitente y destruir el mensaje. > Al no estar asegurada la integridad de este mensaje sobre la red, Atos > no se hace responsable por su contenido. Su contenido no constituye ningun > compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. > Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor > no puede garantizar nada al respecto y no sera responsable de cualesquiera > danos que puedan resultar de una transmision de virus. > ------------------------------------------------------------------ > > >
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy