[Project] Codeberg Events #31

lhinderberger commented 2023年08月24日 23:11:53 +02:00

About the project

An Event Calendar where Codeberg e.V. as well as projects hosted on Codeberg can publish their events (e.g. meetups, workshops, get-togethers).

State

Running - Looking for contributions

List the people who joined the team.

• none

Tasks

Pick one or many ...

• We need more events! :-) Feel free to contribute!
• Announcing regular meetings, including
  • publication to calendar
  • defining the agenda
  • sending reminders and inviting contributors
• Technical maintenance of the underlying static site generator

Which references are already available for the project?

• Site: Currently https://codeberg.codeberg.page/Events - we should get a proper subdomain under codeberg.org sorted out (see Codeberg/Events#9)
• Repo: https://codeberg.org/Codeberg/Events
• Upstream (for technical contributions): https://codeberg.org/lhinderberger/calendity
• Matrix-Channel: None project-specific, but the overall "Contributing to Codeberg" channel is a good place to ask: http://matrix.to/#/%23contributing-to-codeberg:kle.li

Looking for ...

• Teamleads / Maintainers (taking responsibility)
• Co-Maintainers (sharing responsibility)
• Software developers
• System administrators
• Writers
• Designers
• Public Relation / Communication experts
• Input and suggestions
• Testing and Feedback

Technical Details on the calendar setup

Codeberg Events is a statically-generated site based on the calendity project template for Eleventy.

Events are defined by creating a Markdown file that holds the event invitation plus front matter defining an event's metadata (e.g. date and duration).

The static site generator is run in the CI on push to the main branch and generates a site where events can be browsed, as well as RSS and ICS feeds, which is ultimately accessible using Codeberg Pages.

Issue thread meta

• ... discuss the project idea and give general input
• ... discuss technical details about the project
• ... commit yourself to be part of the project (becoming a maintainer etc)
• ... suggest approaches to the project (e.g. creating a repository, chat etc)

### About the project An Event Calendar where Codeberg e.V. as well as projects hosted on Codeberg can publish their events (e.g. meetups, workshops, get-togethers). ### State Running - Looking for contributions ### List the people who joined the team. - none ### Tasks Pick one or many ... - We need more events! :-) Feel free to contribute! - Announcing regular meetings, including - publication to calendar - defining the agenda - sending reminders and inviting contributors - Technical maintenance of the underlying static site generator ### Which references are already available for the project? - Site: Currently https://codeberg.codeberg.page/Events - we should get a proper subdomain under codeberg.org sorted out (see https://codeberg.org/Codeberg/Events/issues/9) - Repo: https://codeberg.org/Codeberg/Events - Upstream (for technical contributions): https://codeberg.org/lhinderberger/calendity - Matrix-Channel: None project-specific, but the overall "Contributing to Codeberg" channel is a good place to ask: http://matrix.to/#/%23contributing-to-codeberg:kle.li ### Looking for ... - [x] Teamleads / Maintainers (taking responsibility) - [ ] Co-Maintainers (sharing responsibility) - [x] Software developers - [ ] System administrators - [x] Writers - [ ] Designers - [x] Public Relation / Communication experts - [x] Input and suggestions - [x] Testing and Feedback ### Technical Details on the calendar setup Codeberg Events is a statically-generated site based on the calendity project template for Eleventy. Events are defined by creating a Markdown file that holds the event invitation plus front matter defining an event's metadata (e.g. date and duration). The static site generator is run in the CI on push to the main branch and generates a site where events can be browsed, as well as RSS and ICS feeds, which is ultimately accessible using Codeberg Pages. ### Issue thread meta - [x] ... discuss the project idea and give general input - [ ] ... discuss technical details about the project - [x] ... commit yourself to be part of the project (becoming a maintainer etc) - [x] ... suggest approaches to the project (e.g. creating a repository, chat etc)

fnetX commented 2023年12月12日 14:57:58 +01:00

I updated the issue description, because I noticed that it appeared to have a focus on technical details, although I think the main focus in this domain is people with no technical background, who would like to help to organize meetings.

The original idea about events (that didn't work out, because no one felt responsible for it long-term) was the following:

• there are bi-weekly meetings on Thursday, 20.00 CET (but searching for other times/days to include other groups is also a welcome task)
• the meetings have alternating topics (technical / non-technical). We want non-technical meetings where technical topics are kept out to encourage contributions from people who do not have a very technical background and rather want to help us with public relations, help , organizing etc etc.

If you are interested and want to learn more, please reach out in the issue tracker, via matrix, or send me an email (details in profile).

I updated the issue description, because I noticed that it appeared to have a focus on technical details, although I think the main focus in this domain is people with no technical background, who would like to help to organize meetings. The original idea about events (that didn't work out, because no one felt responsible for it long-term) was the following: - there are bi-weekly meetings on Thursday, 20.00 CET (but searching for other times/days to include other groups is also a welcome task) - the meetings have alternating topics (technical / non-technical). We want non-technical meetings where technical topics are kept out to encourage contributions from people who do not have a very technical background and rather want to help us with public relations, help , organizing etc etc. If you are interested and want to learn more, please reach out in the issue tracker, via matrix, or send me an email (details in profile).

sanecito commented 2023年12月12日 15:18:44 +01:00

Not sure of the exact duties of Co-Maintainer, but if you need someone to do things like periodically audit and PR away past events from future events list, etc. from the MD file, I can commit to assist with that. I do something similar with a FOSS project that does event tracking w/ Issues.

Not sure of the exact duties of Co-Maintainer, but if you need someone to do things like periodically audit and PR away past events from future events list, etc. from the MD file, I can commit to assist with that. I do something similar with a FOSS project that does event tracking w/ Issues.

jcolomb commented 2023年12月12日 15:31:13 +01:00

What about using mobilizon for this?

What about using mobilizon for this?