Request New Meeting Modal

This dialog allows the meeting request to input a meeting request URL. This is the URL that will be shared with others to indicate their availability. The admin URL of the meeting request is an optional field for the meeting requestor's reference.

Request New Meeting Modal

This dialog allows the meeting request to input a meeting request URL. This is the URL that will be shared with others to indicate their availability. The admin URL of the meeting request is an optional field for the meeting requestor's reference.

Meeting Request Notifications

These notifications appear:
- In the Hub's stream (visible by logged in members. Subscribers and users who have starred the hub will not be able to view these notifications or at the least will not be given the URL to fill out the request.)
- In hub member's personal streams.

Summary version of notification

Preview version of notification

Meeting Request Notifications

These notifications appear:
- In the Hub's stream (visible by logged in members. Subscribers and users who have starred the hub will not be able to view these notifications or at the least will not be given the URL to fill out the request.)
- In hub member's personal streams.

Summary version of notification

Preview version of notification

(Note that the meeting request notifications are action notifications, and not just informational notifications)

Pending Meeting Request Display

Once you've created a meeting, it appears as a 'Requested' meeting in the meeting widget in the hub's sidebar.

Pending Meeting Request Display

Once you've created a meeting, it appears as a 'Requested' meeting in the meeting widget in the hub's sidebar.

Edit Meeting Request

Once a meeting request has been created, the person who requested the meeting (even if not an admin) and the admins of the hub it was created in will be able to see the "Edit" button in the meetings widget next to the requested meeting's listing. If they click on edit, they'll see the following modal dialog:

• Clicking on "Create Meeting" dismisses the meeting as a request so any notifications prompting people to visit the URL will be dismissed, and the meeting will no longer appear as "Requested" in the Meetings widget. The link will bring the user clicking on it to the calendar where the hub's calendar feed resides, ideally to the 'create new meeting' page (eg in fedocal) in a new browser window. They create the meeting, and then can input the url of the new meeting in the dialog (more than anything so we know it's safe to dismiss all the requests bc the new meeting has been created.)

• Clicking on "Cancel Meeting Requst" dismisses the meeting as a request so any notifications prompting people to visit the URL will be dismissed, and the meeting will no longer appear as "Requested" in the Meetings widget.

Edit Meeting Request

Once a meeting request has been created, the person who requested the meeting (even if not an admin) and the admins of the hub it was created in will be able to see the "Edit" button in the meetings widget next to the requested meeting's listing. If they click on edit, they'll see the following modal dialog:

• Clicking on "Create Meeting" dismisses the meeting as a request so any notifications prompting people to visit the URL will be dismissed, and the meeting will no longer appear as "Requested" in the Meetings widget. The link will bring the user clicking on it to the calendar where the hub's calendar feed resides, ideally to the 'create new meeting' page (eg in fedocal) in a new browser window. They create the meeting, and then can input the url of the new meeting in the dialog (more than anything so we know it's safe to dismiss all the requests bc the new meeting has been created.)

• Clicking on "Cancel Meeting Requst" dismisses the meeting as a request so any notifications prompting people to visit the URL will be dismissed, and the meeting will no longer appear as "Requested" in the Meetings widget.

(I didn't make a mockup with the created-meeting URL yet... i wonder how hokey my idea above is for creating the meeting successfully - let's talk through this one and make sure it makes sense or see if there's a better way.)

To clarify the suggested implementation here:

• The user can specify whichever meeting time finder external app they want. whenisgood.net is a popular one amongst Fedora users.

• Once they figure out a time through the external app, they put it in here and it will create a fedocal event. The calendar widget displays meetings based on what is present on the team's fedocal.

• This will require some enhancements to fedocal as its API is read only ATM.

Once they figure out a time through the external app, they put it in here and it will create a fedocal event. The calendar widget displays meetings based on what is present on the team's fedocal.

Hm question about this one: Is the plan to have hubs query the external app to figure out the date/time agreed? Or will this be provided by the admins to hubs so that it can create the meeting in fedocal?

I've come to realize something about this widget, it creates the 'gap' we want to avoid by splitting the communication channels.

By storing the meeting invite in hubs, we cannot ensure the information has been spread elsewhere (for example to a mailing list), so between the 'old-timers' using the list and the new-comers using hubs, the information may vary and not everyone may see it :(

^ very late response :) the simple answer to conundrum above is to send an email to the team list with the meeting request link when the meeting request is submitted.