Next stage for session curation

[Saallen]

@mmmavis as we will be confirming all the sessions coming to MozFest next week, the next stage is getting the sessions into good stead to present at MozFest. If Wranglers want to make edits to session descriptions what is the process to update. Do they start a new comment? Is editing on the top comment a big NoNo 🙅

[mmmavis]

Hey @Saallen is it just the description field wranglers want to update?

[Saallen]

Hi @mmmavis I believe so The might want to add in another facilitator but this can be done when we have ported back over to the googlesheet

[mmmavis]

Hi @Saallen , is there a deadline for session facilitators to update session description on GitHub? After we have exported things from GitHub to a new Google Spreadsheet(used to feed Schedule app) changes made to Github will not reflect on Google Spreadsheet. If we are letting people update session description we should set a deadline for that.

[Saallen]

Hi @mmmavis, Where would you prefer for them to update? Google or gihtub? Let me think about the deadline as we will need to work backwards from release of schedule app testing of schedule porting over information finalising info ( you can decide where this takes place, github or google)

[mmmavis]

If description changes are made by session facilitators it should definitely be made on Github as we need to limit access to the event app spreadsheet. I'll need to know more before I can suggest how to get the updated description up on Github. 😁

[mmmavis]

Hey @Saallen , I suggest asking session facilitators (or space wranglers) to add a new comment using the following format

### Amended Description

i'm the amended description i'm the amended description i'm the amended description 

They can replace i'm the amended description i'm the amended description i'm the amended description with their real description but the ### Amended Description and the line break after it are essential for the script to parse info from GitHub comment.

There should only be ONE comment marked in this format otherwise it's impossible for the script to know which "Amended Description" comment is the most up to date one.

Do this make sense?

[mmmavis]

below is how the comment should look like

[mmmavis]

Amended Description

i'm the amended description i'm the amended description i'm the amended description

[mmmavis]

@Saallen do we wanna set the date to lock the program repo?

According to https://public.etherpad-mozilla.org/p/2016-mozfest-event-app (line 13) we are aiming for Sept 29. Just wanna confirm that pathway labels will be assigned to sessions before Sept 29 as well. 🐹

[Saallen]

Hellloo @mmmavis Yes- the labels will ready by then 😮

[mmmavis]

note for @mmmavis

Make the script for that it looks for "amended description" (not case sensitive) in the first line. If "amended description" exists extract the amended description after the 2nd line.

[Saallen]

@mmmavis What happens if they add way more detail ..see issue https://github.com/MozillaFoundation/mozfest-program-2016/issues/247

[mmmavis]

hey @Saallen

@mmmavis What happens if they add way more detail ..see issue MozillaFoundation/mozfest-program-2016#247

Everything after the "amended description" header (first line) will be extracted by the script as the description. In other words, please only include the amended description and not other meta. 👍

[Saallen]

thanks!