The BSDCan Papers Committee is an independent body that selects which events happen at BSDCan. The Papers Committee is expected to select from proposals that represent the greatest interest to the community. Papers committee members have the following responsibilities. (Thank you PNMH for allowing us to pillage your list for EuroBSDCon!)

====== Pre-conference ======

- review the talks from the previous conference and/or any notes from same (videos will help), note in internal notes

- watch development in your favorite OS and the environment community, contact people who sound like they could be good speakers, urge to submit (TIP: the projects generally have mailing lists for commits, consider subscribing to those and/or checking list archives such as [[https://marc.info|https://marc.info]] regularly)

- read and suggest improvement to call for participation posting text

====== When CFP Goes Out ======

- keep contacting likely good presenters

- repost the CFP or links to it on mailing lists, forums, diverse social media (including any local user groups)

====== During CFP ======

- watch submissions coming in, grade early

- keep contacting likely good presenters

- repost the CFP or links to it on mailing lists, forums, diverse social media (including any local user groups)

- encourage submitters to improve their submissions if they seem incomplete (remember to cc the pc mailing list). We *require* complete contact information, full name, title and a meaningful abstract.

- we can consider contacting prospective speakers to have them do a test presentation of a shortened version of their talk for the PC over Jitsi or similar

====== After CFP deadline ======

- Grade submissions as soon as possible after CFP deadline. The sooner we can conclude grading, the sooner we can put the initial program together and announce

- Consider input from con chair on logistics or individual issues with proposals. (Con chair is a non-voting member: you can override their input, we just ask that you listen and consider.)

====== After initial program is posted (and registration starts) ======

- repost the program and/or links to it on mailing lists, forums, diverse social media (including any local user groups)

- Take care of random program problems as needed (select replacements if talks are canceled, etc)

====== After the conference ======

- watch development in your favorite OS and the environment community, contact people who sound like they could be good speakers, urge to submit (see above)

- read and suggest improvement to call for participation posting text

And during it all, keep in contact with the program committee and potential and prospective speakers with a view to making the next conference even better.