[logseq-plugin-git:commit] 2026-02-04T16:49:10.844Z

pages/todoist___2001-02-05.md

@@ -19,4 +19,10 @@
   todoist-id:: [6fvwqvpX524XvrWg](https://todoist.com/showTask?id=6fvwqvpX524XvrWg)
   todoist-project:: #Inbox
   todoist-due:: 2001-02-05
+  todoist-status:: ◼️
+- [[2001-02-05]] [[Benchmarking framework]]
+  todoist-id:: [6cqMhJPhw74vH3wp](https://todoist.com/showTask?id=6cqMhJPhw74vH3wp)
+  todoist-project:: #🚀 Projects-EU-MOSAICO
+  todoist-due:: 2001-02-05
+  todoist-labels:: #deepwork #goal #logseqed
   todoist-status:: ◼️

pages/todoist___2026-02-04.md

@@ -49,11 +49,6 @@
   todoist-project:: #🎓 Services-PHDICT
   todoist-due:: 2026-02-04
   todoist-status:: ◼️
-- [[2026-02-04]] Chiedere Donatella per Juri
-  todoist-id:: [6frjgc5gjf6c98r8](https://todoist.com/showTask?id=6frjgc5gjf6c98r8)
-  todoist-project:: #🦮 Mentoring
-  todoist-due:: 2026-02-04
-  todoist-status:: ◼️
 - [[2026-02-04]] 🧠​​ EASE 2026 Research Papers Track
   todoist-id:: [6frFf4WCxMV283m6](https://todoist.com/showTask?id=6frFf4WCxMV283m6)
   todoist-project:: #📜 REVIEWS
@@ -106,12 +101,6 @@
   todoist-due:: 2026-02-04
   todoist-desc:: From: disorbo@unisannio.it Received: 2026-01-20T09:03:13Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAidZtYrAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Here's a summary of the email content and the corresponding actionable task: **Task Summary:** The email is a rejection notification from the Journal of Systems and Software (JSS) for the submission "Examining Fairness Issues in Machine Learning-based Systems" (Ref. No.: JSSOFTWARE-D-25-01604). While the paper is rejected, the editor strongly advises resubmission after addressing the reviewers' detailed comments. The reviewers highlight significant areas for improvement in the manuscript's framing of fairness, integration of related work, methodological structure and detail (especially for the qualitative analysis), dataset selection justification, and the significance and implications of the results. The resubmitted paper will be treated as a new submission. **Actionable Task:** **Task:** Revise and Resubmit Paper to Journal of Systems and Software **Description:** The submission "Examining Fairness Issues in Machine Learning-based Systems" (Ref. No.: JSSOFTWARE-D-25-01604) has been rejected by the Journal of Systems and Software. However, the editor encourages resubmission after addressing detailed reviewer comments. Key areas for improvement include: * **Framing of Fairness:** Clearly define whether fairness is treated as a technical, socio-technical, or hybrid concern. * **Related Work:** Synthesize the literature into a coherent argument rather than an enumerative survey. * **Methodology:** * Present a unified methodological structure with clear workflows and transitions between phases. * Provide more detailed explanations for the qualitative coding process, including iteration, rater interaction, and reliance on LLM summaries. * Clarify the sequencing of methodological steps and ensure logical dependencies. * Justify dataset selection criteria and report exclusion numbers. * Ensure consistency between research questions and the role of LLMs. * Consider extending the dataset size if feasible through pre-screening. * **Results and Discussion:** * Explicitly discuss novel vs. incremental findings and align with previous empirical work. * Provide concrete examples of implications for practitioners. * Consider adding new research questions and discussions. * Clarify the rationale for using large language models. * **Overall Cohesion:** Improve the integration and cohesion across different methods employed in the study. **Recommended Actions:** 1. **Thoroughly read and understand all reviewer comments.** 2. **Develop a detailed plan to address each comment.** Categorize comments by theme (e.g., Introduction, Methodology, Results, Discussion) to facilitate systematic revision. 3. **Rewrite sections of the manuscript** based on the reviewer feedback, focusing on the identified weaknesses. 4. **Prepare a comprehensive response letter** detailing how each reviewer comment has been addressed. 5. **Ensure the resubmitted manuscript is treated as a NEW submission** but consider disclosing the original submission information and reference number. 6. **Consult empirical research guidelines** (e.g., Paul Ralph et al. 2020) for structuring the revised manuscript and methodology. 7. **Consider creating a methodological diagram** to clarify the workflow. **No Deadline:** The email does not specify a deadline for resubmission. --- Buongiorno a tutti, vi giro la mail ricevuta da JSS. Saluti, Andrea ---------- Forwarded message --------- Da: Journal of Systems and Software <em@editorialmanager.com> Date: lun 19 gen 2026 alle ore 10:59 Subject: Decision on your submission
   todoist-status:: ◼️
-- [[2026-02-04]] [[Benchmarking framework]]
-  todoist-id:: [6cqMhJPhw74vH3wp](https://todoist.com/showTask?id=6cqMhJPhw74vH3wp)
-  todoist-project:: #🚀 Projects-EU-MOSAICO
-  todoist-due:: 2026-02-04
-  todoist-labels:: #deepwork #goal #logseqed
-  todoist-status:: ◼️
 - [[2026-02-04]] Chiamare Lina Calandra
   todoist-id:: [6frjr4pqhF8PjMff](https://todoist.com/showTask?id=6frjr4pqhF8PjMff)
   todoist-project:: #👨‍🏫 Teaching

pages/todoist___2026-02-09.md

@@ -68,4 +68,9 @@
   todoist-project:: #👷 WORK
   todoist-due:: 2026-02-09
   todoist-desc:: From: salvatore.distefano@unime.it Received: 2025-12-30T16:33:44Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAiQFox%2FAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Okay, let's break down this document and create a detailed action plan to complete the task. The document is a web page displaying a meeting invitation for a Google Group called "Quantitative Methods in Informatics." Here's a breakdown of what it’s saying and what needs to be done to follow through: **1. Understanding the Purpose & Context** * **Meeting Invitation:** The document is a notification about a meeting scheduled within Google Groups dedicated to quantitative methods. * **Key Attendees:** The group is likely comprised of researchers, analysts, and others interested in this topic. * **Action Required:** The user needs to respond to the meeting invitation and confirm their attendance. **2. Action Plan - Step-by-Step** Here’s a breakdown of what to do, prioritized by urgency: **Phase 1: Immediate Response (Within 24 Hours)** 1. **Read the Invitation Carefully:** Thoroughly understand the meeting details: * **Date & Time:** Confirm the exact time. * **Location:** Where is the meeting held? (Zoom link, Google Meet URL, etc.) * **Agenda:** What topics will be discussed? (This helps prepare.) * **Required Materials/Preparation:** Are there any documents to review beforehand? 2. **Respond to the Meeting Invitation:** * **Confirm Attendance:** Reply immediately: “Yes, I’m coming!” or “I’ll be there.” * **Briefly Confirm:** A short, polite acknowledgement is sufficient (e.g., "Great, looking forward to it!") 3. **Check Your Calendar:** Ensure your schedule doesn’t conflict with the meeting. **Phase 2: Preparation & Engagement (1-2 Days Before)** 4. **Review Materials (If Applicable):** If the agenda includes documents, pre-read them. 5. **Prepare Questions/Contributions:** Think about what you want to discuss. Jot down some initial thoughts or questions. This demonstrates engagement. 6. **Join the Discussion (Optional):** Consider participating in the discussion if you have relevant expertise or insights. **Phase 3: Confirmation & Attendance (Day of Meeting)** 7. **Confirm Attendance (via Group Chat):** If it’s a Google Meet, reply to the chat and confirm your participation. (e.g., “I'm in!”) 8. **Review the Agenda:** Quickly glance at the agenda again to make sure you're prepared. 9. **Prepare for the Meeting:** If you're contributing, think about what you'll share. 10. **Join the Meeting:** Log in to the meeting link. **Phase 4: Post-Meeting (Immediately After)** 11. **Note Key Takeaways:** Shortly after the meeting, jot down any key takeaways, decisions made, or action items assigned. 12. **Follow Up (If Needed):** If you have specific questions or feedback, reach out to the organizers or attendees. **3. Tools & Resources (Useful for the Action Plan)** * **Google Calendar:** For scheduling and calendar visibility. * **Google Groups:** To find relevant meetings and communication within the group. * **Zoom/Google Meet/Other Meeting Platform:** For the actual meeting. **4. Important Considerations** * **Respect Group Rules:** Follow any guidelines or etiquette established within the Google Group. * **Be Professional:** Maintain a polite and respectful tone in your communication. --- **To help me refine this further, could you tell me:** * What specifically are you hoping to do *after* responding to the invitation? (e.g., do you need to provide specific details, share a thought, or take a particular action?) --- Cari, mando a un ristretto gruppo di amici un reminder per il Wshop QuCS su quantitative CyberSec per ItaSec. Tutti noi siamo stati coinvolti, direttamente o indirettamente in SERICS, e potrebbe essere una buona venue per interagire con la comunità di c
+  todoist-status:: ◼️
+- [[2026-02-09]] Chiedere Donatella per Juri
+  todoist-id:: [6frjgc5gjf6c98r8](https://todoist.com/showTask?id=6frjgc5gjf6c98r8)
+  todoist-project:: #🦮 Mentoring
+  todoist-due:: 2026-02-09
   todoist-status:: ◼️