Guide on open issues

[niccokunzmann]

@SashankBhamidi would like to contribute. Here is my guidance.

These are good issues to start with:

• Set necessary attributes #134
• Merging event/calendar colors #17
• Generate VTIMEZONEs when not available #7 - icalendar can do this and we also have an issue open in icalendar which can be retrieved for mergecal because it needs to be resolved upstream: [BUG] icalendar generates UTC timezone collective/icalendar#1124
• running merge twice should result in the same result #135 - consider this again: I want all the tests to use calendars in files to merge them. Do not put any calendar code into .py files and keep the tests as small as possible.
• task 7.c

[SashankBhamidi]

@abe-101,

Over the last few days, I’ve gone through the MergeCal codebase and have a solid high-level understanding of how everything fits together.

What issues should I be focusing on mainly?

[abe-101]

What issues should I be focusing on mainly

• Stability 😸 running merge twice should result in the same result #135
• More tests. I'd start with adding more anonymized calendars from various platforms. (Google, Apple, luma.com, nextcloud and many more) and ensuring that the merged output consistently is the same.