Add short HOWTO for editing the community calendar #166
Conversation
|
I was actually able to check the editing permissions - it's currently which seems just fine to me. |
_includes/navbar.ext
Outdated
| @@ -31,6 +31,7 @@ | |||
| <li><a href="/technical_notes.html">Technical Notes</a></li> | |||
| <li><a href="/newsletter.html">Newsletter</a></li> | |||
| <li><a href="/organization/minutes.html">Meeting Notes</a></li> | |||
| <li><a href="/calendar.html">Community Calendar Editing</a></li> | |||
There was a problem hiding this comment.
Why not to add this menu to 'Get Involved' rather than 'Communication'?
There was a problem hiding this comment.
I'm ok with that. As Get Involved is a single page link, do you think just add calendar editing as part of that page? It's short enough that a separate page is perhaps unnecessary.
calendar.md
Outdated
| layout: default | ||
| --- | ||
|
|
||
| The HSF [Community Calendar](https://calendar.google.com/calendar/embed?src=e4v33e1a1drbncdle1n03ahpcs%40group.calendar.google.com&ctz=Europe/Amsterdam) |
There was a problem hiding this comment.
May be remove the timezone in the URL?
There was a problem hiding this comment.
And after the (link), may be add {:target="_hsf_calendar"} (no space between () and {}) to get the calendar in a new tab, being able to continue to read the doc...
There was a problem hiding this comment.
Fine be me, done for the next commit,
calendar.md
Outdated
| --- | ||
|
|
||
| The HSF [Community Calendar](https://calendar.google.com/calendar/embed?src=e4v33e1a1drbncdle1n03ahpcs%40group.calendar.google.com&ctz=Europe/Amsterdam) | ||
| can be edited by people in the [HSF Startup Team](https://groups.google.com/forum/#!forum/hep-sf-startup-team) |
There was a problem hiding this comment.
I still don't like the idea that we use one group for 2 different purposes. Why not to create (it is so easy) a group hep-sf-calendar-editors where we could add people who may be legitimate editors and don't want to be in the startup team list (despite the notification trick). We can then just add this group to the calendar sharing list (any startup team member can do it) and document the usual +subscribe trick to subscribe to this group. Additionally this will give us the ability to contact calendard editors if we need to share some information, something not possible if people disabled email notifications...
There was a problem hiding this comment.
I can't say I deeply care, but if we do this I think the startup team should be able to also edit (I suppose you were proposing that, right). Then the new group is for extra editors (and should be approved subscriptions I think).
calendar.md
Outdated
| calendar and, if you are in the startup | ||
| team group, add them. | ||
|
|
||
| Please ask to join the startup |
There was a problem hiding this comment.
See my previous comment... To be adjusted if we go for another group.
graeme-a-stewart
changed the title
|
@jouvin I pushed some updates in line with your suggestions, but I made this a WIP pending the decision on the second editing group. Let's see what others think - for me it's fine either way. |
|
@graeme-a-stewart I'm fine with your changes. Let's wait the decision on the editor group to finalize it, as you suggested. |
graeme-a-stewart
force-pushed
the
hsf-calendar-instructions
branch
from
17b8b0b
to
4b9b1a0
Compare
graeme-a-stewart
changed the title
|
@jouvin - should be good to go now |
|
LGTM! BTW, have you added the editors group to the calendar with the appropriate rights (probably adding/modifying events is enough, startup team has the right to manage the sharing if I'm right). |
|
Yes, the new group is added and is allowed to create events. |
This PR adds a short section on how to edit the community calendar, publicising the URL that you need to use to add the HSF calendar to your own calendar application. Instructions are given for Google Calendar.
I tried the URL with a throw-away Google account that I have and it would not let me add events, so the editing permissions do seem to be locked down (@pelmer can probably confirm it's the startup team).
I added this link under the Communication navigation item.