11:06 a.m.
https://meetbot.fedoraproject.org/fedora-flock/2017-04-19/regcfp_flock_20...
Summary to follow.
~m
1:53 p.m.
Hi,
As promised,a meeting summary follows below. Note that I intend to blog
this too, so I would greatly appreciate some 'fact-checking' on my
summary below! Also note the open question at the bottom.
Cheers,
~m
Flock Details Update
============
Flock Session Focus Changes
--------------------------------------------
Overall, the Council aims for Flock to be more of a "do" and less of a
"talk" event than in the past. This will affect the types of session
proposals that will be accepted - a team status report will be less
likely to be accepted than a collaborative team working session or a
workshop.
The driving factor here is that the Council would like to make sure we
have the right people at Flock to be able to be productive and achieve
our goals.
Rough Flock Schedule Plan:
------------------------------------------
Day 1: Talks + level-setting
Day 2: "Do" events - hackfests / workshops / working meetings for teams
/ etc.
Day 3: "Do" events - hackfests / workshops / working meetings for teams
/ etc.
Day 4: Conclusions, show & Tell
There will be varied available durations for sessions. Time blocks could
include 30, 60, 90, or 120 minute sessions. The Flock team will work
out schedule based on CFP entries, and by working with various
submitters where needed so the schedule-tetris varying slot durations
causes will work out.
Tentative Registration / CFP Dates:
----------------------------------------------------
Tentative plan (based on development work needed for regcfp):
Registration open: May 1*
Call for Proposals open: May 1 - June 1*
Dates may change based on puiterwijk's ability to implement necessary
features into regcfp. (More details on that in sections below.)
Flock Funding Changes
------------------------------------
• We are going to charge a nominal registration fee for Flock this year.
This fee will vary based on registrant's country, perhaps using a system
such as the Big Mac Index
(http://www.economist.com/content/big-mac-index/). Tenative suggested US
registrant fee is $25.
• We are going to go to a funding model where some participants may be
partially funded rather than 100% funded.
• We are going to collect cost estimates for travel funding requests,
collect payment for co-funded situations, and book travel for those
registrants only after their co-funding / registration payment has been
received.
• We are investigating whether or not we can use PayPal for managing
payments.
Call for Proposals Notes
==============
regcfp RFEs for CFP:
------------------------------
1) We need a new field for CFP submission. The field should allow
session proposers to indicate "Who needs to be present in this session
for it to be successful?" User needs to include name or FAS ID in
regcfp UI. A multi-value field for this to allow for multiple people to
be indicated in the answer is desirable. It would also be nice for the
field to allow freeform name entry and FAS id lookup.
2) We need a new CFP submission field to ask proposers to indicate how
much time they would like for their session. puiterwijk suggested using
the tracks system for this. A number of durations should be available to
be selected from. (What durations? Multiple of a common unit?) (Maybe
there should be an unsure option?)
Registration Notes
===========
Fields in regcfp today
---------------------------------
The registration info regcfp collects today:
• email
• name
• country
• subsidy request
• invite letter
• vegetarian
• dietary (e.g. allergies / medical issues)
• volunteer
• family
• shirtsize
• roomshare
• roommate
• hotel booked
• brno bus
• ircnick
• blog
• twitter
• badge extra line
Payment System
--------------------------
• PayPal and pay-on-site supported by regcfp.
• We will not use pay-on-site option (all tickets must be paid online in
advance.) bex working on getting PayPal cleared by RH.
• puiterwijk will need API keys / various permissions on account to be
able to implement paypal
Travel Funding Request Functionality
-------------------------------------------------------
• We are going to offer a "would you like to add more $$ to help
subsidize the travel of other contributors" option.
• We can ask users for country and prefill a suggested / default amount,
or have a table and allow people to fill out themselves. May need a box
for extra amount (eg cab/bus to get to airport?) that would be added
into the total.
• We want to display the expected cost of the person's funding level to
them. This will involve some basic math fields on things like hotel
rooms (nights x rate), etc. we will also need to ask them to input
things like estimated airfare costs and have a checkbox about whether
they can afford the ticket or not.
• We want to ask them, what if anything they can afford to pay. The
idea is to take our funding from 0% or 100% to a more flexibile number.
so after that we need to be able to later bill the people who are
accepted if they are paying anything. we also want to add some
information on things that will not be covered - for funded and
non-funded people - add links to this screen to reemphasize data on the
main site. like "only X meals are provided, average meal cost is Y - be
prepared" ...etc.
• Bill must be paid before anything is booked.
• After people submit a request, the details will be worked out out of
the system? Or do we need to do all of that inside there too?
‣ If someone needs to change their terms they can talk to us
‣ We want to look to the system for bookkeeping.
‣ We need to download the data and if needed adjust amounts being
requested from the person in the system.
‣ It'd be nice to have the system be able to know if someone paid, and
funding co-pay if any
regcfp RFEs for registration:
------------------------------------------
1) Registration: Add field for "What are you goals in attending Flock?"
in registration
2) Registration: Add reminder about FAS email address so registrants
know what email address to check for Flock info. by default emails sent
to fas(a)fedoraproject.org https://github.com/puiterwijk/regcfp/issues/200
- potentially allow email editing
3) Registration: Handle scaled registration fee:
https://github.com/puiterwijk/regcfp/issues/199
4) Registration: Hardship justification for subsidy request:
https://github.com/puiterwijk/regcfp/issues/198 (mizmo to mock up)
Action items:
========
• puiterwijk to work on regcfp RFEs above
• mizmo to put together mockup for subsidy request
• puiterwijk to set up check in for next week
Open questions:
==============
• T-shirts - included or add-on item? If not included, will require
changes to registration form we didn't discuss.
5:49 a.m.
On Wed, Apr 19, 2017, at 08:53 PM, Máirín Duffy wrote:
Hi,
As promised,a meeting summary follows below. Note that I intend to blog
this too, so I would greatly appreciate some 'fact-checking' on my
summary below! Also note the open question at the bottom.
I am planning to steal some of this for the announcement post :)
Flock Details Update
============
Flock Session Focus Changes
--------------------------------------------
Overall, the Council aims for Flock to be more of a "do" and less of a
"talk" event than in the past. This will affect the types of session
proposals that will be accepted - a team status report will be less
likely to be accepted than a collaborative team working session or a
workshop.
The driving factor here is that the Council would like to make sure we
have the right people at Flock to be able to be productive and achieve
our goals.
I read it as:
Additionally, the programming and funding teams will be considering
whether we will have the right people at Flock to be able to be
productive and achieve our goals, so we will be asking for proposers to
identify those people.
Rough Flock Schedule Plan:
------------------------------------------
Day 1: Talks + level-setting
Day 2: "Do" events - hackfests / workshops / working meetings for teams
/ etc.
Day 3: "Do" events - hackfests / workshops / working meetings for teams
/ etc.
Day 4: Conclusions, show & Tell
There will be varied available durations for sessions. Time blocks could
include 30, 60, 90, or 120 minute sessions. The Flock team will work
out schedule based on CFP entries, and by working with various
submitters where needed so the schedule-tetris varying slot durations
causes will work out.
Tentative Registration / CFP Dates:
----------------------------------------------------
Tentative plan (based on development work needed for regcfp):
Registration open: May 1*
Call for Proposals open: May 1 - June 1*
Dates may change based on puiterwijk's ability to implement necessary
features into regcfp. (More details on that in sections below.)
Flock Funding Changes
------------------------------------
• We are going to charge a nominal registration fee for Flock this year.
This fee will vary based on registrant's country, perhaps using a system
such as the Big Mac Index
(http://www.economist.com/content/big-mac-index/). Tenative suggested US
registrant fee is $25.
• We are going to go to a funding model where some participants may be
partially funded rather than 100% funded.
• We are going to collect cost estimates for travel funding requests,
collect payment for co-funded situations, and book travel for those
registrants only after their co-funding / registration payment has been
received.
• We are investigating whether or not we can use PayPal for managing
payments.
Call for Proposals Notes
==============
regcfp RFEs for CFP:
------------------------------
1) We need a new field for CFP submission. The field should allow
session proposers to indicate "Who needs to be present in this session
for it to be successful?" User needs to include name or FAS ID in
regcfp UI. A multi-value field for this to allow for multiple people to
be indicated in the answer is desirable. It would also be nice for the
field to allow freeform name entry and FAS id lookup.
2) We need a new CFP submission field to ask proposers to indicate how
much time they would like for their session. puiterwijk suggested using
the tracks system for this. A number of durations should be available to
be selected from. (What durations? Multiple of a common unit?) (Maybe
there should be an unsure option?)
My gut feeling after the session yesterday was: 60, 120, 240
> Registration Notes
> ===========
>
> Fields in regcfp today
> ---------------------------------
>
> The registration info regcfp collects today:
>
> • email
> • name
> • country
> • subsidy request
> • invite letter
> • vegetarian
> • dietary (e.g. allergies / medical issues)
> • volunteer
> • family
> • shirtsize
> • roomshare
> • roommate
> • hotel booked
> • brno bus
> • ircnick
> • blog
> • twitter
> • badge extra line
>
> Payment System
> --------------------------
>
> • PayPal and pay-on-site supported by regcfp.
> • We will not use pay-on-site option (all tickets must be paid online in
> advance.) bex working on getting PayPal cleared by RH.
> • puiterwijk will need API keys / various permissions on account to be
> able to implement paypal
>
> Travel Funding Request Functionality
> -------------------------------------------------------
>
> • We are going to offer a "would you like to add more $$ to help
> subsidize the travel of other contributors" option.
> • We can ask users for country and prefill a suggested / default amount,
> or have a table and allow people to fill out themselves. May need a box
> for extra amount (eg cab/bus to get to airport?) that would be added
> into the total.
> • We want to display the expected cost of the person's funding level to
> them. This will involve some basic math fields on things like hotel
> rooms (nights x rate), etc. we will also need to ask them to input
> things like estimated airfare costs and have a checkbox about whether
> they can afford the ticket or not.
> • We want to ask them, what if anything they can afford to pay. The
> idea is to take our funding from 0% or 100% to a more flexibile number.
> so after that we need to be able to later bill the people who are
> accepted if they are paying anything. we also want to add some
> information on things that will not be covered - for funded and
> non-funded people - add links to this screen to reemphasize data on the
> main site. like "only X meals are provided, average meal cost is Y - be
> prepared" ...etc.
> • Bill must be paid before anything is booked.
> • After people submit a request, the details will be worked out out of
> the system? Or do we need to do all of that inside there too?
> ‣ If someone needs to change their terms they can talk to us
> ‣ We want to look to the system for bookkeeping.
> ‣ We need to download the data and if needed adjust amounts being
> requested from the person in the system.
> ‣ It'd be nice to have the system be able to know if someone paid, and
> funding co-pay if any
>
>
> regcfp RFEs for registration:
> ------------------------------------------
>
>
> 1) Registration: Add field for "What are you goals in attending Flock?"
> in registration
>
> 2) Registration: Add reminder about FAS email address so registrants
> know what email address to check for Flock info. by default emails sent
> to fas(a)fedoraproject.org https://github.com/puiterwijk/regcfp/issues/200
> - potentially allow email editing
>
> 3) Registration: Handle scaled registration fee:
> https://github.com/puiterwijk/regcfp/issues/199
>
> 4) Registration: Hardship justification for subsidy request:
> https://github.com/puiterwijk/regcfp/issues/198 (mizmo to mock up)
>
>
> Action items:
> ========
>
> • puiterwijk to work on regcfp RFEs above
> • mizmo to put together mockup for subsidy request
> • puiterwijk to set up check in for next week
>
> Open questions:
> ==============
>
> • T-shirts - included or add-on item? If not included, will require
> changes to registration form we didn't discuss.
> _______________________________________________
> flock-planning mailing list -- flock-planning(a)lists.fedoraproject.org
> To unsubscribe send an email to
> flock-planning-leave(a)lists.fedoraproject.org
8:01 a.m.
On 04/20/2017 06:49 AM, Brian Exelbierd wrote:
On Wed, Apr 19, 2017, at 08:53 PM, Máirín Duffy wrote:
...
> Call for Proposals Notes
> ==============
>
> regcfp RFEs for CFP:
> ------------------------------
>
> 1) We need a new field for CFP submission. The field should allow
> session proposers to indicate "Who needs to be present in this session
> for it to be successful?" User needs to include name or FAS ID in
> regcfp UI. A multi-value field for this to allow for multiple people to
> be indicated in the answer is desirable. It would also be nice for the
> field to allow freeform name entry and FAS id lookup.
>
> 2) We need a new CFP submission field to ask proposers to indicate how
> much time they would like for their session. puiterwijk suggested using
> the tracks system for this. A number of durations should be available to
> be selected from. (What durations? Multiple of a common unit?) (Maybe
> there should be an unsure option?)
My gut feeling after the session yesterday was: 60, 120, 240
I think it should be different for the level-setting talks, the "do"
sessions
and the report-outs.
My suggestions:
* Talks on Day 1 may have either 30 or 60 minute slots
* "do" sessions cannot be successful at shorter than 120 minutes (from past
experience). The first hour of any workshop always involves getting everyone up
and running.
* All approved sessions for days two and three have a mandatory 15-minute
summary presentation on Day Four. These should be in the Keynote room and
broadcast to overflow rooms as needed. No other sessions should be scheduled in
conflict with them.
8:57 a.m.
On Thu, Apr 20, 2017, at 03:01 PM, Stephen Gallagher wrote:
On 04/20/2017 06:49 AM, Brian Exelbierd wrote:
> On Wed, Apr 19, 2017, at 08:53 PM, Máirín Duffy wrote:
...
>> Call for Proposals Notes
>> ==============
>>
>> regcfp RFEs for CFP:
>> ------------------------------
>>
>> 1) We need a new field for CFP submission. The field should allow
>> session proposers to indicate "Who needs to be present in this session
>> for it to be successful?" User needs to include name or FAS ID in
>> regcfp UI. A multi-value field for this to allow for multiple people to
>> be indicated in the answer is desirable. It would also be nice for the
>> field to allow freeform name entry and FAS id lookup.
>>
>> 2) We need a new CFP submission field to ask proposers to indicate how
>> much time they would like for their session. puiterwijk suggested using
>> the tracks system for this. A number of durations should be available to
>> be selected from. (What durations? Multiple of a common unit?) (Maybe
>> there should be an unsure option?)
>
> My gut feeling after the session yesterday was: 60, 120, 240
>
I think it should be different for the level-setting talks, the "do"
sessions
and the report-outs.
My suggestions:
* Talks on Day 1 may have either 30 or 60 minute slots
* "do" sessions cannot be successful at shorter than 120 minutes (from
past
experience). The first hour of any workshop always involves getting
everyone up
and running.
I like it. To make it easy to select in the track list, I am
interpreting your idea to be choices of:
Talk (30 min)
Talk (60 min)
Do-Session (120 Min)
Do-Session (240 Min)
* All approved sessions for days two and three have a mandatory
15-minute
summary presentation on Day Four. These should be in the Keynote room and
broadcast to overflow rooms as needed. No other sessions should be
scheduled in
conflict with them.
I also like this :)
Sounds like we need to alert in the CFP that do-sessions have this
requirement. We should also mention that if you need more than 240 min
you should propose a "part 1" and a "part 2" and just note that both
are
required (or if part 2 is optional).
regards,
bex
2563
days inactive
2564
days old
flock-planning@lists.fedoraproject.org
4 comments
4 participants
participants (4)
-
Brian Exelbierd -
Máirín Duffy -
Máirín Duffy -
Stephen Gallagher