[uds-announce] Using Summit at UDS-R

[Chris Johnston]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings,

I wanted to take a few minutes to let everyone know of two of the
changes that have happened in Summit that may effect you. The first
and biggest change is that a user is no longer able to set themselves
as required to a meeting. There are now three levels of participation
to hopefully reduce some of the unnecessary conflicts when creating
schedules. The three levels are:

 * Attending
 * Very interested in attending
 * Required

When Summit can, it will move the schedule around to suit all
participants. If it is unable to work out for those who are very
interested in attending a meeting, it will default to attempting to
work out the schedule for those who are required. If a user marks
participation essential on a blueprint, that no longer translates to
required in Summit. Participation Essential is now equivalent to 'very
interested in attending.' In order to be marked as a required
attendee, either the person who created the meeting, or the track lead
for the particular track that the meeting is in must mark the user as
required. This will hopefully reduce the conflicts in scheduling that
occurs at every event.

The second change is that we added the ability for searching inside of
Summit. This will hopefully make it easier for you to find a
particular session that you may be looking for.

Another note for you to know is that if you look in the top right
corner of Summit while you are logged in you will see a link to 'My
Schedule.' This page will show you a list of all of the meetings that
you are signed up to attend. The 'My Schedule' page and the daily
schedule pages are both mobile accessible, a QR code to their location
will soon be available at the top of each page.

cJ

- -- 
Respectfully,

Chris Johnston - cjohnston
Ubuntu Member
chrisjohnston at ubuntu.com
www.chrisjohnston.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAlCM2tAACgkQyDxSNf9BQVylLACgxCdN23dkE428fAG/LWjuryiE
2f0An06emcf6KQEZtY3MbZDfjJZTmhnR
=IIKz
-----END PGP SIGNATURE-----