nextcloud / nextcloud/calendar
Calendar Import Issuses Overview
Open
Nobody has claimed this yet.
1. to develop
bug
Feature: Importing
overview
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
This is an overview ticket of all import issues
- https://github.com/nextcloud/calendar/issues/1508
- https://github.com/nextcloud/calendar/issues/4876
- https://github.com/nextcloud/calendar/issues/7039
- https://github.com/nextcloud/calendar/issues/5647
- https://github.com/nextcloud/calendar/issues/6919
- https://github.com/nextcloud/calendar/issues/6022
- https://github.com/nextcloud/calendar/issues/3053
- https://github.com/nextcloud/calendar/issues/1483
- https://github.com/nextcloud/calendar/issues/642
- https://github.com/nextcloud/calendar/issues/2065
- https://github.com/nextcloud/calendar/issues/5531
- https://github.com/nextcloud/calendar/issues/5750
- https://github.com/nextcloud/calendar/issues/2570
- https://github.com/nextcloud/calendar/issues/4518
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked issues, beginning with #1508 and #4876, to understand the separate calendar import problems and their current status. This overview does not name files, tests, or a single change; completion would require addressing or otherwise closing the listed import issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100