FOSS4G 2018 Lessons Learned - Revision history

Wiki-Maria at 08:29, 23 September 2018

2018-09-23T08:29:11Z

2018-09-23T08:24:47Z

2018-09-18T18:24:20Z

Security

2018-09-18T18:10:12Z

Paper selection

2018-09-18T18:08:09Z

Academic Track

2018-09-18T13:33:44Z

Security

2018-09-18T13:33:30Z

Security

2018-09-18T13:32:14Z

Code of Conduct

2018-09-18T13:28:20Z

FOSS4G 2018 Lessons Learned

2018-09-18T13:26:12Z

Security

@@ Line 63: / Line 63: @@
 === Workshops ===
-=== Key Note ===
+=== Keynote ===
-One of the Key Note (that of OSGeo) was planned to be during the Gala Dinner. What we experienced is that mixing the two was impossible and we had to postpone the Key Note on the last day of Conference.
+One of the Keynote (that of OSGeo) was planned to be during the Gala Dinner. What we experienced is that mixing the two was impossible and we had to postpone the Keynote on the last day of Conference.
-Unless it is very well checked that the location is optimal for a Key Note, it is better to have at most short speeches (few minutes) during the Gala Dinner because people want more to dance and to see the show than listen at keynoter. The ideal location for the key notes is the biggest room of the conference.
+Unless it is very well checked that the location is optimal for a Keynote, it is better to have at most short speeches (few minutes) during the Gala Dinner because people want more to eat, to chat, to dance and to see the show than listen at keynoter. The ideal location for the keynotes is the biggest room of the conference.
 === Code of Conduct ===

← Older revision		Revision as of 08:24, 23 September 2018
Line 62:		Line 62:

	=== Workshops ===		=== Workshops ===
		+
		+	=== Key Note ===
		+	One of the Key Note (that of OSGeo) was planned to be during the Gala Dinner. What we experienced is that mixing the two was impossible and we had to postpone the Key Note on the last day of Conference.
		+	Unless it is very well checked that the location is optimal for a Key Note, it is better to have at most short speeches (few minutes) during the Gala Dinner because people want more to dance and to see the show than listen at keynoter. The ideal location for the key notes is the biggest room of the conference.

	=== Code of Conduct ===		=== Code of Conduct ===

@@ Line 71: / Line 71: @@
 There needs to be a security plan. There were some people who attempted to attend the conference "off the street" and we needed a plan on how to deal with this.
-''Sidebar'': in Boston, the venue had a dedicated security team and plan.
+''Sidebar'': in Boston, and as reported by Vasile, the venue had/will have a dedicated security team and plan provided by the venue.
 === Academic Track ===

← Older revision		Revision as of 18:10, 18 September 2018
Line 57:		Line 57:

	=== Paper selection ===		=== Paper selection ===
		+
		+
		+	For the Academic Track papers were selected by the Scientific Committee.

	=== Workshops ===		=== Workshops ===

← Older revision		Revision as of 18:08, 18 September 2018
Line 71:		Line 71:

	=== Academic Track ===		=== Academic Track ===
		+
		+	It was chosen to use as a platform for managing the process Easychair and everything was smooth and easy.
		+
		+	It was chosen to organize the Academic Track with ISPRS (OSGeo has a MoU with ISPRS) and this gave the possibility of having indexed Proceedings and the presence of two people from the ISPRS Council (Prof. Charles Toth and Prof. Chen Jun). The choice of indexed Proceedings is of greater value for the authors and ensures a good level of the papers.
		+
		+	The choice of having a Scientific Committee ensured a good peer-review process.
		+
		+	Moreover, the Proceedings are open access publications, published under the Creative Common Attribution 3.0 License.
		+
		+	The Proceeding where available more than one month before the start of the Conference, giving the possibility to potential attendees to read not only the abstract but also the complete paper.
		+	https://www.int-arch-photogramm-remote-sens-spatial-inf-sci.net/XLII-4-W8/
		+
		+	The Academic Track was well attended; discussions were fruitful.
		+
		+	Chair Persons of the Academic Track should be selected from the members of the Scientific Committee because this, in general, brings to more interactive/active sessions.

	=== Code Sprint ===		=== Code Sprint ===

@@ Line 61: / Line 61: @@
 === Code of Conduct ===
-There was a code of conduct violation. It was handled as per the Code of Conduct process. There are some definite lessons we learned in handling this.
+There was a code of conduct violation. It was handled as per the Code of Conduct process. There are some definite lessons we learned in handling this. Key people involved in managing the CoC, got pulled away from the Gala and conducting the agenda of presentations that were supposed to be given at the Gala.
 It would be beneficial to have a CoC training session prior the conference. Key people should know their roles and the process in advance.

← Older revision		Revision as of 13:26, 18 September 2018
Line 64:		Line 64:

	=== Security ===		=== Security ===
		+	There needs to be a security plan. There were some people who attempted to attend the conference "off the street" and we needed a plan on how to deal with this.

	=== Academic Track ===		=== Academic Track ===