Hi Gianmario, Thanks for your email! I know there’s nothing able to substitute actual professionalism and willingness to improve quality. As you very well point out. I only want to set up a frame where we can express it in a way it can be perceived. I think it would be important to reduce variability, otherwise, the perception anybody can get from those descriptions is lack of criteria. (As it actually occurs). My proposal comes from observing actual distributions for GEI enablers. But I’m willing to take other limits/definitions to the frame. Censorship is out of context in my opinion. (Having rules is something organizations use daily for their benefit). So, if requested by your WP Leader, I can follow the official procedure to submit the proposal for vote, and to request alternatives to this proposal. Kind regards, Manuel From: Bollano Gianmario [mailto:gianmario.bollano at telecomitalia.it] Sent: miércoles, 19 de marzo de 2014 10:36 To: MANUEL ESCRICHE VICENTE; fiware-wpl at lists.fi-ware.eu Cc: fiware-wpa at lists.fi-ware.eu Subject: R: [Fiware-wpl] [Fiware-wpa] Backlog Content - Reviews : Criteria for open descriptions Hi Manuel, I don’t see any real improvement in changing – again – rules for the backlog & wiki review. This is especially important now because all FI-WARE partners have huge amount of work now that the final release 3.3 is closing: finalizing and delivering SW and tests, preparing documentation wikis and courses, aligning the backlog tickets status and Materializing/Tech Roadmap pages. It even happens that some of us are still waiting a review of SW wiki release 3.2 when we should deliver release 3.3 in few weeks. Consider we can say the same thing using 7 or 17 or even 100 words, without any real improvement in quality. Let me show you an example from your example: MetadataPreprocessing.FormatTransformation: Actual, 17 words: “The enabler receives metadata encoded in one representation and outputs the same metadata represented in another representation.” Using 7 words: “Translates input metadata into a different representation” Using 42 words: “This enablers is designed to receive input metadata encoded in one specific representation, and to apply them a translation of their representation, with the purpose of providing to the output the same metadata received in input, encoded using a different output representation.” As you see, a description with 42 words don’t say anything more and may be less clear than one using 17, as well as the description with 7 words exactly tells the same thing of the other sentences, probably even in a more clear way (not to mention 42 should even contain the “meaning of Life, the universe and everything”). Even more useless to set an upper limit to the words used; apart from censorship I don’t see any practical usefulness in considering a long description as a forbidden text. If you still think that your proposal may be helpful to someone, my suggestion is to set those limits in a way that they may be commonly agreed to be useful – especially not again to increase the number of “rules infringement” in the backlog report. Best, Gianmario Da: fiware-wpl-bounces at lists.fi-ware.eu<mailto:fiware-wpl-bounces at lists.fi-ware.eu> [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di MANUEL ESCRICHE VICENTE Inviato: martedì 18 marzo 2014 18:28 A: Sandfuchs, Thorsten; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu> Cc: fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu> Oggetto: Re: [Fiware-wpl] [Fiware-wpa] Backlog Content - Reviews : Criteria for open descriptions Hi Thorsten, I know it doesn’t make sense to do any effort from a local short-term perspective as yours. Those who believe that FI-WARE is a platform wanting to become something bigger and bigger, those who think improving quality here and there may help, may have a different perspective. So, please, allow the partners who want to improve, do it!! Thanks for your cooperation!! Kind regards, Manuel From: Sandfuchs, Thorsten [mailto:thorsten.sandfuchs at sap.com] Sent: martes, 18 de marzo de 2014 18:10 To: MANUEL ESCRICHE VICENTE; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu> Cc: fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu> Subject: AW: [Fiware-wpa] Backlog Content - Reviews : Criteria for open descriptions Hi manuel, How many real fiware users or even the reviewers complaint about missing text on these pages? How much work would you like to impose to the consortium in which we couldn't focus on packaging or use case support or other tasks related to real deliverables at hand? How vital for the project is this proposal in M34 of the project? Thanks for you comments -- Thorsten Sandfuchs SAP AG Sent from a mobile device, please excuse the brevity. Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx -------- Ursprüngliche Nachricht -------- Von: MANUEL ESCRICHE VICENTE Datum:18.03.2014 15:56 (GMT+01:00) An: fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu> Cc: fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu> Betreff: [Fiware-wpa] Backlog Content - Reviews : Criteria for open descriptions Dear WP Leaders, As I progress on the criteria to identify issues on backlog items’ open descriptions, I need to query you in order to propose modifying previous criteria used. As backlog items’ open descriptions, I refer to the descriptions provided in the wiki openly, an example: http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Data.MetadataPreprocessing.FormatTransformation Currently the get views showing the outlook of descriptions based on the number of words. As an example you can see FI-WARE project and Cloud chapter below: [cid:image001.png at 01CF435F.CF02B910] The link above is an example of average open description with 73 words used. [cid:image002.jpg at 01CF435F.CF02B910] I think there’s need to improve the upper and lower extremes. Therefore, I need to query you on objections to limiting the number of words used to describe open backlog items’ descriptions: In my opinion there’s need to limit them to a window of about 60-250 words. The lowest limit would be implemented with the following individual limits: • goal (>=10 words), description (>=30 words), rational (>= 20 words) • total record (<=250 words) Would you have any objections to it? I think these limits would help identify cases like this below: http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.Cloud.CE.MGT.PlatformFeatures [cid:image003.png at 01CF435F.CF02B910] Or the opposite. The longest description belongs to MiWi with 560 words: http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.MiWi.AdvWebUI.DataflowProcessing There aren’t many items with more than 250 words. Apps(0), Cloud(5), IoT(0), Data(5), I2ND(4), Security(0), MiWi(3) The previous rules for the fields Goal, Description and Rationale only checked fields had content. Thanks for cooperation!! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telefónica Digital Parque Tecnológico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es<http://www.tid.es/> ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20140319/a55c8c99/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19485 bytes Desc: image001.png URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20140319/a55c8c99/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 27772 bytes Desc: image002.jpg URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20140319/a55c8c99/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 11912 bytes Desc: image003.png URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20140319/a55c8c99/attachment-0001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 677 bytes Desc: image004.gif URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20140319/a55c8c99/attachment.gif>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy