nofusscomputing / nofusscomputing/centurion_erp

Calendar integration

Open
#253 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type::feature
Dominant language
Python
Stars
1
Forks
1
Avg merge
2h 18m
Merged PRs (30d)
8

Description

The ability to integrate a calendar into Centurion ERP and future features.

Requested features:

  • Adding due dates to tickets

  • Ability to set devices status on the calendar e.g down for maintenance, offline etc

  • export calendar and add to other calendar services (google, outlook, home assistant).

  • Set users status e.g busy, away

  • Use the calendar to trigger automations e.g deploy software on a date

  • relate: https://github.com/nofusscomputing/centurion_erp/issues/254


EoF OP


For the user to be able to forecast and plan, a calendar is a desired feature.

Details

Add the required features where each user can have their own calendar that they can use for planning. The calendar feature will be based off of RFC 5545 - iCalendar Specification. Add support for Components:

  • VCALENDAR (The overall calendar container, required)
  • VEVENT (Defines an event, e.g., a meeting or appointment)
  • #254 VTODO (Defines a to-do task)
  • VFREEBUSY (Defines free/busy time)
  • VALARM (Defines an alarm or reminder)
  • VAVAILABILITY (Defines an availability schedule)

Links

Features

  • Support for VJOURNAL (Defines a journal entry) Component
    User Should have ability to add journal entries if they desire

  • Ticket Due dates show on user calendar
    if user is assigned a ticket, add the ticket due date to the ticket.

  • Event-Based Webhooks[^github-379]
    Based off of events, trigger outbound webhooks

Requirements

  • Calendar permissions by user
  • User can share calendar
  • User can import via .ics file
  • User Can import via CardDav Server
  • CardDav Server Endpoint available
  • Two-way sync
  • Optional Read-Only endpoint available

[^github-379]: Blocked By: #379

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked RFC 5545 iCalendar Specification and the related issue #254. Define the scope across the listed calendar components, ticket due dates, webhooks, permissions, imports, CardDAV, and synchronization before implementation. Done means the agreed calendar capabilities and requirements are implemented and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.