Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] Add a Calendar Feed for NIST OSCAL Events to OSCAL Site? #1408

Closed
9 tasks done
aj-stein-nist opened this issue Aug 11, 2022 · 11 comments · Fixed by #1642 or #1677
Closed
9 tasks done

[RFC] Add a Calendar Feed for NIST OSCAL Events to OSCAL Site? #1408

aj-stein-nist opened this issue Aug 11, 2022 · 11 comments · Fixed by #1642 or #1677
Assignees
Labels
Discussion Needed This issues needs to be reviewed by the OSCAL development team. enhancement User Story

Comments

@aj-stein-nist
Copy link
Contributor

aj-stein-nist commented Aug 11, 2022

User Story

As an OSCAL stakeholder and active community member, in order to have a more consistent way to keep abreast of any OSCAL event (dev lunch, model meeting, and mini workshops), I want a hosted calendar to automatically update my email/calendar management client. I also want to know what others think of this, so this is currently a Request for Comment (RFC). :-)

Goals

Dependencies

Acceptance Criteria

  • Design a solution with common community use cases in mind.
  • Implement the calendaring solution, if well-received.
  • All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
  • A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
  • The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.
@GaryGapinski
Copy link

While proprietary, Google Calendar works quite well for me for a multiple calendar view. However, that is not the same as receiving calendar invitations and selectively choosing them to add to one of my personal calendars.

@aj-stein-nist
Copy link
Contributor Author

While proprietary, Google Calendar works quite well for me for a multiple calendar view. However, that is not the same as receiving calendar invitations and selectively choosing them to add to one of my personal calendars.

Absolutely, excellent point, Gary. The design intent of this would be, for Google's GMail/Workspaces, Office365/hosted Exchange and Outlook, and the macOS/iOS calendars, creating a publicly readable ICS-based calendar could allow people to 1) passively receive all invites and/or accept/reject calendar events onto your own personal calendar by copying/moving preferred events at your leisure.

A research note for us to pick up with that approach, if others encourage and the community wants it.

https://www.jvt.me/posts/2019/05/22/ical-events-hugo/

@david-waltermire david-waltermire added the Discussion Needed This issues needs to be reviewed by the OSCAL development team. label Aug 16, 2022
@aj-stein-nist aj-stein-nist self-assigned this Jan 19, 2023
@aj-stein-nist
Copy link
Contributor Author

I have been looking into this in relationship to #1604. Earlier in the week, I met with Michaela and Chris to discuss the viability of the CSRC CMS tool for managing the calendar. Michaela gave us a 30 minute demo around the pages functionality and some of the calendar functionality. It seems like it might not be a good fit, but a little more experimentation is needed given the ICS calendaring functionality it will give us for free.

@aj-stein-nist
Copy link
Contributor Author

I tried the csrc.nist.gov CMS and it had a couple fundamental problems. The public NIST website doesn't seem ideal, but this shared calendar solution through Outlook seems to preliminarily serve most of our needs.

https://outlook.office365.com/calendar/published/[email protected]/aebfdc75f48a44a4a2588a54d4cd70308785621945585929004/calendar.html

https://outlook.office365.com/owa/calendar/[email protected]/aebfdc75f48a44a4a2588a54d4cd70308785621945585929004/calendar.ics

Further testing is needed and I might wrap it into the website and make a SOP for the rest of the team to use this approach for all event invites.

/cc @canb227 ;-)

@aj-stein-nist
Copy link
Contributor Author

I have some updates and need to make a decision record and get buy-in and endorsement from the rest of the NIST OSCAL Team (because their opinion matters here a lot). I will need to complete that early in the next sprint.

@aj-stein-nist
Copy link
Contributor Author

I tried the csrc.nist.gov CMS and it had a couple fundamental problems. The public NIST website doesn't seem ideal, but this shared calendar solution through Outlook seems to preliminarily serve most of our needs.

https://outlook.office365.com/calendar/published/[email protected]/aebfdc75f48a44a4a2588a54d4cd70308785621945585929004/calendar.html

https://outlook.office365.com/owa/calendar/[email protected]/aebfdc75f48a44a4a2588a54d4cd70308785621945585929004/calendar.ics

Further testing is needed and I might wrap it into the website and make a SOP for the rest of the team to use this approach for all event invites.

/cc @canb227 ;-)

We deprecated the calendar mentioned above ☝️ in favor of a functional account in NIST parlance to run a calendar we can publish from (as HTML and ICS file) and integrate that into our public website. More to follow in a decision doc about the options tried, use case requirements not met, and this final recommendation from me I hope the team will appreciate.

Updated test calendars. Michaela has tested this for one of our next community meetings.

https://outlook.office365.com/owa/calendar/[email protected]/e72d2ca648dc4c3db7470fb7339674f211929765598025548039/calendar.html

https://outlook.office365.com/owa/calendar/[email protected]/e72d2ca648dc4c3db7470fb7339674f211929765598025548039/calendar.ics

@iMichaela
Copy link
Contributor

Updated test calendars. Michaela has tested this for one of our next community meetings.

@aj-stein-nist - I tested it with our team, I did not invite the entire community through this calendar. to not confuse people, and not force them to accept it again. I will use the [email protected] calendar for all future events.

@aj-stein-nist
Copy link
Contributor Author

Updated test calendars. Michaela has tested this for one of our next community meetings.

@aj-stein-nist - I tested it with our team, I did not invite the entire community through this calendar. to not confuse people, and not force them to accept it again. I will use the [email protected] calendar for all future events.

OK, thanks. I must have misread a stream of emails that came through as I was in between tasks. Thanks for testing it in any case.

aj-stein-nist added a commit to aj-stein-nist/OSCAL-forked that referenced this issue Feb 6, 2023
aj-stein-nist added a commit to aj-stein-nist/OSCAL-forked that referenced this issue Feb 6, 2023
aj-stein-nist added a commit that referenced this issue Feb 6, 2023
aj-stein-nist added a commit to aj-stein-nist/OSCAL-forked that referenced this issue Feb 7, 2023
aj-stein-nist added a commit to aj-stein-nist/OSCAL-forked that referenced this issue Feb 7, 2023
@aj-stein-nist aj-stein-nist moved this from In Progress to Under Review in NIST OSCAL Work Board Feb 13, 2023
aj-stein-nist added a commit that referenced this issue Feb 21, 2023
…L Team (#1638)

* Add ADR structure for #1408.

* Add decision record for use of shared calendar for #1408

* Take wording suggestion from @Compton-NIST.

Co-authored-by: Chris Compton <[email protected]>

* Integrate feedback into ADR 2 from @iMichaela.

* Update decisions/0002-record-architecture-decisions.md

Co-authored-by: Wendell Piez <[email protected]>

* Update decisions/0002-record-architecture-decisions.md

* Rename file per @nikitawooten-nist's feedback.

* Update decisions/0002-communicating-nist-oscal-events-to-the-public.md

---------

Co-authored-by: Chris Compton <[email protected]>
Co-authored-by: Wendell Piez <[email protected]>
@aj-stein-nist
Copy link
Contributor Author

OK, I believe the next step is determining and documenting a SOP for handling calendar events to be completed before or alongside #1642.

@aj-stein-nist
Copy link
Contributor Author

AJ discussed this in the last status meeting, he will quickly draft a status meeting SOP to publish for staff. @iMichaela and @wendellpiez offered to review.

@github-project-automation github-project-automation bot moved this from Under Review to Done in NIST OSCAL Work Board Feb 28, 2023
aj-stein-nist added a commit to aj-stein-nist/OSCAL-forked that referenced this issue Feb 28, 2023
aj-stein-nist added a commit to aj-stein-nist/OSCAL-forked that referenced this issue Feb 28, 2023
I missed these in usnistgov#1638 as part of usnistgov#1408. As it pertains to the calendar
management work, might as well touch this up as well.
@aj-stein-nist aj-stein-nist reopened this Feb 28, 2023
@github-project-automation github-project-automation bot moved this from Done to In Progress in NIST OSCAL Work Board Feb 28, 2023
@aj-stein-nist
Copy link
Contributor Author

Missed some stuff need to open this up for a little bit longer.

@aj-stein-nist aj-stein-nist linked a pull request Feb 28, 2023 that will close this issue
7 tasks
@aj-stein-nist aj-stein-nist moved this from In Progress to Under Review in NIST OSCAL Work Board Feb 28, 2023
aj-stein-nist added a commit that referenced this issue Feb 28, 2023
…1677)

* Woops, fix missing headers for #1408.

* Woops, mark ADRs approved.

I missed these in #1638 as part of #1408. As it pertains to the calendar
management work, might as well touch this up as well.
@github-project-automation github-project-automation bot moved this from Under Review to Done in NIST OSCAL Work Board Feb 28, 2023
nikitawootten-nist pushed a commit that referenced this issue Apr 10, 2023
…L Team (#1638)

* Add ADR structure for #1408.

* Add decision record for use of shared calendar for #1408

* Take wording suggestion from @Compton-NIST.

Co-authored-by: Chris Compton <[email protected]>

* Integrate feedback into ADR 2 from @iMichaela.

* Update decisions/0002-record-architecture-decisions.md

Co-authored-by: Wendell Piez <[email protected]>

* Update decisions/0002-record-architecture-decisions.md

* Rename file per @nikitawooten-nist's feedback.

* Update decisions/0002-communicating-nist-oscal-events-to-the-public.md

---------

Co-authored-by: Chris Compton <[email protected]>
Co-authored-by: Wendell Piez <[email protected]>
nikitawootten-nist pushed a commit that referenced this issue Apr 10, 2023
…1677)

* Woops, fix missing headers for #1408.

* Woops, mark ADRs approved.

I missed these in #1638 as part of #1408. As it pertains to the calendar
management work, might as well touch this up as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment