Skip to content

A repo for the side quests I've encountered during my PhD

License

Notifications You must be signed in to change notification settings

caggursoy/phdSideQuests

Repository files navigation


Logo

phdSideQuests

A repository for side quests (i.e. projects) I've encountered (i.e. I plan to meddle with) during my PhD.
Report Bug . Request Feature

Contributors Forks Stargazers Issues License

Table Of Contents

About The Project

labmeeting-protocol

An automated protocol poster for weekly KliPs department meetings. Takes the info from a .docx file Ellen generates every week, posts its location for Linux/Windows paths and converts the .docx to a .png and posts to the dedicated channel for ease of access

labmeeting-rocketchat

An automated reminder for weekly KliPs deparment meetings. Can do the following:

  • Reminds the persons who are scheduled to be the presenter/moderator in the next two meetings to present
  • Posts next two labmeetings presenter/moderator tuple to a dedicated channel
  • Every time there's an update in the KliPs labmeeting schedule repo, it reads the new labmeeting schedule and posts to the dedicated channel

pug23Cal

Works only for PuG23 :) Reads the PuG23 program from the PDF and pushes the events into a GCal where you can subscribe and follow from your apps!

resmanToGCal

Just what we need! We all know that Resman is awesome, but can only be accessed via ZI network. This automaton filters your Resman entries and copies them to a dedicated GCal, so you can check your Resman appointments from your apps!

rocket-greeter

ZI-ECRs RocketChat channel greeter! This is the automaton that greets everyone who joins the ZI-ECRs main channel.

Built With

Until now, I've developed everything with Python; and some wrappers

Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

  • If you have suggestions for adding or removing projects, feel free to open an issue to discuss it, or directly create a pull request after you edit the README.md file with necessary changes.
  • Please make sure you check your spelling and grammar.
  • Create individual PR for each suggestion.
  • Please also read through the Code Of Conduct before posting your first idea as well.

Creating A Pull Request

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

Distributed under the unlicense. See LICENSE for more information.

Authors

About

A repo for the side quests I've encountered during my PhD

Resources

License

Stars

Watchers

Forks