Hi Manuel, There might be a subtype, I’m trying to understand why some of them are available as images but not as full products – this subtype would be iProduct I comment on this sentence in your mail and would like to contribute to this sub-discussion on what to term “product” or not: First, I assume we in this discussion intend to use the term “(software) product” in a sense of IT-level / software engineering domain and not as the term “(business) product” in a business-level sense (customers/users, go-to-market, promises& duties, etc.) since you are dealing with the software-related side in backlogs etc. I hope my assumption is correct. I favor to use the term “product” for _all_ software pieces which are delivered (seriously) from a FI-WARE partners towards the public regardless of IT-based peculiarities of its delivery to a user (passing our FI-WARE go-to-market “gates” like FI-LAB; FIWARE Catalog, etc.). I personally think that not only software “products” with recipes & available at FILAB Product catalogue could and should be named as “products” while others would not be named “products” then. There is no obvious reason for me for such a definition basis recognizable. Choosing only “recipe”-based software to qualify as “product” sound rather arbitrary and afterall we “only” talk of IT-level software delivery terms here, not about business products directly. For example, software in FI-Lab which is deployed as “configured images” would also be named “products”, of course - since only the technical means of delivery to a potential user is different. I think or hope, we can agree that “recipes” are (only) a technical means to support configuration of a software piece. Using recipes is not a “grail” for good products or something as far as I know ☺. One Example: “Marketplace – SAP RI”, that you copy&pasted in your mail: We delivered it as one of the first and chose to deliver as “configured image”. I think you will not doubt that it is a “software product” from us in Fi-WARE, so using the term “product” for it would seem viable. What I want to highlight with that example is therefore simply that the “product” definition (recipes & FI-LAB/Catalog presence) seems to not be a good final choice. In my opinion, we should not forget that EC is directly pressing us to deliver software products. But they for sure do not care for details of software delivery (recipes or not), or at least I hope they do not care. So we might end up in an (unbeneficial) situation that some partners end up with being asked why some partners seem to have “products” while they clearly have only a software piece with – by intention or by luck – chosen recipes configuration technique while others in this wording schema would end up not having “products” – simply because a recipe configuration technique is used or not. This can obviously not be a good choice IMHO since FI-WARE ends up in cutting a set of results down which will be not very good PR for _all_ of us (and such arbitrary and not widely-used definition of “product” would be confusing for the public, too, IMHO). So as my discussion contribution I propose to use “software product” simply for both – recipe-based or configured image – which is simple and crystal clear for communication and reporting purposes. Best Markus From: fiware-ge-owners-bounces at lists.fi-ware.org [mailto:fiware-ge-owners-bounces at lists.fi-ware.org] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Montag, 21. Juli 2014 10:51 To: fiware-ge-owners at lists.fi-ware.org Cc: fiware-wpl at lists.fi-ware.org; FI-WARE WPA (fiware-wpa at lists.fi-ware.org) Subject: [Fiware-ge-owners] FILAB - monitoring deployment Dear Partners, Find updated the report monitoring the deployment at FILAB. This version includes a GEI’s classification: product, service and component. Accordingly: - Products have recipes and are available at FILAB product catalogue. There might be a subtype, I’m trying to understand why some of them are available as images but not as full products – this subtype would be iProduct - Services are available at end points - Components aren’t available at FILAB, as cloud component used to build the platform. I would appreciate you’d check whether your GEI’s classification is accurate. As an example: [cid:image001.png at 01CFA4E4.78E4C0F0] This report also holds a tab for bundles. Next reports will be uploaded at the forge. Next version I expect to provide input about images and blueprints. Thanks for cooperation! Kind regards, Manuel ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-ge-owners/attachments/20140721/3df92940/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 11199 bytes Desc: image001.png URL: <https://lists.fiware.org/private/old-fiware-ge-owners/attachments/20140721/3df92940/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy