Difference between revisions of "Team:Content-Tool-Evaluation"

From IFCAT wiki
Jump to: navigation, search
 
(11 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
This subpage helps [[Team:Content|Team Content]] define and assess criteria for Conference Planning Tools (CPT). Up until now, Team Content has used [http://frab.github.io/frab/ frab] (Ruby-on-rails), but will now assess [https://pretalx.com/p/about/ Pretalx] (Python) as potential replacement. An early iteration of this assessment work can be found [https://resistencia.pads.ccc.de/4 here] (Etherpad).
 
This subpage helps [[Team:Content|Team Content]] define and assess criteria for Conference Planning Tools (CPT). Up until now, Team Content has used [http://frab.github.io/frab/ frab] (Ruby-on-rails), but will now assess [https://pretalx.com/p/about/ Pretalx] (Python) as potential replacement. An early iteration of this assessment work can be found [https://resistencia.pads.ccc.de/4 here] (Etherpad).
 +
 +
The assessment will be discussed on [[2020-04-11-Content-meeting|Team Content's meeting 2020-04-11]].
  
 
{| class="wikitable sortable"
 
{| class="wikitable sortable"
Line 7: Line 9:
 
| Support CfP|| Yes || Yes
 
| Support CfP|| Yes || Yes
 
|-
 
|-
| Support rating of submissions ||  ||  
+
| Submission: Availability ||  || Yes
 
|-
 
|-
| Support confirmation of submissions in several stages ||  ||  
+
| Submission: Notes for the organiser ||  || Yes
 
|-
 
|-
| Support mass mails to submitters/speakers ||  ||  
+
| Submission: Recording opt-out ||  || Yes
 
|-
 
|-
| Support mass mails to subsets of submitters/speakers ||  ||  
+
| Submission: Image ||  || Yes
 
|-
 
|-
| Support feed-back from audience* ||  ||  
+
| Submission: Need financial support ||  || Partial<sup>4</sup><sup>NoteClaudia_1</sup>
 
|-
 
|-
| Planning tool (graphical) || ||  
+
| Support rating of submissions || Yes || Yes
 
|-
 
|-
| Planning publishing ||  ||  
+
| Support confirmation of submissions in several stages ||  || Yes (We may have accepted, rejected and pending events in parallel)
 
|-
 
|-
| Support for a ticketing system || ||  
+
| Support mass mails to submitters/speakers || <sup>NoteClaudia_2</sup> || Yes
 
|-
 
|-
| Interface to Angel system || ||  
+
| Support mass mails to subsets of submitters/speakers || || Yes
 
|-
 
|-
| In a "common" language*** || No (Ruby-on-rails) || Yes (python)
+
| Support feed-back from audience¹ || || Yes (At least text, no kind of "star" like rating)
 
|-
 
|-
| Secure (whatever that means)** ||  ||  
+
| Planning tool (graphical) ||  || Yes (but maybe limited)
 
|-
 
|-
| Reimbursement management || ||  
+
| Export of sticky notes for planning purposes (rating score, title, speakername, time needed, type) || (cards.pdf generated by hand hacking, not all info possible) || Unknown
 
|-
 
|-
| Reimbursement management per speaker || ||  
+
| Export of talk info for website / social media publishing purposes (title, abstract, type, speakername) || no || Unknown
 
|-
 
|-
| Manually mark speaker as arrived ||  ||  
+
| Planning publishing ||  || Yes
 
|-
 
|-
| Delete a submission category ||  ||  
+
| Support for a ticketing system ||  || Not directly (only via Email CC)
 +
|-
 +
| Interface to Angel system || || Yes (Frab export from Pretalx and then import into Engelsystem)
 +
|-
 +
| In a "common" language³ || No (Ruby-on-rails) || Yes (python)
 +
|-
 +
| Secure (whatever that means)² ||  || Yes
 +
|-
 +
| Reimbursement management ||  || No
 +
|-
 +
| Reimbursement management per speaker || <sup>NoteClaudia_3</sup> || No
 +
|-
 +
| Manually mark speaker as arrived ||  || No (but it's probably easy to implement)
 +
|-
 +
| Delete a submission category ||  || Yes
 
|}
 
|}
  
* Does this mean feedback from audience once a talk has been given, or also during the evaluation phase?  
+
¹ Does this mean feedback from audience once a talk has been given, or also during the evaluation phase?  
 +
 
 +
² Seems like both frab and pretalx are "secure" within some definition of secure - how stringent do we want these requirements?
 +
 
 +
³ I took the liberty of classifying ruby-on-rails as "uncommon"
 +
 
 +
<sup>4</sup> You can add additional questions
 +
 
 +
=== Pretalx missing features ===
 +
 
 +
==== Missing support for the ticketing system ====
 +
 
 +
Pretalx currently has no support for a ticketing system, but there is at least a central place in the code where Emails are send. We may extend that to something that doesn't send the mail directly via SMTP but updates a corresponding ticket instead. Alternatively the calling function needs to be patched:
 +
 
 +
https://github.com/pretalx/pretalx/blob/master/src/pretalx/common/mail.py
 +
 
 +
Alternatively we may do that via CC of the relevant emails.
 +
 
 +
=== Notes ===
 +
Claudia
 +
1 - financtial support => we need actually that ppl that asked for financial support to get flagged and that these requests are displayed in some page or the like
  
** Seems like both frab and pretalx are "secure" within some definition of secure - how stringent do we want these requirements?
+
2- mails => we need to have automated the grouping of people that are for instance waiting for x months and automated emails that give them some feedback ( we are still working on it , etc)
  
*** I took the liberty of classifying ruby-on-rails as "uncommon"
+
3- reimboursement management "=> this is not nice to have, this is really a requirement

Latest revision as of 12:30, 22 April 2020

This subpage helps Team Content define and assess criteria for Conference Planning Tools (CPT). Up until now, Team Content has used frab (Ruby-on-rails), but will now assess Pretalx (Python) as potential replacement. An early iteration of this assessment work can be found here (Etherpad).

The assessment will be discussed on Team Content's meeting 2020-04-11.

Property frab Pretalx
Support CfP Yes Yes
Submission: Availability Yes
Submission: Notes for the organiser Yes
Submission: Recording opt-out Yes
Submission: Image Yes
Submission: Need financial support Partial4NoteClaudia_1
Support rating of submissions Yes Yes
Support confirmation of submissions in several stages Yes (We may have accepted, rejected and pending events in parallel)
Support mass mails to submitters/speakers NoteClaudia_2 Yes
Support mass mails to subsets of submitters/speakers Yes
Support feed-back from audience¹ Yes (At least text, no kind of "star" like rating)
Planning tool (graphical) Yes (but maybe limited)
Export of sticky notes for planning purposes (rating score, title, speakername, time needed, type) (cards.pdf generated by hand hacking, not all info possible) Unknown
Export of talk info for website / social media publishing purposes (title, abstract, type, speakername) no Unknown
Planning publishing Yes
Support for a ticketing system Not directly (only via Email CC)
Interface to Angel system Yes (Frab export from Pretalx and then import into Engelsystem)
In a "common" language³ No (Ruby-on-rails) Yes (python)
Secure (whatever that means)² Yes
Reimbursement management No
Reimbursement management per speaker NoteClaudia_3 No
Manually mark speaker as arrived No (but it's probably easy to implement)
Delete a submission category Yes

¹ Does this mean feedback from audience once a talk has been given, or also during the evaluation phase?

² Seems like both frab and pretalx are "secure" within some definition of secure - how stringent do we want these requirements?

³ I took the liberty of classifying ruby-on-rails as "uncommon"

4 You can add additional questions

Pretalx missing features

Missing support for the ticketing system

Pretalx currently has no support for a ticketing system, but there is at least a central place in the code where Emails are send. We may extend that to something that doesn't send the mail directly via SMTP but updates a corresponding ticket instead. Alternatively the calling function needs to be patched:

https://github.com/pretalx/pretalx/blob/master/src/pretalx/common/mail.py

Alternatively we may do that via CC of the relevant emails.

Notes

Claudia 1 - financtial support => we need actually that ppl that asked for financial support to get flagged and that these requests are displayed in some page or the like

2- mails => we need to have automated the grouping of people that are for instance waiting for x months and automated emails that give them some feedback ( we are still working on it , etc)

3- reimboursement management "=> this is not nice to have, this is really a requirement