Fargo3d/3DPrintMeetup
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update August meetup details, permanent location, and sync wiki

Browse Source 
- Establish West Fargo Public Library as standard meeting location
- Sync August 2026 Gridfinity challenge and September upcoming challenge
- Update Copilot instructions with location and date sync guidelines
- Update submodule wiki-fargo3d

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
Meetup Organizer
2026-08-16 21:12:11 -05:00
parent 447ced49b4
commit 9e93556e1c
9 changed files with 79 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
.github/copilot-instructions.md vendored
View File

@@ -46,18 +46,42 @@ Challenges follow a specific monthly cycle:
# Content Synchronization
The `wiki-fargo3d` submodule contains the official documentation. Some content is mirrored in the main repository root.
The `wiki-fargo3d` submodule contains the official documentation. Some content is mirrored in the main repository root and `wiki-content-gitea`.
- **Readme.md vs wiki-fargo3d/Home.md**: Keep announcements and general descriptions in sync.
- **challenges.md vs wiki-fargo3d/Current-Challenge.md**: `challenges.md` should reflect the active challenge found in the wiki.
- **itinerary.md vs wiki-fargo3d/Itinerary.md**: Keep meeting schedules in sync.
## Synchronization Matrix
When updating monthly challenges, dates, or announcements, update all corresponding locations:
- **Root `Readme.md` vs `wiki-fargo3d/Home.md` (and `wiki-content-gitea/Home.md`)**:
- Keep active challenge name, upcoming challenge name, and general descriptions in sync.
- **Root `challenges.md` vs `wiki-fargo3d/Current-Challenge.md` (and `wiki-content-gitea/Current-Challenge.md`)**:
- Keep active challenge details, requirements, judging, timeline, and challenge archive table in sync.
- **Root `itinerary.md` vs `wiki-fargo3d/Itinerary.md` (and `wiki-content-gitea/Itinerary.md`)**:
- Keep meeting schedules and segment timelines in sync.
- **`wiki-fargo3d/Upcoming-Challenge.md` vs `wiki-content-gitea/Upcoming-Challenge.md`**:
- Keep upcoming challenge announcement details in sync.
- **`wiki-fargo3d/Important-Dates.md` vs `wiki-content-gitea/Important-Dates.md`**:
- Keep upcoming meetup dates, completed statuses, and challenge milestones in sync.
- **`announcements/<MonthYear>.md` vs `challenges/<Month-Year>/readme.md`**:
- Keep announcement email texts, meeting dates/locations, and challenge folders in sync.
## Meeting Location Standards
- **Primary / Standard Location**:
```text
West Fargo Public Library
215 Third St. E.
West Fargo, ND 58078
```
- All regular meetings, `Important-Dates.md`, and announcements should reflect the West Fargo Public Library unless a specific one-off meeting venue is designated.
## "Last Updated" Date Policy
- Any page containing a `**Last Updated**: <Date>` footer (e.g., `Home.md`, `Important-Dates.md`) **must** be updated to reflect the current date whenever changes or reviews occur.
## Git Workflow for Wiki Updates
1. Make changes in `wiki-fargo3d/`.
1. Make changes in `wiki-fargo3d/` (and mirror to `wiki-content-gitea/` if applicable).
2. Commit and push changes in `wiki-fargo3d`.
3. Go to root `P:\3dPrintMeetup`.
4. Commit the submodule update.
5. Push root changes.
3. Update root documentation (`Readme.md`, `challenges.md`, `itinerary.md`, `announcements/`).
4. Go to root `/home/espoon/photos/3dPrintMeetup` (or `P:\3dPrintMeetup`).
5. Commit root changes including the submodule pointer update.
6. Push root changes.
## Example Front Matter