Ryan Lerch kindly pulled together a branch for the fedora-websites: https://pagure.io/fedora-websites/branch/flock2017-WIP
You can see the results by cloning the repo, changing to that branch, moving to the flocktofedora.org/ folder, and running 'make en test'. (Read the README to make sure you have the right stuff installed on Fedora to do the build.) Run 'make stoptest' when done.
First, thanks to Ryan to pulling this together very quickly. I think it looks beautiful. It's in the spirit of last year's Krakow site theme but has its own character/color scheme. Hopefully we can use this for 2017.
Second, this brings up a number of things needed to push it live:
1. A registration site -- we should be able to reuse register.flocktofedora.org along with the backing app, but it does need set up. IIRC this was simply run in our OpenStack instance up through the time of the conference.
2. We've also spoken about having a modest registration fee to offset swag and/or deal with the no-show registration issue. The site can also handle this IIRC, just needs a decision from Flock planners.
Things not needed immediately to push the site out, but needed soon for community awareness and/or a better conference:
3. The registration site also does CFP. So we need to know whether and when there is a CFP. This can be turned on at any time, even after the registrations are already being accepted.
4. A flock-attendees-2017 mailing list people can join, to be linked on the site. I believe a flock-speakers-2017 mailing list is also needed and used later for speakers once selected.
5. We can strip out other leftover content from Krakow, for example sponsors. However, it would be good to know what the plan is for finding sponsors, as we are only five months out from the event.
Brian, I can work with my team to provide the registration site. Can you provide clarity on #2 above, as well as a date when we need to open registration?
Any other thoughts on things we need so we can start building Flock awareness publicly?
On Wed, Mar 29, 2017 at 9:53 AM, Paul W. Frields stickster@gmail.com wrote:
Ryan Lerch kindly pulled together a branch for the fedora-websites: https://pagure.io/fedora-websites/branch/flock2017-WIP
You can see the results by cloning the repo, changing to that branch, moving to the flocktofedora.org/ folder, and running 'make en test'. (Read the README to make sure you have the right stuff installed on Fedora to do the build.) Run 'make stoptest' when done.
First, thanks to Ryan to pulling this together very quickly. I think it looks beautiful. It's in the spirit of last year's Krakow site theme but has its own character/color scheme. Hopefully we can use this for 2017.
Second, this brings up a number of things needed to push it live:
A registration site -- we should be able to reuse register.flocktofedora.org along with the backing app, but it does need set up. IIRC this was simply run in our OpenStack instance up through the time of the conference.
We've also spoken about having a modest registration fee to offset swag and/or deal with the no-show registration issue. The site can also handle this IIRC, just needs a decision from Flock planners.
Things not needed immediately to push the site out, but needed soon for community awareness and/or a better conference:
The registration site also does CFP. So we need to know whether and when there is a CFP. This can be turned on at any time, even after the registrations are already being accepted.
A flock-attendees-2017 mailing list people can join, to be linked on the site. I believe a flock-speakers-2017 mailing list is also needed and used later for speakers once selected.
We can strip out other leftover content from Krakow, for example sponsors. However, it would be good to know what the plan is for finding sponsors, as we are only five months out from the event.
Brian, I can work with my team to provide the registration site. Can you provide clarity on #2 above, as well as a date when we need to open registration?
Bex is traveling today. We discussed this and a number of other ideas related to registration and format at the Council FAD. I expect he will be pinging the planning committee about that soon.
josh
Any other thoughts on things we need so we can start building Flock awareness publicly?
-- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com _______________________________________________ flock-planning mailing list -- flock-planning@lists.fedoraproject.org To unsubscribe send an email to flock-planning-leave@lists.fedoraproject.org
On Wed, Mar 29, 2017 at 10:11:38AM -0400, Josh Boyer wrote:
On Wed, Mar 29, 2017 at 9:53 AM, Paul W. Frields stickster@gmail.com wrote:
Ryan Lerch kindly pulled together a branch for the fedora-websites: https://pagure.io/fedora-websites/branch/flock2017-WIP
You can see the results by cloning the repo, changing to that branch, moving to the flocktofedora.org/ folder, and running 'make en test'. (Read the README to make sure you have the right stuff installed on Fedora to do the build.) Run 'make stoptest' when done.
First, thanks to Ryan to pulling this together very quickly. I think it looks beautiful. It's in the spirit of last year's Krakow site theme but has its own character/color scheme. Hopefully we can use this for 2017.
Second, this brings up a number of things needed to push it live:
A registration site -- we should be able to reuse register.flocktofedora.org along with the backing app, but it does need set up. IIRC this was simply run in our OpenStack instance up through the time of the conference.
We've also spoken about having a modest registration fee to offset swag and/or deal with the no-show registration issue. The site can also handle this IIRC, just needs a decision from Flock planners.
Things not needed immediately to push the site out, but needed soon for community awareness and/or a better conference:
The registration site also does CFP. So we need to know whether and when there is a CFP. This can be turned on at any time, even after the registrations are already being accepted.
A flock-attendees-2017 mailing list people can join, to be linked on the site. I believe a flock-speakers-2017 mailing list is also needed and used later for speakers once selected.
We can strip out other leftover content from Krakow, for example sponsors. However, it would be good to know what the plan is for finding sponsors, as we are only five months out from the event.
Brian, I can work with my team to provide the registration site. Can you provide clarity on #2 above, as well as a date when we need to open registration?
Bex is traveling today. We discussed this and a number of other ideas related to registration and format at the Council FAD. I expect he will be pinging the planning committee about that soon.
Any other thoughts on things we need so we can start building Flock awareness publicly?
Hi, I know the Council FAD required some work to report out and so forth. I'm wondering how we're doing on schedule for Flock pieces like a CFP.
With many other critical deliverables from my team for F26/F27, we're not left with much time to spare for registration or CFP features.
flock-planning@lists.fedoraproject.org
-
Josh Boyer -
Paul W. Frields