From 2603a007216fd10a50d45a3b69d0c037f4f91774 Mon Sep 17 00:00:00 2001 From: Davide Di Ruscio Date: Fri, 30 Jan 2026 12:54:10 +0100 Subject: [PATCH] [logseq-plugin-git:commit] 2026-01-30T11:54:08.488Z --- pages/todoist___2001-02-03.md | 7 ++++++ pages/todoist___2026-01-30.md | 42 ++++++++++++----------------------- pages/todoist___2026-01-31.md | 7 ++++++ pages/todoist___2026-02-01.md | 5 +++++ pages/todoist___2026-02-02.md | 18 +++++++++++++++ pages/todoist___Backlog.md | 5 ----- 6 files changed, 51 insertions(+), 33 deletions(-) create mode 100644 pages/todoist___2001-02-03.md diff --git a/pages/todoist___2001-02-03.md b/pages/todoist___2001-02-03.md new file mode 100644 index 00000000..5bfde5fb --- /dev/null +++ b/pages/todoist___2001-02-03.md @@ -0,0 +1,7 @@ +- +- [[2001-02-03]] Stato TIZIANO + todoist-id:: [6fMGMX5f829Cx3J8](https://todoist.com/showTask?id=6fMGMX5f829Cx3J8) + todoist-project:: #🦮 Mentoring + todoist-due:: 2001-02-03 + todoist-desc:: - **Piano di ricerca (ci farà avere il prima dl meeting di mercoledi settimana prossima)** - Diverse track - Tecniche MDE e GitHub a Prompt per LLM + todoist-status:: ◼️ \ No newline at end of file diff --git a/pages/todoist___2026-01-30.md b/pages/todoist___2026-01-30.md index 26350b3b..f5c902c0 100644 --- a/pages/todoist___2026-01-30.md +++ b/pages/todoist___2026-01-30.md @@ -1,10 +1,4 @@ - -- [[2026-01-30]] Acquistare trasformatore - todoist-id:: [6fWf6CF6R77g64wg](https://todoist.com/showTask?id=6fWf6CF6R77g64wg) - todoist-project:: #📗 Personal - todoist-due:: 2026-01-30 - todoist-desc:: [RemaTarlazzi S.p.A. · Via Nuova, 7/a, 67051 Avezzano AQ, Italy](https://maps.app.goo.gl/VU54rc4pwBPx3dUQ7) Telefono 0863455041 - todoist-status:: ◼️ - [[2026-01-30]] Studiare nuovi regolamenti su incarichi di ricerca e post-doc todoist-id:: [6fFFQ9v3PM5g4qJ8](https://todoist.com/showTask?id=6fFFQ9v3PM5g4qJ8) todoist-project:: #🏢 Admin @@ -50,13 +44,6 @@ todoist-desc:: [Web Link](https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AjoVpQvBez0Ss5ZY2WGWEJgAIotZUCwAA&exvsurl=1&viewmodel=ReadMessageItem) Here is the description of the task created from the provided email content: --- **Task Title:** Access and Review Shared Folder: PROG_DI_ATENEO_2026 **Description:** Carmela Berloffa has shared a folder named "PROG_DI_ATENEO_2026" with you. This task involves accessing the shared folder to confirm its availability and briefly review its contents to understand its purpose and any immediate actions required. This folder likely contains important documentation or resources related to the "University Program 2026." **Origin:** Email from Carmela Berloffa (Shared Folder Notification) **Due Date:** [Leave blank or set to ASAP if immediate action is implied by context not provided] **Priority:** Normal **Steps to Accomplish:** 1. **Locate the Email Notification:** Find the original email from Carmela Berloffa with the subject "Carmela Berloffa ha condiviso la cartella 'PROG_DI_ATENEO_2026' con te" (or similar shared folder notification). 2. **Access the Folder:** Click on the link provided within the email to open the "PROG_DI_ATENEO_2026" shared folder. 3. **Verify Access:** Confirm that you can successfully open and browse the contents of the folder without any permission issues. 4. **Review Contents (Initial):** Spend a few minutes reviewing the top-level files or subfolders to get an initial understanding of what the "PROG_DI_ATENEO_2026" project entails and your expected involvement (if any). 5. **Acknowledge and Inquire (Optional but Recommended):** Reply to Carmela Berloffa to confirm that you have successfully accessed the folder. If the purpose or your role regarding the folder's content isn't immediately clear, you can take this opportunity to ask for clarification. 6. **Integrate (If Necessary):** If this folder is critical to your ongoing work, consider adding it to your Quick Access (if using Windows File Explorer with OneDrive/SharePoint) or syncing it to your local machine for easier future access. --- todoist-labels:: #outlook365 todoist-status:: ◼️ -- [[2026-01-30]] Re: FW: FW: Un breve corso su Quantum Computing - todoist-id:: [6frj3mGxqcGgmqvg](https://todoist.com/showTask?id=6frj3mGxqcGgmqvg) - todoist-project:: #Inbox - todoist-due:: 2026-01-30 - todoist-desc:: [Web Link](https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AjoVpQvBez0Ss5ZY2WGWEJgAIotZT7QAA&exvsurl=1&viewmodel=ReadMessageItem) 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-01-30]] GSSI Committee Documents – Draft Minutes and Regulation todoist-id:: [6fVFH9Gfqgfh6cj8](https://todoist.com/showTask?id=6fVFH9Gfqgfh6cj8) todoist-project:: #👷 WORK @@ -76,25 +63,24 @@ todoist-desc:: [Web Link](https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AjoVpQvBez0Ss5ZY2WGWEJgAIjj4wRQAA&exvsurl=1&viewmodel=ReadMessageItem) 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-01-30]] Finalizzare Verbale ultimo Collegio - todoist-id:: [6fr6MGrcrjRmjwP9](https://todoist.com/showTask?id=6fr6MGrcrjRmjwP9) - todoist-project:: #🎓 Services-PHDICT - todoist-due:: 2026-01-30 - todoist-status:: ◼️ -- [[2026-01-30]] Estratto verbale autorizzazione tutoraggio - todoist-id:: [6fr3x84vP3ghfWJ8](https://todoist.com/showTask?id=6fr3x84vP3ghfWJ8) - todoist-project:: #🎓 Services-PHDICT - todoist-due:: 2026-01-30 - todoist-desc:: From: federico.grande@graduate.univaq.it Received: 2026-01-26T13:32:28Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAihJn8IAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- **Task Summary:** Federico is inquiring about the Quantum Computing course with Professor Guidoni. He wants to know if there have been any changes to the course schedule as the stated start date of January 13th has passed without updates and his attempt to join a Teams meeting was unsuccessful. Additionally, Federico has received approval for his tutoring activity from the faculty and requests a document to present to the call commission. **Recommended Actions:** * **Clarify Quantum Computing Course Schedule:** * Confirm the current start date and any changes to the schedule for Professor Guidoni's Quantum Computing course. * Investigate why the Teams meeting was empty. * Communicate the updated course information to Federico. * **Provide Document for Tutoring Activity:** * Generate and provide an official document confirming the approval of Federico's tutoring activity by the faculty. * Ensure the document is suitable for presentation to the call commission. **Deadline:** None specified in the email. --- Buon pomeriggio Professore, volevo chiederle un’informazione riguardo al corso di Quantum Computing del Prof. Guidoni. Dal documento sul sito risultava che le lezioni dovessero iniziare il 13 gennaio, ma non ho trovato aggiornamenti a riguardo. Ho anche - todoist-status:: ◼️ - [[2026-01-30]] TOSEM-2026-0025 - Invitation to Review todoist-id:: [6frqVf6RWQ6cvchc](https://todoist.com/showTask?id=6frqVf6RWQ6cvchc) todoist-project:: #📧EmailsToAnswer todoist-due:: 2026-01-30 todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-29T23:01:58Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAii1IetAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Okay, here’s a concise summary of the email, suitable for a Todoist task, focusing on the key actions and deadlines: **Task: Review Manuscript - ATLAS** **Goal:** Submit a review of the ATLAS manuscript to TOSEM. **Details:** * **Deadline:** Four weeks from today (November 29, 2026). * **Action Items:** * Click the link: https://mc.manuscriptcentral.com/tosem?URL_MASK=c21db279cfdf4430b74a45be8e05afdc to confirm your review. * Confirm the review process (requires a webpage with the link). **Resources:** * Professor Ajitha Rajan’s review guidelines: https://www.acm.org/publications/policies/peer-review **Note:** This is a two-step process; you’ll need to confirm before proceeding. --- 29-Jan-2026 Dear Dr. Di Ruscio, I am writing to you on behalf of the Editorial Board of the ACM Transactions on Software Engineering and Methodology (TOSEM) regarding the following manuscript, which has been submitted to TOSEM: ATLAS: Artifact Ge todoist-status:: ◼️ -- [[2026-01-30]] Mandare mail alla sac circa la. scheda - todoist-id:: [6frmWg2HQHPMmHr8](https://todoist.com/showTask?id=6frmWg2HQHPMmHr8) +- [[2026-01-30]] Estratto verbale autorizzazione tutoraggio + todoist-id:: [9954300206](https://todoist.com/showTask?id=9954300206) todoist-project:: #Inbox - todoist-due:: 2026-01-30 - todoist-status:: ◼️ \ No newline at end of file + todoist-completed:: [[2026-01-30]] + todoist-status:: ✅ +- [[2026-01-30]] Finalizzare Verbale ultimo Collegio + todoist-id:: [9955880742](https://todoist.com/showTask?id=9955880742) + todoist-project:: #Inbox + todoist-completed:: [[2026-01-30]] + todoist-status:: ✅ +- [[2026-01-30]] Mandare mail alla sac circa la. scheda + todoist-id:: [9966015191](https://todoist.com/showTask?id=9966015191) + todoist-project:: #Inbox + todoist-completed:: [[2026-01-30]] + todoist-status:: ✅ \ No newline at end of file diff --git a/pages/todoist___2026-01-31.md b/pages/todoist___2026-01-31.md index 64a17972..29c27f50 100644 --- a/pages/todoist___2026-01-31.md +++ b/pages/todoist___2026-01-31.md @@ -288,4 +288,11 @@ todoist-due:: 2026-01-31 todoist-desc:: Subject: TOSEM-2026-0117 - Invitation to Review Sender: onbehalfof@manuscriptcentral.com Weblink: [Outlook](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAii1IeVAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) Content Summary: You have been invited by the Editorial Board of ACM TOSEM to review the manuscript titled "GoLink: A Bridge for Migrating from GoPath to Go Modules in Go Ecosystem" (TOSEM-2026-0117), authored by Wang, Chao et al. The Associate Editor responsible is Dr. Damian Tamburri. Main Task: - Decide whether to accept or decline the review invitation within three working days. - If accepted, complete the review report within four weeks, or request an extension if more time is needed by emailing atemplet@gmail.com. Subtasks: 1. Respond to the invitation via the provided links to accept: [ScholarOne Manuscripts](https://mc.manuscriptcentral.com/tosem?URL_MASK=41bd4d634f7e4355bc131c252b2f2333) or decline: [ScholarOne Manuscripts](https://mc.manuscriptcentral.com/tosem?URL_MASK=8d7cd40397b842db9633ba784030a603) within three working days. 2. Download the manuscript and review guidelines after confirmation. 3. Submit the review report within four weeks from acceptance. 4. If additional time beyond four weeks is needed, request it by emailing atemplet@gmail.com. Due Date: 2026-02-26 (four weeks from 29-Jan-2026 as mentioned) Note: If you identify conflicts of interest, report them as per the reviewer responsibilities before proceeding. Editor-in-Chief: Abhik Roychoudhury todoist-labels:: #ai-generated-main-task + todoist-status:: ◼️ +- [[2026-01-31]] Re: FW: FW: Un breve corso su Quantum Computing + todoist-id:: [6frj3mGxqcGgmqvg](https://todoist.com/showTask?id=6frj3mGxqcGgmqvg) + todoist-project:: #Inbox + todoist-due:: 2026-01-31 + todoist-desc:: [Web Link](https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AjoVpQvBez0Ss5ZY2WGWEJgAIotZT7QAA&exvsurl=1&viewmodel=ReadMessageItem) 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:: ◼️ \ No newline at end of file diff --git a/pages/todoist___2026-02-01.md b/pages/todoist___2026-02-01.md index 2218c2fa..e0ed1e2e 100644 --- a/pages/todoist___2026-02-01.md +++ b/pages/todoist___2026-02-01.md @@ -44,4 +44,9 @@ todoist-id:: [6fjWHCmHqGFFvMvF](https://todoist.com/showTask?id=6fjWHCmHqGFFvMvF) todoist-project:: #📗 Personal todoist-due:: 2026-02-01 + todoist-status:: ◼️ +- [[2026-02-01]] Aggiornare sito con gli ultimi due corsi aggiuntivi + todoist-id:: [6frwc82JfjrWXH2h](https://todoist.com/showTask?id=6frwc82JfjrWXH2h) + todoist-project:: #🎓 Services-PHDICT + todoist-due:: 2026-02-01 todoist-status:: ◼️ \ No newline at end of file diff --git a/pages/todoist___2026-02-02.md b/pages/todoist___2026-02-02.md index 57a1461a..2c1cb964 100644 --- a/pages/todoist___2026-02-02.md +++ b/pages/todoist___2026-02-02.md @@ -132,4 +132,22 @@ todoist-project:: #🚀 Projects-EU-MOSAICO todoist-due:: 2026-02-02 todoist-labels:: #deepwork #goal #logseqed + todoist-status:: ◼️ +- [[2026-02-02]] Acquistare trasformatore + todoist-id:: [6fWf6CF6R77g64wg](https://todoist.com/showTask?id=6fWf6CF6R77g64wg) + todoist-project:: #📗 Personal + todoist-due:: 2026-02-02 + todoist-desc:: [RemaTarlazzi S.p.A. · Via Nuova, 7/a, 67051 Avezzano AQ, Italy](https://maps.app.goo.gl/VU54rc4pwBPx3dUQ7) Telefono 0863455041 + todoist-status:: ◼️ +- [[2026-02-02]] SW-2025-10-0161.R1 Review Submitted - Di Sipio + todoist-id:: [6frwVhMF3mGmJfCg](https://todoist.com/showTask?id=6frwVhMF3mGmJfCg) + todoist-project:: #Inbox + todoist-due:: 2026-02-02 + todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-30T08:52:23Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAikQGH6AAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- 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-02]] Comunicazione Registri delle lezioni I semestre a.a.2025-2026 + todoist-id:: [6frwVhQVmF246hM8](https://todoist.com/showTask?id=6frwVhQVmF246hM8) + todoist-project:: #Inbox + todoist-due:: 2026-02-02 + todoist-desc:: From: disim.uprodid@strutture.univaq.it Received: 2026-01-30T09:02:07Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAikQGH7AAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- --- 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:: ◼️ \ No newline at end of file diff --git a/pages/todoist___Backlog.md b/pages/todoist___Backlog.md index 4ca32d51..90ca6c21 100644 --- a/pages/todoist___Backlog.md +++ b/pages/todoist___Backlog.md @@ -1692,11 +1692,6 @@ todoist-desc:: ✉: https://s.diruscio.org/KxsDS 📱: https://s.diruscio.org/nhuoy Sender: GitHub Sent: Tue Aug 12 2025 17:01:48 GMT+0200 (Central European Summer Time) --- The latest launches from GitHub. See what’s new and how to get started. ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ( [GitHub · Build and ship software on a single, collaborative platform](https://github.com?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) ************************ GitHub release round-up, August edition ************************ The latest launches from GitHub. See what’s new and how to get started. Here’s a roundup of what shipped in the last month, including an update to our legal terms removing blockers for using preview features as well as several updates and improvements to Copilot coding agent. ( [Defense of third-party claims added for volume licensing customers - GitHub Changelog](https://github.blog/changelog/2025-08-08-defense-of-third-party-claims-added-for-volume-licensing-customers/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) Our Pre-release License Terms support you better: ( [Defense of third-party claims added for volume licensing customers - GitHub Changelog](https://github.blog/changelog/2025-08-08-defense-of-third-party-claims-added-for-volume-licensing-customers/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- * Use preview features with confidence, since you gain the same IP protections as when we make them generally available. * Retain ownership of your AI inputs in preview, and have assurance they (and their outputs) won’t be used for training purposes. ( [OpenAI GPT-5 is now in public preview for GitHub Copilot - GitHub Changelog](https://github.blog/changelog/2025-08-07-openai-gpt-5-is-now-in-public-preview-for-github-copilot/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) More models, more options ------------------------- * OpenAI GPT-5 is here: ( [OpenAI GPT-5 is now in public preview for GitHub Copilot - GitHub Changelog](https://github.blog/changelog/2025-08-07-openai-gpt-5-is-now-in-public-preview-for-github-copilot/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) Available for public preview in *Chat* , *Ask* , or *Agent* mode, the model is available in VS Code, on github.com ( [GitHub · Build and ship software on a single, collaborative platform](http://Github.com?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) , and on GitHub mobile. * Anthropic Claude Opus 4.1 is in public preview for Copilot Enterprise users: ( [Anthropic Claude Opus 4.1 is now in public preview in GitHub Copilot - GitHub Changelog](https://github.blog/changelog/2025-08-05-anthropic-claude-opus-4-1-is-now-in-public-preview-in-github-copilot/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) Now available in Copilot Chat, Claude Opus 4.1 succeeds Opus 4 as Anthropic’s most capable model to support extended thinking, tool use, and logical summaries. ( [Agents page for GitHub Copilot coding agent - GitHub Changelog](https://github.blog/changelog/2025-07-02-agents-page-for-copilot-coding-agent-in-public-preview/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) Copilot coding agent is easier to access and more customizable to meet your needs --------------------------------------------------------------------------------- * Simplified costs: ( [GitHub Copilot coding agent now uses one premium request per session - GitHub Changelog](https://github.blog/changelog/2025-07-10-github-copilot-coding-agent-now-uses-one-premium-request-per-session/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) The agent now uses a single Copilot premium request ( [Requests in GitHub Copilot - GitHub Docs](https://docs.github.com/copilot/concepts/billing/copilot-requests#what-are-premium-requests?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) per session, regardless of how complex the task is. Know the cost before starting a request, and complete more tasks within your monthly request limit! * Start from (almost) anywhere: ( [Agents page for GitHub Copilot coding agent - GitHub Changelog](https://github.blog/changelog/2025-07-02-agents-page-for-copilot-coding-agent-in-public-preview/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) Kick off Copilot coding agent requests from the new *Agents* page, VS Code ( [Start and track GitHub Copilot coding agent sessions from Visual Studio Code - GitHub Changelog](https://github.blog/changelog/2025-07-14-start-and-track-github-copilot-coding-agent-sessions-from-visual-studio-code/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) , the GitHub MCP server ( [Delegate tasks to Copilot coding agent from the GitHub MCP server - GitHub Changelog](https://github.blog/changelog/2025-07-09-delegate-tasks-to-copilot-coding-agent-from-the-github-mcp-server/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) , or any base branch ( [Agents page: Set the base branch for GitHub Copilot coding agent tasks - GitHub Changelog](https://github.blog/changelog/2025-07-23-agents-page-set-the-base-branch-for-github-copilot-coding-agent-tasks/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) , making it even easier to get Copilot to take on some of the heavy lifting. * MCP: ( [Copilot coding agent now supports remote MCP servers - GitHub Changelog](https://github.blog/changelog/2025-07-09-copilot-coding-agent-now-supports-remote-mcp-servers/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) The agent now has the ability to configure and use MCP servers, either built-in or custom. Connect other applications with Copilot, expanding its context and capabilities. * New guardrails: ( [Configure internet access for Copilot coding agent - GitHub Changelog](https://github.blog/changelog/2025-07-15-configure-internet-access-for-copilot-coding-agent/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) Control the level of access that Copilot has to the internet, and provide tailored guidance for your org with custom instructions ( [GitHub Copilot coding agent now supports .instructions.md custom instructions - GitHub Changelog](https://github.blog/changelog/2025-07-23-github-copilot-coding-agent-now-supports-instructions-md-custom-instructions/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ). ( [Agent mode for JetBrains, Eclipse, and Xcode is now generally available - GitHub Changelog](https://github.blog/changelog/2025-07-16-agent-mode-for-jetbrains-eclipse-and-xcode-is-now-generally-available/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) Powering up IDEs ---------------- * Agent mode added to multiple IDEs: ( [Agent mode for JetBrains, Eclipse, and Xcode is now generally available - GitHub Changelog](https://github.blog/changelog/2025-07-16-agent-mode-for-jetbrains-eclipse-and-xcode-is-now-generally-available/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) Designed to autonomously perform complex, multi-step tasks, agent mode has become one of the most used features in VS Code. It is now generally available in JetBrains, Xcode, and Eclipse. * Combining AI and open source: ( [GitHub Copilot in VS Code June release (v1.102) - GitHub Changelog](https://github.blog/changelog/2025-07-15-github-copilot-in-vs-code-june-release-v1-102/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) VS Code has open sourced the Copilot Chat extension, allowing bugs to be found and addressed more quickly, and opportunity for community led updates and custom extension solutions. ----------- Other ships ----------- * GitHub Spark, our AI-powered assistant capable of developing entire apps from natural language, launched in public preview. ( [GitHub Spark in public preview for Copilot Pro+ subscribers - GitHub Changelog](https://github.blog/changelog/2025-07-23-github-spark-in-public-preview-for-copilot-pro-subscribers/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) * Administrators can now configure private registry entries for Dependabot at the organization level, allowing them to manage their repositories in a central location. ( [Centralized private registry configuration for Dependabot is now generally available - GitHub Changelog](https://github.blog/changelog/2025-07-22-centralized-private-registry-configuration-for-dependabot-is-now-generally-available/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) *With love* ❤️, Mona and the team at GitHub ( [GitHub Universe](https://githubuniverse.com?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) ( [GitHub (@github) on X](https://x.com/github?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) ( https://www.instagram.com/GitHub/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025 ) ( https://www.youtube.com/github?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025 ) ( [GitHub | LinkedIn](https://www.linkedin.com/company/github/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) ( [GitHub · Build and ship software on a single, collaborative platform](https://github.com/?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) Sign in to GitHub ( [Build software better, together](https://github.com/login?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) • Unsubscribe ( [Unsubscribe successful](https://mailing.github.com/wf/unsubscribe?upn=u001.Pi7o6M8nPadRvtg46Rl6K2YQgj0-2BzdoBr4cZzwXsTcEwmljoObvfSFGGbSWsNelZe0g2RHIZSlsE51oxBkZz6WFwXoudW7zScGGjb9Rk8y4EqAguns4zs-2FXei1BfkNf7hKG7r-2BIZVHO-2BN6tOPbFyfP5Ekqg2HBkJ6PvUy16GruZOCg7drzoR2kbd83QiGV5x9L0xvBr18j3hR-2FBXOqmX8jJNYYgT0Q2Jnk0FaznZI5UXANbgwksE48nbT-2F7SZA3YDyG60U-2Bjx1vnRSPHn1mUVsEGQ06330PBmppeNd8s-2FPrUd8n-2B6kzJ38F2gD-2BkkVrCeLwArSOnzo94NPUHnI-2Bi3CxbnzFnrimobqZ1jqwLPn8MlilupCGk1hY95OEDMh1e-2B-2FdV8GJW-2FmGiJhpkreD9wBo9r68OtDg8KV9NVkmrliYXpDhbUDVNzdcERvMUJvmeZnXpeWJJSTLZ-2BGnAgNu9u7463KZfG4i0IL9tPHig15fSM4ngiSCHnaah4DOKMlqGdCcm-2BUIJOTEb3Mm-2FiaZK825nsROQhBLkr08X6grDcr1sbh5GtWFO1xwKZQwkS0niPuE2M7zLyF23abB4yeTI5grVeT9-2FrXBxfOHkvPyOd-2FugEVIPtgiu5-2B4XVTOm49-2Fh7kLvt8xbIypNb-2BdIdqjafWBq6yuYVW18DY-2FT6bHx3w6vg2ZS3SQbd8UBeC79bGeMmfyfktRlVc5BUMlHhqMK-2B90UT8PHQO2bkUYEjiOgBcvaUbIIsZPUo-2F9aBIYtxX-2FW74ie2UzH7ISoDPoSUQeIBKmJ4L0TqWEanBaltAZLH8JASTVTk4cdDfM2p8fFJpmLNpKq5m-2B1DBRAPXDP1PykdtRwmv8zCKw3GU-2BHj6J2QZS3CNVkFKYFwohZXjxV48jQ2vusNZZ-2F9AMKl8TCw81utLU7Cjl363uo1Kr-2FTNbCp6IU7njkentfaryebVlmqGS9PaRzHxQiJpuiwzZu5Wp8aUl2DNfiBgsogtb1mrUpYBVEdArD1v2akODIGgbKRmds) ) Privacy policy ( [GitHub General Privacy Statement - GitHub Docs](https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) • Terms of use ( [GitHub Terms of Service - GitHub Docs](https://docs.github.com/en/site-policy/github-terms/github-terms-of-service?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) • Contact us ( [Contacting GitHub Support - GitHub Docs](https://docs.github.com/en/support/contacting-github-support?utm_source=github&utm_medium=email&utm_campaign=mpu_august2025) ) GitHub, Inc. • 88⁠ Colin P⁠ Kelly Jr Street • San⁠ Francisco,⁠ CA⁠ 94107 You are receiving this because you are the administrator of a GitHub account. --- todoist-labels:: #reading todoist-status:: ◼️ -- [[No due date]] Stato TIZIANO - todoist-id:: [6fMGMX5f829Cx3J8](https://todoist.com/showTask?id=6fMGMX5f829Cx3J8) - todoist-project:: #🦮 Mentoring - todoist-desc:: - **Piano di ricerca (ci farà avere il prima dl meeting di mercoledi settimana prossima)** - Diverse track - Tecniche MDE e GitHub a Prompt per LLM - todoist-status:: ◼️ - [[No due date]] [L'alpinista Nirmal Purja risponde alle polemiche social: «Io sprovveduto con le sneakers sul Monte Rosa? So quello che faccio»](https://www.open.online/2022/08/21/alpinista-nirmal-purja-risponde-polemiche-social/) todoist-id:: [66hmx5fVx48Gxrrm](https://todoist.com/showTask?id=66hmx5fVx48Gxrrm) todoist-project:: #📗 Personal