Dear Jose and All, Also on TI's side we have cases where a SCM different from github is used, so it would be important considering this requirement as a SHOULD. I do support the proposal by Monica of loading on github snapshots of GEs at each FIWARE release (maybe minor release). About using APIARY: in principle we don't have main objections, and it seems very easy to use (moreover is advantageous if there will be automated tools to produce the specs from this). However our developers pointed out this is very handy when building REST APIs: while nearly all FIWARE API are REST, for other kind of API it might not be practical using APIARY, as it would require formalizing them in REST-like style. So I agree with the comment you sent to Alex's mail yesterday, i.e. reporting that the use of APIARY will become a SHOULD requirement (accepting the fact we loose the automated generation facilities). Thanks and BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Da: fiware-chapter-leaders-bounces at lists.fi-ware.org [mailto:fiware-chapter-leaders-bounces at lists.fi-ware.org] Per conto di Monica Franceschini Inviato: mercoledì 1 luglio 2015 15:33 A: fiware-chapter-leaders at lists.fi-ware.org; fiware-chapter-architects at lists.fiware.org; Miguel Carrillo; JUAN JOSE HIERRO SUREDA; MANUEL ESCRICHE VICENTE Oggetto: Re: [Fiware-chapter-leaders] GEi Developer Guidelines : v1 candidate Dear all, I totally agree with Cyril. In our scenario we face similar issues, maybe a little worse, because SpagoBI (reference implementation of Data Visualisation GE), is a 10 years old open source project, with its own repository (OW2), that is targeted from the SpagoBI community and contributors too. Moreover we have our own versioning tool (SVN) and it will be a great effort to switch to another one. My proposal was to put a snapshot of SpagoBI (both binaries and source code) on GitHub for each FIWARE release, so that it can be used within FIWARE documentation/Catalogue. Thank you very much for considering our point of view, kind regards, Monica Monica Franceschini Solution Architecture Manager Big Data Competence Center Engineering Group Corso Stati Uniti 23/C, 35127 Padova, Italia Tel: +39 049.8283547 Fax: +39 049.8692566 Twitter: @twittmonique www.spagobi.org<http://www.spagobi.org> - www.eng.it<http://www.eng.it/web/eng_en/home> proud SpagoBI supporter and contributor [SpagoBI] [cid:image002.jpg at 01D0B5AF.1E67AE80] Respect the environment. Please don't print this e-mail unless you really need to. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Il 01/07/2015 11:04, DANGERVILLE Cyril ha scritto: Dear Jose and all, After internal discussion with the GE owners in my chapter (Security), I would like to express major concerns about the github.com and Apiary MUST guidelines. Last week, I asked Juanjo for a slot to discuss the guidelines again on last Monday's Architects' meeting but I received notification that it was canceled. Reason unknown to me. So I'll try to express our concerns here then: 1. The guideline saying "the SCM *MUST* be github.com" is hardly acceptable for us. What if developers refuse to create an account on Github.com (or other service provider out of the control of FIWARE consortium or EU regulations altogether) because they distrust their security or business model? More importantly because they don't want to be forced by FIWARE management to give up their privacy that way? This is the case for us. It also gives us a strong feeling that it is now the policy of the EC to allow subsidizing US companies that are not bound by (e.g.) EU privacy regulations, isn't it? So is there a reason why FIWARE cannot provide its own github instance (with Gitlab software) like we have our own instance for other tools like Jira, Gforge and so forth? OR, if not possible, at least leave the choice to partners/developers to use their own? For instance, our partner ZHAW is already running their own public github instance (https://github.engineering.zhaw.ch) that offers the same features that you get for free at Github.com. So my suggestion: either change *MUST* to *SHOULD*, OR change Github.com to "any public Git or SVN repository that complies with requirements X, Y, Z...". 2. Same issue for "Apiary MUST be used". Some of us have spent considerable time developing their own documentation tools and have documented all their APIs with it. We hardly see a reason to change this. I suspect this to be the same for many other partners. (If we had known from day 1 that "Apiary MUST be used", the situation would have been different, but 10 months into the project this presents us with considerable difficulties, not least of them being the time we would have to invest to move everything over to the demanded toolset, and which we would like to spend more on making better software.) My suggestion: change *MUST* to *SHOULD*. 3. The last issue concerns the Apiary MUST guideline as well. So far we have provided the User and Programmer's guide and API specification on the wiki. If we switch to Apiary, are we done with the wiki pages? Or will we have to provide both, in which case the FIWARE Tools team would provide some tool to generate these deliverables from Apiary automatically to avoid duplicating the work and wasting time synchronizing the two? Thank you for your understanding. We are open to discussion. Kind regards, Cyril -- Cyril DANGERVILLE, Thales Services FIWARE Security Chapter Architect Authorization PDP (ex-Access Control) GE Owner De : fiware-bounces at lists.fi-ware.org<mailto:fiware-bounces at lists.fi-ware.org> [mailto:fiware-bounces at lists.fi-ware.org] De la part de JOSE MANUEL CANTERA FONSECA Envoyé : mardi 30 juin 2015 11:32 À : fiware at lists.fiware.org<mailto:fiware at lists.fiware.org> Cc : MIGUEL CARRILLO PACHECO; JUAN JOSE HIERRO SUREDA Objet : [Fiware] GEi Developer Guidelines : v1 candidate Importance : Haute Dear Partners, Here is the latest version of the GEi Developer Guidelines. https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Developer_Guidelines As you know the GEi Developer Guidelines summarize what we believe are the best practices in developing your GEi. Some of these Guidelines are a must, so this may have an impact on your work. Those Guidelines were already circulated and have already been presented at the FIWARE WG and Architects Leads conference call. We would like you to have a final look at them. Please send your final comments before Friday 3rd July. On Friday, if there are no substantial objections we will make them official as v1 of such guidelines. The only substantive change made with respect to the version presented at Architects Conf. Call has been the introduction of a (SHOULD) requirement about Docker (under binary releases section). This has been explicitly requested by our project coordinator, Juanjo Hierro. Many thanks for your help and support All the best ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição _______________________________________________ Fiware-chapter-leaders mailing list Fiware-chapter-leaders at lists.fi-ware.org<mailto:Fiware-chapter-leaders at lists.fi-ware.org> https://lists.fi-ware.org/listinfo/fiware-chapter-leaders Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-chapter-leaders/attachments/20150703/1ae611ef/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3639 bytes Desc: image001.png URL: <https://lists.fiware.org/private/fiware-chapter-leaders/attachments/20150703/1ae611ef/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 4716 bytes Desc: image002.jpg URL: <https://lists.fiware.org/private/fiware-chapter-leaders/attachments/20150703/1ae611ef/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: <https://lists.fiware.org/private/fiware-chapter-leaders/attachments/20150703/1ae611ef/attachment-0001.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy