Hi, Miguel, I just checked with Stefan Lemme, DFKI, who created the tool for FI-C2. The problem ist that FI-C2 is using DocuWiki, while FIWARE uses MediaWiki. Also the tools is not really designed to be reusable in another context and would require a few changes to be able to deal with the FIWARE requirements. Unfortunately, Stefan is pretty busy in his projects and will not be able to do these changes. However, if there is anyone who could invest some time in this, all the code is actually freely available at the following Github link: https://github.com/stlemme/python-dokuwiki-export BTW, we do all the technical deliverables in FI-C2 through this tool and it has greatly helped us to be efficient with deliverables. Sorry, for not being able to be more helpful. Best, Philipp Am 03.03.2015 um 10:57 schrieb MIGUEL CARRILLO PACHECO: > Hi, > > We do have a problem. > > 1) I tend to copy-paste the wiki pages directly on word. It does the > trick and saving-opening-reformating as you did seems more cumbersome. > Maybe I am wrong, I do not have time to test both methods. > > 2) *@Philipp*, you were offering the tools from another project. It is > becoming urgent to see if it is suitable. Can you please look into it? > > The tools from SAP are out of the question, unfortunately. > > Bitergia have been overloaded from the start of the project. You do not > see all the traffic of requests but I do. Also, we have asked for > backups, monitorization, JIRA installations, forge migrations, > evaluations of tools, lists management, ... They are doing a terrific > job that people do not generally perceive as they do it silently. Now > the forge is causing trouble on top of which they are migrating lists > from fi-ware.org to fiware.org etc. There always seems to be something > stopping us from starting with the deliverable creation tool! > > Regards, > > Miguel > > > > El 02/03/2015 a las 23:56, Alex Glikson escribió: >> Dear coordinator & partners, >> >> I wanted to share my experience working on the architecture deliverable. >> Maybe there is a better way to do it, but I found myself doing quite a >> lot of manual editing of the resulting Word document, to make it >> reasonably formatted for a formal deliverable. In particular, I had to >> do the following (this is a partial list): >> 1. Saved the individual wiki pages in mht format (web archive, single >> file), which can be then edited in Word (and saved in native docx format) >> 2. Removed 'garbage' text related to wiki info etc >> 3. Copied all the files into a single file >> 4. Added standard FIWARE title page and 'preface' pages (executive >> summary, change history, etc), header/footer, etc >> 5. Removed individual Legal Notice sections, added a single Legal >> Notice section under the 'preface' section (we did standardize on a >> single legal notice for all GEs) >> 6. Created 1st level headings for "Introduction" (the main Cloud >> architecture page) and for each GE, specifying the GE name (rather >> than the cryptic wiki page name) >> 7. Removed individual TOCs of each page, created the overall TOC >> (leaving only 2 levels) >> 8. Updated *all* the headings and levels of sub-section titles to >> reflect the new hierarchy, as well as to add sections numbering >> 9. Fixed all figure sizes, added figure captions, added table of figures >> 10. Did overall editing of the deliverable >> >> ..and I am surely missing some steps I applied. >> >> I am curious to know whether others are going through a similar >> process, and maybe even achieved similar results in an easier way? >> After all, it might be desirable to have consistent outcomes (and we >> are already few days late). FYI, attaching the current draft (several >> inconsistencies and various content issues still to be fixed). Any >> thoughts/comments are welcome. >> >> >> Thanks, >> Alex >> >> ==================================================================================== >> Alex Glikson >> Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab >> Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: >> +972-54-6466667 | Fax: +972-4-8296112 >> >> >> >> _______________________________________________ >> Fiware-chapter-architects mailing list >> Fiware-chapter-architects at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-chapter-architects > > -- > > Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com > > ---------------------------------------------------------------------- > _/ _/_/ Miguel Carrillo Pacheco > _/ _/ _/ _/ Telefónica Distrito Telefónica > _/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 9 > _/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N > _/ _/_/ 28050 Madrid (Spain) > Tel: (+34) 91 483 26 77 > > e-mail: miguel.carrillopacheco at telefonica.com > > Follow FIWARE on the net > > Website: http://www.fiware.org > Facebook: https://www.facebook.com/eu.fiware > Twitter: http://twitter.com/Fiware > LinkedIn: https://www.linkedin.com/groups/FIWARE-4239932 > ---------------------------------------------------------------------- > > > ------------------------------------------------------------------------ > > 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 > https://lists.fi-ware.org/listinfo/fiware-chapter-leaders > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Geschäftsführung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-chapter-leaders/attachments/20150303/d1699e7a/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy