From Fedora Project Wiki

(Remove blank lines)
 
(7 intermediate revisions by 3 users not shown)
Line 31: Line 31:
 
!! Use !! System
 
!! Use !! System
 
|-
 
|-
| General content for users to read (pre-conference) || WordPress
+
| General content for users to read (pre-conference) || fedora-web module
 
|-
 
|-
 
| Registration, CfP, voting on papers || regcfp
 
| Registration, CfP, voting on papers || regcfp
Line 42: Line 42:
 
Content consists of information and messaging for the general public. This is how we advertise dates, venue, transportation information, travel tips, and calls to action.
 
Content consists of information and messaging for the general public. This is how we advertise dates, venue, transportation information, travel tips, and calls to action.
  
;WordPress
+
;Static site
:Continue to use WordPress to post general information for the public about Flock. It will still reside at https://flocktofedora.org.
+
:Use a static site, managed with the fedora-web git repo similar to all other main Fedora websites, to post general information for the public about Flock. It will still reside at https://flocktofedora.org.
:Move the installation to an appropriate location in the Fedora infrastructure. '''TODO: File ticket with fedora-infrastructure to include on the infra cloud.'''
+
:Request help from Design team (Ryan Lerch), hopefully building on a well known theme or model to bring into line with Fedora branding
:Simplify the installation to eliminate some custom theme/plugins which have resulted in confusing and difficult administration.
+
:Here is the [https://git.fedorahosted.org/cgit/fedora-web.git git repo] and a direct link to the [https://git.fedorahosted.org/cgit/fedora-web.git/tree/flocktofedora.org folder in the tree].
:Request refreshed theme from Design team to
 
  
 
;Sched.org
 
;Sched.org
Line 57: Line 56:
  
 
;regcfp
 
;regcfp
:Use [https://github.com/puiterwijk/GUADEC-regcfp regcfp application] for registration, desk, call for papers activity, and paper voting/acceptance. '''TODO: File RfR ticket with fedora-infrastructure, likely for Patrick to handle.'''
+
:Use [https://github.com/puiterwijk/GUADEC-regcfp regcfp application] for registration, desk, call for papers activity, and paper voting/acceptance. <strike>'''TODO: File RfR ticket with fedora-infrastructure, likely for Patrick to handle.'''</strike> DONE - to be available at https://register.flocktofedora.org
 
:Visual elements will reflect Fedora branding.
 
:Visual elements will reflect Fedora branding.
 
:The software team will create an administration and maintenance document on wiki for Flock planners using the system.
 
:The software team will create an administration and maintenance document on wiki for Flock planners using the system.
:'''TBD: Generalize an ansible playbook so this app can be used for other Fedora events if desired.'''
+
:<strike>'''TBD: Generalize an ansible playbook so this app can be used for other Fedora events if desired.'''</strike> - IN PROGRESS - Patrick handling
 
:Users will visit via https://register.flocktofedora.org URL.
 
:Users will visit via https://register.flocktofedora.org URL.
 
:The software team will monitor incoming issues and prioritize based on the Flock planning team's needs.
 
:The software team will monitor incoming issues and prioritize based on the Flock planning team's needs.
 
=== Details ===
 
 
 
 
  
 
[[Category:Flock]]
 
[[Category:Flock]]
 +
[[Category:Flock 2016]]

Latest revision as of 15:55, 23 March 2019

This page is about a revamp of software to use for Flock 2016 and beyond.

Background

Here are our preliminary notes on problem statements, and proposed fixes for our issues with Flock software.

Here are our comparisons of existing tools.

Proposal

The core team of folks looking at software for Flock include the following:

  • Paul Frields
  • Máirín Duffy
  • Patrick Uiterwijk
  • Josh Boyer

With substantial assistance from:

  • Ruth Suehle
  • Luke Macken

The main issues we identified in summary were:

  • Inability to manage content easily
  • Registration process required frequent manual hacking
  • Multiple single points of failure for maintenance
  • Inability to relate funding decisions to content decisions

Given the comparison matrix, availability of useful software upstream, and the rate at which problems are addressed upstream, we agreed to propose this solution to the Flock staff.

Summary

! Use System
General content for users to read (pre-conference) fedora-web module
Registration, CfP, voting on papers regcfp
Content for event (at conference) Sched.org

Content

Content consists of information and messaging for the general public. This is how we advertise dates, venue, transportation information, travel tips, and calls to action.

Static site
Use a static site, managed with the fedora-web git repo similar to all other main Fedora websites, to post general information for the public about Flock. It will still reside at https://flocktofedora.org.
Request help from Design team (Ryan Lerch), hopefully building on a well known theme or model to bring into line with Fedora branding
Here is the git repo and a direct link to the folder in the tree.
Sched.org
Use sched.org for schedule arrangement, publishing, web + mobile access for attendees
(unchanged from Flock 2015)

User activities

User activities are the actions we ask for users to take ahead of the conference to provide data for the organizers.

regcfp
Use regcfp application for registration, desk, call for papers activity, and paper voting/acceptance. TODO: File RfR ticket with fedora-infrastructure, likely for Patrick to handle. DONE - to be available at https://register.flocktofedora.org
Visual elements will reflect Fedora branding.
The software team will create an administration and maintenance document on wiki for Flock planners using the system.
TBD: Generalize an ansible playbook so this app can be used for other Fedora events if desired. - IN PROGRESS - Patrick handling
Users will visit via https://register.flocktofedora.org URL.
The software team will monitor incoming issues and prioritize based on the Flock planning team's needs.