Difference between revisions of "28-03-2020"

From IFCAT wiki
Jump to: navigation, search
(Created page with "Agenda")
 
m (Get to a milestone planning)
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
Agenda
+
== Agenda ==
 +
 
 +
=== Evaluate PretalX ===
 +
https://pretalx-dev.ifcat.org/orga/login/?next=/orga/ (Add your findings in the pad https://resistencia.pads.ccc.de/4 )
 +
 
 +
'''Info on pretalx'''
 +
https://github.com/pretalx/pretalx/wiki/Events
 +
 
 +
'''missed in FRAB''':
 +
* automatic feedback when a speaker entered the content 
 +
* some way to manage finances per speaker
 +
 
 +
'''other requirements:'''
 +
* We should encourage speakers to enter their phone number and/or IM handle (Telegram/Signal/Wire/whatever).
 +
* I need the ability to manually mark the speaker as arrived.
 +
* I guess if I want pretalx to work without javascript, I gotta write it myself and submit a pull request on github?
 +
[aa: if this is something we want to do, will it be possible to get it done before we need it up and running by July 2020?]
 +
* integration with redmine (think about things that need to be done for a particular speaker that is recorded as ticket in redmine)
 +
 
 +
'''Feedback'''
 +
* Confirmation is missing for serious stuff, e.g. sending out batch e-mails or deleting a submission category.
 +
* When changing talk state, the confirmation (positive) button appears as secondary because of gray background used.
 +
 
 +
=== Document outlines of processes ===
 +
* Content team: how many people do we prefer to have
 +
* First thoughts on the budget we would like to have
 +
 
 +
=== Get to a milestone planning ===
 +
* We gotta remember to submit an entry to cfptime et al. In about a year I guess? January/Feb 2021?
 +
 
 +
=== Draft Call for Participation ===
 +
=== Lessons learned from SHA2017 ===
 +
 
 +
https://orga.sha2017.org/index.php?title=Team:Content 
 +
 
 +
https://orga.sha2017.org/index.php?title=Team:Content/Heralds
 +
 
 +
https://orga.sha2017.org/index.php?title=Team:Content/Speakerdesk

Revision as of 11:43, 23 March 2020

Agenda

Evaluate PretalX

https://pretalx-dev.ifcat.org/orga/login/?next=/orga/ (Add your findings in the pad https://resistencia.pads.ccc.de/4 )

Info on pretalx https://github.com/pretalx/pretalx/wiki/Events

missed in FRAB:

  • automatic feedback when a speaker entered the content
  • some way to manage finances per speaker

other requirements:

  • We should encourage speakers to enter their phone number and/or IM handle (Telegram/Signal/Wire/whatever).
  • I need the ability to manually mark the speaker as arrived.
  • I guess if I want pretalx to work without javascript, I gotta write it myself and submit a pull request on github?

[aa: if this is something we want to do, will it be possible to get it done before we need it up and running by July 2020?]

  • integration with redmine (think about things that need to be done for a particular speaker that is recorded as ticket in redmine)

Feedback

  • Confirmation is missing for serious stuff, e.g. sending out batch e-mails or deleting a submission category.
  • When changing talk state, the confirmation (positive) button appears as secondary because of gray background used.

Document outlines of processes

  • Content team: how many people do we prefer to have
  • First thoughts on the budget we would like to have

Get to a milestone planning

  • We gotta remember to submit an entry to cfptime et al. In about a year I guess? January/Feb 2021?

Draft Call for Participation

Lessons learned from SHA2017

https://orga.sha2017.org/index.php?title=Team:Content

https://orga.sha2017.org/index.php?title=Team:Content/Heralds

https://orga.sha2017.org/index.php?title=Team:Content/Speakerdesk