From eacdc51bff62de404046d12839bd2a90305bc51d Mon Sep 17 00:00:00 2001 From: Brendan Golden Date: Mon, 14 Apr 2025 15:12:59 +0100 Subject: [PATCH 01/29] handover: added teh Head Sysadmin to kick things off Will need more changes --- .../Handovers/Senior_System_Administrator.md | 109 ++++++++++++++++++ 1 file changed, 109 insertions(+) create mode 100644 Committee/2024-2025/Handovers/Senior_System_Administrator.md diff --git a/Committee/2024-2025/Handovers/Senior_System_Administrator.md b/Committee/2024-2025/Handovers/Senior_System_Administrator.md new file mode 100644 index 0000000..ddcdef1 --- /dev/null +++ b/Committee/2024-2025/Handovers/Senior_System_Administrator.md @@ -0,0 +1,109 @@ +## Senior System Administrator +#### Brendan Golden + +The purpose of this document is to assist the incoming Senior System Administrator for the upcoming year 2025/26. + +### Duties +- Oversee the Skynet computer cluster. + - Maintaining existing hardware. + - Sourcing new hardware. + - Improving the software. +- Promote the cluster's use +- Oversee development of Skynet. +- Oversee the Root team. +- Oversee training for junior members of the Root team. +- Oversee communications with ITD. +- Help develop server related skills in the general membership. +- Manages: + * Linux Webhost for members + * LDAP + * DNS + * [Gitlab][0] + * [Nextcloud][1] (Selfhosted Google) + * [VaultWarden][2] (password manager) + +### Guide +#### Baseline +1. Dont be a dick. +2. You are a society committee member, so you have a basic responsibility to look after society members and other committee members and make sure events are a fun and safe environment. +3. The core goal of the Skynet cluster is to provide services for the society. + * These are the more visible services like the linux host/gitlab/nextcloud/.... + * It also includes training for anyone who wants to get more hands on, both administration/hardware. + * Its not your fiefdom, everything must improve it for others, even if it takes you out of your comfort zone. + +#### Onboarding +##### New Committee +1. Ensure that each committee member has a skynet account + * If they dont then assist them through the process. +2. Add their chosen usernames to the [nixos][3] under ``committee`` +3. Run them through the process of gaining access to the password manager: [pw.skynet.ie][2] + * Separate but linked account is security feature, unavoidable. + * They will gain access to the ``Compsoc`` collection of passwords. +4. They will automatically gain access to the ``Compsoc`` folder on [nextcloud][1] + +##### Root team - Trainee +1. Ensure that each root member has a skynet account + * If they dont then assist them through the process. +2. Add their chosen usernames to the [nixos][3] under ``trainee`` +3. They will automatically gain access to the ``Skynet`` folder on [nextcloud][1] +4. Provide training + +##### Root team - Admin +1. They will already have a skynet account. +2. Add their chosen usernames to the [nixos][3] under ``admin`` +3. They will automatically gain access to the ``Skynet_Admin`` folder on [nextcloud][1] +4. Run them through the process of gaining access to the password manager: [pw.skynet.ie][2] + * Separate but linked account is security feature, unavoidable. + * They will gain access to the ``Skynet`` collection of passwords. +5. Contact ITD to get them added to the VPN. +6. Provide training + +##### Sr Sysadmin +Need to figure out this process. +My FYP next year will be primarily about this aspect. + +#### Annual Events +##### Sign up Fair +{link to event guide/write up} + +##### Renew Domains +We have two domains, both with Blacknight. +* ``skynet.ie`` is sponsored to us. +* ``ulcompsoc.ie`` we have to pay for, renew for two years but check yearly. + +##### Inform ITD that servers are up-to-date and patched +Part of the agreement with ITD is to show them every semester that the server are patched and up to date. + +#### Regular Events +##### Email +I generally check all the email accounts for new mail once a day or so. +There is a good chunk of spam but we do get a fair few mails from alumni trying to reactivate accounts. + +##### Reactivate old accounts +Alumni regularly get in contact to re-activate their skynet accounts. +Be polite and respectful when dealing with them. + +Much of this process is covered by [renew][5] and [recovery][6] however more documentation needs to be added on how to verify users. + +### Summary + +This has been mostly a managerial role, involving organisation and mentorship. +The role looks really good on a CV/LinkedIn. + +The roles that Skynet has played over the years has changed dramatically (as outlined in the [old history][7]). +One of the main draws for it was the email and cloud storage. +At one point it employed 5 admins, each in charge of their own servers. +Now in this era of DevOps each admin can do so much more while also requiring more diverse knowledge. +This change is exciting, stressful and rewarding. + +Brendan Golden. + + +[0]: https://forgejo.skynet.ie +[1]: https://nextcloud.skynet.ie +[2]: https://pw.skynet.ie +[3]: https://forgejo.skynet.ie/Skynet/nixos/src/branch/main/config/users.nix#L51 +[5]: https://renew.skynet.ie/ +[6]: https://renew.skynet.ie/recovery/ +[7]: https://2016.skynet.ie/history.html + From bab6409cff8ee19e1f6f8b718dd9f65c330d5bca Mon Sep 17 00:00:00 2001 From: Brendan Golden Date: Mon, 14 Apr 2025 15:28:57 +0100 Subject: [PATCH 02/29] budget: added baseline for the budget --- .../Budget/07._Committee_Development.md | 38 ++++ Committee/2024-2025/Budget/08._Performance.md | 14 ++ Committee/2024-2025/Budget/09._Publicity.md | 36 ++++ .../2024-2025/Budget/10._Guest_Speakers.md | 27 +++ .../2024-2025/Budget/11._Profile_Speakers.md | 54 ++++++ Committee/2024-2025/Budget/12._Events.md | 177 ++++++++++++++++++ Committee/2024-2025/Budget/13._Showcases.md | 21 +++ Committee/2024-2025/Budget/Points.md | 164 ++++++++++++++++ 8 files changed, 531 insertions(+) create mode 100644 Committee/2024-2025/Budget/07._Committee_Development.md create mode 100644 Committee/2024-2025/Budget/08._Performance.md create mode 100644 Committee/2024-2025/Budget/09._Publicity.md create mode 100644 Committee/2024-2025/Budget/10._Guest_Speakers.md create mode 100644 Committee/2024-2025/Budget/11._Profile_Speakers.md create mode 100644 Committee/2024-2025/Budget/12._Events.md create mode 100644 Committee/2024-2025/Budget/13._Showcases.md create mode 100644 Committee/2024-2025/Budget/Points.md diff --git a/Committee/2024-2025/Budget/07._Committee_Development.md b/Committee/2024-2025/Budget/07._Committee_Development.md new file mode 100644 index 0000000..7d142dc --- /dev/null +++ b/Committee/2024-2025/Budget/07._Committee_Development.md @@ -0,0 +1,38 @@ +## Committee Development + +### Large Committee +We have had twelve titled committee members and two OCM's during this Academic Year. +On top of that we had seven Advisors who are previous committee members. + +As outlined last year having Advisors is extremely important in our society due to the large amount of domain knowledge required to run both the society and the computer cluster. +Due to the type of society we are we tend to have unique events on a weekly basis, being able to draw upon the wisdom of the elders helps keeps things running smoothly. + +We have the full quota of core positions: +* President +* Secretary +* Treasurer +* Public Relations Officer (PRO) +* Health and Safety Officer + +The Skynet team has one Head Systems Administrator and two members in training. +In the next year or two it is hoped that oen of those will replace the current Head Sysadmin. + +Throughout this academic year, there were no major grievances other than the resignation of 2 committee members, our Health & Safety Officer and our Assistant PRO, we replaced the HSO in an AGM and the Assistant PRO's duties were split amongst our Events officer and the incoming HSO by mutual agreement. + +### Documentation +All handover documents have been submitted except those from our advisors, +who do not provide handover documents. All minutes have also been submitted. + +This year we are trialling a new system called [Open Governance][0] where much of the background work is made available for our members to view (including these points submissions). +It also serves as a long term archive of events, handover documents and minutes going forward. + + +### Administration +During the Academic Year, we have held a committee meeting almost every week, that usually lasts between an hour to an hour and a half. +The Secretary (and President on occasion) took down minutes for the meeting. + +For bank statements, any that we received throughout the academic year were uploaded to wolves, though we stopped getting them after semester one despite checking the post regularly. +For dealing with money, there was a delay in getting access to the bank account again, though this was rectified in the later half of semester 2 and all creditors are now paid up. + + +[0]: https://forgejo.skynet.ie/Computer_Society/open-goverance \ No newline at end of file diff --git a/Committee/2024-2025/Budget/08._Performance.md b/Committee/2024-2025/Budget/08._Performance.md new file mode 100644 index 0000000..416e059 --- /dev/null +++ b/Committee/2024-2025/Budget/08._Performance.md @@ -0,0 +1,14 @@ +## Performance +As mentioned in the committee development section, the only grievances that we +had throughout the academic year was the resignation of two of our committee +members, which we replaced through an EGM in semester 2. Other than that there +was no other grievances. + +Also as mentioned in the committee development section, there was a delay in +getting access to our online banking system but that was resolved mid-way through +semester 2 and we repaid everyone at that stage. We wrapped up the year with no +creditors outstanding in line with this. + +Throughout the academic year, the Society has had a consistent number attending +our events and interacting with our society through our Discord Server, this has +created a welcoming environment. diff --git a/Committee/2024-2025/Budget/09._Publicity.md b/Committee/2024-2025/Budget/09._Publicity.md new file mode 100644 index 0000000..437b671 --- /dev/null +++ b/Committee/2024-2025/Budget/09._Publicity.md @@ -0,0 +1,36 @@ +## Publicity +Over the course of the year, we had our 21 events listed on wolves and announced on Discord. + +We had a regular weekly activity on Wednesday. +We utilized our Discord Server and emails to inform our members of upcoming events and opportunities. +Our Discord server was our social hub of communication between members and committee. +Our Discord server has now grown to have ~300 members. + +Midway through Semester two however, we started having a regular bi-weekly Minecraft event on Saturdays. +These were announced primarily through Discord. + +We used graphic design for our posters, but were used minimally and reserved for larger announcements such as +our regular weekly activity. + +### Other Societies + +We worked with a number of Societies over the last year which has meant that when +advertising our events. They would be advertised by the other societies on their own discord +servers and instagram which we think gave both societies a boost as it meant that +people who may not have known about what we do or talked to us were given a chance +to get a taste of what our society does and talk with our members + +![Games Soc post on the Retro Pi Event](09._Publicity_02.png) + +### Posters + +Posters can be found [on our gitlab][0] + +### Event Announcements + +Event Announcements can be found [on our gitlab][1] + +![Discord announcement on software licensing](09._Publicity_01.png) + +[0]: https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2023-2024/Posters +[1]: https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2023-2024 \ No newline at end of file diff --git a/Committee/2024-2025/Budget/10._Guest_Speakers.md b/Committee/2024-2025/Budget/10._Guest_Speakers.md new file mode 100644 index 0000000..adb5e4f --- /dev/null +++ b/Committee/2024-2025/Budget/10._Guest_Speakers.md @@ -0,0 +1,27 @@ +## Guest speakers + +Our first event of the spring semester was Lightning Talks: Co-op. +The goal of this event was to bridge the gap between members returning from Co-op and those that had joined us this year. +Viewers would be able to get insights into what co-op is like, the Good, the Bad and the Ugly. +Individual presenters talked on a variety of topics. +Some talked about opportunities they were given by their company. +We had others give guidance on what was expected by the company as well as what tools and methodologies would give a leg up. +It wasn't all sunshine and roses, presenters also pointed out areas where they +and/or the companies dropped the ball as well as how they would handle them in the future. + +We had eight speakers for this event, all of which are members of LM051 currently +in 3rd year. + +* Amie Patterson +* Bayan Nezamabad +* Brendan Golden +* Milan Kovacs +* Mohammad Humayun +* Prabudda Hans + + +### Event Photos + +![Milan Kovacs & Bayan Nezamabad presenting on their time in Coop](10._Guest_Speakers_01.jpg) + +![The people listening to the lighting talks](10._Guest_Speakers_02.jpg) \ No newline at end of file diff --git a/Committee/2024-2025/Budget/11._Profile_Speakers.md b/Committee/2024-2025/Budget/11._Profile_Speakers.md new file mode 100644 index 0000000..1e1341d --- /dev/null +++ b/Committee/2024-2025/Budget/11._Profile_Speakers.md @@ -0,0 +1,54 @@ +## Profile Speakers + +This year 30 members of Computer Society attended PyCon 2023 in the Radisson Blu Royal Hotel Dublin. +PyCon is an international conference about the programming language Python. +There are several PyCon conferences run in Europe each year, with the Dublin one being one of the largest ones. +As such there is a large variety of top tier and distinguished presenters. +While it is a two-day event we were only able to attend the Saturday of it. + + +### Pablo Galindo Salgado +#### The snake of Theseus +Pablo was the keynote speaker for Saturday of this conference. +His presentation was focusing on how the language itself has changed over time, so much so that the original code has all been replaced. +Yet it is still Python. +Even with Countless contributors over the years Python has changed, yet remained the same. +Different syntax, personalities and methodologies have contributed to shaping the language to what it is today and inspiring it forwards into the future. + +![Pycon Info card on Pablo Galindo Salgado](11._Profile_Speakers_01.png) + +### Mia Bajić +#### The Standard Library TourK +Mia is a regular speaker at Python Conferences as well as co-organising the Prague PyCon in 2023. + +Her talk was aimed at enlightening attendees by informing them of the tools they did not know they needed, the unknown unknowns. +She opened up the powerful functions and methods contained within the inbuilt library to show us what we had been missing before now. +It was quite interesting seeing the emotions flash through the audience when folks realised that there were inbuilt and easier ways to handle objects and arrays. +Everyone left the lecture hall knowing far more than they entered. + +![Pycon Info card on Mia Bajić](11._Profile_Speakers_02.png) + +### Rodrigo Girão Serrão +#### How to implement a Python-like programming language +Rodrigo is an educator for mathematics and Python, particularly in the area of data processing and analysis. + +His main section in the conference was a workshop on how to create a new programming language by using Python. +This was an engaging introduction to compilers, a topic that is only covered by Computer Science in 4th year. +Within the two hours participants had constructed a small functional language and were given the tools/knowledge to work on it further. +Several of the attendees from our group have continued to work on their own language, taking inspiration from this workshop + + +![Pycon Info card on Rodrigo Girão Serrão](11._Profile_Speakers_03.png) + +### Steve Holden +#### The death of PyCon +Steve is the founder of PyCon. +He has been the Chairman and a director of the Python Foundation. + +He had the honor of opening the Lightning Talks for the conference. +Lightning Talks are 5-minute presentations where anyone can volunteer to present. + +His chosen topic was ``The Death of PyCon`` where he outlined that community run events die if all the attendees stand back and watch. +The way forward is to roll up your sleeves and pitch in, in doing so it is a far better experience for all involved. + +<> diff --git a/Committee/2024-2025/Budget/12._Events.md b/Committee/2024-2025/Budget/12._Events.md new file mode 100644 index 0000000..302f28b --- /dev/null +++ b/Committee/2024-2025/Budget/12._Events.md @@ -0,0 +1,177 @@ +## Events + +### Overview + +- We are proud that this year we had a lot of big events and a lot more engagement with our members. +- The events discussed here required a lot of planning and organisation to complete. +- The society held 21 events and meetups over the course of the academic year. +- We also held much larger events such as the trip to Pycon, and the collaboration with Games Development Society and Games Society, such as our pub quiz and RetroPi. +- We're proud that we got a new bi-weekly Minecraft event that our members enjoy. + +### Semester 1 + +#### meet_greet.exe + +- Introductory event to the society. +- Idea was to give a taste of future events and a social mixer. +- Venue: We booked KBG15 from 18:00-21:00. +- Announced via Discord and emails. + +![Meet and Greet](12._Events_01.jpg) + +![Meet and Greet2](12._Events_02.jpg) + +#### Skynet Introduction + +- Introductory event to Skynet. +- Idea was to help members with setting up their accounts. +- Venue: Room 3 to allow enough room for incoming members. +- Members were required to bring their laptops to set up their Skynet accounts. + +![Skynet](12._Events_03.jpg) + +#### Capture The Flag + +- Interactive Event: Members were asked to bring their laptops to participate in the event. +- Venue: Room 3 was booked to allow appropriate space for our participants +- Email and Discord announcements were written to advertise the event. + +#### Movie Night + +- Because it was Halloween, we decided to organise a movie night being projected. +- Venue: Room 3 was booked to allow enough room for our participants. +- We made a post on Discord and wrote an Email to advertise to our members. +- We asked our members to vote for which movie they wanted to watch on Discord. +- The movie that members picked out was Donnie Darko. +- We got permission from the office first before showing the movie. +- After we got permission to show the movie to our members, we acquired popcorn beforehand and used the microwave outside Room 3 to cook it. + +#### Pycon + +- A large event that had plenty of organisational overhead, and was a trip to Dublin. +- A number of members joined due to this event. +- Bought event tickets and tote bags. +- We applied for the trip's approval through Wolves. +- Sent emails to Pycon to get group tickets. +- Event costs were subsidized for members as a result. +- Payments were tracked through wolves and processed online. + +![PyCon](12._Events_04.jpg) + +#### Game Engines - Presentation + +- Presentation about game engines; rehearsed beforehand. +- Venue: Room 3 for participants. +- Email had been written with some humor to enhance member engagement. + +#### Advent of Code + +- Long-term running series of events, throughout December and early 2nd semester. +- Useful to giving first years more coding experience. +- 2 posters were made, and sent by emails. +- Our own leaderboard was created for our members to compete, code for it was emailed separately. +- We had an in-person as a primer to prepare members for the event. +- Coding challenges released with Advent of Code and members were given the chance to solve them. +- Separate forum topic was created on Discord for this purpose, members received help with the programming challenges. + +### Semester 2 + +#### Lightning Talks - Co-op + +- Lightning talks from students who were returning from Co-op. +- Each talk was set to a maximum of five minutes. +- Goal was to have a relaxing social event to promote networking. +- Venue: Room 3, we had plenty of members and speakers coming in. +- We had pizza at the end to cap it off. +- We announced it via emails and a Discord announcement. + +![Lightning talks 1](10._Guest_Speakers_01.jpg) + +![Lightning talks 2](10._Guest_Speakers_02.jpg) + +#### Film Night + +- An event proposed by a member. +- The movie in question was an hour-long video about Randy Pausch's last lecture on achieving your dreams. +- Venue: Room 3 to allow enough room and chairs for members. +- We purchased popcorn beforehand and cooked it in the microwave outside Room 3. +- We advertised it via emails and Discord announcements. + +#### Minecraft LAN + +- This event occurred right after an EGM so plenty of members had arrived. +- Firstly we had a brief presentation on how to install a mod for voice chat in Minecraft, then helped people to join the server. +- Members were required to have a Minecraft account and a Minecraft Launcher installed. +- Members also required a Discord account in the CompSoc server. +- Members also had to link their Discord account to their ULWolves email to access our Minecraft Server. +- We ordered some pizza as well to cap off the event. +- Venue: Courtyard Room, we swapped with Music Soc for the rest of the semester as it suited us more due to it having more plugs than Room 3. + +#### Quiz with Games Dev + +- Another large event that required a large amount of planning overhead as it was part of a collab with Games Dev and us. +- This was a pub quiz that we hosted together with Games Dev. +- Venue: The Pavilion, it was large enough to accommodate our all the members who attended. +- Money for the quiz participants was collected via a mix of Cash and Revolut for those who didn't have cash. +- As a result of choosing The Pavilion, we managed to get free food for our participants. +- As part of collabing with Games Dev, we created the questions for the quiz as a group. +- We also bought prizes for 1st, 2nd, and 3rd place. +- We put out multiple posters from both CompSoc and Games Dev to advertise the event across campus. + + +![Pub Quiz 1](12._Events_05.jpg) + +![Pub Quiz 2](12._Events_06.jpg) + +#### Licenses Presentation + +- A social event about a presentation on Licences. +- Venue: Courtyard Room, we used the TV in the room to help with presenting. +- Our members came out learning more about software licences after the presentation. +- We advertised this via Discord announcements and Email. + +#### Minecraft Server Event + +- Our first event on our Minecraft Server. +- We advertised this event via Discord announcements. +- In this event we determined the winners by who collected the most valuable materials. +- A fun event that a lot of people looked forward to, and the next ones after. +- This event was online since most people were at home, and it was easier for people to join. + +#### Domain + Hosting + +- A social event that was a presentation about Domains and Hosting websites. +- Venue: Courtyard Room, TV came in handy for presenting. +- Our members came out learning a lot about domains and hosting their own websites. +- Advertised by our Discord announcements and emails as per usual. + +#### Treasure Hunt + +- Our next Recurring Minecraft event. +- This time it was a treasure hunt where people went looking for chests with items in our Minecraft Server. +- The event was chaotic as per the nature of Minecraft, and a lot of members came out enjoying the event. +- This event was online again, due to people being at home. +- We advertised the event using Discord announcements. + +#### Virtual Machines + +- A social event that was a presentation about virtual machines, what they are and how do we use them. +- Venue: Courtyard Room, accommodated all of our members, we used the plugs and TV to help with presenting. +- We advertised this event via Discord announcements and emails. +- Our members enjoyed the event and came out learning a lot more about virtual machines. + +#### RetroPi + +- Another large event that had a lot of planning overhead, as this was a massive collab between Games Dev and GSoc and us. +- Games Dev was behind the games we were planning to use. +- GSoc gave us the Controllers to play the games with. +- We were behind getting the hardware, the Raspberry PIs and getting them to work. +- Venue: Courtyard Room, we had plenty of plugs and chairs there to use. We also used the TV to display the games we were playing. +- We advertised this event via Discord announcements and Emails. + + +![RetroPi 1](12._Events_07.jpg) + +![RetroPi 2](12._Events_08.jpg) + +![RetroPi 3](12._Events_09.jpg) \ No newline at end of file diff --git a/Committee/2024-2025/Budget/13._Showcases.md b/Committee/2024-2025/Budget/13._Showcases.md new file mode 100644 index 0000000..35be5e1 --- /dev/null +++ b/Committee/2024-2025/Budget/13._Showcases.md @@ -0,0 +1,21 @@ +## Showcases + +### PyCon Ireland 2023 Trip + +For proof of trip attendance please see <> + +This was a trip made by UL Computer Society to PyCon Ireland 2023, hosted in the Radisson Blu Hotel in Dublin on November 11th-November 12th, 2023. +This section will cover the organization of the trip. + +Since we had to find transportation for this trip, preparation for this event took a lot of organization. +We needed to find transport for all Computer Society members that wanted to attend the event from Limerick to Dublin and back to Limerick without being late for the event in addition to getting tickets for our members, the cost of which was subsidized by the Society itself. +We were able to coordinate the committee towards surveying our members to find those that were interested in attending the conference, finding and paying for transportation to and from Limerick to Dublin, and negotiating bulk ticket purchasing deals with the staff at PyCon Ireland. +Once we had the numbers regarding who were planning on attending, we booked the tickets for the events and the buses from Limerick to Dublin and back. +Things went smoothly, and we were able to adhere to our initial itinerary. +The return journey also went smoothly. + +### RetroPi + +In Semester 2 of this year we ran a RetroPi presentation event in which our Society collaborated with UL Games Development Society and Games Society to present RetroPi, a system that uses Raspberry Pis to play retro games. +We made an interactive presentation where we showed off what the Raspberry Pi is capable of, and demonstrated how it can be used to play retro arcade games. +It also offered our members a hands-on demonstration of how Raspberry Pis work and how we can run programs on it. diff --git a/Committee/2024-2025/Budget/Points.md b/Committee/2024-2025/Budget/Points.md new file mode 100644 index 0000000..8a79f12 --- /dev/null +++ b/Committee/2024-2025/Budget/Points.md @@ -0,0 +1,164 @@ +## Points for Budget +This file is to organise the written part of the [points][0] for the budget. + +Current (and previous) submissions + +* [2023][1] +* [2024][0] +* [2025][7] + +Any extra PDF's can be found [here][6] + + +[6]: https://forgejo.skynet.ie/Computer_Society/open-goverance/releases +[1]: https://cp.ulwolves.ie/budget/points/2022 +[0]: https://cp.ulwolves.ie/budget/points/2023 +[7]: https://cp.ulwolves.ie/budget/points/2024 + +### 7. Committee Development +#### Instructions + +> * 5 Points - Based on Computer Society having a minimum of 5 core committee members: Chairperson, Secretary, Treasurer, PRO, and Health & Safety Officer (this will be checked online so be sure that your Committee details are up-to-date) +> Societies are deemed to be low risk and therefore they can double up their H&S officer responsibilities with another core committee members, i.e. they must have a minimum of 4 core committee members +> * 2 Points - For uploading good quality handover documents to the HANDOVER DOCUMENTS page (each core committee person must submit their own handover document, 1 per position) +> * 2 Points - For uploading all committee meeting minutes for the past academic year to the COMMITTEE MINUTES page +> * 3 Points - For evidence of managing your Financial affairs (for Bank Statements use the BANK BALANCES page) +> * 1 Point - For providing information to the C&S Office if required or asked to do so throughout the Academic Year + +#### Notes +* For most committee this relates to handovers. +* Handovers PDFs can be found [browse/download][3] +* Minutes PDFs can be found [browse]/download[5] +* See [Last years section][1] for guidelines + +[3]: https://forgejo.skynet.ie/Computer_Society/open-goverance/releases/tag/handovers_latest +[5]: https://forgejo.skynet.ie/Computer_Society/open-goverance/releases/tag/minutes_latest + +#### Details +See [the separate file](07._Committee_Development.md) for the full details. + +### 8. Performance +#### Instructions + +> * 2 Points - If Computer Society have no creditors outstanding (any outstanding debts have been cleared prior to budget submission) +> * 3 Points - If Computer Society has had no grievances throughout the year (if you have had a grievance and have dealt with it in a a good and fair manner the office will deliberate on points to be awarded) +> * 4 Points - Overall and General Track Record of Computer Society +> * 3 Points - Attendance at Council over a 3 year period as a percentage of total meetings (assessed based on sign-in records) + + +#### Notes +* This is mostly for Treasurer to ensure no outstanding debts. +* Aside from this it relates to our actions over the past year/3 years +* See [Last years section][1] for guidelines + +#### Details +See [the separate file](08._Performance.md) for the full details. + + +### 9. Publicity +#### Instructions + +> * 5 Points - Collective Platform: Regular updates on ulwolves.ie ([NEWS][news] / [EVENTS][events] / [ACTIVITIES][activities] / [FIXTURES][fixtures] - these must have been entered at the time and can't be backdated) +> * 4 Points - Computer Society Individual Publicity (Computer Society's own social media, text groups, email groups, posters) +> * 2 Points - Internal UL Media +> * 2 Points - External to UL Media +> +> Evidence of all must be attached + +[news]: https://cp.ulwolves.ie/manage/news +[events]: https://cp.ulwolves.ie/manage/events +[activities]: https://cp.ulwolves.ie/manage/activities +[fixtures]: https://cp.ulwolves.ie/manage/fixtures + +#### Notes +* This is for PRO's. +* Its an important reason to add the event on time to Wolves on a weekly basis. +* Have links to posters (can link to this repo by using ``https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2024-2025`` as a base), +* Photos of emails/discord. +* See [Last years section][1] for guidelines + +#### Details +See [the separate file](09._Publicity.md) for the full details. + +### 10. Guest Speakers + +#### Instructions +> Any speaker such as local councillors, local activists that do not satisfy the criteria of a profile speaker +> +> This speaker must be respected either inside or outside their field of expertise +> +> Computer Society must provide a biography of the speaker detailing their achievements to date and explaining why they are a profile speaker +> * Politicians/Journalists with a national and/or international profile +> * TV/Showbiz personality +> * Accredited Academic - within UL and/or are considered one of the most eminent experts within their field +> * High Profile Industry/field of speciality + +#### Notes +* See [Last years section][1] for guidelines + +#### Details +See [the separate file](10._Guest_Speakers.md) for teh full details. + + +### 11. Profile Speakers +#### Instructions +> This speaker must be respected either inside or outside their field of expertise +> +> Computer Society must provide a biography of the speaker detailing their achievements to date and explaining why they are a profile speaker +> +> * Politicians/Journalists with a national and/or international profile +> * TV/Showbiz personality +> * Accredited Academic - within UL and/or are considered one of the most eminent experts within their field +> * High Profile Industry/field of speciality +> +> Any other speaker such as local councillors, local activists that do not satisfy the above would be regarded as ordinary speakers + + +#### Notes +* We can use SISTEM/PyCon for this +* See [Last years section][1] for guidelines + +#### Details +See [the separate file](11._Profile_Speakers.md) for teh full details. + +### 12. Events +#### Instructions +> Computer Society events are those that involve a level of organisation above a normal weekly meeting/training/class session +> +> An event involves at least two of more of the following logistics: organising a venue, speaker, accommodation, reception, transport, special advertising, special pre-training, entry fee, etc + + +#### Notes +* See [Last years section][1] for guidelines + +#### Details +See [the separate file](12._Events.md) for the full details. + + +### 13. Showcases +#### Instructions + +> A Showcase Event is assessed to be "SHOWCASE" if it will bring with it an increased workload and planning beyond the normal levels of the Society +> +> If the event has been held before, the effort involved shall be on par or greater than the previous attempt +> +> * Pre-Planning – possible Computer Society sub committee +> * Higher associated costs +> * Successful Sponsorship +> * Attempt to involve the broader campus community beyond their own membership and/or external involvement via wider community or other third level institutes +> * Visible Profile on campus including a media profile +> * Prestigious speakers-politicians and personalities +> * Campus Based event + + +#### Notes +* We can use the joint Computer/GamesDev/Games event for this ([event details][2]) ([Wolves][2_wolves]) +* See [Last years section][1] for guidelines + + +[2_wolves]: https://cp.ulwolves.ie/manage/events/16998 +[2]: Insert Birthday Event here from https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2024-2025 + + +#### Details +See [the separate file](13._Showcases.md) for the full details. From fe068ee5f43e8f95e8f6503cbca6f1a013b930fa Mon Sep 17 00:00:00 2001 From: Eoghan Conlon Date: Tue, 25 Feb 2025 13:13:31 +0000 Subject: [PATCH 03/29] Treasurer handover copied from last year with information from bank account handover Signed-off-by: Eoghan Conlon --- Committee/2024-2025/Handovers/Treasurer.md | 117 +++++++++++++++++++++ 1 file changed, 117 insertions(+) create mode 100644 Committee/2024-2025/Handovers/Treasurer.md diff --git a/Committee/2024-2025/Handovers/Treasurer.md b/Committee/2024-2025/Handovers/Treasurer.md new file mode 100644 index 0000000..d7bc794 --- /dev/null +++ b/Committee/2024-2025/Handovers/Treasurer.md @@ -0,0 +1,117 @@ +## Treasurer +#### Eoghan Conlon + +The purpose of this document is to assist the incoming Treasurer for the AY2024/25 +### Duties +The main duty of the treasurer of UL Computer Society is to manage the finances of the society, so that the society can +grow. This may involve the following tasks: +* Transferring the **bank mandate** and online banking details with Bank of Ireland (BoI). +* Planning income and expenditure for this year (income / (expenditure + projections) = **1 + 2 ratio**) +* Requesting capitations after large purchases +* Ensuring we use our capitations +* Projecting expenditure for next year +* Uploading all receipts and bank statements to UL Wolves website +* Ensuring our budget points stay intact +* Issuing invoices e.g. for the C&S Fair +* Ensuring we receive sponsorships where relevant +* Collecting money from members (event fees, memberships) +* Lodging in cash to Bank of Ireland branch (beside Spar by the Flagpoles) +* Collecting the post +* Keeping the bank documents in order +* Planning the budget part of the trip and making a projection early, if you are planning one +* Doing the annual budget before the deadline in May. +* Attend the yearly treasurer's workshops +* Attend some C&S Council meetings + +### Guide +As Treasurer, you are in charge of the society's finances. You need to make sure the committee makes good financial +decisions. Sometimes this means telling them to save money, other times you have to encourage them to spend it. It's +important to use the capitation funding for activities that benefit the society so that we can get enough funding in the +future. + +I mentioned in duties that you are to attend the yearly treasurer's workshops, these dates will be communicated with +committees some time in advance of the workshops. I would advise you to attend, but it is possible that if you are on work +placement and are unable to attend the workshop yourself to ask another committee member to attend in your stead. + +All receipts must state paid, or be obvious that it is paid, examples of this are: +* Invoices that state that there is no balance remaining, or mark that they have been paid in some way shape or form +* Receipts from shops that either state card payment or cash payment +* Electronic bus tickets if required for a trip. + +On receipts, get them uploaded to the Nextclod drive in the with the name format ``YYYYMM-{Event}-{Person}.{extension}`` +and upload them to wolves on a regular basis as they may be worth budget points (8 total, 4 per semester, 2 per quarter). +Unfortunately budgets only get released around week 3 or 4 as capitation available is based on attendance at the admin +seminars in weeks 1 and 2 of each semester. + +Mentioning the admin seminars above, as a core committee position, you, along with the other core positions, (President, +Secretary, PRO & HSO) must make up one of the 2 attendees at C&S Council, so if it is possible for you to attend some of +them please do so, the other attendee just has to be a committee member. + +After the AGM, you have to begin the process of getting the change of admins on the Bank Account, these are at least the +President and you, sometimes we have the secretary, though it is possible for another core committee position to take the +place of either the President or secretary as signatory if required. There is more information in regard to this on Nextcloud +due to the nature of the information. + +It is also your responsibility to invoice C&S for the networking services that we provide at the C&S fairs each semester, +we are to bill them €2500 after the second semester one, there are more details available on the document on Nextcloud +where I go into specifics on it. The template for the invoice will be on Nextcloud too. + +We need to remember to keep arround €2000 in the bank account as a float for purchases. This money must be replaced every +year. + +When making large purchases, it must be added to the 3-year plan. Purchases are made first by a committee member and then +they are paid back, generally by Electronic Funds Transfer to the committee member. + +There are 2 types of events where we would be accepting payments, trips and fundraisers. For trips, I would advise that +we use the Stripe payment facility available through the event on UL wolves, while there is a charge applied to this by +Stripe, it makes things easier on our end as we don't have to keep track on who had paid and who hasn't paid. As for the +fundraising events, we can accept cash or electronic payments. Cash is simple enough, you take the **lockable** lock box. +For electronic payments, I would advise the incoming committee to get one of the Sum up or Square card readers to process +card transactions, while there may be fees involved in this, it is one less job for you to get the money into the account +this way then the alternative of taking payments over Revolut. + +If you are in doubt about anything, ping Eoghan (eoghanconlon73), or the advisors role on Discord for help. + +#### Banking +##### Bank Mandate +{Information on bank mandate} + +##### Business online +###### Admin +For this, you need to fill in a form at https://businessbanking.bankofireland.com/payments-and-cards/online-banking/business-online/update-your-details/ to change your administrator details. For this, we need some information, listed below. + +| | | +|-----------------------------------|-------------------------------------------------------------| +| Business Online Customer Number | Contact previous committee for this information when needed | +| Company Name | UL Computer Society | +| Jurisdiction | ROI | +| Company Entity Type | Unincorporated Organisation | +| Update your Administrator details | Updating Admin 1 or 2 and their contact details | +| Account Holder Authorisation | Contact details for 2 of the account signatories | + +Once that form is filled in the request will be processed, then everyone will be sent on forms to sign to authorise the change. Once those forms have been completed, you will get an email saying that you can call to get the admin's temporary passwords. When you call, you will need the information in the table below. + +* Business online Customer Number +* Company Name + * UL Computer Society +* Last 4 digits of the account number +* Phone number + * Specific per year, should be Admin 1's number. +* Date of birth +* Middle name + * If applicable +* Mother's Maiden Name +* 2 Usernames + * ULCOM002 (Admin Username) + * 1 of the previous user's usernames +* Daily Control Limit + + +###### Users +Once the Admin account has been signed in, you can set up the user accounts for those that will be using the account, usually the President, Secretary & Treasurer, the account signatories. + +### Summary +The Treasurer is one of the most important roles on committee, it helps with the running of the Society. Make sure that +you keep the receipts up to date, and plan the income and expenditure, and always remember to project all the funds that +we have available. Also remember that filling in the Budget is a team effort, get help with it. Most importantly enjoy +your time on committee. Best of luck for the upcoming academic year! \ No newline at end of file From 463916c7cb1ad07e8449799ca007c03d7f9c0cc0 Mon Sep 17 00:00:00 2001 From: Eoghan Conlon Date: Thu, 1 May 2025 17:24:00 +0100 Subject: [PATCH 04/29] Removing admin username from handover, will put it in doc in treasurer folder Signed-off-by: Eoghan Conlon --- Committee/2024-2025/Handovers/Treasurer.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Committee/2024-2025/Handovers/Treasurer.md b/Committee/2024-2025/Handovers/Treasurer.md index d7bc794..fa9a40c 100644 --- a/Committee/2024-2025/Handovers/Treasurer.md +++ b/Committee/2024-2025/Handovers/Treasurer.md @@ -101,8 +101,8 @@ Once that form is filled in the request will be processed, then everyone will be * Middle name * If applicable * Mother's Maiden Name -* 2 Usernames - * ULCOM002 (Admin Username) +* 2 Usernames (which can be gotten from the previous committee) + * Admin Username * 1 of the previous user's usernames * Daily Control Limit From 5d5acfef77507b1a9ad4d609f2f8ab2e71c827d2 Mon Sep 17 00:00:00 2001 From: Eoghan Conlon Date: Thu, 1 May 2025 17:24:55 +0100 Subject: [PATCH 05/29] Adding section on Bank transfers and cut-off times Signed-off-by: Eoghan Conlon --- Committee/2024-2025/Handovers/Treasurer.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Committee/2024-2025/Handovers/Treasurer.md b/Committee/2024-2025/Handovers/Treasurer.md index fa9a40c..9bc052a 100644 --- a/Committee/2024-2025/Handovers/Treasurer.md +++ b/Committee/2024-2025/Handovers/Treasurer.md @@ -106,6 +106,16 @@ Once that form is filled in the request will be processed, then everyone will be * 1 of the previous user's usernames * Daily Control Limit +##### Bank Transfers +Bank transfers are the main way that we have of reimbursing committee members for purchasing things for the Society, there +are cut-off times for this, where the most up to date version can be seen [here](https://businessbanking.bankofireland.com/payments-and-cards/online-banking/business-online/payment-cut-off-times/). +I have also included the relevant cut-off times as of the time of writing (1/5/2025) below. + +| Payment | Cycle | Cut-off time | +|------------------------------------|----------|--------------| +| SEPA Payments (to Bank of Ireland) | Same Day | 5.00pm | +| SEPA Payments (to Irish Accounts) | Next Day | 5.00pm | +| SEPA Payments (to EU Zone) | Next Day | 5.00pm | ###### Users Once the Admin account has been signed in, you can set up the user accounts for those that will be using the account, usually the President, Secretary & Treasurer, the account signatories. From 24c8ea07805131540531a24e2ebca1e392b569f6 Mon Sep 17 00:00:00 2001 From: Nanda Date: Tue, 6 May 2025 13:50:56 +0100 Subject: [PATCH 06/29] update events documentation: Finished first part of events.md --- Committee/2024-2025/Budget/12._Events.md | 247 ++++++++++-------- .../Budget/Pictures/12._Events_01.png | 3 + .../Budget/Pictures/12._Events_02.png | 3 + .../Budget/Pictures/12._Events_03.png | 3 + .../Budget/Pictures/12._Events_04.png | 3 + .../Budget/Pictures/12._Events_05.png | 3 + .../Budget/Pictures/12._Events_06.png | 3 + .../Budget/Pictures/12._Events_07.png | 3 + .../Budget/Pictures/12._Events_08.jpeg | 3 + .../Budget/Pictures/12._Events_09.png | 3 + .../Budget/Pictures/12._Events_10.png | 3 + Events/2024-2025/Semester-1_Week-03.md | 33 +++ 12 files changed, 202 insertions(+), 108 deletions(-) create mode 100644 Committee/2024-2025/Budget/Pictures/12._Events_01.png create mode 100644 Committee/2024-2025/Budget/Pictures/12._Events_02.png create mode 100644 Committee/2024-2025/Budget/Pictures/12._Events_03.png create mode 100644 Committee/2024-2025/Budget/Pictures/12._Events_04.png create mode 100644 Committee/2024-2025/Budget/Pictures/12._Events_05.png create mode 100644 Committee/2024-2025/Budget/Pictures/12._Events_06.png create mode 100644 Committee/2024-2025/Budget/Pictures/12._Events_07.png create mode 100644 Committee/2024-2025/Budget/Pictures/12._Events_08.jpeg create mode 100644 Committee/2024-2025/Budget/Pictures/12._Events_09.png create mode 100644 Committee/2024-2025/Budget/Pictures/12._Events_10.png diff --git a/Committee/2024-2025/Budget/12._Events.md b/Committee/2024-2025/Budget/12._Events.md index 302f28b..a259ae0 100644 --- a/Committee/2024-2025/Budget/12._Events.md +++ b/Committee/2024-2025/Budget/12._Events.md @@ -3,175 +3,206 @@ ### Overview - We are proud that this year we had a lot of big events and a lot more engagement with our members. -- The events discussed here required a lot of planning and organisation to complete. +- The events discussed here required a lot of planning and organization to complete. - The society held 21 events and meetups over the course of the academic year. -- We also held much larger events such as the trip to Pycon, and the collaboration with Games Development Society and Games Society, such as our pub quiz and RetroPi. -- We're proud that we got a new bi-weekly Minecraft event that our members enjoy. +- We also held much larger events such as the trip to Pycon, and the Berlin trip. +- We're proud that we were able to host regular weekly events. ### Semester 1 -#### meet_greet.exe +#### Society Introduction - Introductory event to the society. - Idea was to give a taste of future events and a social mixer. -- Venue: We booked KBG15 from 18:00-21:00. +- Venue: We booked Courtyard Room from 18:00-20:30. - Announced via Discord and emails. -![Meet and Greet](12._Events_01.jpg) -![Meet and Greet2](12._Events_02.jpg) +#### Skynet + Git Introduction -#### Skynet Introduction - -- Introductory event to Skynet. -- Idea was to help members with setting up their accounts. -- Venue: Room 3 to allow enough room for incoming members. +- Introductory event to Skynet & Git. +- Idea was to help members with setting up their accounts and understanding Git. +- Venue: Courtyard Room to give enough free space for committee members to run around offering tech support. - Members were required to bring their laptops to set up their Skynet accounts. +- Email and Discord announcements were written to advertise the event. -![Skynet](12._Events_03.jpg) +#### Virtual Machines! + +- Introducing members to Virtual Machines and Docker. +- Venue: Courtyard Room was booked since it was easier to do presentations there. +- Included an optional interactive element where members could follow along on their laptops. +- Email and Discord announcements were written to advertise the event. + +![Virtual Machines](Pictures/12._Events_01.png) + +#### Unity Workshop: A Collaboration with Games Development Society + +- Collab with Game Dev Society. +- Venue: Courtyard Room was picked since it was large enough to accommodate all the members. +- We made a post on Discord and wrote an Email to advertise to our members. +- Members were required to bring their laptops with Unity & Visual Studio Code pre-installed. + +![Unity Workshop](Pictures/12._Events_02.png) + +#### Server Building + +- Collab with NetApp. +- Recieved 700€ in sponsorship from NetApp. +- Assembled the servers during the event. +- Also had a NetApp representative provide a talk about their company & graduate role opportunities. +- NetApp also sponsored finger food from Scholars for the event. +- Venue: Courtyard Room +- Announcements sent out via discord and email. + +![Server Building w/ NetApp](Pictures/12._Events_03.png) + +#### Halloween Movie Night! + +- Yearly social event to watch a movie on Halloween. +- Movie was selected between the committee this time +- We decided to show Corpse Bride. +- We made sure to get permission from the office first before showing the movie. +- Venue: Room 3 since it was better suited for movies. +- Announcements sent out via discord and email. + +![Halloween Movie Night](Pictures/12._Events_04.png) #### Capture The Flag +- Yearly event to teach members about using the terminal and SSH. - Interactive Event: Members were asked to bring their laptops to participate in the event. -- Venue: Room 3 was booked to allow appropriate space for our participants +- Venue: Courtyard Room - Email and Discord announcements were written to advertise the event. -#### Movie Night +![Capture The Flag](Pictures/12._Events_05.png) -- Because it was Halloween, we decided to organise a movie night being projected. -- Venue: Room 3 was booked to allow enough room for our participants. -- We made a post on Discord and wrote an Email to advertise to our members. -- We asked our members to vote for which movie they wanted to watch on Discord. -- The movie that members picked out was Donnie Darko. -- We got permission from the office first before showing the movie. -- After we got permission to show the movie to our members, we acquired popcorn beforehand and used the microwave outside Room 3 to cook it. +#### PyCon Refresher -#### Pycon +- Refresher on Python, so people don't show up to PyCon without knowing what Python is. +- Venue: Courtyard Room +- We used the TV in the room to help with presenting. +- Announcements sent out via discord + email. -- A large event that had plenty of organisational overhead, and was a trip to Dublin. -- A number of members joined due to this event. -- Bought event tickets and tote bags. -- We applied for the trip's approval through Wolves. -- Sent emails to Pycon to get group tickets. -- Event costs were subsidized for members as a result. -- Payments were tracked through wolves and processed online. +#### PyCon -![PyCon](12._Events_04.jpg) +- A large event that had plenty of organizational overhead and was a trip to Dublin. +- Yearly event, we had a number of members join due to this event. +- Bought event tickets and tote bags along with arranging transport. +- Got trip approval through Wolves. +- Subsidized event costs for members. +- Payments tracked through Wolves and processed online. +- Venue: Radisson Blu Royal Hotel, Dublin. -#### Game Engines - Presentation +![PyCon](Pictures/12._Events_06.png) -- Presentation about game engines; rehearsed beforehand. -- Venue: Room 3 for participants. -- Email had been written with some humor to enhance member engagement. +#### Advent of Code Primer -#### Advent of Code - -- Long-term running series of events, throughout December and early 2nd semester. +- Long-term running series of events every year, throughout December and early 2nd semester. - Useful to giving first years more coding experience. -- 2 posters were made, and sent by emails. -- Our own leaderboard was created for our members to compete, code for it was emailed separately. -- We had an in-person as a primer to prepare members for the event. +- We had an in-person primer to prepare members for the event. - Coding challenges released with Advent of Code and members were given the chance to solve them. - Separate forum topic was created on Discord for this purpose, members received help with the programming challenges. +- Announcements for the primer were done via email and Discord. +- Venue: Courtyard Room + +![Advent Of Code Primer](Pictures/12._Events_07.png) ### Semester 2 #### Lightning Talks - Co-op - Lightning talks from students who were returning from Co-op. -- Each talk was set to a maximum of five minutes. +- No time limit was set for this event, people were free to talk as much as they wanted - Goal was to have a relaxing social event to promote networking. -- Venue: Room 3, we had plenty of members and speakers coming in. +- Venue: Courtyard Room since it was easier to give talks. - We had pizza at the end to cap it off. - We announced it via emails and a Discord announcement. -![Lightning talks 1](10._Guest_Speakers_01.jpg) +#### Intro to Skynet, Discord & Minecraft -![Lightning talks 2](10._Guest_Speakers_02.jpg) - -#### Film Night - -- An event proposed by a member. -- The movie in question was an hour-long video about Randy Pausch's last lecture on achieving your dreams. -- Venue: Room 3 to allow enough room and chairs for members. -- We purchased popcorn beforehand and cooked it in the microwave outside Room 3. +- Introductory event to Skynet, Discord and Minecraft. +- Lined up with a project that most first years had regarding creating a blog site. +- To this end, we tailored the event to help users set up their Skynet accounts and access their personal sites. +- We also introduced them to Discord and Minecraft. +- Especially, how to access our Minecraft server. +- Venue: Courtyard Room. - We advertised it via emails and Discord announcements. -#### Minecraft LAN +#### Patch Presentation -- This event occurred right after an EGM so plenty of members had arrived. -- Firstly we had a brief presentation on how to install a mod for voice chat in Minecraft, then helped people to join the server. -- Members were required to have a Minecraft account and a Minecraft Launcher installed. -- Members also required a Discord account in the CompSoc server. -- Members also had to link their Discord account to their ULWolves email to access our Minecraft Server. -- We ordered some pizza as well to cap off the event. -- Venue: Courtyard Room, we swapped with Music Soc for the rest of the semester as it suited us more due to it having more plugs than Room 3. +- Sponsored event by Patch. +- They came in to provide an info session on their startup accelerator and other programs. +- Brought in other students who had also gone through the program. +- Sponsored Pizza for the event. +- Venue: Courtyard Room +- Announcements sent out via discord and email. -#### Quiz with Games Dev +![Patch Workshop](Pictures/12._Events_08.jpeg) -- Another large event that required a large amount of planning overhead as it was part of a collab with Games Dev and us. -- This was a pub quiz that we hosted together with Games Dev. -- Venue: The Pavilion, it was large enough to accommodate our all the members who attended. -- Money for the quiz participants was collected via a mix of Cash and Revolut for those who didn't have cash. -- As a result of choosing The Pavilion, we managed to get free food for our participants. -- As part of collabing with Games Dev, we created the questions for the quiz as a group. -- We also bought prizes for 1st, 2nd, and 3rd place. -- We put out multiple posters from both CompSoc and Games Dev to advertise the event across campus. +#### Computer Concepts Through Factory Games +- Social event that involved expressing computer concepts like abstraction and interfaces through factory games. +- Presentation by a committee member. +- Venue: Courtyard Room +- Announcements sent out via discord and email. -![Pub Quiz 1](12._Events_05.jpg) +#### Capture The Flag -![Pub Quiz 2](12._Events_06.jpg) - -#### Licenses Presentation - -- A social event about a presentation on Licences. -- Venue: Courtyard Room, we used the TV in the room to help with presenting. -- Our members came out learning more about software licences after the presentation. +- Repeat event from semester 1. +- Interactive event: Members were asked to bring their laptops to participate in the event. +- The point of the event was to teach members about using the terminal and SSH. +- Venue: Courtyard Room - We advertised this via Discord announcements and Email. -#### Minecraft Server Event +#### Movie Night! -- Our first event on our Minecraft Server. -- We advertised this event via Discord announcements. -- In this event we determined the winners by who collected the most valuable materials. -- A fun event that a lot of people looked forward to, and the next ones after. -- This event was online since most people were at home, and it was easier for people to join. +- Collaboration with Out in UL. +- Similar to the Halloween Movie Night, movie was decided between Committees. +- We decided to show The Imitation Game. +- Received permission from the office. +- Also brought cookies. +- Event advertised through Discord announcements and emails. +- Venue: Courtyard Room, we used the TV in the room to show the movie. -#### Domain + Hosting +#### Alumni Meet && Greet -- A social event that was a presentation about Domains and Hosting websites. +- A social event right after a EGM +- We invited graduates to come in and meet with our members. +- They gave presentations on what they have done during their time at work, and how life outside UL is like. - Venue: Courtyard Room, TV came in handy for presenting. -- Our members came out learning a lot about domains and hosting their own websites. - Advertised by our Discord announcements and emails as per usual. -#### Treasure Hunt +#### Fistful of Frags LAN Party -- Our next Recurring Minecraft event. -- This time it was a treasure hunt where people went looking for chests with items in our Minecraft Server. -- The event was chaotic as per the nature of Minecraft, and a lot of members came out enjoying the event. -- This event was online again, due to people being at home. +- Lightweight event to prepare for SISTEM on Saturday. +- Chose a free source-based game, Fistful of Frags, to play. +- Members were required to bring laptops. +- Venue: Courtyard Room - We advertised the event using Discord announcements. -#### Virtual Machines +#### SISTEM -- A social event that was a presentation about virtual machines, what they are and how do we use them. -- Venue: Courtyard Room, accommodated all of our members, we used the plugs and TV to help with presenting. -- We advertised this event via Discord announcements and emails. -- Our members enjoyed the event and came out learning a lot more about virtual machines. +- Student Inter-Society Technology and Enterprise Meetup. +- Yearly event that happens all across Ireland +- This year, we at UL CompSoc were chosen to host it. +- Organized by students for students, largest of its kind. +- It Involved collaboration from multiple universities, all the way from DCU to UCC. +- Included speakers from LERO & Industry, like Google +- Ticket costs 12€ for normal attendees, but only cost 5€ for UL CompSoc members when applying through us. +- Hit the record for most pizzas for any event in UL, 50 pizzas ordered. +- Announcements sent out via email, discord, and through other societies + instagram. +- Venue: KBG15, to accommodate the large number of people attending. +- Refreshments and snacks were also provided. -#### RetroPi +![SISTEM](Pictures/12._Events_09.png) +![!SISTEM](Pictures/12._Events_10.png) -- Another large event that had a lot of planning overhead, as this was a massive collab between Games Dev and GSoc and us. -- Games Dev was behind the games we were planning to use. -- GSoc gave us the Controllers to play the games with. -- We were behind getting the hardware, the Raspberry PIs and getting them to work. -- Venue: Courtyard Room, we had plenty of plugs and chairs there to use. We also used the TV to display the games we were playing. -- We advertised this event via Discord announcements and Emails. +#### Lan Party +- Polled members for a game to play, TF2 was chosen. +- Setup a custom TF2 server on Skynet for the event. +- Members were required to bring their laptops with TF2 pre-installed. +- Venue: Courtyard Room +- We advertised the event using Discord announcements and emails. +- We also bought spar chips for the events -![RetroPi 1](12._Events_07.jpg) - -![RetroPi 2](12._Events_08.jpg) - -![RetroPi 3](12._Events_09.jpg) \ No newline at end of file diff --git a/Committee/2024-2025/Budget/Pictures/12._Events_01.png b/Committee/2024-2025/Budget/Pictures/12._Events_01.png new file mode 100644 index 0000000..2d7a934 --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/12._Events_01.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bdc3a96e7c19336a8ae61cac4ef60126b78043563ee1f37ca1b23e32eb5e148 +size 2859747 diff --git a/Committee/2024-2025/Budget/Pictures/12._Events_02.png b/Committee/2024-2025/Budget/Pictures/12._Events_02.png new file mode 100644 index 0000000..e860137 --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/12._Events_02.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9ac3d8824bcc561818e17256e93509b6187185e5d1edb744c967f85c1b8f36d +size 320408 diff --git a/Committee/2024-2025/Budget/Pictures/12._Events_03.png b/Committee/2024-2025/Budget/Pictures/12._Events_03.png new file mode 100644 index 0000000..ba53e15 --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/12._Events_03.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a6daecddb0617a4c0a94c66f9d00360f65d55d5c2efd4d5a0a368bb45758442 +size 86764 diff --git a/Committee/2024-2025/Budget/Pictures/12._Events_04.png b/Committee/2024-2025/Budget/Pictures/12._Events_04.png new file mode 100644 index 0000000..5fe56bb --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/12._Events_04.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:998f3e6715ee4ddb6926c22600db2dbcb9408b67d21cc8d5393177d6a669b470 +size 576189 diff --git a/Committee/2024-2025/Budget/Pictures/12._Events_05.png b/Committee/2024-2025/Budget/Pictures/12._Events_05.png new file mode 100644 index 0000000..8a001ec --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/12._Events_05.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:070445252f3c03d1e8025ba50b622774bebee902bb5a3b21d4e6ab940764732f +size 3810309 diff --git a/Committee/2024-2025/Budget/Pictures/12._Events_06.png b/Committee/2024-2025/Budget/Pictures/12._Events_06.png new file mode 100644 index 0000000..64a1078 --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/12._Events_06.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25e58f3a88924304ec67e004e2f5ad04baca18229613e781d26109fc70170c95 +size 131048 diff --git a/Committee/2024-2025/Budget/Pictures/12._Events_07.png b/Committee/2024-2025/Budget/Pictures/12._Events_07.png new file mode 100644 index 0000000..e0764a0 --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/12._Events_07.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b94429f344e633e93b1a88e38337e4c62753ddd8ae52164168379f680e9414c5 +size 47257772 diff --git a/Committee/2024-2025/Budget/Pictures/12._Events_08.jpeg b/Committee/2024-2025/Budget/Pictures/12._Events_08.jpeg new file mode 100644 index 0000000..1cd7133 --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/12._Events_08.jpeg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4babbb2383afaa99ba44482cfc2f2268bda4c7a24d0bc81b7b52e17c3f37d6b +size 95770 diff --git a/Committee/2024-2025/Budget/Pictures/12._Events_09.png b/Committee/2024-2025/Budget/Pictures/12._Events_09.png new file mode 100644 index 0000000..b01e9b7 --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/12._Events_09.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5da713f5e5f78a4d355b673fe4abed43b43e5a45a4d7c9f7455bb12876866713 +size 5797673 diff --git a/Committee/2024-2025/Budget/Pictures/12._Events_10.png b/Committee/2024-2025/Budget/Pictures/12._Events_10.png new file mode 100644 index 0000000..d90dce0 --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/12._Events_10.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5c4593f5df082209bbfa3acb66b9024164e8a09e9e85798dea693fdf4ea92d6 +size 5524765 diff --git a/Events/2024-2025/Semester-1_Week-03.md b/Events/2024-2025/Semester-1_Week-03.md index 6bbe25c..d19457d 100644 --- a/Events/2024-2025/Semester-1_Week-03.md +++ b/Events/2024-2025/Semester-1_Week-03.md @@ -23,12 +23,45 @@ Will be a small tutorial to get folks their own skynet account. ## Promotion ### Email ``` +Welcome back Everybody! +As a refresher for older members AND our newer ones, +we're having an introductory event to Computer Soc for the new year! +Where we explain what Comp Soc is and what we do here. + +We'll be in the Courtyard Room. +This Wednesday, at 6.00 in the evening as per our usual timings. +We also have free pizza! + +If you can't find us a member of committee will help you outside in the Courtyard. +Did I also mention there's free pizza? + +We also plan to help you guys get registered on our discord, + if you haven't already been registered. + +We hope to see you all there! ``` ### Discord +<> ``` +Welcome back @everyone +As a refresher for older members AND our newer ones, +we're having an introductory event to Computer Soc for the new year! +Where we explain what Comp Soc is and what we do here. + +We'll be in the Courtyard Room. +This Wednesday, at 6.00 in the evening as per our usual timings. +We also have free pizza! + +If you can't find us a member of committee will help you outside in the Courtyard. +Did I also mention there's free pizza? + +We also plan to help you guys get registered on our discord, +if you haven't already been registered. + +We hope to see you all there! ``` ### Poster From c0e33fc63cf946a03b07682de71dccdcfb0c2c1c Mon Sep 17 00:00:00 2001 From: Nanda Date: Tue, 6 May 2025 15:07:50 +0100 Subject: [PATCH 07/29] doc: Corrected LAN Party heading and added Show & Tell section with details --- Committee/2024-2025/Budget/12._Events.md | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/Committee/2024-2025/Budget/12._Events.md b/Committee/2024-2025/Budget/12._Events.md index a259ae0..8932a00 100644 --- a/Committee/2024-2025/Budget/12._Events.md +++ b/Committee/2024-2025/Budget/12._Events.md @@ -195,9 +195,9 @@ - Refreshments and snacks were also provided. ![SISTEM](Pictures/12._Events_09.png) -![!SISTEM](Pictures/12._Events_10.png) +![SISTEM-2](Pictures/12._Events_10.png) -#### Lan Party +#### LAN Party - Polled members for a game to play, TF2 was chosen. - Setup a custom TF2 server on Skynet for the event. @@ -206,3 +206,13 @@ - We advertised the event using Discord announcements and emails. - We also bought spar chips for the events +### Show & Tell + +- Members were to show off any project they were proud of to win prizes +- Prizes included: + - 1st place: Monitor + - 2nd place: Keyboard + - 3rd,4th,5th places: Minecraft Accounts +- Venue: Courtyard Room +- We advertised the event using Discord announcements and emails. +- We bought cookies for the event. From 47c096552cb02e1f4e60622907fb5e8ff95833b5 Mon Sep 17 00:00:00 2001 From: Nanda Date: Tue, 6 May 2025 15:10:52 +0100 Subject: [PATCH 08/29] doc: wupsie daisie forgot the show&tell poster --- Committee/2024-2025/Budget/12._Events.md | 2 ++ Committee/2024-2025/Budget/Pictures/12._Events_11.png | 3 +++ 2 files changed, 5 insertions(+) create mode 100644 Committee/2024-2025/Budget/Pictures/12._Events_11.png diff --git a/Committee/2024-2025/Budget/12._Events.md b/Committee/2024-2025/Budget/12._Events.md index 8932a00..c13bdb4 100644 --- a/Committee/2024-2025/Budget/12._Events.md +++ b/Committee/2024-2025/Budget/12._Events.md @@ -216,3 +216,5 @@ - Venue: Courtyard Room - We advertised the event using Discord announcements and emails. - We bought cookies for the event. + +![Show&Tell](Pictures/12._Events_11.png) diff --git a/Committee/2024-2025/Budget/Pictures/12._Events_11.png b/Committee/2024-2025/Budget/Pictures/12._Events_11.png new file mode 100644 index 0000000..6dbe64e --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/12._Events_11.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16d16142ee3cc63a9f050a3326bbcccddff04e6acd2b8b6282642397f97f3c4d +size 2203120 From 11ac9de97b1a430309bb5f5325eea6f7716d000e Mon Sep 17 00:00:00 2001 From: Brendan Golden Date: Sun, 18 May 2025 13:12:11 +0100 Subject: [PATCH 09/29] handover: duties for Sr Sysadmin havent really changed --- .../Handovers/Senior_System_Administrator.md | 36 +++---------------- 1 file changed, 4 insertions(+), 32 deletions(-) diff --git a/Committee/2024-2025/Handovers/Senior_System_Administrator.md b/Committee/2024-2025/Handovers/Senior_System_Administrator.md index ddcdef1..f5b17f7 100644 --- a/Committee/2024-2025/Handovers/Senior_System_Administrator.md +++ b/Committee/2024-2025/Handovers/Senior_System_Administrator.md @@ -32,35 +32,7 @@ The purpose of this document is to assist the incoming Senior System Administrat * Its not your fiefdom, everything must improve it for others, even if it takes you out of your comfort zone. #### Onboarding -##### New Committee -1. Ensure that each committee member has a skynet account - * If they dont then assist them through the process. -2. Add their chosen usernames to the [nixos][3] under ``committee`` -3. Run them through the process of gaining access to the password manager: [pw.skynet.ie][2] - * Separate but linked account is security feature, unavoidable. - * They will gain access to the ``Compsoc`` collection of passwords. -4. They will automatically gain access to the ``Compsoc`` folder on [nextcloud][1] - -##### Root team - Trainee -1. Ensure that each root member has a skynet account - * If they dont then assist them through the process. -2. Add their chosen usernames to the [nixos][3] under ``trainee`` -3. They will automatically gain access to the ``Skynet`` folder on [nextcloud][1] -4. Provide training - -##### Root team - Admin -1. They will already have a skynet account. -2. Add their chosen usernames to the [nixos][3] under ``admin`` -3. They will automatically gain access to the ``Skynet_Admin`` folder on [nextcloud][1] -4. Run them through the process of gaining access to the password manager: [pw.skynet.ie][2] - * Separate but linked account is security feature, unavoidable. - * They will gain access to the ``Skynet`` collection of passwords. -5. Contact ITD to get them added to the VPN. -6. Provide training - -##### Sr Sysadmin -Need to figure out this process. -My FYP next year will be primarily about this aspect. +Details on how to onboard and offboard can now be found on the [wiki][8]. #### Annual Events ##### Sign up Fair @@ -103,7 +75,7 @@ Brendan Golden. [1]: https://nextcloud.skynet.ie [2]: https://pw.skynet.ie [3]: https://forgejo.skynet.ie/Skynet/nixos/src/branch/main/config/users.nix#L51 -[5]: https://renew.skynet.ie/ -[6]: https://renew.skynet.ie/recovery/ +[5]: https://wiki.skynet.ie/support/renew/ +[6]: https://wiki.skynet.ie/support/recovery/ [7]: https://2016.skynet.ie/history.html - +[8]: https://wiki.skynet.ie/procedures/committee_modify/ From 7e5c679dbe8886908273425596b13b384ba32c81 Mon Sep 17 00:00:00 2001 From: Brendan Golden Date: Sun, 18 May 2025 13:46:07 +0100 Subject: [PATCH 10/29] doc: this doc was found in the 2021-2022 President handover --- Committee/2024-2025/Handovers/President.md | 96 +++++++++++++++++++ .../protocols_administration_skynet.pdf | 3 + 2 files changed, 99 insertions(+) create mode 100644 Committee/2024-2025/Handovers/President.md create mode 100644 Resources/Documents/protocols_administration_skynet.pdf diff --git a/Committee/2024-2025/Handovers/President.md b/Committee/2024-2025/Handovers/President.md new file mode 100644 index 0000000..a2a416c --- /dev/null +++ b/Committee/2024-2025/Handovers/President.md @@ -0,0 +1,96 @@ +## President +#### Brendan Golden + +The purpose of this document is to assist the incoming CompSoc President for the upcoming year 2025/26. + +### Duties +The position of President comes with the duties of running both a society and overseeing the Skynet Cluster. +These duties include: + +* Overseeing the running of the Computer Society +* Coordinate the training of new committee +* Finding resolution in cases of dispute among committee and members +* Chair all meetings of the society and prepare an agenda for each meeting beforehand +* Organise and manage a team of society members for both Recruitment Drives +* Liaise with C&S Development Officer (Paul Lee) in areas that need to be discussed e.g. details for the C&S recruitment drive and Redevelopment Fund +* Scheduling events and assigning tasks to committee, making sure all other committee members are doing their jobs and provide help when they need it +* Ensure the growth of the Computer Society in general +* People will approach you at events with ideas and suggestions be receptive to everything. + Keep a list if multiple different ideas come in and try to do them and do new stuff throughout the year. + +It is not the president’s job to do all of the work for the society, if tasks are not delegated properly or are not being carried out, you will end up with a lot of work to do and the end result for the society could be worse events. + +### Guide +As President, you will be responsible for the general running of the society and the committee. +You should have a good understanding of the Clubs and Societies constitution found on wolves.ie under Resource Documents. +Be aware that the Computer Society has its own constitution too that must adhere to. This can be found on our google drive. + +The computer society has typically been a group of people whose common interest is computers but have interest in much wider fields. +You need to make sure that there are things happening to keep members interested and engaged in the society. +It doesn't always have to be deeply technical, not everyone will be interested in heavily technical meetups, even something as simple as meetups over a few pints helps keep things running. +It is important to try and have some variety in the meetups also to ensure that everyone is interested. These meetups usually fall into one of the categories of Programming, Electronics, Technology and Social. +We simply meet up in a location usually Room 3 (Make sure to block book it early on in September AND again in early January before college starts). + +PR is important for the society this needs to be really kept on top of. +Ensure consistent emails are sent out, make sure you understand how the email mailing list works. +One tip that we found worked well was to have multiple people help out with writing the email. +Have people write quick paragraphs on sections if they are more knowledgeable on it than the PRO and post it in the PRO chat in our Discord server. +Use that chat as a hub to add all the info the PRO needs for the weekly emails and Instagram posts etc. +Usually PRO sends the email to the president or put it into the PRO chat before it was sent out to the society. +Our social media is something that should be used and maintained for the whole year. +Also make sure that the emails do go out before the events start and keep on top of the status of how ready the email is. +Offer to write parts of the email for the PRO or even send the email the odd week for the PRO to give them some time off. +Also make sure to keep Wolves updated, the news and activity sections should have all the event details as well. + +We aim to have money in the budget this year to have twenty meetups, there should also be money for two social meetups. +The social meetups have been historically held in Scholars. +The most important thing to remember is quality over quantity. +Maybe plan bigger events 2 weeks in advance and skip a week. + +Events should be organised based on the wants of the members of the computer society but try to have a variety. +For example, if a large base would like to see how to set up WordPress, then you should try to organise a workshop on this. +However, you can't keep everyone happy, so don't try. Your main objective is to have vision, direction and come to conclusions, not to keep the committee happy. +You will make decisions which people will disagree with, but if you have a good committee, they will respect the differences of opinion and move on. +It is up to you to foster the kind of intra-committee relationships that will allow respectful differences of opinion instead of destructive bickering. + +As President, you chair the committee meetings and the societies AGM. +On previous years, Committee Meetings were made early on the week (usually Mondays), but that didn't give much time to organise the event (Wednesday), so this year was changed to Thursdays and it worked very well. +Ideally, all committee members should join the meeting, but it can happen that they can't attend for any reason. I would recommend you to ask them to advise you at least two hours before the meeting starts and to try not to skip many. +You need to ensure that an agenda is prepared before each meeting and email it out to committee a few days beforehand for review. +One recommendation is to set up the thread on Discord with some points days before the meeting, so other people can add up more points to the thread and it gives you time to prepare the agenda. + +Committee meetings can be held in the Server Room, but being flexible is always good, so some people can join online if they can't make it in person. +Booking a room in the library is also very easy for larger meetings, or if the building is closed. +It's up to you to ensure all those present get a fair chance to put their point across. +It is also important that you know what's happening within the society at all levels. + +Since the President is frequently looked up to as the leader (even subconsciously) it is important to hold your own opinions until the others have outlined theirs first. +Allow the discussion to develop before you bring your own opinions to the table, quite often this will be the conclusion of the discussion, with your opinion shaping the final decision of the committee rather than influencing the discussion from the outset. +You also need to keep the committee meetings moving and not allow the committee to become “bogged down” on any one issue. +If any other issue requires major attention a separate meeting should be called with some committee members. + +If the society is buying stuff always try to get a discount or sponsorship as this saves us money and can count as income. +The society has secured a lot of money in sponsorship through the years and this was done by directly contacting companies that we were planning to buy stuff from explain who we were and offer them exposure. +It doesn’t always work but we have been very successful at doing this. + +The budget is a very important process and should involve as many committee members as possible throughout the year, it should not be left to one person at the end of the year. +Irregular Expenditure should be voted on by committee. You should be able to look at the submitted budget from the end of September onwards. +Budget points are very important, and you should always be on the lookout for opportunities to gain more points. +Points are given for Guest Speakers, High Profile Speakers, Events, Showcase Events (Big on campus events), Publicity, proper minutes, proper use of Wolves.ie, etc. +At the end of your tenure as President, you must make sure that the incoming President is well briefed on the role. +If possible, it is advisable to retain a role on the next committee to facilitate the transition but be wary of being a backseat President. +If you know in advance that you won’t be seeking re-election as President, you should let the committee know this and start grooming a successor from within the current committee. +You should work to ensure good continuity from one committee to the next. + +As the second semester progresses you should be listening to the existing committee about their intentions for the following year, especially core positions. +If people are not planning to take up the same roles the following year, you need to be thinking about who might replace them. +Canvass the committee members for interest in shadowing the core positions with a view to taking over the following year. +On this basis, it’s important to have a good crew of OCMs on board, use the less important positions to bring new people on board each year and ensure they are engaged in the work of the committee through the year. + +### Summary +In conclusion it’s a big job with massive responsibility. +It will test you and you will gain new skills when dealing with people. +Appreciate the massive work done by your committee. +This is what makes the society great, you can always ask someone for help. +Don’t be the one stuck with all of the work, delegate tasks. +Best of luck and I look forward to seeing the impact you will make on the society. diff --git a/Resources/Documents/protocols_administration_skynet.pdf b/Resources/Documents/protocols_administration_skynet.pdf new file mode 100644 index 0000000..b6c8a32 --- /dev/null +++ b/Resources/Documents/protocols_administration_skynet.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f097ebcdbe13a9e35fc0c6c05b759fd49da55f6cdf61f0c2673b3797378fae2c +size 552773 From f3d6a8b5359f79b42e294314e9cca136c8afd4e4 Mon Sep 17 00:00:00 2001 From: Brendan Golden Date: Sun, 18 May 2025 23:50:36 +0100 Subject: [PATCH 11/29] handover: committing on behalf of Lorcan --- Committee/2024-2025/Handovers/Secretary.md | 75 ++++++++++++++++++++++ 1 file changed, 75 insertions(+) create mode 100644 Committee/2024-2025/Handovers/Secretary.md diff --git a/Committee/2024-2025/Handovers/Secretary.md b/Committee/2024-2025/Handovers/Secretary.md new file mode 100644 index 0000000..ba8c4ad --- /dev/null +++ b/Committee/2024-2025/Handovers/Secretary.md @@ -0,0 +1,75 @@ +## Secretary +#### Lorcán Rooney + +The purpose of this document is to assist the incoming CompSoc Secretary for the upcoming year 2025/26. + +### Duties +The duties of the Secretary include: +* Taking minutes at meetings. +* Distributing the minutes during committee meetings and AGMs. +* Creating a topic summary of what should be put in the weekly email for the PRO +* Working with the president to ensure people are completing their tasks/roles and offering assistance where needed. +* Helping to organise other things as needed along with other committee members + +### Guide +Your primary responsibility as Secretary is to take detailed minutes during committee meetings and Annual General Meetings (AGMs). +These minutes serve as a vital record of the society's decisions and discussion topics. +It is crucial to upload these minutes to the designated repository for the 2025/26 term, either by creating a Markdown file during the meeting or transcribing handwritten notes afterwards. +This ensures accessibility for all committee members. +At the end of the year, you will also need to upload all the accumulated minutes to Wolves, serving as a permanent record for future committees. + +During meetings, you should record the following information at the beginning: +* Date and time of the meeting +* Present committee members +* Excused committee members (those who have notified in advance of their absence) +* Absent committee members + +During discussions, it is important to record: +* Main points and topics discussed +* Key bullet points or summarized ideas that were raised +* Decisions made, such as event prizes, event location, task assignments, and important discussions that require detailed descriptions + +Your recordings may consist of rough sentences that may not be grammatically perfect, as long as they convey the essence of the conversation and decisions. +It is essential to note down volunteers or individuals assigned to tasks. +Alternatively, you can create a to-do list for all committee members and email it to them, ensuring everyone has a record of their responsibilities. + +At the end of each meeting, create a bullet point summary for the weekly email, acting as a template for the PROs (Public Relations Officers) to include all key information. +This summary should include: + +* This week's event details (date, time, location) +* If event signup is required, include a signup form link for the PRO to include +* Event cost (if applicable) +* Specifics needed for the event poster +* Zoom link / Discord link / Skynet meet link for online events +* A teaser for next week's event +* A poster may be included for "this week's event" but not for the following week, unless it is a significant event like the Show and Tell or a major Guest Speaker event +* Skynet update for any issues or important announcements +* Any other society news + +Outside of committee meetings, you can assist other committee members as needed. +As Secretary, your experience within the society, as a former regular committee member, and possibly as a regular member, provides valuable knowledge and expertise. +You can support junior committee members by sharing your insights. +In the computer society, we aim for ambitious events that require extensive planning and effort. +We strive to distribute the workload evenly among the committee members to avoid overwhelming anyone. +As Secretary, you can be a versatile resource and provide assistance where needed. + +#### Efficiency Tips +* The agenda for committee meetings is stored on Computer Society’s NextCloud, it is advised to use the agenda to prepare preliminary headings for the minutes. +* The minutes are automatically converted to pdf format on open goverance and can be bulk downloaded for a slightly less painful upload to Wolves. +* A level of proficiency in Git is highly advised as much of the Society’s document management is done through a Git server hosted on Skynet. + + +### Summary +As a support role within the team, your contribution may be in smaller but valuable ways. +You play a crucial role in keeping track of tasks and their progress through the use of to-do lists. +Additionally, you are responsible for recording the minutes during meetings and providing support to the Public Relations Officer (PRO) by summarizing the necessary content for the weekly emails or social media posts. + +During committee meetings, it is your responsibility to raise any matters that are pending or require the committee's attention from the previous meeting. +This ensures that the society stays on track and avoids falling behind on important tasks. + +The position of Secretary offers an excellent opportunity to gain a comprehensive understanding of the society as a core member. +You will have the chance to explore various aspects of the society and contribute to making significant decisions. + +Moreover, serving as Secretary can serve as a valuable stepping stone towards potentially assuming the roles of President or Treasurer in the following year, if you desire. +Lorcán Rooney + From 475ed433e34e43c0661d9ba59615cde53bf3d57f Mon Sep 17 00:00:00 2001 From: Brendan Golden Date: Mon, 19 May 2025 00:14:18 +0100 Subject: [PATCH 12/29] handover: for some reason it wasnt rendering correctly without teh extra newline --- Committee/2024-2025/Handovers/Secretary.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Committee/2024-2025/Handovers/Secretary.md b/Committee/2024-2025/Handovers/Secretary.md index ba8c4ad..5175ac4 100644 --- a/Committee/2024-2025/Handovers/Secretary.md +++ b/Committee/2024-2025/Handovers/Secretary.md @@ -1,4 +1,5 @@ -## Secretary + +## Secretary #### Lorcán Rooney The purpose of this document is to assist the incoming CompSoc Secretary for the upcoming year 2025/26. From 25637460aa190a0b0b0d5b05a30b2dca891e39a9 Mon Sep 17 00:00:00 2001 From: Nanda128 Date: Mon, 19 May 2025 02:03:44 +0100 Subject: [PATCH 13/29] doc: PRO Handover Docs at 2AM yippee --- Committee/2024-2025/Handovers/PRO.md | 273 +++++++++++++++++++++++++++ 1 file changed, 273 insertions(+) create mode 100644 Committee/2024-2025/Handovers/PRO.md diff --git a/Committee/2024-2025/Handovers/PRO.md b/Committee/2024-2025/Handovers/PRO.md new file mode 100644 index 0000000..b733480 --- /dev/null +++ b/Committee/2024-2025/Handovers/PRO.md @@ -0,0 +1,273 @@ +## PRO + +#### Nanda Vinayakrishnan + +### Duties + +Your duties as a Public Relations Officer are usually to promote the society and its events. + +As part of this, you might have to take photos at events, reply to direct messages on social media, and post on social +media. + +#### General Overview + +You will need to at least have three of the following things done for **every single** event. +I recommend using a per-event checklist, maybe a Notion page or whatever suits you. + +It needs to have: + +- [ ] Wolves +- [ ] Email +- [ ] Discord +- [ ] Poster (Optional) +- [ ] Social Media + +More elaboration on what each of these sections entails is below. + +Part of your job will also involve delegating some of these tasks to other folks, like your Assistant PROs. +Trying to do everything yourself is a recipe for burnout. + +##### Wolves + +- **Every** event needs to be posted up on Wolves. +- Familiarize yourself with the Committee Panel on ulwolves.ie, especially the "Events" section. +- For each upcoming event, you need to navigate + to https://cp.ulwolves.ie/manage/events/add and fill out the form. +- For the "Description" section, you can copy and paste the email or discord announcement (removing things like the " + ```@everyone```" tag). +- Every event needs to be bookable, so click on the "Book on UL Wolves" radio button in the "Pre-Booking" section. You + don't need tickets (unless its big events like PyCon) or booking notifications. +- Leave all settings as default with respect to bookings, unless otherwise specified. +- (Consult with the Treasurer if you need to charge for tickets, if so, how much, and how to handle the money.) +- Once you've created the event, go to https://ulwolves.ie/whatson, filter by "Computer" and check that the event is + listed. +- Click on the event and copy the link, and put it in your discord, email, poster (as a QR code), and social media posts + and tell people to book on it. +- More people booking on Wolves is better for record-keeping. + +##### Discord + +- **Every** event also needs to be announced on Discord. +- The society usually conducts most communication and activity on Discord, so you should try to point people + to https://discord.skynet.ie as much as you can. Especially in the beginning of the year. +- Every announcement begins life as a thread in the "pro-forum" channel in the Committee Discord. You'll need to create + a new post on the forum with the format as follows: ```YYYY-MM-DD {Event Name} Comms``` with the date referring to the + date of the event. +- For example, if the event is a capture the flag on the 1st of October, the post should be titled + ```2025-10-01 CTF Comms```. +- In the thread, you want to link to the committee forum thread in the first post and any important information you + might need to make an announcement off of. +- Start making a base announcement, there isn't a specific format but usually ours followed something like this: + +``` +Hey everyone/@everyone, + +{Quip about the event} + +We'll be having {Event Name} on {Day} the {Date} of {Month}. +It will be held in {Location} at {Start Time : End Time}. [WRITERS NOTE: TRY NOT TO USE 24HR IT CONFUSES NORMAL PEOPLE] + +See you then! + +Book your slot on Wolves: {Wolves Link} + +[Any other important links] [P.S. Do not use embeds, have the links out there. People wouldn't feel secure clicking on a random link they cant see at first glance in an email] +``` + +- Ideally you want to include more than just the base format, you don't want things getting too same-y +- After making the announcement, put it in the pro-forum thread and wrap it in triple backticks to make it a code block. + This will make it easier to read and copy. (The backtick is usually above your Tab key) +- Post that into the thread, and reply to it with a "@Committee" ping. You will need the assent of at least two other + committee members to post it (one if it's an emergency). +- Being funny in the announcements channel is completely fine, make sure you're not annoying people or making the + announcement difficult to read. +- Don't use the ``@everyone`` tag for stupid reasons, you don't want people to start muting the announcement channel. + +##### Emails + +- **Every** event should also be announced via E-mail. +- It's completely fine to copy the Discord Announcement and paste it into the email, but make sure to fix the + formatting. +- To make an email, navigate to https://cp.ulwolves.ie/mailbox/computer#compose and click on the "BCC {Number}/{Number} + Active Members (who have opted in to emails)" +- You don't need to add any other users to the email, as the BCC will send it to all members. +- Make sure to include the subject line, which is usually the type of event and what event it is. For example, for + events, we'd have the subject as "``[Event] Capture the Flag``" or "``[Event] PyCon 2025``". +- Every time a link is pasted into the email box, select the link text and click on the "Link" button in the toolbar. + This will make it a clickable link. +- The same requirements as Discord announcements apply, make sure the UL Wolves link is in the email, and make sure to + include any other important links. +- E-mails can't be taken back once sent, so make sure to save things as a draft before clicking "Send" and making sure + you have the assent of committee members. + +##### Posters + +- Posters can be a bit time-consuming, so you don't need to have one for every single event. +- You absolutely should, if you can, have a poster for your larger events. +- If it's allowed, you can also use preexisting posters for the event as the poster for the event. +- This poster needs to be uploaded on UL Wolves Event Creation page in the "Image/Poster" section. +- Some Guidelines for Poster-Making: + - Make sure to include the following information: + - Time + - Date + - Place + - Event Name + - UL Wolves Booking link QR Code + - 10-word tagline (optional) + - Make sure to use the UL Computer Society Logo, in any corner, usually the top left + - You can include the Time, Date, Place, and Location in the corner of the poster + - When putting information in the corners, make sure it floats off of the corner to prevent cropping. +- Attach the poster as an attachment in the Discord Announcement and the E-mail. +- Make sure to include the poster in the pro-forum thread + +##### Non-Discord Social Media + +- We have a few social media accounts, but they are not very active. +- We have official accounts on Instagram and LinkedIn, though we usually use the Instagram account. +- People will often try to reach out to us on Instagram direct messages, so make sure to check them regularly. +- You can also use the Instagram account to post about events, but make sure to check with the committee first. +- There isn't an established format for announcing, but since Instagram's visuals-heavy you'd want to only promote + events with posters or good visuals +- Consider handing this to an Assistant PRO, since its really easy to get outstretched with managing insta, discord, and + emails on top of everything. +- LinkedIn has been dead forever, consider not bothering with it or don't, whichever one works. + +##### Photography + +- Take pictures at most, if not all, events. +- CRUCIAL: ASK PEOPLE FOR PERMISSION TO TAKE THEIR PICTURE. IF NOT, MAKE SURE THEY'RE NOT CAUGHT IN THE ANGLES OF OTHER + PHOTOS. +- You can use these in the budget and for insta posts or other archival stuff. +- The Society has its own camera, so make sure to use it. Also use your own phone camera if needed. +- Take a million pictures of the same scene if you have to, you can get a better chance of a good picture if you do. + +##### Registering events on open-governance + +- Another part of your job is to archive events that happened on open-governance. +- What you want to do is clone open-governance to your system, navigate to open-governance/Events/{YYYY-YYYY}/ and + create a new file with the name of the event in the format Semester-{Semester Number}_Week-{Week Number}.md. +- At the top will be a title, with one ``#`` followed by the event name, so "``# PyCon``". +- Then you want to create a table with the date, location, time, type, and lead. +- The type is usually either "Technical" or "Social," and the lead is usually the person who organized the event. +- For the "Lead" section, try to use the forgejo handle of the person who organized the event. +- You can use the following template: + +``` +# {Event Name} + +| Date | {Date} | +|----------|----------------| +| Location | {Location} | +| Time | {Start Time} - {End Time} | +| Type | {Type} | +| Lead | {Lead} | + +## Overview + +{Overview of the event} + +## Requirements + +{Requirements for the event, if any} + +## Promotion + +### Email + +{Email for the event} + +### Discord + +{Discord announcement for the event} + +### Poster +![Poster]({Poster Link}) +``` + +- Upload any posters to the same directory as the event file, and link to them in the "Poster" section. +- Copy the same filename as the Markdown file, and rename the poster to it. + +##### Committee Meetings + +- At every committee meeting, there'll be a section for PROs. +- In that section, you want to ask if the previous event has been archived on open-governance and if not, who'll do it. +- Usually that's you. +- Later down the meeting, usually, there'll be a section for upcoming events. +- There, you need to ask yourself (and maybe the assistant PROs too) the following: + - Is the event up on Wolves? + - Is the announcement ready? + - Is any information needed? + - Is the poster ready? Do we need a poster? +- Don't rely on your memory, make sure to write down important stuff in the minutes. + +#### Flavors of PROdom + +###### Vanilla (Announcement Goblin PRO) + +- Typically, has no assistant PROs or just one semi-inactive one. +- Work on emails, discord, and instagram optionally. +- Reply to Direct Messages on Social Media + - Discord + - Instagram +- Photography + - The Society has a camera, and you can use your mobile phone camera + - Once again: Ask for permission to take pictures of people. +- Posters take a backseat, and you can use preexisting posters for events if needed. + +###### Marble (Announcement Goblin PRO + PRO who does Posters) + +- Person 1: + - Manages Discord and Email +- Person 2: + - Manages Posters and Instagram + +This distribution of labor isn't set in stone, you can shift responsibilities around and add and remove some ones. +This is just a suggestion based on a previous way the society's public relations was done +You want to not overwork one side over the other, since unfair distribution can make people burn out faster. + +###### Neapolitan (Announcement Goblin PRO + PRO who does Posters + PRO who does Social Media) + +- The PRO team has never gone past 3 people and never needed to. +- Having 3 people is nice because you get more flexibility when delegating work. +- Generally, it follows the same distribution as the Marble team, but with a third person who does instagram and can pop + in to help elsewhere like archiving. +- Same as Marble, you can shift things between roles and add new ones like archival, photos, etc. +- This is going to need more management of people, so make sure to ping them to remind them of things and to ask them + how things are going along. + +### Misc/Experience + +The position's really fun since you get a lot more space to just do things you want, but you also get a load of chances +to fumble, especially with things like emails which are hard to take back. +You don't really need to be technical to be a PRO of this society, you can be completely new to everything and still do +a good job. +The committee is also full of helpful people who will help you out if you ask them, so don't be afraid to ask for help. + +One important thing that needs noting is that everyone on this committee is a volunteer, and they are all doing this for +free. +This means that you need to be respectful of their time and effort, and not expect them to do everything for you. +You can't be overbearing, since that's just socially not the done thing, but you also can't be too hands-off that people +forget they're on the committee. + +Golden rule for doing anything PRO-related: **If you can finish the task in the time its taking you to ping someone else +and wait for them to get it done, you can do it yourself.** + +You should also get used to pinging Committee to re-check your announcements. +Always better to have someone get annoyed at you for pinging them than to have a bad announcement go out. + +Also, remember that this is a volunteer position, not a job. +If it starts to feel like one, take a step back and consider delegating more or raising it with the committee. +It's okay to take breaks, and it's okay to drop off the face of the earth for a while as long as you let folks know. +Additionally, if you see someone else getting burnt out, be the first to step in and help them out. +People are more likely to accept other people helping than they are to ask for help themselves. + +### Summary + +The Public Relations Officer is a committee position who's main purpose is to manage, well, the Public Relations of UL +CompSoc. +Your job will be to announce events, keep people informed, maybe promote things, take pictures, and archive events. +Depending on the situation, you might also be the first point of contact for people who want to talk to the society. +You'll need to work with a team, or on your own, but the most important part is that you don't get burnt out. +Being a PRO is almost as much teamwork as it is actual public relations, and just enjoy stuff. + +And of course, the first rule of PROdom: ✨ **Have fun** ✨ From 24fedaef724a1cae3ba8919795c5e7e31d29c2be Mon Sep 17 00:00:00 2001 From: Nanda128 Date: Mon, 19 May 2025 02:14:48 +0100 Subject: [PATCH 14/29] handovers: Oopsie daisie with the triple backtick markdown --- Committee/2024-2025/Handovers/PRO.md | 24 ++++++++++-------------- 1 file changed, 10 insertions(+), 14 deletions(-) diff --git a/Committee/2024-2025/Handovers/PRO.md b/Committee/2024-2025/Handovers/PRO.md index b733480..d75c40c 100644 --- a/Committee/2024-2025/Handovers/PRO.md +++ b/Committee/2024-2025/Handovers/PRO.md @@ -34,7 +34,7 @@ Trying to do everything yourself is a recipe for burnout. - For each upcoming event, you need to navigate to https://cp.ulwolves.ie/manage/events/add and fill out the form. - For the "Description" section, you can copy and paste the email or discord announcement (removing things like the " - ```@everyone```" tag). + ``@everyone``" tag). - Every event needs to be bookable, so click on the "Book on UL Wolves" radio button in the "Pre-Booking" section. You don't need tickets (unless its big events like PyCon) or booking notifications. - Leave all settings as default with respect to bookings, unless otherwise specified. @@ -51,15 +51,14 @@ Trying to do everything yourself is a recipe for burnout. - The society usually conducts most communication and activity on Discord, so you should try to point people to https://discord.skynet.ie as much as you can. Especially in the beginning of the year. - Every announcement begins life as a thread in the "pro-forum" channel in the Committee Discord. You'll need to create - a new post on the forum with the format as follows: ```YYYY-MM-DD {Event Name} Comms``` with the date referring to the + a new post on the forum with the format as follows: ``YYYY-MM-DD {Event Name} Comms`` with the date referring to the date of the event. - For example, if the event is a capture the flag on the 1st of October, the post should be titled - ```2025-10-01 CTF Comms```. + ``2025-10-01 CTF Comms``. - In the thread, you want to link to the committee forum thread in the first post and any important information you might need to make an announcement off of. -- Start making a base announcement, there isn't a specific format but usually ours followed something like this: +- Start making a base announcement, there isn't a specific format, but usually ours followed something like this: -``` Hey everyone/@everyone, {Quip about the event} @@ -71,8 +70,7 @@ See you then! Book your slot on Wolves: {Wolves Link} -[Any other important links] [P.S. Do not use embeds, have the links out there. People wouldn't feel secure clicking on a random link they cant see at first glance in an email] -``` +{Any other important links} [P.S. Do not use embeds, have the links out there. People wouldn't feel secure clicking on a random link they cant see at first glance in an email] - Ideally you want to include more than just the base format, you don't want things getting too same-y - After making the announcement, put it in the pro-forum thread and wrap it in triple backticks to make it a code block. @@ -152,15 +150,14 @@ Book your slot on Wolves: {Wolves Link} - For the "Lead" section, try to use the forgejo handle of the person who organized the event. - You can use the following template: -``` # {Event Name} -| Date | {Date} | -|----------|----------------| -| Location | {Location} | +| Date | {Date} | +|----------|---------------------------| +| Location | {Location} | | Time | {Start Time} - {End Time} | -| Type | {Type} | -| Lead | {Lead} | +| Type | {Type} | +| Lead | {Lead} | ## Overview @@ -182,7 +179,6 @@ Book your slot on Wolves: {Wolves Link} ### Poster ![Poster]({Poster Link}) -``` - Upload any posters to the same directory as the event file, and link to them in the "Poster" section. - Copy the same filename as the Markdown file, and rename the poster to it. From 98e17515c6e934a7bf5544629303df7687c3d89a Mon Sep 17 00:00:00 2001 From: Nanda128 Date: Mon, 19 May 2025 02:21:09 +0100 Subject: [PATCH 15/29] handovers: oopsie daisie again i shouldve picked a better time to work on handovers --- Committee/2024-2025/Handovers/PRO.md | 33 +--------------------------- 1 file changed, 1 insertion(+), 32 deletions(-) diff --git a/Committee/2024-2025/Handovers/PRO.md b/Committee/2024-2025/Handovers/PRO.md index d75c40c..05ab72e 100644 --- a/Committee/2024-2025/Handovers/PRO.md +++ b/Committee/2024-2025/Handovers/PRO.md @@ -148,38 +148,7 @@ Book your slot on Wolves: {Wolves Link} - Then you want to create a table with the date, location, time, type, and lead. - The type is usually either "Technical" or "Social," and the lead is usually the person who organized the event. - For the "Lead" section, try to use the forgejo handle of the person who organized the event. -- You can use the following template: - -# {Event Name} - -| Date | {Date} | -|----------|---------------------------| -| Location | {Location} | -| Time | {Start Time} - {End Time} | -| Type | {Type} | -| Lead | {Lead} | - -## Overview - -{Overview of the event} - -## Requirements - -{Requirements for the event, if any} - -## Promotion - -### Email - -{Email for the event} - -### Discord - -{Discord announcement for the event} - -### Poster -![Poster]({Poster Link}) - +- You can use the template from older events as a base, but make sure to change details. - Upload any posters to the same directory as the event file, and link to them in the "Poster" section. - Copy the same filename as the Markdown file, and rename the poster to it. From b89c63a21b8bcbb004c326eff015977c58de88c7 Mon Sep 17 00:00:00 2001 From: Prabuddha Hans <21313482@studentmail.ul.ie> Date: Tue, 20 May 2025 23:09:47 +0100 Subject: [PATCH 16/29] Handover: HSO draft 1 --- .../Handovers/Health_And_Safety_Officer.md | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 Committee/2024-2025/Handovers/Health_And_Safety_Officer.md diff --git a/Committee/2024-2025/Handovers/Health_And_Safety_Officer.md b/Committee/2024-2025/Handovers/Health_And_Safety_Officer.md new file mode 100644 index 0000000..633ef30 --- /dev/null +++ b/Committee/2024-2025/Handovers/Health_And_Safety_Officer.md @@ -0,0 +1,30 @@ +## Health And Safety Officer +#### Prabuddha Hans + +The purpose of this document is to assist the incoming CompSoc Health and Safety Officer for the upcoming year 2025/26. + +### Duties +The position of HSO involves the following duties: + +- Ensure that Health and Safety is a priority at all society events, hazards need to be avoided at all times +- Make sure CompSoc members don't get injured at our events. +- Keep up to date with COVID-19 guidelines from UL Wolves C&S, University of Limerick, and the Government. +- Ensure that members are aware of our required safety measures. +- Review Computer Society's Safety statement. +- Report accidents and injuries. +- Report potential hazards to members at events. +- Take responsibility for members during trips. +- Ensure that CompSoc's First Aid kit is stocked and up to date, and available at events and brought during trips. +- Check for food allergies and dietary preferences when food is being ordered. + + +### Guide +Make sure you know how to handle minor wounds and injuries like cuts and bruises. + +If you are going on trips with the society, keep an eye on the headcount to make sure nobody's missing. +Again, keep an eye out for any potential hazards like broken chairs, desks or a heavy item being in an unsafe position. + +### Summary +As the HSO you need to keep an eye out for any dangerous behaviours (safety hammer does not count) and review the Health and Safety Statements. +In the case of another global pandemic, it's vital as part of your role that you ensure that Governmental, UL, and C&S requirements are followed in +Comp Soc while running society events. From 9f8280e255c9adc455fb029f39ef516f7dabea24 Mon Sep 17 00:00:00 2001 From: Brendan Golden Date: Thu, 22 May 2025 23:34:19 +0100 Subject: [PATCH 17/29] handover initial draft of handover doc for the President --- Committee/2024-2025/Handovers/President.md | 116 +++++++-------------- 1 file changed, 36 insertions(+), 80 deletions(-) diff --git a/Committee/2024-2025/Handovers/President.md b/Committee/2024-2025/Handovers/President.md index a2a416c..0d5c922 100644 --- a/Committee/2024-2025/Handovers/President.md +++ b/Committee/2024-2025/Handovers/President.md @@ -3,94 +3,50 @@ The purpose of this document is to assist the incoming CompSoc President for the upcoming year 2025/26. -### Duties -The position of President comes with the duties of running both a society and overseeing the Skynet Cluster. -These duties include: +### Past Handovers +* [2021](../../2020-2021/Handovers/President.md) +* [2022](../../2021-2022/Handovers/President.md) +* [2023](../../2022-2023/Handovers/President.md) +* [2024](../../2023-2024/Handovers/President.md) -* Overseeing the running of the Computer Society -* Coordinate the training of new committee -* Finding resolution in cases of dispute among committee and members -* Chair all meetings of the society and prepare an agenda for each meeting beforehand -* Organise and manage a team of society members for both Recruitment Drives -* Liaise with C&S Development Officer (Paul Lee) in areas that need to be discussed e.g. details for the C&S recruitment drive and Redevelopment Fund -* Scheduling events and assigning tasks to committee, making sure all other committee members are doing their jobs and provide help when they need it -* Ensure the growth of the Computer Society in general -* People will approach you at events with ideas and suggestions be receptive to everything. - Keep a list if multiple different ideas come in and try to do them and do new stuff throughout the year. +### What teh role entails +The role of President of CompSoc is much like the role of the President of Ireland. +Uachtarán na hÉireann does not carry much "power", the main ones being able to Veto legislation as well as signing legislation into law. +Rather the main "power" of the President is diplomacy, with each president to date expanding out this to be what they want to guide the International image of Ireland into being. -It is not the president’s job to do all of the work for the society, if tasks are not delegated properly or are not being carried out, you will end up with a lot of work to do and the end result for the society could be worse events. +The president of CompSoc fulfils much the same function. +* You will be on the bank mandate and can approve payees. +* You have a (strong) say in what events teh society does during teh year. +* You can sign in as a core committee member to Council. +* You have access to teh Captains/Presidents whatsapp grouping. +Thats on paper at least. -### Guide -As President, you will be responsible for the general running of the society and the committee. -You should have a good understanding of the Clubs and Societies constitution found on wolves.ie under Resource Documents. -Be aware that the Computer Society has its own constitution too that must adhere to. This can be found on our google drive. - -The computer society has typically been a group of people whose common interest is computers but have interest in much wider fields. -You need to make sure that there are things happening to keep members interested and engaged in the society. -It doesn't always have to be deeply technical, not everyone will be interested in heavily technical meetups, even something as simple as meetups over a few pints helps keep things running. -It is important to try and have some variety in the meetups also to ensure that everyone is interested. These meetups usually fall into one of the categories of Programming, Electronics, Technology and Social. -We simply meet up in a location usually Room 3 (Make sure to block book it early on in September AND again in early January before college starts). - -PR is important for the society this needs to be really kept on top of. -Ensure consistent emails are sent out, make sure you understand how the email mailing list works. -One tip that we found worked well was to have multiple people help out with writing the email. -Have people write quick paragraphs on sections if they are more knowledgeable on it than the PRO and post it in the PRO chat in our Discord server. -Use that chat as a hub to add all the info the PRO needs for the weekly emails and Instagram posts etc. -Usually PRO sends the email to the president or put it into the PRO chat before it was sent out to the society. -Our social media is something that should be used and maintained for the whole year. -Also make sure that the emails do go out before the events start and keep on top of the status of how ready the email is. -Offer to write parts of the email for the PRO or even send the email the odd week for the PRO to give them some time off. -Also make sure to keep Wolves updated, the news and activity sections should have all the event details as well. +You are Duct Tape and WD40 that keeps the society ticking. +Under you are four other core committee members plus a sysadmin for the Skynet cluster. +It is your job to nudge them along in a good direction as well as helping to clear roadblocks that they may encounter. +This can be "kidnapping" them so they can be introduced to a key person (see office or other persons of interest), this is outsourcing the solution. +Another approach would be to use yer own life, the successes and especially the failures to chose a path forward (sometimes just the act of moving is enough) +The final approach is to call upon the wisdom of teh Ancients, namely the advisors in the Discord server. -We aim to have money in the budget this year to have twenty meetups, there should also be money for two social meetups. -The social meetups have been historically held in Scholars. -The most important thing to remember is quality over quantity. -Maybe plan bigger events 2 weeks in advance and skip a week. -Events should be organised based on the wants of the members of the computer society but try to have a variety. -For example, if a large base would like to see how to set up WordPress, then you should try to organise a workshop on this. -However, you can't keep everyone happy, so don't try. Your main objective is to have vision, direction and come to conclusions, not to keep the committee happy. -You will make decisions which people will disagree with, but if you have a good committee, they will respect the differences of opinion and move on. -It is up to you to foster the kind of intra-committee relationships that will allow respectful differences of opinion instead of destructive bickering. +You should always be on the lookout for folks who ye suspect might be a good fit for committee next year. +Talk to them, include them, give folks freedom, encourage them to become committee. +The society is student driven, without new voices and viewpoints we would turn into just another echo chamber, and no-body wants that (if ye do then ye may not be the ebst person for teh job).26 -As President, you chair the committee meetings and the societies AGM. -On previous years, Committee Meetings were made early on the week (usually Mondays), but that didn't give much time to organise the event (Wednesday), so this year was changed to Thursdays and it worked very well. -Ideally, all committee members should join the meeting, but it can happen that they can't attend for any reason. I would recommend you to ask them to advise you at least two hours before the meeting starts and to try not to skip many. -You need to ensure that an agenda is prepared before each meeting and email it out to committee a few days beforehand for review. -One recommendation is to set up the thread on Discord with some points days before the meeting, so other people can add up more points to the thread and it gives you time to prepare the agenda. +By now you most likely have contacts in UL, introduce them to yer current committee, share the knowledge. +This is everyone from ITD, CSIS staff and of course the C&S office. +As outlined above "kidnapping" is a valid approach. +Networking (and other soft skills) are immensely important for all who pass through this society ( and I am not just talking about Cat7e and SPF+) -Committee meetings can be held in the Server Room, but being flexible is always good, so some people can join online if they can't make it in person. -Booking a room in the library is also very easy for larger meetings, or if the building is closed. -It's up to you to ensure all those present get a fair chance to put their point across. -It is also important that you know what's happening within the society at all levels. -Since the President is frequently looked up to as the leader (even subconsciously) it is important to hold your own opinions until the others have outlined theirs first. -Allow the discussion to develop before you bring your own opinions to the table, quite often this will be the conclusion of the discussion, with your opinion shaping the final decision of the committee rather than influencing the discussion from the outset. -You also need to keep the committee meetings moving and not allow the committee to become “bogged down” on any one issue. -If any other issue requires major attention a separate meeting should be called with some committee members. - -If the society is buying stuff always try to get a discount or sponsorship as this saves us money and can count as income. -The society has secured a lot of money in sponsorship through the years and this was done by directly contacting companies that we were planning to buy stuff from explain who we were and offer them exposure. -It doesn’t always work but we have been very successful at doing this. +Finally ye are a bridge between different clubs/societies, diversity makes everything better, giving more viewpoints. +As a society we have been and can be a glue, providing services to other Clubs/Socs, try to promote this. +So talk to them, make friends and allies, who knows what intersting mix of collab that might lead to. +Other Clubs/Socs tend to be good folks. -The budget is a very important process and should involve as many committee members as possible throughout the year, it should not be left to one person at the end of the year. -Irregular Expenditure should be voted on by committee. You should be able to look at the submitted budget from the end of September onwards. -Budget points are very important, and you should always be on the lookout for opportunities to gain more points. -Points are given for Guest Speakers, High Profile Speakers, Events, Showcase Events (Big on campus events), Publicity, proper minutes, proper use of Wolves.ie, etc. -At the end of your tenure as President, you must make sure that the incoming President is well briefed on the role. -If possible, it is advisable to retain a role on the next committee to facilitate the transition but be wary of being a backseat President. -If you know in advance that you won’t be seeking re-election as President, you should let the committee know this and start grooming a successor from within the current committee. -You should work to ensure good continuity from one committee to the next. -As the second semester progresses you should be listening to the existing committee about their intentions for the following year, especially core positions. -If people are not planning to take up the same roles the following year, you need to be thinking about who might replace them. -Canvass the committee members for interest in shadowing the core positions with a view to taking over the following year. -On this basis, it’s important to have a good crew of OCMs on board, use the less important positions to bring new people on board each year and ensure they are engaged in the work of the committee through the year. +All in all try to leave teh Soc in a better position than when ye started. +If ye dont succedd its not teh end of the world though, uni is a good palce to be and provices many safetynets. -### Summary -In conclusion it’s a big job with massive responsibility. -It will test you and you will gain new skills when dealing with people. -Appreciate the massive work done by your committee. -This is what makes the society great, you can always ask someone for help. -Don’t be the one stuck with all of the work, delegate tasks. -Best of luck and I look forward to seeing the impact you will make on the society. +have fun and feel free to contact me on discord/email. +Brendan Golden. \ No newline at end of file From fef66199c4e3a1f7c8ab1f3c97e6308af46563f9 Mon Sep 17 00:00:00 2001 From: Brendan Golden Date: Fri, 23 May 2025 21:48:39 +0100 Subject: [PATCH 18/29] budget: tiedied up Committee Development --- .../2024-2025/Budget/07._Committee_Development.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Committee/2024-2025/Budget/07._Committee_Development.md b/Committee/2024-2025/Budget/07._Committee_Development.md index 7d142dc..22cb0de 100644 --- a/Committee/2024-2025/Budget/07._Committee_Development.md +++ b/Committee/2024-2025/Budget/07._Committee_Development.md @@ -1,8 +1,8 @@ ## Committee Development ### Large Committee -We have had twelve titled committee members and two OCM's during this Academic Year. -On top of that we had seven Advisors who are previous committee members. +We have had thirteen titled committee members during this Academic Year. +On top of that we had five Advisors who are previous committee members. As outlined last year having Advisors is extremely important in our society due to the large amount of domain knowledge required to run both the society and the computer cluster. Due to the type of society we are we tend to have unique events on a weekly basis, being able to draw upon the wisdom of the elders helps keeps things running smoothly. @@ -17,14 +17,14 @@ We have the full quota of core positions: The Skynet team has one Head Systems Administrator and two members in training. In the next year or two it is hoped that oen of those will replace the current Head Sysadmin. -Throughout this academic year, there were no major grievances other than the resignation of 2 committee members, our Health & Safety Officer and our Assistant PRO, we replaced the HSO in an AGM and the Assistant PRO's duties were split amongst our Events officer and the incoming HSO by mutual agreement. +Throughout this academic year, there were no major grievances other than the resignation of 2 committee members, our Health & Safety Officer and our Secretary, we subsequently held an EGM to elect new officers as well as make amendments to our constitution. ### Documentation All handover documents have been submitted except those from our advisors, who do not provide handover documents. All minutes have also been submitted. -This year we are trialling a new system called [Open Governance][0] where much of the background work is made available for our members to view (including these points submissions). -It also serves as a long term archive of events, handover documents and minutes going forward. +Our system of [Open Governance][0] has worked incredibly well this past year, with several members of the society who read our minutes and ongoing event planning. +It has also allowed us to build upon last years handovers and budger submissions not to mention helping us identify events we can host on an annual basis. ### Administration From ba86268ef5bcf29e9c1dd08c2ed91f19987d2cc8 Mon Sep 17 00:00:00 2001 From: Brendan Golden Date: Fri, 23 May 2025 22:56:19 +0100 Subject: [PATCH 19/29] budget: initial draft for Guest Speakers --- .../2024-2025/Budget/10._Guest_Speakers.md | 28 ++++--------------- 1 file changed, 6 insertions(+), 22 deletions(-) diff --git a/Committee/2024-2025/Budget/10._Guest_Speakers.md b/Committee/2024-2025/Budget/10._Guest_Speakers.md index adb5e4f..9d5eb78 100644 --- a/Committee/2024-2025/Budget/10._Guest_Speakers.md +++ b/Committee/2024-2025/Budget/10._Guest_Speakers.md @@ -1,27 +1,11 @@ ## Guest speakers -Our first event of the spring semester was Lightning Talks: Co-op. -The goal of this event was to bridge the gap between members returning from Co-op and those that had joined us this year. -Viewers would be able to get insights into what co-op is like, the Good, the Bad and the Ugly. -Individual presenters talked on a variety of topics. -Some talked about opportunities they were given by their company. -We had others give guidance on what was expected by the company as well as what tools and methodologies would give a leg up. -It wasn't all sunshine and roses, presenters also pointed out areas where they -and/or the companies dropped the ball as well as how they would handle them in the future. - -We had eight speakers for this event, all of which are members of LM051 currently -in 3rd year. - -* Amie Patterson -* Bayan Nezamabad -* Brendan Golden -* Milan Kovacs -* Mohammad Humayun -* Prabudda Hans +After our EGM in semester 2 we continued the evening with two guest alumni speakers, talking about their experiences in the field of computer science. +They introduced us to their respective companies and took us on a journey of both understanding and a descent into madness in making systems work in production. +### Speakers +#### Evan _________ +#### Mark _________ ### Event Photos - -![Milan Kovacs & Bayan Nezamabad presenting on their time in Coop](10._Guest_Speakers_01.jpg) - -![The people listening to the lighting talks](10._Guest_Speakers_02.jpg) \ No newline at end of file +(if available) From e84bdae80e8ec09175634e67b82a43ea51a87369 Mon Sep 17 00:00:00 2001 From: Brendan Golden Date: Fri, 23 May 2025 23:03:50 +0100 Subject: [PATCH 20/29] budget: fixed newlines --- .../Budget/07._Committee_Development.md | 26 +++++----- Committee/2024-2025/Budget/08._Performance.md | 16 ++---- Committee/2024-2025/Budget/09._Publicity.md | 2 +- Committee/2024-2025/Handovers/President.md | 52 +++++++++---------- 4 files changed, 45 insertions(+), 51 deletions(-) diff --git a/Committee/2024-2025/Budget/07._Committee_Development.md b/Committee/2024-2025/Budget/07._Committee_Development.md index 22cb0de..184c5fa 100644 --- a/Committee/2024-2025/Budget/07._Committee_Development.md +++ b/Committee/2024-2025/Budget/07._Committee_Development.md @@ -1,13 +1,13 @@ ## Committee Development ### Large Committee -We have had thirteen titled committee members during this Academic Year. -On top of that we had five Advisors who are previous committee members. +We have had thirteen titled committee members during this Academic Year. +On top of that we had five Advisors who are previous committee members. As outlined last year having Advisors is extremely important in our society due to the large amount of domain knowledge required to run both the society and the computer cluster. -Due to the type of society we are we tend to have unique events on a weekly basis, being able to draw upon the wisdom of the elders helps keeps things running smoothly. +Due to the type of society we are we tend to have unique events on a weekly basis, being able to draw upon the wisdom of the elders helps keeps things running smoothly. -We have the full quota of core positions: +We have the full quota of core positions: * President * Secretary * Treasurer @@ -15,24 +15,24 @@ We have the full quota of core positions: * Health and Safety Officer The Skynet team has one Head Systems Administrator and two members in training. -In the next year or two it is hoped that oen of those will replace the current Head Sysadmin. +In the next year or two it is hoped that oen of those will replace the current Head Sysadmin. -Throughout this academic year, there were no major grievances other than the resignation of 2 committee members, our Health & Safety Officer and our Secretary, we subsequently held an EGM to elect new officers as well as make amendments to our constitution. +Throughout this academic year, there were no major grievances other than the resignation of 2 committee members, our Health & Safety Officer and our Secretary, we subsequently held an EGM to elect new officers as well as make amendments to our constitution. ### Documentation -All handover documents have been submitted except those from our advisors, +All handover documents have been submitted except those from our advisors, who do not provide handover documents. All minutes have also been submitted. -Our system of [Open Governance][0] has worked incredibly well this past year, with several members of the society who read our minutes and ongoing event planning. -It has also allowed us to build upon last years handovers and budger submissions not to mention helping us identify events we can host on an annual basis. +Our system of [Open Governance][0] has worked incredibly well this past year, with several members of the society who read our minutes and ongoing event planning. +It has also allowed us to build upon last years handovers and budger submissions not to mention helping us identify events we can host on an annual basis. ### Administration -During the Academic Year, we have held a committee meeting almost every week, that usually lasts between an hour to an hour and a half. +During the Academic Year, we have held a committee meeting almost every week, that usually lasts between an hour to an hour and a half. The Secretary (and President on occasion) took down minutes for the meeting. -For bank statements, any that we received throughout the academic year were uploaded to wolves, though we stopped getting them after semester one despite checking the post regularly. -For dealing with money, there was a delay in getting access to the bank account again, though this was rectified in the later half of semester 2 and all creditors are now paid up. +For bank statements, any that we received throughout the academic year were uploaded to wolves, though we stopped getting them after semester one despite checking the post regularly. +For dealing with money, there was a delay in getting access to the bank account again, though this was rectified in the later half of semester 2 and all creditors are now paid up. -[0]: https://forgejo.skynet.ie/Computer_Society/open-goverance \ No newline at end of file +[0]: https://forgejo.skynet.ie/Computer_Society/open-goverance diff --git a/Committee/2024-2025/Budget/08._Performance.md b/Committee/2024-2025/Budget/08._Performance.md index 416e059..aef170c 100644 --- a/Committee/2024-2025/Budget/08._Performance.md +++ b/Committee/2024-2025/Budget/08._Performance.md @@ -1,14 +1,8 @@ ## Performance -As mentioned in the committee development section, the only grievances that we -had throughout the academic year was the resignation of two of our committee -members, which we replaced through an EGM in semester 2. Other than that there -was no other grievances. +As mentioned in the committee development section, the only grievances that we had throughout the academic year was the resignation of two of our committee members, which we replaced through an EGM in semester 2. +Other than that there was no other grievances. -Also as mentioned in the committee development section, there was a delay in -getting access to our online banking system but that was resolved mid-way through -semester 2 and we repaid everyone at that stage. We wrapped up the year with no -creditors outstanding in line with this. +Also as mentioned in the committee development section, there was a delay in getting access to our online banking system but that was resolved mid-way through semester 2 and we repaid everyone at that stage. +We wrapped up the year with no creditors outstanding in line with this. -Throughout the academic year, the Society has had a consistent number attending -our events and interacting with our society through our Discord Server, this has -created a welcoming environment. +Throughout the academic year, the Society has had a consistent number attending our events and interacting with our society through our Discord Server, this has created a welcoming environment. diff --git a/Committee/2024-2025/Budget/09._Publicity.md b/Committee/2024-2025/Budget/09._Publicity.md index 437b671..ac18a64 100644 --- a/Committee/2024-2025/Budget/09._Publicity.md +++ b/Committee/2024-2025/Budget/09._Publicity.md @@ -33,4 +33,4 @@ Event Announcements can be found [on our gitlab][1] ![Discord announcement on software licensing](09._Publicity_01.png) [0]: https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2023-2024/Posters -[1]: https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2023-2024 \ No newline at end of file +[1]: https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2023-2024 diff --git a/Committee/2024-2025/Handovers/President.md b/Committee/2024-2025/Handovers/President.md index 0d5c922..a9b1c1a 100644 --- a/Committee/2024-2025/Handovers/President.md +++ b/Committee/2024-2025/Handovers/President.md @@ -10,43 +10,43 @@ The purpose of this document is to assist the incoming CompSoc President for the * [2024](../../2023-2024/Handovers/President.md) ### What teh role entails -The role of President of CompSoc is much like the role of the President of Ireland. -Uachtarán na hÉireann does not carry much "power", the main ones being able to Veto legislation as well as signing legislation into law. -Rather the main "power" of the President is diplomacy, with each president to date expanding out this to be what they want to guide the International image of Ireland into being. +The role of President of CompSoc is much like the role of the President of Ireland. +Uachtarán na hÉireann does not carry much "power", the main ones being able to Veto legislation as well as signing legislation into law. +Rather the main "power" of the President is diplomacy, with each president to date expanding out this to be what they want to guide the International image of Ireland into being. -The president of CompSoc fulfils much the same function. +The president of CompSoc fulfils much the same function. * You will be on the bank mandate and can approve payees. * You have a (strong) say in what events teh society does during teh year. * You can sign in as a core committee member to Council. * You have access to teh Captains/Presidents whatsapp grouping. -Thats on paper at least. +Thats on paper at least. -You are Duct Tape and WD40 that keeps the society ticking. -Under you are four other core committee members plus a sysadmin for the Skynet cluster. -It is your job to nudge them along in a good direction as well as helping to clear roadblocks that they may encounter. -This can be "kidnapping" them so they can be introduced to a key person (see office or other persons of interest), this is outsourcing the solution. -Another approach would be to use yer own life, the successes and especially the failures to chose a path forward (sometimes just the act of moving is enough) -The final approach is to call upon the wisdom of teh Ancients, namely the advisors in the Discord server. +You are Duct Tape and WD40 that keeps the society ticking. +Under you are four other core committee members plus a sysadmin for the Skynet cluster. +It is your job to nudge them along in a good direction as well as helping to clear roadblocks that they may encounter. +This can be "kidnapping" them so they can be introduced to a key person (see office or other persons of interest), this is outsourcing the solution. +Another approach would be to use yer own life, the successes and especially the failures to chose a path forward (sometimes just the act of moving is enough) +The final approach is to call upon the wisdom of teh Ancients, namely the advisors in the Discord server. -You should always be on the lookout for folks who ye suspect might be a good fit for committee next year. -Talk to them, include them, give folks freedom, encourage them to become committee. -The society is student driven, without new voices and viewpoints we would turn into just another echo chamber, and no-body wants that (if ye do then ye may not be the ebst person for teh job).26 +You should always be on the lookout for folks who ye suspect might be a good fit for committee next year. +Talk to them, include them, give folks freedom, encourage them to become committee. +The society is student driven, without new voices and viewpoints we would turn into just another echo chamber, and no-body wants that (if ye do then ye may not be the ebst person for teh job). -By now you most likely have contacts in UL, introduce them to yer current committee, share the knowledge. -This is everyone from ITD, CSIS staff and of course the C&S office. -As outlined above "kidnapping" is a valid approach. -Networking (and other soft skills) are immensely important for all who pass through this society ( and I am not just talking about Cat7e and SPF+) +By now you most likely have contacts in UL, introduce them to yer current committee, share the knowledge. +This is everyone from ITD, CSIS staff and of course the C&S office. +As outlined above "kidnapping" is a valid approach. +Networking (and other soft skills) are immensely important for all who pass through this society ( and I am not just talking about Cat7e and SPF+) -Finally ye are a bridge between different clubs/societies, diversity makes everything better, giving more viewpoints. -As a society we have been and can be a glue, providing services to other Clubs/Socs, try to promote this. -So talk to them, make friends and allies, who knows what intersting mix of collab that might lead to. -Other Clubs/Socs tend to be good folks. +Finally ye are a bridge between different clubs/societies, diversity makes everything better, giving more viewpoints. +As a society we have been and can be a glue, providing services to other Clubs/Socs, try to promote this. +So talk to them, make friends and allies, who knows what intersting mix of collab that might lead to. +Other Clubs/Socs tend to be good folks. -All in all try to leave teh Soc in a better position than when ye started. -If ye dont succedd its not teh end of the world though, uni is a good palce to be and provices many safetynets. +All in all try to leave teh Soc in a better position than when ye started. +If ye dont succedd its not teh end of the world though, uni is a good palce to be and provices many safetynets. -have fun and feel free to contact me on discord/email. -Brendan Golden. \ No newline at end of file +Have fun and feel free to contact me on discord/email. +Brendan Golden. From 45a3c3ac3115dc7eae770975bb9e0c6b4962faf9 Mon Sep 17 00:00:00 2001 From: Nanda128 Date: Fri, 23 May 2025 23:33:43 +0100 Subject: [PATCH 21/29] publicity: update publicity.md and fixed annoying typo in my handover doc --- Committee/2024-2025/Budget/09._Publicity.md | 49 +++++++++++-------- .../Budget/Pictures/09._Publicity_01.png | 3 ++ .../Budget/Pictures/09._Publicity_02.png | 3 ++ Committee/2024-2025/Handovers/PRO.md | 2 +- 4 files changed, 36 insertions(+), 21 deletions(-) create mode 100644 Committee/2024-2025/Budget/Pictures/09._Publicity_01.png create mode 100644 Committee/2024-2025/Budget/Pictures/09._Publicity_02.png diff --git a/Committee/2024-2025/Budget/09._Publicity.md b/Committee/2024-2025/Budget/09._Publicity.md index ac18a64..c853b5a 100644 --- a/Committee/2024-2025/Budget/09._Publicity.md +++ b/Committee/2024-2025/Budget/09._Publicity.md @@ -1,36 +1,45 @@ ## Publicity -Over the course of the year, we had our 21 events listed on wolves and announced on Discord. +Over the course of the year, we ran a total of 25 events, all listed on wolves and announced on Discord. -We had a regular weekly activity on Wednesday. -We utilized our Discord Server and emails to inform our members of upcoming events and opportunities. -Our Discord server was our social hub of communication between members and committee. -Our Discord server has now grown to have ~300 members. +We ran regular weekly activities on Wednesday, +using our Discord Server and emails to inform our members of upcoming events and opportunities. +Our Discord server was our social hub of communication between members and committee +and has now grown to have ~300 members. -Midway through Semester two however, we started having a regular bi-weekly Minecraft event on Saturdays. -These were announced primarily through Discord. +We also collaborated a lot with other societies, which helped bring a lot of new eyes to us and to what we do. -We used graphic design for our posters, but were used minimally and reserved for larger announcements such as -our regular weekly activity. +We used posters for larger events, since we began putting more effort and quality into the creation of our posters. +This helped create a more professional image for our society and helped us stand out from other societies. ### Other Societies -We worked with a number of Societies over the last year which has meant that when -advertising our events. They would be advertised by the other societies on their own discord -servers and instagram which we think gave both societies a boost as it meant that -people who may not have known about what we do or talked to us were given a chance -to get a taste of what our society does and talk with our members +We worked with several Societies over the last year +which has meant more advertising for our society in addition to helping other societies grow. +This includes collaborations and larger-scale events like our Birthday event, SISTEM, and our Unity Workshop. + +![Games Soc poster on the Birthday Event](Pictures/09._Publicity_01.png) +![Poster for SISTEM Event](Pictures/09._Publicity_02.png) -![Games Soc post on the Retro Pi Event](09._Publicity_02.png) ### Posters -Posters can be found [on our gitlab][0] +This year included a shift in our approach to posters. +We decided to put more effort and quality into the creation of our posters, +which also made them difficult to create for weekly events. +Thus, +we could ensure that our larger events had more powerful visuals +and helped communicate to our members that this event is more significant than our weekly events. + +Posters can be found [on our forgejo][0] ### Event Announcements -Event Announcements can be found [on our gitlab][1] +We primarily used Discord and Emails for our event announcements, +while prompting our users to sign up for events on Wolves. +This helped us keep track of who was attending our events and allowed us to send out reminders to our members. +Our Discord server also allowed us to quickly issue reminders or updates to our members, which greatly improved our communication. -![Discord announcement on software licensing](09._Publicity_01.png) +Event Announcements can be found [on our forgejo][1] -[0]: https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2023-2024/Posters -[1]: https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2023-2024 +[0]: https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2024-2025/Posters +[1]: https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2024-2025 diff --git a/Committee/2024-2025/Budget/Pictures/09._Publicity_01.png b/Committee/2024-2025/Budget/Pictures/09._Publicity_01.png new file mode 100644 index 0000000..ec41206 --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/09._Publicity_01.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7596cb82c93fa80916b7167a4b88534cfd50d5008b56f5de11376fd90af779a7 +size 2915254 diff --git a/Committee/2024-2025/Budget/Pictures/09._Publicity_02.png b/Committee/2024-2025/Budget/Pictures/09._Publicity_02.png new file mode 100644 index 0000000..7f63eb4 --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/09._Publicity_02.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85585bfc1b8888f1e046bb6c59ba8d06e09a78658e99afa007057f43dd53a135 +size 1853582 diff --git a/Committee/2024-2025/Handovers/PRO.md b/Committee/2024-2025/Handovers/PRO.md index 05ab72e..5463464 100644 --- a/Committee/2024-2025/Handovers/PRO.md +++ b/Committee/2024-2025/Handovers/PRO.md @@ -228,7 +228,7 @@ People are more likely to accept other people helping than they are to ask for h ### Summary -The Public Relations Officer is a committee position who's main purpose is to manage, well, the Public Relations of UL +The Public Relations Officer is a committee position whose main purpose is to manage, well, the Public Relations of UL CompSoc. Your job will be to announce events, keep people informed, maybe promote things, take pictures, and archive events. Depending on the situation, you might also be the first point of contact for people who want to talk to the society. From ba8b364d653d3eab51f9f84761f282c7acc98d76 Mon Sep 17 00:00:00 2001 From: Nanda128 Date: Sat, 24 May 2025 00:32:01 +0100 Subject: [PATCH 22/29] showcases: updated showcases.md to update SISTEM info and PyCon '24 --- Committee/2024-2025/Budget/13._Showcases.md | 44 +++++++++++++++------ 1 file changed, 31 insertions(+), 13 deletions(-) diff --git a/Committee/2024-2025/Budget/13._Showcases.md b/Committee/2024-2025/Budget/13._Showcases.md index 35be5e1..eeb84e7 100644 --- a/Committee/2024-2025/Budget/13._Showcases.md +++ b/Committee/2024-2025/Budget/13._Showcases.md @@ -1,21 +1,39 @@ ## Showcases -### PyCon Ireland 2023 Trip +### PyCon Ireland 2024 Trip -For proof of trip attendance please see <> +To prove trip attendance, please see <> -This was a trip made by UL Computer Society to PyCon Ireland 2023, hosted in the Radisson Blu Hotel in Dublin on November 11th-November 12th, 2023. +This was a trip made by UL Computer Society to PyCon Ireland 2024, +hosted in the Radisson Blu Hotel in Dublin on November 16th-November 17th, 2024. This section will cover the organization of the trip. -Since we had to find transportation for this trip, preparation for this event took a lot of organization. -We needed to find transport for all Computer Society members that wanted to attend the event from Limerick to Dublin and back to Limerick without being late for the event in addition to getting tickets for our members, the cost of which was subsidized by the Society itself. -We were able to coordinate the committee towards surveying our members to find those that were interested in attending the conference, finding and paying for transportation to and from Limerick to Dublin, and negotiating bulk ticket purchasing deals with the staff at PyCon Ireland. -Once we had the numbers regarding who were planning on attending, we booked the tickets for the events and the buses from Limerick to Dublin and back. -Things went smoothly, and we were able to adhere to our initial itinerary. -The return journey also went smoothly. +Since we had to find transportation for this trip, preparation for this event took a lot of organization. +Thankfully, we had lots of information from previous years to help us with this. +We arranged transport for all members to and from Dublin & Limerick, and their event tickets. +The cost for both transport and tickets was subsidized from us, +making attendance to the event much cheaper for our members. +We used interest checks and surveys to gauge how many members were interested in attending the event, using that information to know how many tickets we needed to buy. +We were also able to negotiate a group discount for the tickets, which helped us save money. +Once we had the numbers regarding who were planning on attending, +we booked the tickets for the events and the buses from Limerick to Dublin and back. +Things went smoothly, and we were able to adhere to our initial itinerary. +We didn't have to rush coming back to Limerick, since we gave ourselves plenty of time to get back. +This gave us more time for things like unplanned bathroom breaks. -### RetroPi +### SISTEM -In Semester 2 of this year we ran a RetroPi presentation event in which our Society collaborated with UL Games Development Society and Games Society to present RetroPi, a system that uses Raspberry Pis to play retro games. -We made an interactive presentation where we showed off what the Raspberry Pi is capable of, and demonstrated how it can be used to play retro arcade games. -It also offered our members a hands-on demonstration of how Raspberry Pis work and how we can run programs on it. +In Semester 2 of this year we helped run an event called SISTEM, +the Student Inter-Society Technology and Enterprise Meetup. +This was a large event that happened in the Kemmy Business School on March 29th, 2025. +Usually, this event is run by multiple societies, across multiple universities in Ireland. +It is the largest event of its kind in Ireland, an entirely-student run event. + +We had 30-40 people attending, across multiple universities, like UL, UCC, and UCD. +The event also gathered sponsorship from LERO, and assistance from Google. + +In addition to the sponsorship and assistance, we also had industry speakers from companies like Google, and LERO at the event. +They would give talks about specific topics they're currently working on, with plenty of time for questions and answers. + +One of the more impressive events that UL Computer Society was able to run this year, +we were able to hit the record for the number of pizzas ordered for an event in UL history. From 9a03ce048d14eeaf68f578ca93e4eb894221b5c2 Mon Sep 17 00:00:00 2001 From: Nanda128 Date: Sat, 24 May 2025 16:46:53 +0100 Subject: [PATCH 23/29] publicity/showcase: improve formatting and readability in Publicity and Showcases documents --- Committee/2024-2025/Budget/09._Publicity.md | 43 +++++++++---------- Committee/2024-2025/Budget/13._Showcases.md | 47 ++++++++++----------- 2 files changed, 43 insertions(+), 47 deletions(-) diff --git a/Committee/2024-2025/Budget/09._Publicity.md b/Committee/2024-2025/Budget/09._Publicity.md index c853b5a..4e47089 100644 --- a/Committee/2024-2025/Budget/09._Publicity.md +++ b/Committee/2024-2025/Budget/09._Publicity.md @@ -1,21 +1,20 @@ ## Publicity -Over the course of the year, we ran a total of 25 events, all listed on wolves and announced on Discord. +Over the course of the year, we ran a total of 25 events, all listed on wolves and announced on Discord. -We ran regular weekly activities on Wednesday, -using our Discord Server and emails to inform our members of upcoming events and opportunities. -Our Discord server was our social hub of communication between members and committee -and has now grown to have ~300 members. +We ran regular weekly activities on Wednesday, using our Discord Server and emails to inform our members of upcoming events and opportunities. +Our Discord server was our social hub of communication between members and committee +and has now grown to have ~300 members. -We also collaborated a lot with other societies, which helped bring a lot of new eyes to us and to what we do. +We also collaborated a lot with other societies, which helped bring a lot of new eyes to us and to what we do. -We used posters for larger events, since we began putting more effort and quality into the creation of our posters. -This helped create a more professional image for our society and helped us stand out from other societies. +We used posters for larger events, since we began putting more effort and quality into the creation of our posters. +This helped create a more professional image for our society and helped us stand out from other societies. ### Other Societies -We worked with several Societies over the last year -which has meant more advertising for our society in addition to helping other societies grow. -This includes collaborations and larger-scale events like our Birthday event, SISTEM, and our Unity Workshop. +We worked with several Societies over the last year +which has meant more advertising for our society in addition to helping other societies grow. +This includes collaborations and larger-scale events like our Birthday event, SISTEM, and our Unity Workshop. ![Games Soc poster on the Birthday Event](Pictures/09._Publicity_01.png) ![Poster for SISTEM Event](Pictures/09._Publicity_02.png) @@ -23,23 +22,21 @@ This includes collaborations and larger-scale events like our Birthday event, SI ### Posters -This year included a shift in our approach to posters. -We decided to put more effort and quality into the creation of our posters, -which also made them difficult to create for weekly events. -Thus, -we could ensure that our larger events had more powerful visuals -and helped communicate to our members that this event is more significant than our weekly events. +This year included a shift in our approach to posters. +We decided to put more effort and quality into the creation of our posters, which also made them difficult to create for weekly events. +Thus, we could ensure that our larger events had more powerful visuals +and helped communicate to our members that this event is more significant than our weekly events. -Posters can be found [on our forgejo][0] +Posters can be found [on our forgejo][0] ### Event Announcements -We primarily used Discord and Emails for our event announcements, -while prompting our users to sign up for events on Wolves. -This helped us keep track of who was attending our events and allowed us to send out reminders to our members. -Our Discord server also allowed us to quickly issue reminders or updates to our members, which greatly improved our communication. +We primarily used Discord and Emails for our event announcements, +while prompting our users to sign up for events on Wolves. +This helped us keep track of who was attending our events and allowed us to send out reminders to our members. +Our Discord server also allowed us to quickly issue reminders or updates to our members, which greatly improved our communication. -Event Announcements can be found [on our forgejo][1] +Event Announcements can be found [on our forgejo][1] [0]: https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2024-2025/Posters [1]: https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2024-2025 diff --git a/Committee/2024-2025/Budget/13._Showcases.md b/Committee/2024-2025/Budget/13._Showcases.md index eeb84e7..0c72980 100644 --- a/Committee/2024-2025/Budget/13._Showcases.md +++ b/Committee/2024-2025/Budget/13._Showcases.md @@ -4,36 +4,35 @@ To prove trip attendance, please see <> -This was a trip made by UL Computer Society to PyCon Ireland 2024, +This was a trip made by UL Computer Society to PyCon Ireland 2024, hosted in the Radisson Blu Hotel in Dublin on November 16th-November 17th, 2024. This section will cover the organization of the trip. -Since we had to find transportation for this trip, preparation for this event took a lot of organization. -Thankfully, we had lots of information from previous years to help us with this. -We arranged transport for all members to and from Dublin & Limerick, and their event tickets. -The cost for both transport and tickets was subsidized from us, -making attendance to the event much cheaper for our members. -We used interest checks and surveys to gauge how many members were interested in attending the event, using that information to know how many tickets we needed to buy. -We were also able to negotiate a group discount for the tickets, which helped us save money. -Once we had the numbers regarding who were planning on attending, -we booked the tickets for the events and the buses from Limerick to Dublin and back. -Things went smoothly, and we were able to adhere to our initial itinerary. -We didn't have to rush coming back to Limerick, since we gave ourselves plenty of time to get back. -This gave us more time for things like unplanned bathroom breaks. +Since we had to find transportation for this trip, preparation for this event took a lot of organization. +Thankfully, we had lots of information from previous years to help us with this. +We arranged transport for all members to and from Dublin & Limerick, and their event tickets. +The cost for both transport and tickets was subsidized from us, making attendance to the event much cheaper for our members. +We used interest checks and surveys to gauge how many members were interested in attending the event, using that information to know how many tickets we needed to buy. +We were also able to negotiate a group discount for the tickets, which helped us save money. +Once we had the numbers regarding who were planning on attending, +we booked the tickets for the events and the buses from Limerick to Dublin and back. +Things went smoothly, and we were able to adhere to our initial itinerary. +We didn't have to rush coming back to Limerick, since we gave ourselves plenty of time to get back. +This gave us more time for things like unplanned bathroom breaks. ### SISTEM -In Semester 2 of this year we helped run an event called SISTEM, -the Student Inter-Society Technology and Enterprise Meetup. -This was a large event that happened in the Kemmy Business School on March 29th, 2025. -Usually, this event is run by multiple societies, across multiple universities in Ireland. -It is the largest event of its kind in Ireland, an entirely-student run event. +In Semester 2 of this year we helped run an event called SISTEM, +the Student Inter-Society Technology and Enterprise Meetup. +This was a large event that happened in the Kemmy Business School on March 29th, 2025. +Usually, this event is run by multiple societies, across multiple universities in Ireland. +It is the largest event of its kind in Ireland, an entirely-student run event. -We had 30-40 people attending, across multiple universities, like UL, UCC, and UCD. -The event also gathered sponsorship from LERO, and assistance from Google. +We had 30–40 people attending, across multiple universities, like UL, UCC, and UCD. +The event also gathered sponsorship from LERO, and assistance from Google. -In addition to the sponsorship and assistance, we also had industry speakers from companies like Google, and LERO at the event. -They would give talks about specific topics they're currently working on, with plenty of time for questions and answers. +In addition to the sponsorship and assistance, we also had industry speakers from companies like Google, and LERO at the event. +They would give talks about specific topics they're currently working on, with plenty of time for questions and answers. -One of the more impressive events that UL Computer Society was able to run this year, -we were able to hit the record for the number of pizzas ordered for an event in UL history. +One of the more impressive events that UL Computer Society was able to run this year, +we were able to hit the record for the number of pizzas ordered for an event in UL history. From f3cef149bc6330493ad27150158f9be367b26af1 Mon Sep 17 00:00:00 2001 From: Nanda128 Date: Sat, 24 May 2025 18:02:13 +0100 Subject: [PATCH 24/29] publicity: replace accidental comma-newline combos, oopsie daisy --- Committee/2024-2025/Budget/09._Publicity.md | 3 +-- Committee/2024-2025/Budget/13._Showcases.md | 14 +++++--------- 2 files changed, 6 insertions(+), 11 deletions(-) diff --git a/Committee/2024-2025/Budget/09._Publicity.md b/Committee/2024-2025/Budget/09._Publicity.md index 4e47089..52bd94c 100644 --- a/Committee/2024-2025/Budget/09._Publicity.md +++ b/Committee/2024-2025/Budget/09._Publicity.md @@ -2,8 +2,7 @@ Over the course of the year, we ran a total of 25 events, all listed on wolves and announced on Discord. We ran regular weekly activities on Wednesday, using our Discord Server and emails to inform our members of upcoming events and opportunities. -Our Discord server was our social hub of communication between members and committee -and has now grown to have ~300 members. +Our Discord server was our social hub of communication between members and committee and has now grown to have ~300 members. We also collaborated a lot with other societies, which helped bring a lot of new eyes to us and to what we do. diff --git a/Committee/2024-2025/Budget/13._Showcases.md b/Committee/2024-2025/Budget/13._Showcases.md index 0c72980..bf307fb 100644 --- a/Committee/2024-2025/Budget/13._Showcases.md +++ b/Committee/2024-2025/Budget/13._Showcases.md @@ -4,9 +4,8 @@ To prove trip attendance, please see <> -This was a trip made by UL Computer Society to PyCon Ireland 2024, -hosted in the Radisson Blu Hotel in Dublin on November 16th-November 17th, 2024. -This section will cover the organization of the trip. +This was a trip made by UL Computer Society to PyCon Ireland 2024, hosted in the Radisson Blu Hotel in Dublin on November 16th-November 17th, 2024. +This section will cover the organization of that trip. Since we had to find transportation for this trip, preparation for this event took a lot of organization. Thankfully, we had lots of information from previous years to help us with this. @@ -14,16 +13,14 @@ We arranged transport for all members to and from Dublin & Limerick, and their e The cost for both transport and tickets was subsidized from us, making attendance to the event much cheaper for our members. We used interest checks and surveys to gauge how many members were interested in attending the event, using that information to know how many tickets we needed to buy. We were also able to negotiate a group discount for the tickets, which helped us save money. -Once we had the numbers regarding who were planning on attending, -we booked the tickets for the events and the buses from Limerick to Dublin and back. +Once we had the numbers regarding who were planning on attending, we booked the tickets for the events and the buses from Limerick to Dublin and back. Things went smoothly, and we were able to adhere to our initial itinerary. We didn't have to rush coming back to Limerick, since we gave ourselves plenty of time to get back. This gave us more time for things like unplanned bathroom breaks. ### SISTEM -In Semester 2 of this year we helped run an event called SISTEM, -the Student Inter-Society Technology and Enterprise Meetup. +In Semester 2 of this year we helped run an event called SISTEM, the Student Inter-Society Technology and Enterprise Meetup. This was a large event that happened in the Kemmy Business School on March 29th, 2025. Usually, this event is run by multiple societies, across multiple universities in Ireland. It is the largest event of its kind in Ireland, an entirely-student run event. @@ -34,5 +31,4 @@ The event also gathered sponsorship from LERO, and assistance from Google. In addition to the sponsorship and assistance, we also had industry speakers from companies like Google, and LERO at the event. They would give talks about specific topics they're currently working on, with plenty of time for questions and answers. -One of the more impressive events that UL Computer Society was able to run this year, -we were able to hit the record for the number of pizzas ordered for an event in UL history. +One of the more impressive events that UL Computer Society was able to run this year, we were able to hit the record for the number of pizzas ordered for an event in UL history. From 133883b10cdf4a57873312789959e60ba27edbec Mon Sep 17 00:00:00 2001 From: Brendan Golden Date: Sun, 25 May 2025 09:24:08 +0100 Subject: [PATCH 25/29] budget: profile speakers --- .../2024-2025/Budget/10._Guest_Speakers.md | 13 ++++-- .../2024-2025/Budget/11._Profile_Speakers.md | 46 ++++++------------- .../Pictures/11._Profile_Speakers_01.jpg | 3 ++ .../Pictures/11._Profile_Speakers_03.jpg | 3 ++ 4 files changed, 29 insertions(+), 36 deletions(-) create mode 100644 Committee/2024-2025/Budget/Pictures/11._Profile_Speakers_01.jpg create mode 100644 Committee/2024-2025/Budget/Pictures/11._Profile_Speakers_03.jpg diff --git a/Committee/2024-2025/Budget/10._Guest_Speakers.md b/Committee/2024-2025/Budget/10._Guest_Speakers.md index 9d5eb78..aa47af5 100644 --- a/Committee/2024-2025/Budget/10._Guest_Speakers.md +++ b/Committee/2024-2025/Budget/10._Guest_Speakers.md @@ -4,8 +4,13 @@ After our EGM in semester 2 we continued the evening with two guest alumni speak They introduced us to their respective companies and took us on a journey of both understanding and a descent into madness in making systems work in production. ### Speakers -#### Evan _________ -#### Mark _________ +#### Evan Cassidy +Evan is an Electronics Engineer working at Analog Devices with three years of industry experience. +Evan graduated from UL with a Bachelors in Electronic and Computer Engineering. +He was previously a committee member of Compsoc. + +#### Mark Mc Nabola +Mark is a software engineer working at Cisco on video conferencing devices and has four years of experience.. +Mark graduated from UL with a Bachelors in Computer Systems. +He was previously a committee member of Compsoc, being on committee for all four years of his degree. -### Event Photos -(if available) diff --git a/Committee/2024-2025/Budget/11._Profile_Speakers.md b/Committee/2024-2025/Budget/11._Profile_Speakers.md index 1e1341d..fef89e1 100644 --- a/Committee/2024-2025/Budget/11._Profile_Speakers.md +++ b/Committee/2024-2025/Budget/11._Profile_Speakers.md @@ -1,32 +1,27 @@ ## Profile Speakers -This year 30 members of Computer Society attended PyCon 2023 in the Radisson Blu Royal Hotel Dublin. +This year 30 members of Computer Society attended PyCon 2024 in the Radisson Blu Royal Hotel Dublin. PyCon is an international conference about the programming language Python. There are several PyCon conferences run in Europe each year, with the Dublin one being one of the largest ones. As such there is a large variety of top tier and distinguished presenters. While it is a two-day event we were only able to attend the Saturday of it. -### Pablo Galindo Salgado -#### The snake of Theseus -Pablo was the keynote speaker for Saturday of this conference. -His presentation was focusing on how the language itself has changed over time, so much so that the original code has all been replaced. -Yet it is still Python. -Even with Countless contributors over the years Python has changed, yet remained the same. -Different syntax, personalities and methodologies have contributed to shaping the language to what it is today and inspiring it forwards into the future. +### Mykalin Jones +#### A journey into Regular Expressions +I am a Particle Physicist-turned-Data Analyst with over a decade of teaching experience. +I have written curricula for various topics including Python for Children, The Basics of Python, Intermediate Python, and Data Science for Beginners. +I provide individual and group classes on all of these topics as well as maths, science, and standardized test prep. +I am currently based in France, but I especially enjoy traveling as much as possible and discovering different cultures and languages. -![Pycon Info card on Pablo Galindo Salgado](11._Profile_Speakers_01.png) +![Pycon Info card on Mykalin Jones](11._Profile_Speakers_01.jpg) -### Mia Bajić -#### The Standard Library TourK -Mia is a regular speaker at Python Conferences as well as co-organising the Prague PyCon in 2023. +### Marcel-Jan Krijgsman +#### E-ink dashboards everywhere +Marcel-Jan Krijgsman is a senior data engineer with 25 years experience in data. +Learning Python when switching his career to data engineering, he used it to plot locations of cycling videos on a map, to land rockets in a computer game and automatically categorise space and astronomy news. -Her talk was aimed at enlightening attendees by informing them of the tools they did not know they needed, the unknown unknowns. -She opened up the powerful functions and methods contained within the inbuilt library to show us what we had been missing before now. -It was quite interesting seeing the emotions flash through the audience when folks realised that there were inbuilt and easier ways to handle objects and arrays. -Everyone left the lecture hall knowing far more than they entered. - -![Pycon Info card on Mia Bajić](11._Profile_Speakers_02.png) +![Pycon Info card on Marcel-Jan Krijgsman](11._Profile_Speakers_02.jpg) ### Rodrigo Girão Serrão #### How to implement a Python-like programming language @@ -38,17 +33,4 @@ Within the two hours participants had constructed a small functional language an Several of the attendees from our group have continued to work on their own language, taking inspiration from this workshop -![Pycon Info card on Rodrigo Girão Serrão](11._Profile_Speakers_03.png) - -### Steve Holden -#### The death of PyCon -Steve is the founder of PyCon. -He has been the Chairman and a director of the Python Foundation. - -He had the honor of opening the Lightning Talks for the conference. -Lightning Talks are 5-minute presentations where anyone can volunteer to present. - -His chosen topic was ``The Death of PyCon`` where he outlined that community run events die if all the attendees stand back and watch. -The way forward is to roll up your sleeves and pitch in, in doing so it is a far better experience for all involved. - -<> +![Pycon Info card on Rodrigo Girão Serrão](11._Profile_Speakers_03.jpg) diff --git a/Committee/2024-2025/Budget/Pictures/11._Profile_Speakers_01.jpg b/Committee/2024-2025/Budget/Pictures/11._Profile_Speakers_01.jpg new file mode 100644 index 0000000..3ea4e6b --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/11._Profile_Speakers_01.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:679185d5365a604b1648c59e36de2e3cdfd5f2f8af3a2ac6f277c8b1ec99cf3e +size 31121 diff --git a/Committee/2024-2025/Budget/Pictures/11._Profile_Speakers_03.jpg b/Committee/2024-2025/Budget/Pictures/11._Profile_Speakers_03.jpg new file mode 100644 index 0000000..f652988 --- /dev/null +++ b/Committee/2024-2025/Budget/Pictures/11._Profile_Speakers_03.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8f2077128e7bed20bfa595b1c78d30892fdfceb2988e53ae99d454c9ae5562b +size 16830 From 5f27ff20b2c59544307ac8eab800a14a580b4895 Mon Sep 17 00:00:00 2001 From: Brendan Golden Date: Sun, 25 May 2025 22:36:53 +0100 Subject: [PATCH 26/29] budget: fix profile speakers --- .../2024-2025/Budget/11._Profile_Speakers.md | 16 ++-------------- ...eakers_03.jpg => 11._Profile_Speakers_02.jpg} | 0 2 files changed, 2 insertions(+), 14 deletions(-) rename Committee/2024-2025/Budget/Pictures/{11._Profile_Speakers_03.jpg => 11._Profile_Speakers_02.jpg} (100%) diff --git a/Committee/2024-2025/Budget/11._Profile_Speakers.md b/Committee/2024-2025/Budget/11._Profile_Speakers.md index fef89e1..4a6c8c9 100644 --- a/Committee/2024-2025/Budget/11._Profile_Speakers.md +++ b/Committee/2024-2025/Budget/11._Profile_Speakers.md @@ -14,23 +14,11 @@ I have written curricula for various topics including Python for Children, The B I provide individual and group classes on all of these topics as well as maths, science, and standardized test prep. I am currently based in France, but I especially enjoy traveling as much as possible and discovering different cultures and languages. -![Pycon Info card on Mykalin Jones](11._Profile_Speakers_01.jpg) +![Pycon Info card on Mykalin Jones](./Pictures/11._Profile_Speakers_01.jpg) ### Marcel-Jan Krijgsman #### E-ink dashboards everywhere Marcel-Jan Krijgsman is a senior data engineer with 25 years experience in data. Learning Python when switching his career to data engineering, he used it to plot locations of cycling videos on a map, to land rockets in a computer game and automatically categorise space and astronomy news. -![Pycon Info card on Marcel-Jan Krijgsman](11._Profile_Speakers_02.jpg) - -### Rodrigo Girão Serrão -#### How to implement a Python-like programming language -Rodrigo is an educator for mathematics and Python, particularly in the area of data processing and analysis. - -His main section in the conference was a workshop on how to create a new programming language by using Python. -This was an engaging introduction to compilers, a topic that is only covered by Computer Science in 4th year. -Within the two hours participants had constructed a small functional language and were given the tools/knowledge to work on it further. -Several of the attendees from our group have continued to work on their own language, taking inspiration from this workshop - - -![Pycon Info card on Rodrigo Girão Serrão](11._Profile_Speakers_03.jpg) +![Pycon Info card on Marcel-Jan Krijgsman](./Pictures/11._Profile_Speakers_02.jpg) \ No newline at end of file diff --git a/Committee/2024-2025/Budget/Pictures/11._Profile_Speakers_03.jpg b/Committee/2024-2025/Budget/Pictures/11._Profile_Speakers_02.jpg similarity index 100% rename from Committee/2024-2025/Budget/Pictures/11._Profile_Speakers_03.jpg rename to Committee/2024-2025/Budget/Pictures/11._Profile_Speakers_02.jpg From 1df8bd2044dcabe398f167759c7fc788e09d9367 Mon Sep 17 00:00:00 2001 From: Eoghan Conlon Date: Sun, 25 May 2025 23:55:14 +0100 Subject: [PATCH 27/29] Adding text on Wiki pages & moving Users to a more natural place Signed-off-by: Eoghan Conlon --- Committee/2024-2025/Handovers/Treasurer.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/Committee/2024-2025/Handovers/Treasurer.md b/Committee/2024-2025/Handovers/Treasurer.md index 9bc052a..cb59dcd 100644 --- a/Committee/2024-2025/Handovers/Treasurer.md +++ b/Committee/2024-2025/Handovers/Treasurer.md @@ -74,7 +74,8 @@ If you are in doubt about anything, ping Eoghan (eoghanconlon73), or the advisor #### Banking ##### Bank Mandate -{Information on bank mandate} +The process for this will be on the Skynet wiki under committee, a link will be added here after budget submission once +the page has gone live. ##### Business online ###### Admin @@ -106,6 +107,10 @@ Once that form is filled in the request will be processed, then everyone will be * 1 of the previous user's usernames * Daily Control Limit +###### Users +Once the Admin account has been signed in, you can set up the user accounts for those that will be using the account, +usually the President, Secretary & Treasurer, the account signatories. + ##### Bank Transfers Bank transfers are the main way that we have of reimbursing committee members for purchasing things for the Society, there are cut-off times for this, where the most up to date version can be seen [here](https://businessbanking.bankofireland.com/payments-and-cards/online-banking/business-online/payment-cut-off-times/). @@ -117,8 +122,10 @@ I have also included the relevant cut-off times as of the time of writing (1/5/2 | SEPA Payments (to Irish Accounts) | Next Day | 5.00pm | | SEPA Payments (to EU Zone) | Next Day | 5.00pm | -###### Users -Once the Admin account has been signed in, you can set up the user accounts for those that will be using the account, usually the President, Secretary & Treasurer, the account signatories. +##### Sum-up +The process for this will be on the Skynet wiki under committee, a link will be added here after budget submission once +the page has gone live. + ### Summary The Treasurer is one of the most important roles on committee, it helps with the running of the Society. Make sure that From 77b66cdaa7a0a81c8f5cdc633914dfeb0a1f52a9 Mon Sep 17 00:00:00 2001 From: Eoghan Conlon Date: Sun, 25 May 2025 23:55:47 +0100 Subject: [PATCH 28/29] Formatting. Adding new line to long line in Admin section of Business online Signed-off-by: Eoghan Conlon --- Committee/2024-2025/Handovers/Treasurer.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Committee/2024-2025/Handovers/Treasurer.md b/Committee/2024-2025/Handovers/Treasurer.md index cb59dcd..fa9c87c 100644 --- a/Committee/2024-2025/Handovers/Treasurer.md +++ b/Committee/2024-2025/Handovers/Treasurer.md @@ -79,7 +79,8 @@ the page has gone live. ##### Business online ###### Admin -For this, you need to fill in a form at https://businessbanking.bankofireland.com/payments-and-cards/online-banking/business-online/update-your-details/ to change your administrator details. For this, we need some information, listed below. +For this, you need to fill in a form at https://businessbanking.bankofireland.com/payments-and-cards/online-banking/business-online/update-your-details/ +to change your administrator details. For this, we need some information, listed below. | | | |-----------------------------------|-------------------------------------------------------------| From e3fa5d775e3fde81f6d620d8f89010f0f7933ff8 Mon Sep 17 00:00:00 2001 From: Eoghan Conlon Date: Sun, 25 May 2025 23:59:31 +0100 Subject: [PATCH 29/29] Formatting. Removing additional newline at the end of the Sum-up section Signed-off-by: Eoghan Conlon --- Committee/2024-2025/Handovers/Treasurer.md | 1 - 1 file changed, 1 deletion(-) diff --git a/Committee/2024-2025/Handovers/Treasurer.md b/Committee/2024-2025/Handovers/Treasurer.md index fa9c87c..079512f 100644 --- a/Committee/2024-2025/Handovers/Treasurer.md +++ b/Committee/2024-2025/Handovers/Treasurer.md @@ -127,7 +127,6 @@ I have also included the relevant cut-off times as of the time of writing (1/5/2 The process for this will be on the Skynet wiki under committee, a link will be added here after budget submission once the page has gone live. - ### Summary The Treasurer is one of the most important roles on committee, it helps with the running of the Society. Make sure that you keep the receipts up to date, and plan the income and expenditure, and always remember to project all the funds that