To maintain clarity and ensuring that our research and resources remain accessible, LUGAN follows a strict file organization strategy. Please adhere to these guidelines when creating new files or repositories.
Where: documentation (This repository)
This repository is the central archive for the organization’s “bureaucracy” and identity. It is the single source of truth for how we operate.
Where: events repository
All information regarding our meetups, workshops, and gatherings, whether they are past, in-progress, or future, must be stored in the dedicated events repository.
events repo, create a specific folder for each event (e.g., YYYY-MM-DD_EventName).When organizing an event, we distinguish between presentation materials and source code:
Location: inside the specific folder in the events repository.
.pdf, .pptx), a flyer, or a text summary of the meeting, upload it directly to the event’s folder.Location: A dedicated new repository.
events repo.workshop-python-automation).events repo.README.md or a link file pointing to that new code repository.Here is how the organization looks in practice:
github.com/Linux-User-Group-ANcona/
│
├── documentation/ (This Repo)
│ ├── MANIFESTO.md
│ ├── CODE_OF_CONDUCT.md
│ └── STRUCTURE.md
│
├── events/ (The History Log)
│ ├── 2025-10-15_IntroToLinux/
│ │ └── slides.pdf
│ │
│ └── 2025-11-20_AdvancedPython/
│ ├── presentation.pdf
│ └── README.md -----> [LINK to 'workshop-python-code' repo]
│
└── workshop-python-code/ (Actual Code)
├── main.py
└── requirements.txt
| Content Type | Destination Repository | Note |
|---|---|---|
| Policies, Rules, CoC | documentation |
Keep this repo clean and text-focused. |
| Event Slides/PDFs | events |
Inside a specific folder named by date. |
| Event Source Code | New Dedicated Repo | Link this new repo inside the events folder. |