| Line 46: | Line 46: | ||
:Move the installation to an appropriate location in the Fedora infrastructure. '''TODO: File ticket with fedora-infrastructure to include on the infra cloud.''' | :Move the installation to an appropriate location in the Fedora infrastructure. '''TODO: File ticket with fedora-infrastructure to include on the infra cloud.''' | ||
:Simplify the installation to eliminate some custom theme/plugins which have resulted in confusing and difficult administration. | :Simplify the installation to eliminate some custom theme/plugins which have resulted in confusing and difficult administration. | ||
:Request refreshed theme from Design team to | :Request refreshed theme from Design team, hopefully building on a well known theme or model to bring minimally in line with Fedora branding | ||
;Sched.org | ;Sched.org | ||
Revision as of 20:05, 19 November 2015
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) | WordPress |
| 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.
- WordPress
- Continue to use WordPress 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.
- Simplify the installation to eliminate some custom theme/plugins which have resulted in confusing and difficult administration.
- Request refreshed theme from Design team, hopefully building on a well known theme or model to bring minimally in line with Fedora branding
- 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.
- 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.
- 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.