4.3 KiB
4.3 KiB
progress:: {{renderer :todomaster}}
icon:: 📅
boox-notes::
- ### Tasks
-
- ### Notes
- #### **Meeting with students Tesfay and Abu dicussing on using MAS to generate README files**
type:: [[meeting]]
tags:: [[SoftwareMiningGroup]]
collapsed:: true
- 
- 
- First of all, what's hight quality README files?
- What README files should include? You know that there are deployment instructions, how to use the projects, how to contribute? So the issue that I see is the definition of quality that should be considered to generate high quality README files
- 
- 
- 
- 
- An issue that I can see is that it is highly probable that README files have been seen by LLMs
- [LARCH: Large Language Model-based Automatic Readme Creation with Heuristics](https://arxiv.org/pdf/2308.03099)
- 
- 
- 
- What's the validity of the standard README file structure?
- 
- 
- Repository-specific README structure
- It means that you need to train by considering different kinds of repositories. What can you say about the representativeness of the analyzed repositories?
- Actually you don't know how many kinds of repositories you have, right? What can you say about the completeness of the process?
- 
- 
- 
- 
- 
- Ablation study is also OK but there is the bias issue that I mentioned before that's a critial threats to validity of the overall process.
- 
- How similar/different are the generated README files with respect to the original README file?
- 
- **Meeting WP5 [[PROJECTS/MOSAICO]]**
type:: [[meeting]]
tags:: [[PROJECTS/MOSAICO]]
- [Demo from UY](https://imtatlantiquefr.sharepoint.com/:v:/r/sites/MOSAICO/Shared%20Documents/Work%20Packages/WP1/D1.2/20251210%20-%20Mosaico%20Coding%20Extension%20Demo%202.mp4?csf=1&web=1&e=cnoYvM&xsdata=MDV8MDJ8fGUxZmI1NTIzYWZjZjQwN2I2MmEyMDhkZTNjOTRkYTQwfDhmOWI4OGE3M2YzZTRiZTNhYWU0MjAwNmQ0YzQyMzA2fDB8MHw2MzkwMTQ4MDcxNDc2NjgxMzB8VW5rbm93bnxWR1ZoYlhOVFpXTjFjbWwwZVZObGNuWnBZMlY4ZXlKRFFTSTZJbFJsWVcxelgwRlVVRk5sY25acFkyVmZVMUJQVEU5R0lpd2lWaUk2SWpBdU1DNHdNREF3SWl3aVVDSTZJbGRwYmpNeUlpd2lRVTRpT2lKUGRHaGxjaUlzSWxkVUlqb3hNWDA9fDF8TDJOb1lYUnpMekU1T20xbFpYUnBibWRmVG5wVmVWbHRTbTFaYlZsMFRrZFJNMWxUTURCUFZHZDRURmRLYlU1cVdYUk9lbWMxVGpKUk5VNUhUVEpPTWtWNVFIUm9jbVZoWkM1Mk1pOXRaWE56WVdkbGN5OHhOelkxT0Rnek9URXpOVEV6fDM2NTI3ZTZmNjI1MTRjNjVhOWQwMDhkZTNjOTRkYTNmfGRlNjQzOGFiYjY3NzQ0OTg5ODdkZTI2Yzk4MTYyMjg4&sdata=Z3NJS0N0MzdkTFdxWjNhbWhZbmQxSWtoNTNQMlg1Ymp1WXVsWGlmMHVEcz0%3D&ovuser=9df08a7c-31d7-4024-9ba6-5ed5efac1a01%2Cdavide.diruscio%40univaq.it)
- {:height 503, :width 848}
- Each agent gives back a card to understand how to use it?
- https://a2a-protocol.org/v0.3.0/specification/#55-agentcard-object-structure
- We use the A2A card to **use** the agent, but we don't need it to **find** or **select** it (it's enough with the MOSAICO repository metadata)
- We discussed [MOSAICO_system_architecture_sequence_diagram_v3.drawio](https://imtatlantiquefr.sharepoint.com/:u:/r/sites/MOSAICO/Shared%20Documents/Work%20Packages/WP5/T5.2/System%20Architecture/MOSAICO_system_architecture_sequence_diagram_v3.drawio?csf=1&web=1&e=hvJq9x)
- Tutti gli agenti sono un server A2A
- Reference and Collaboration sono sia client che server
- Supervision and Solution are only server
-
-
-