logseq/pages/todoist___2026-02-03.md

• 2026-02-03 Preparare missione per Difesa Dottorato Unimib todoist-id:: 6fpJW7WhfQMvWGCc todoist-project:: #✈ Missioni todoist-due:: 2026-02-03 todoist-desc:: Partenza 18 Febbraio mattina ritorno 19 Febbraio pomeriggio todoist-status:: ◼️
• 2026-02-03 Missione thesis defense Barcellona todoist-id:: 6fpMJPHCF85RJH7c todoist-project:: #✈ Missioni todoist-due:: 2026-02-03 todoist-desc:: Weblink: Outlook todoist-status:: ◼️
• 2026-02-03 [mosaico-all] MOSAICO CM3 todoist-id:: 6f67vMc5RgHcgVR8 todoist-project:: #✈ Missioni todoist-due:: 2026-02-03 todoist-desc:: From: zhanna.zhussupova@imt-atlantique.fr Received: 2025-10-16T14:25:53Z ✉: Web Link --- Dear all, We are pleased to confirm that the MOSAICO CM3 will be kindly hosted by Netcompany-Intrasoft at its Athens headquarters, located at 13 Fragkokklisias Street, Maroussi, Greece. Please find attached the directions to the venue and the list of todoist-status:: ◼️
• 2026-02-03 Rivedere Composizione Collegio todoist-id:: 6X4Jp7W4VW84FHqh todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-02-03 todoist-labels:: #goal todoist-status:: ◼️
• 2026-02-03 [Dottorato PNRR] Relazione annuale di sintesi todoist-id:: 6fj3mhqW972xv5c8 todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-02-03 todoist-desc:: From: alessandra.galassi@graduate.univaq.it Received: 2026-01-09T11:04:30Z ✉: Web Link --- Okay, here’s a synthesized summary of the email, broken down into actionable tasks, based on the content: Task Summary: The email is a formal message from a "Chiar.mo Coordinatore del corso dottorale in ICT prof. Di Ruscio" (Coordination Officer for the PhD in ICT Professor Di Ruscio) to the recipient. The recipient is being sent a completed and signed form outlining a course. Actionable Tasks: 1. Review and Confirm Completeness: Carefully read the completed and signed form to ensure all required information is accurately present. 2. Attach the Form: Attach the completed form to this email. 3. Send the Form: Send the attached form to the recipient. 4. Express Good Wishes: Compose a polite and cordial message to the recipient, wishing them a happy New Year. 5. Verify Sender Information: Ensure the email is sent from a valid and trusted source. Let me know if you'd like me to elaborate on any of these points or add more detail! --- Chiar.mo Coordinatore del corso dottorale in ICT prof. Di Ruscio, come da guida utente, in allegato, invio compilata e firmata quanto specificato in oggetto. Grazie. L’occasione è gradita per porgere i migliori auguri di buon anno! Un saluto cordiale, todoist-status:: ◼️
• 2026-02-03 Manuscript in your Reviewer Center - IEEE Software, SWSI-2026-01-0024 todoist-id:: 6fjh74qpCPV5HJ38 todoist-project:: #📜 REVIEWS todoist-due:: 2026-02-03 todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-12T07:28:14Z ✉: Web Link --- Okay, here’s a synthesis of the email content, transforming it into actionable tasks for completing the task of reviewing the manuscript. I’ve focused on clarity and providing specific steps. Task Summary: Review the IEEE Software manuscript ("SWSI-2026-01-0024") for adherence to peer review guidelines, focusing on confidentiality and providing substantive feedback. Actionable Tasks & Breakdown: 1. Review Policies Understanding (Priority: High): * Action: Thoroughly read the reviewer policies document (link: [https://magazines.ieeeauthorcenter.ieee.org/submit-your-article-for-peer-review/about-the-peer-review-process]) to understand the specific requirements for content, format, and communication. Pay close attention to the emphasis on confidentiality regarding AI-generated feedback. * Deliverable: A concise summary of key policy points – particularly concerning what constitutes acceptable or unacceptable review comments. 2. Manuscript Review & Initial Assessment (Priority: High): * Action: Begin reviewing the manuscript – specifically focusing on the sections related to the agentic system engineering context. Identify key sections: * Abstract: Ensure it accurately summarizes the manuscript's purpose and scope. * Introduction: Evaluate the relevance of the context engineering concept to the manuscript’s topic. * Methodology: Assess the methods used – are they appropriate for the context? * Results & Discussion: Confirm the results are logically supported by the methods. * Conclusion: Assess the final conclusion – is it justified and well-supported? * Deliverable: A brief (1-2 paragraph) summary of initial impressions, highlighting potential areas of concern (e.g., a lack of specific details, unclear methodology). 3. Identify Key Concerns - Confidentiality & AI Feedback (Priority: Medium): * Action: Specifically look for the sections where the reviewer emphasizes caution regarding sharing information about the manuscript with AI platforms for text generation. * Deliverable: A list of 2-3 specific concerns regarding the manuscript's use of AI-generated content, which you will need to address in your review. 4. Content Review & Feedback (Priority: High): * Action: Address the following points based on your concerns: * Referencing: Ensure all citations are accurate and properly formatted. * Specificity: Ensure claims are supported by evidence. * Context: Clarify the agentic system engineering context. Does it adequately demonstrate its significance? * AI Integration: Carefully assess the role and influence of AI. Does it feel like a supplementary tool or integral to the core work? (The reviewer’s concern about shared information is key here.) * Deliverable: Draft review comments addressing each identified concern, focusing on providing specific, constructive feedback. (Focus on the why behind your comments – not just stating the problem.) 5. Review Score Sheet & Submission (Priority: Medium): * Action: Carefully and accurately fill out the review score sheet, ensuring all sections are completed (Confidential Comments, Public Comments, and any other required fields). * Deliverable: Completed review score sheet, with all required fields filled. 6. Communication Protocol (Priority: Medium): * Action: Respond promptly to any questions from the editor or reviewer. Be professional and courteous. * Deliverable: A record of your communication attempts – noting the date, content, and outcome of each communication. 7. Final Review & Submission (Priority: Low): Once you've completed all steps, submit the manuscript for review. Important Note: Document everything – your reasoning behind the feedback, specific examples, and any changes made during the review process. This will provide a clear audit trail for future review decisions. --- Let me know if you'd like me to elaborate on any of these tasks or provide more specific examples! --- IEEE Software, SWSI-2026-01-0024 manuscript type: SWSI: Agentic System Engineering (Sep/Oct 2026) "Context Engineering for Software Engineering Agents" 12-Jan-2026 Dear Prof. Di Ruscio: Thank you for agreeing to review the above reference manus todoist-status:: ◼️
• 2026-02-03 Memorandum di prenotazione todoist-id:: 9977644999 todoist-project:: #Inbox todoist-completed:: 2026-02-03 todoist-status:: ✅
• 2026-02-03 Re: Thesis supervision todoist-id:: 6fvm3MqmxF6M5q28 todoist-project:: #🦮 Mentoring todoist-due:: 2026-02-03 todoist-desc:: From: tesfaywelegebreal.tesfay@student.univaq.it Received: 2026-01-26T23:09:30Z ✉: Web Link --- Okay, here's a concise summary of the email, focusing on the key actions and prioritizing tasks: Summary: The email is a request from Davide Di Ruscio to Tesfay Welegebreal to discuss thesis supervision. Davide wants to schedule a meeting next (Monday afternoon/Tuesday). He's leaving for a project meeting and needs to coordinate with Andrea De Marcellis and Guido Di Patrizio Stanchieri. He's sharing his message with them and offers to provide more information. The email requests the recipient to respond with a suitable meeting time. Actionable Tasks (Based on the email): 1. Schedule a meeting: Davide needs to arrange a meeting with Tesfay, Andrea, and Guido to discuss thesis supervision. 2. Send message: Send the email containing the message to Tesfay and the other collaborators. 3. Inform Collaborators: Notify Andrea and Guido about the email and his plans. 4. Provide Further Information: Provide further details to Tesfay regarding his departure and the meeting schedule. Let me know if you'd like me to expand on any of these tasks! --- Dear Professor Davide, Thank you for your message. I would be glad to discuss my ideas on the thesis in more detail. I am available in person on Monday afternoon, February 2nd, or Tuesday before noon, February 3rd. I can also be available online on an todoist-status:: ◼️
• 2026-02-03 TOOL DEMO TRACK - MODELS 2026 Organizing Committee todoist-id:: 6fQ7HCGxPvcHGHgg todoist-project:: #💺 EditoringChairing todoist-due:: 2026-02-03 todoist-desc:: From: lolaburgueno@uma.es todoist-labels:: #goal #logseqed todoist-status:: ◼️
• 2026-02-03 I: PRIN 2022 e PRIN 2022 PNRR - FAQ VIII elenco todoist-id:: 6fpqJRPHvj4MCXQg todoist-project:: #🚀 Projects-PRIN2022-FRINGE todoist-due:: 2026-02-03 todoist-desc:: From: disim.sac@strutture.univaq.it Received: 2026-01-21T09:40:01Z ✉: Web Link --- This email is a notification regarding the final reporting for PRIN 2022 and PRIN 2022 PNRR projects. Key information: * Expenses for "Acquisti e/o personale a costo reale" (Purchases and/or real-cost personnel) paid in February 2025 will not be eligible for the final report. * The email also forwards the latest FAQs from the Ministry for final reporting. Task Recommendation: Task: Review PRIN 2022 and PRIN 2022 PNRR project expenses and ensure compliance with reporting guidelines. Actions: 1. Review expenditure records: Carefully examine all project expenses, particularly those related to "Acquisti e/o personale a costo reale." 2. Identify ineligible expenses: Flag any expenses paid in February 2025 for purchases or real-cost personnel. 3. Consult FAQs: Read the provided Ministry FAQs for PRIN 2022 and PRIN 2022 PNRR to ensure a thorough understanding of all reporting requirements. 4. Adjust financial reporting: Make necessary adjustments to the financial reports to exclude any ineligible expenses identified. 5. Communicate with project teams: Inform relevant project teams about the exclusion criteria and ensure they are aware of the reporting deadlines and requirements. Deadline: N/A (No explicit deadline mentioned for this specific action, but it's crucial for the overall project reporting which will have deadlines). --- Buongiorno, vi invio per opportuna conoscenza l'ultima nota dell'ufficio PRIN per quanto riguarda la chiusura delle rendicontazione dei progetti PRIN 2022 e PRIN 2022 PNRR. Nello specifico vi segnalo che non saranno ammissibili alla rendicontazione fi todoist-status:: ◼️
• 2026-02-03 fra le università straniere va aggiunta la Aalborg University che ha ospitato Roberta di Fonzo e con cui abbiamo alcune pubblicazioni, anche su IEEE Transactions on Industrial Informatics e on Industry Applications il dottorando Noman Liaqat andrà pres... todoist-id:: 6fG9FrXwcrvMxhp8 todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-02-03 todoist-desc:: Web Link todoist-labels:: #outlook365 todoist-status:: ◼️
• 2026-02-03 Mandare carta d'identità al notaio todoist-id:: 6fvcChcP8VVC9P6m todoist-project:: #📗 Personal todoist-due:: 2026-02-03 todoist-status:: ◼️
• 2026-02-03 Manuscript ID SOSYM-26-00005495 is now in your Editor Center todoist-id:: 6fqqJqV6XmqFHJVg todoist-project:: #💺 EditoringChairing todoist-due:: 2026-02-03 todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-25T14:55:25Z ✉: Web Link --- ## Task Summary: Reviewer Assignment for Manuscript SOSYM-26-00005495 A manuscript titled "Integrating Pretrained Large Language Models and Graph Neural Networks For Model-Driven Engineering: A Graph Language Modeling Framework" (ID SOSYM-26-00005495) has been submitted to the journal Software and Systems Modeling. Professor Davide Di Ruscio is requested to assign reviewers for this manuscript. ## Actionable Task for Professor Davide Di Ruscio: Task Title: Assign Reviewers for Manuscript SOSYM-26-00005495 Description: Assign appropriate reviewers for the submitted manuscript SOSYM-26-00005495. Key Actions: 1. Login: Access the journal's editorial system at https://mc.manuscriptcentral.com/sosym using your credentials (User ID: davide.diruscio@univaq.it). 2. Navigate: Go to your "Editor Center". 3. Locate Manuscript: Click on "Awaiting Reviewer Selection" and then click "Take Action" for manuscript SOSYM-26-00005495. 4. Search & Select Reviewers: Utilize the quick or advanced search fields to find suitable reviewers. Select reviewers using the checkboxes and click "Add". 5. Create New Reviewers (Optional): If necessary, create new reviewer accounts, ensuring no duplicates. 6. Invite Reviewers: Press the "Invite" button in the "Reviewer List". 7. Edit & Send Invitation: Edit the invitation message as desired and then press "Save and Send". 8. Monitor Review Quality: Be vigilant about the quality of reviews provided, considering the potential misuse of Generative AI. 9. Consult Guidelines: Refer to the Editor guidelines at http://www.sosym.org/editor_guidelines/ for additional information. Deadline: As soon as possible. --- 25-Jan-2026 Dear Professor Davide Di Ruscio: Manuscript ID SOSYM-26-00005495 entitled "Integrating Pretrained Large Language Models and Graph Neural Networks For Model-Driven Engineering: A Graph Language Modeling Framework," with Professor Bork as todoist-status:: ◼️
• 2026-02-03 SW-2025-10-0161.R1 Review Submitted - Di Sipio todoist-id:: 6frwVhMF3mGmJfCg todoist-project:: #💺 EditoringChairing todoist-due:: 2026-02-03 todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-30T08:52:23Z ✉: Web Link --- Okay, here’s a concise summary of the email, suitable for a Todoist task: Task: Respond to Davide Di Sipio's review of the "Explainer Pattern" manuscript. Summary: Thank Davide for his feedback and provide access to the scoresheet (via IEEE Software ScholarOne Manuscripts). Actionable Steps: 1. Access Scoresheet: Go to the IEEE Software ScholarOne Manuscripts website: https://mc.manuscriptcentral.com/sw-cs 2. Review Feedback: Read Davide’s review of the manuscript. 3. Acknowledge Feedback: Respond to Davide with a thank you and acknowledge the key points raised. --- SW-2025-10-0161.R1, "Explainer Pattern – A Design Pattern for the Integration of Explanations in Code" Manuscript Type: Regular 30-Jan-2026 Dear Davide, Mr. Claudio Di Sipio just submitted a review for the above referenced manuscript. We would l todoist-status:: ◼️
• 2026-02-03 Fare rinnovo contratto via Zara todoist-id:: 6fhrmQrx8rwwwWFm todoist-project:: #📗 Personal todoist-due:: 2026-02-03 todoist-status:: ◼️
• 2026-02-03 Re: Follow-up: Invitation to Review for Software and Systems Modeling todoist-id:: 6frxPVRrX2Wwjwrg todoist-project:: #💺 EditoringChairing todoist-due:: 2026-02-03 todoist-desc:: From: lissette.almonte@uam.es Received: 2026-01-30T11:55:12Z ✉: Web Link --- --- Dear Professor Di Ruscio, Thank you for your message. Unfortunately, I am unable to review the manuscript at this time, but I would like to suggest Lola Burgueño and Juan de Lara Jaramillo as potential alternative reviewers, as they are highly qualified todoist-status:: ◼️
• 2026-02-03 Registrazione contratto Corsigani todoist-id:: 6fjWHCmHqGFFvMvF todoist-project:: #📗 Personal todoist-due:: 2026-02-03 todoist-status:: ◼️
• 2026-02-03 MODELS SC Consultation (February 2026) todoist-id:: 6fvm2rmq3Jrh6jPg todoist-project:: #💺 EditoringChairing todoist-due:: 2026-02-03 todoist-desc:: From: daniel.varro@gmail.com Received: 2026-02-02T18:33:57Z ✉: Web Link --- Okay, here's a concise summary of the email, suitable for a task management system like Todoist: Task: Model Consultation & Data Gathering Goal: Understand current modeling landscape across different institutions to inform a longer-term strategy for MODELS. Subtasks: 1. Schedule Interviews: Book one-on-one interviews with Models Steering Committee members (link provided). 2. Gather Data: Prepare questions focused on: * Ranking of models in academic evaluations across different career stages (across various institutions). * Progress of open access requirements. * Cost structures of current publication practices. * Sponsorship benefits and potential improvements. 3. Initial Review: Analyze the collected data – identify key trends, challenges, and opportunities. Deadline: N/A - This is a preliminary data gathering task, not a specific deadline. Let me know if you'd like me to expand on any of these subtasks! --- Dear SC members, Last year, we started some (initial but sometimes heated) discussions on MODELS publication policies. The apropos was ACM's move to a full open access model beginning from 2026 - but I think that the scope of the discussions should b todoist-status:: ◼️
• 2026-02-03 Re: Tools and Demo track at MODELS 2026 todoist-id:: 6fvm39C6GgQwF79g todoist-project:: #💺 EditoringChairing todoist-due:: 2026-02-03 todoist-desc:: From: franciscaperez@upv.es Received: 2026-01-28T11:19:48Z ✉: Web Link --- --- Hi Davide, thanks for your message! I wanted to let you know that I am currently on medical leave due to an eye surgery. If everything goes well, I expect to be back on February 16th. That said, it could be a good idea to meet that same week to s todoist-status:: ◼️
• 2026-02-03 Reviewer Assignments for Manuscript ID SOSYM-26-00005495 are now due todoist-id:: 6fvh2PqmhhQmgvJg todoist-project:: #💺 EditoringChairing todoist-due:: 2026-02-03 todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-02-02T07:16:33Z ✉: Web Link --- Okay, here's a concise summary of the email, formatted as a task list suitable for a Todoist project, incorporating the key actions and deadline: Task: Reviewer Assignment for SOSYM-26-00005495 Goal: Assign Reviewers for the "Integrating Pretrained Large Language Models and Graph Neural Networks For Model-Driven Engineering: A Graph Language Modeling Framework" manuscript. Steps: 1. Login: Log in to ManuscriptCentral: https://mc.manuscriptcentral.com/sosym 2. Navigate to Editor Center: Go to "Editor Center". 3. Select "Awaiting Reviewer Selection": Click this button for the assigned manuscript. 4. Add Reviewers: Use the quick or advanced search to find reviewers and add them to the list. 5. Confirm Reviewer Selection: Carefully confirm the selected reviewers. 6. Create Reviewer Account: Create a new Reviewer Account on the right side of the page. 7. Invite Reviewers: Send an invitation message to each reviewer. Important: Ensure browser popup doesn't suppress the message. 8. Edit Reviewer Message: Modify the message as needed. 9. Save and Send: Send the invitation to the reviewer. Deadline: Reviewer assignment is due ASAP. (Assumed to be within the next 24 hours, adjust if necessary). Let me know if you'd like me to refine this further (e.g., add specific instructions for a particular reviewer). --- 02-Feb-2026 Dear Professor Di Ruscio: Manuscript ID SOSYM-26-00005495 entitled "Integrating Pretrained Large Language Models and Graph Neural Networks For Model-Driven Engineering: A Graph Language Modeling Framework," with Professor Bork as submitt todoist-status:: ◼️
• 2026-02-03 Preparare viaggio todoist-id:: 6fvr8XmxRcXH98rV todoist-project:: #👷 WORK todoist-due:: 2026-02-03 todoist-status:: ◼️
• 2026-02-03 Buongiorno Prof. Dovrei aver concluso il progetto con lo sviluppo dei 4 punti che ci siamo detti sopra durante l'esame. Spiego di seguito: un container per ogni componente: Ogni componente logico (Monitor, Analyzer, Planner, Executor, Knowledge Base) è eseguito in un container Docker dedicato e isolato, garantendo modularità, ognuno con le sue dipendenze. estensibilità rispetto a sensori vs attuatori: ho superato la logica hardcoded come ci eravamo detti in riferimento alla slide 06_Slides-Control-Systems-v2.pdf implementando una gestione basata su Control Loops configurabili. Il sistema ora non conosce a priori le regole, ma istanzia dinamicamente i loop (es. Hydration Loop, Safety Loop) leggendoli dalla configurazione. Questo garantisce la totale estensibilità rispetto a nuovi sensori o nuove regole di adattamento senza ricompilare il codice. configurazione con un container dedicato: ho implementato un container dedicato (config-server) che agisce come Single Source of Truth, iniettando le policy di adattamento e la topologia a runtime. documentazione: È allegato il report PDF strutturato secondo il template fornito, completo di tassonomia dell'adattamento, logica formale e validazione visiva degli scenari tramite Dashboard Grafana.Ho inserito tutto nel repo https://github.com/ocraton/smart-olive-grove todoist-id:: 6fr34W536H4grP9g todoist-project:: #👨‍🏫 Teaching todoist-due:: 2026-02-03 todoist-status:: ◼️
• 2026-02-03 Hi Professor, I just wanted to let you know that we have updated everything based on your feedback for the IoT project. The following major changes are now implemented:- The threshold values used for Telegram notifications are now fully dynamic (loaded from the config).- The Grafana dashboards update automatically whenever a new sensor or threshold is added. - All sensor units are now loaded dynamically from the config file.- The main configuration file has been moved to its own config directory. todoist-id:: 6fqFgJPRQHf9hcGg todoist-project:: #👨‍🏫 Teaching todoist-due:: 2026-02-03 todoist-status:: ◼️
• 2026-02-03 Buongiorno Prof. Dovrei aver concluso il progetto con lo sviluppo dei 4 punti che ci siamo detti sopra durante l'esame. Spiego di seguito: un container per ogni componente: Ogni componente logico (Monitor, Analyzer, Planner, Executor, Knowledge Base) è eseguito in un container Docker dedicato e isolato, garantendo modularità, ognuno con le sue dipendenze. estensibilità rispetto a sensori vs attuatori: ho superato la logica hardcoded come ci eravamo detti in riferimento alla slide 06_Slides-Control-Systems-v2.pdf implementando una gestione basata su Control Loops configurabili. Il sistema ora non conosce a priori le regole, ma istanzia dinamicamente i loop (es. Hydration Loop, Safety Loop) leggendoli dalla configurazione. Questo garantisce la totale estensibilità rispetto a nuovi sensori o nuove regole di adattamento senza ricompilare il codice. configurazione con un container dedicato: ho implementato un container dedicato (config-server) che agisce come Single Source of Truth, iniettando le policy di adattamento e la topologia a runtime. documentazione: È allegato il report PDF strutturato secondo il template fornito, completo di tassonomia dell'adattamento, logica formale e validazione visiva degli scenari tramite Dashboard Grafana.Ho inserito tutto nel repo https://github.com/ocraton/smart-olive-grove todoist-id:: 6frVX6QM6Jp4jRw8 todoist-project:: #👨‍🏫 Teaching todoist-due:: 2026-02-03 todoist-status:: ◼️
• 2026-02-03 SE4IOT Final Project Update - Team 7 todoist-id:: 6frhPXP6xcPW7gF8 todoist-project:: #👨‍🏫 Teaching todoist-due:: 2026-02-03 todoist-desc:: From: meteharun.akcay@student.univaq.it Received: 2026-01-29T10:13:50Z ✉: Web Link --- Okay, here's a summary of the email content, followed by actionable task recommendations: Summary of Email Content: The email is a follow-up to a feedback discussion regarding a Smarthouse project. It details the following: * Implemented Updates: The code has been updated and is available in the GitHub repository at https://github.com/phuc-tr/smarthouse. * Changes Summarized: * Room profiles are now configurable within the simulator/config.yaml. * A .env file has been added for the required environment variables. * Altering the alerting logic is now possible without Node-RED changes. * Request for Review: The author requests review and feedback on the updated code. * Actionable Task Recommendation: The author suggests reviewing the changes and notifying them about any further adjustments needed. Actionable Task Recommendations (Todoist Task Creation): 1. Create a Task: "Review Smarthouse Project Updates - GitHub" 2. Assign Priority: High (As this is a follow-up and requires verification) 3. Due Date: Ideally, within 24-48 hours (to allow for review and testing) 4. Include Details: Add: “Investigate the .env file configuration. Confirm the environment variable loading mechanism is working as expected." 5. Consider: "Check if any further configuration changes are needed in the YAML configuration files." Let me know if you'd like me to refine this further! --- Dear Professor, Following your feedback on our Smarthouse project, we implemented the requested improvements. The updated version is now available in our GitHub repository: GitHub - phuc-tr/smarthouse The changes are summarized below: * todoist-status:: ◼️
• 2026-02-03 Chiamare Lina Calandra todoist-id:: 6frjr4pqhF8PjMff todoist-project:: #👨‍🏫 Teaching todoist-due:: 2026-02-03 todoist-status:: ◼️
• 2026-02-03 Final version of the Autonomous Systems project todoist-id:: 6fv73MCMFv963736 todoist-project:: #👨‍🏫 Teaching todoist-due:: 2026-02-03 todoist-desc:: From: alejandro.munozmorillo@student.univaq.it Received: 2026-01-30T16:07:42Z ✉: Web Link --- Okay, here's a summary of the email, focusing on actionable tasks, and including a deadline (as assigned to Todoist): Summary: The email is a follow-up to a course project, specifically regarding architectural changes. The author, Alejandro Muñoz Morillo, has implemented modularity and containerization (Docker/Docker Compose) to improve the system's architecture. They've attached the final project version and GitHub link for review. The key action recommended is to thoroughly review the project and ensure coherence between implementation and documentation. Actionable Tasks: 1. Review the Project: Carefully examine the finalized project version for accuracy and alignment with the original objectives and guidelines. 2. GitHub Link Verification: Confirm the GitHub link is accurate and leads to the correct repository. 3. Update Todoist Task: Assign this task to Todoist to ensure timely completion. (Deadline: Today) Let me know if you'd like me to refine this summary further! --- Dear Professor, I hope you are doing well. We are writing to inform you that we have implemented the changes and improvements you suggested for our project in the course Software Engineering for Autonomous Systems. In particular, we have focused on impr todoist-status:: ◼️
• 2026-02-03 Comunicazione Registri delle lezioni I semestre a.a.2025-2026 todoist-id:: 6frwVhQVmF246hM8 todoist-project:: #👨‍🏫 Teaching todoist-due:: 2026-02-03 todoist-desc:: From: disim.uprodid@strutture.univaq.it Received: 2026-01-30T09:02:07Z ✉: Web Link --- --- Gentilissime e gentilissimi, buongiorno. È nostra prassi ricordarvi la necessità di procedere alla compilazione dei registri delle lezioni relativi al II semestre a.a.2025-2026, alla verifica dei dati e, infine, al loro invio. In caso di eventuali probl todoist-status:: ◼️
• 2026-02-03 Registrazione voto modulo Model Driven Engineering & SE for IoT todoist-id:: 6fvm343P64J5F5xg todoist-project:: #👨‍🏫 Teaching todoist-due:: 2026-02-03 todoist-desc:: From: federico.capricci@student.univaq.it Received: 2026-02-02T16:09:01Z ✉: Web Link --- Okay, here’s a summary of the email content, focusing on actionable tasks and a deadline assignment: Summary: The email requests the registration of student scores for the "Model Driven Engineering & SE for IoT" module. The recipient has the following scores: * MDE = 27 * IoT = 30 Actionable Tasks: 1. Verify and Register Scores: Immediately check and register the provided scores (MDE = 27 and IoT = 30) in the designated system. This is the primary task. 2. Deadline Consideration: Since there are specific scores, it’s important to consider the deadline for these assessments (not provided in the text, but likely a timeframe). Assign a deadline for this registration to Todoist. --- Do you want me to expand on this summary with specific steps or add a deadline assignment if you would like? --- Buongiorno, scriviamo per chiedere la registrazione del voto per il modulo Model Driven Engineering & SE for IoT. Le rispettive valutazioni per gli esami sono state: MDE = 27 IoT = 30 Grazie mille, Buona giornata. todoist-status:: ◼️
• 2026-02-03 Proposta per Univaq On Air - Dottorandi di Ricerca todoist-id:: 6fmfWgpGcX7V285g todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-02-03 todoist-desc:: Weblink: Outlook Email Content Summary: Proposal for the Univaq podcast to feature a series of interventions by research PhD students across various scientific areas and schools. The initiative aligns with the goal to narrate the life of an important and dynamic academic community. Seeking opinion and coordination for necessary steps from the coordinator of the podcast. No specific deadlines mentioned. todoist-labels:: #ai-generated #ai-generated-main-task todoist-status:: ◼️
• 2026-02-03 ECMFA 2026 submission assignment todoist-id:: 6ffWC97GGvHG4qG8 todoist-project:: #📜 REVIEWS todoist-due:: 2026-02-03 todoist-desc:: Web Link Okay, here’s a task description based on the email content "ECMFA 2026 submission assignment," designed to be actionable and clearly outlined: Task Title: Complete ECMFA 2026 Submission – [Specify Document Name/Format - e.g., Final Report, Presentation, etc.] Description: This task requires you to finalize and submit the ECMFA 2026 submission, specifically [State the specific document/deliverable - e.g., the final report, the presentation slides, the data analysis]. This is a crucial step in ensuring the successful completion of the ECMFA 2026 project. Actionable Steps: 1. Review Submission Guidelines: Thoroughly review the official ECMFA 2026 submission guidelines document located at [Insert Link to Document Here – VERY IMPORTANT]. Pay close attention to formatting requirements, data sources, and required elements. 2. Gather Required Data: Collect all necessary data and information as outlined in the guidelines. This may involve [List specific data sources - e.g., accessing the database, reviewing reports, performing specific calculations]. 3. Format and Organize Content: Organize your submission content in a clear, logical, and consistent format. Ensure all sections are properly labeled and aligned. 4. Proofread and Edit: Carefully proofread your entire submission for any grammatical errors, typos, or inconsistencies. Check formatting for consistency. 5. Submit the Submission: Submit the completed document through [Specify Submission Method - e.g., Outlook, SharePoint, designated portal]. 6. [Optional - If applicable] - Submit Feedback: If you have any questions or require clarification on any part of the submission, please send a brief email to [Your Email Address] within 24 hours of submitting. Deadline: [Insert Deadline – Be realistic!] Priority: [High/Medium/Low - Assign a priority level.] Assigned To: [Your Name/Team Name] Notes: If you encounter any roadblocks or require assistance, please don’t hesitate to reach out to [Contact Person/Team for Support - e.g., your supervisor, the ECMFA team]. --- To help me refine this further and make it even more tailored, could you tell me: * What kind of document is this submission for? (Report, presentation, data analysis, etc.?) * Are there any specific guidelines or requirements you want to highlight? (e.g., specific data sources, format requirements, length restrictions?) todoist-labels:: #outlook365 todoist-status:: ◼️
• 2026-02-03 Aggiornare sito con gli ultimi due corsi aggiuntivi todoist-id:: 6frwc82JfjrWXH2h todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-02-03 todoist-status:: ◼️
• 2026-02-03 Re: FW: FW: Un breve corso su Quantum Computing todoist-id:: 6frj3mGxqcGgmqvg todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-02-03 todoist-desc:: Web Link Okay, based solely on the subject line "Re: FW: FW: Un breve corso su Quantum Computing" (A brief course on Quantum Computing), it's highly probable that someone forwarded information about a quantum computing course, and the current email is a response or a directive related to that information. Here's an actionable task description, assuming the most common scenario: the sender wants the recipient to investigate this course further for potential team training or personal development. --- ## Task: Evaluate Quantum Computing Course for Team Training Description: Following up on the forwarded email chain "Un breve corso su Quantum Computing," the goal is to assess the suitability of this brief quantum computing course as a potential training opportunity for the team or relevant individuals. This involves gathering key details, evaluating its content, and determining feasibility. Source Email: * Subject: Re: FW: FW: Un breve corso su Quantum Computing * Likely Sender: [Person who sent the email to you] * Likely Context: The sender has seen information about a quantum computing course and is prompting further investigation. Priority: Medium Due Date: [Suggest a date, e.g., End of next week, 2023-11-24] Assigned To: [Your Name/Recipient of the email] Actions to Accomplish: 1. Locate Original Course Information: * Find the initial email in the thread that contains the details, link, or attachment for "Un breve corso su Quantum Computing." * If the link/information isn't immediately obvious, try searching your inbox for earlier "FW: Un breve corso su Quantum Computing" emails or ask the sender for clarification. 2. Gather Key Course Details: * Curriculum/Topics: What specific quantum computing concepts are covered? * Duration: How long is the course (hours, days, weeks)? * Format: Is it online, in-person, self-paced, live lectures? * Prerequisites: What prior knowledge (e.g., math, programming) is required? * Cost: What is the registration fee? Are there group discounts or organizational rates? * Language: Is the course entirely in Italian, or are there English options/materials? * Instructor(s): Who is teaching it, and what are their qualifications? * Dates/Schedule: When does the course run or when is registration open? 3. Evaluate Suitability for Team/Individuals: * Relevance: Does the course content align with current team projects, future goals, or skill gaps? * Audience: Who on the team would benefit most from this course? (e.g., developers, researchers, project managers). * Level: Is it an introductory, intermediate, or advanced course, and does it match the team's current knowledge level? 4. Assess Logistics & Feasibility: * Time Commitment: Can team members realistically dedicate the necessary time? * Budget: Is the cost within current training budgets? * Availability: Does the course schedule conflict with critical project deadlines or other commitments? 5. Prepare a Summary & Recommendation: * Compile the key findings from steps 2-4 into a concise summary. * Include a recommendation on whether to pursue this course (e.g., recommend for specific individuals, recommend for the whole team, recommend against it, suggest alternatives). * Highlight potential benefits and any significant challenges (cost, time, prerequisites). Expected Outcome: A brief report or email containing the essential details of the quantum computing course, an assessment of its suitability, and a clear recommendation for next steps. todoist-labels:: #outlook365 todoist-status:: ◼️
• 2026-02-03 Re: Autorizzazione periodo di studio e ricerca Chiara Romano (XXXIX ciclo) todoist-id:: 6fvr68hq7rVWr838 todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-02-03 todoist-desc:: From: chiara.romano1@graduate.univaq.it Received: 2026-02-03T06:58:31Z ✉: Web Link --- --- Buongiorno professore, Le scrivo per l’incremento della borsa per il mese corrente. Ne approfitto anche per ringraziarla per la disponibilità per il computer. A presto, Chiara ________________________________ Da: Davide Di Ruscio <davide.diruscio@ todoist-status:: ◼️
• 2026-02-03 PhD defense of Sergio Morales todoist-id:: 6fvfjJcxGXppG326 todoist-project:: #📧EmailsToAnswer todoist-due:: 2026-02-03 todoist-desc:: From: rclariso@uoc.edu Received: 2026-01-28T21:07:49Z ✉: Web Link --- --- Dear all, First of all, we would like to thank you for accepting to participate in the tribunal for Sergio Morales' PhD thesis defense (Davide, ChaTo and Javier as the acting tribunal, Abel and Lola as the substitutes). The proposed date for the def todoist-status:: ◼️
• 2026-02-03 Re: Federico's PhD thesis review todoist-id:: 9976641982 todoist-project:: #Inbox todoist-completed:: 2026-02-03 todoist-status:: ✅
• 2026-02-03 Re: Gennaro's PhD thesis review todoist-id:: 9976644078 todoist-project:: #Inbox todoist-completed:: 2026-02-03 todoist-status:: ✅
• 2026-02-03 Budget per attività di ricerca - anno 2026 todoist-id:: 9977333992 todoist-project:: #Inbox todoist-completed:: 2026-02-03 todoist-status:: ✅