Remove ^M line endings

This commit is contained in:
Ben Sturmfels 2024-03-08 13:45:36 +11:00
parent fca799624d
commit c5013ce86b
Signed by: bsturmfels
GPG key ID: 023C05E2C9C068F0
16 changed files with 1036 additions and 1036 deletions

View file

@ -165,42 +165,42 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 class="page-title">About FOSSY</h1>
<h3>FOSS is back in Portland, OR - July 13-16th 2023 at the Oregon Convention
Center!</h3>
<figure class="tc">
<img src="https://sfconservancy.org/img/occ.jpg" alt="Aerial photograph of the Oregon Convention Center" >
<figcaption class="tc mt2">Oregon Convention Center (CC-BY 2.0)</figcaption>
</figure>
<p>Software Freedom Conservancy is so proud to announce that we are hosting a
community oriented conference this coming summer. FOSSY (Free and Open Source
Yearly) is focused on the creation and impact of free and open source software,
uplifting contributors of all experience. We are also mindful of having a safe
environment for all. In this new time of conferences, we will be focused on
COVID safety and making sure all attendees feel safe participating as much as
they feel comfortable (please take a look at the <a href="../attend/health-and-safety/index.html">policy</a> ).</p>
<p>Taking place in Portland, OR, we hope FOSSY will be a community focused
event that invites local community, as well as the wider internet and global
communites we have formed over the years. Whether you are a long time
contributing member of a free software project, a recent graduate of a
coding bootcamp or university, or just have an interest in the possibilies
that free and open source software bring, FOSSY will have something for
you.</p>
<p>For this first year we are running a conference of this scale, we are having
around 12 tracks with talks over 4 days. With tracks for community building,
development and legal and licensing issues, our conference will provide ample
learning and networking opportunities for contributors of all levels of
experience. There will be hands on workshops, lightning talks and
traditional 50 minute talks.</p>
<p>As we look to the future of conferences, we are excited to focus on using
free software to run a conference and will seek to help reduce the amount of
proprietary software that is treated as default.</p>
<h1 class="page-title">About FOSSY</h1>
<h3>FOSS is back in Portland, OR - July 13-16th 2023 at the Oregon Convention
Center!</h3>
<figure class="tc">
<img src="https://sfconservancy.org/img/occ.jpg" alt="Aerial photograph of the Oregon Convention Center" >
<figcaption class="tc mt2">Oregon Convention Center (CC-BY 2.0)</figcaption>
</figure>
<p>Software Freedom Conservancy is so proud to announce that we are hosting a
community oriented conference this coming summer. FOSSY (Free and Open Source
Yearly) is focused on the creation and impact of free and open source software,
uplifting contributors of all experience. We are also mindful of having a safe
environment for all. In this new time of conferences, we will be focused on
COVID safety and making sure all attendees feel safe participating as much as
they feel comfortable (please take a look at the <a href="../attend/health-and-safety/index.html">policy</a> ).</p>
<p>Taking place in Portland, OR, we hope FOSSY will be a community focused
event that invites local community, as well as the wider internet and global
communites we have formed over the years. Whether you are a long time
contributing member of a free software project, a recent graduate of a
coding bootcamp or university, or just have an interest in the possibilies
that free and open source software bring, FOSSY will have something for
you.</p>
<p>For this first year we are running a conference of this scale, we are having
around 12 tracks with talks over 4 days. With tracks for community building,
development and legal and licensing issues, our conference will provide ample
learning and networking opportunities for contributors of all levels of
experience. There will be hands on workshops, lightning talks and
traditional 50 minute talks.</p>
<p>As we look to the future of conferences, we are excited to focus on using
free software to run a conference and will seek to help reduce the amount of
proprietary software that is treated as default.</p>
<p>If you are interested in sponsoring our conference, please see our <a href="https://sfconservancy.org/docs/Fossy-Prospectus.pdf">Sponsorship Prospectus</a> or contact us at <a href="mailto:conference@sfconservancy.org">conference@sfconservancy.org</a>.</p>
</div>
</div>

View file

@ -165,46 +165,46 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 class="page-title">Code of Conduct</h1>
<h2>tl;dr</h2>
<p>FOSSY is dedicated to providing a harassment-free conference experience for everyone; regardless of
gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, national
origin, race, or religion or lack thereof. This code applies to everyone -- including attendees, speakers,
volunteers and staff. We do not tolerate harassment of conference participants in any form.</p>
<h2>Details</h2>
<p>Please do not include sexualized imagery, off-color jokes or other materials that attendees may deem offensive
in your slides or spoken remarks. If you arent sure if something you intend to show or state is potentially offensive,
please contact us for help in reviewing your presentation materials.</p>
<p>Be kind to others. Do not insult or put down other participants. Behave professionally. Remember that sexist,
racist, or exclusionary jokes are not appropriate for FOSSY.</p>
<p>Harassment will not be tolerated at FOSSY. Harassment includes offensive verbal comments related to
gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, national
origin, race, religion or lack thereof, sexual images in public spaces, deliberate intimidation, stalking, following, harassing
photography or recording without permission, sustained disruption of talks or other parts of the event, inappropriate
physical contact, and unwelcome sexual attention.</p>
<p>Just as we will ask any audience member to cease their behavior and to leave if they are not respectful of you,
we will also ask that you stop presenting should there be offensive or inappropriate material in your slides or
presentation. This code applies to everyone -- including attendees, speakers, volunteers and staff.</p>
<p>Participants asked to stop any harassing behavior are expected to comply immediately. If they do not stop
immediately or their behavior constitutes a potential physical danger to other participants, they may be ejected
from the event without a refund. This will be at the discretion of FOSSY's response team.</p>
<p>If you believe that someone is violating the code of conduct during FOSSY, or have any other concerns,
please contact our response team immediately by emailing <a href="mailto:conference@sfconservancy.org">conference@sfconservancy.org</a>.</p>
<p>Conference staff can help you contact emergency services, local police and/or provide an escort to your hotel.</p>
<h2>Credits</h2>
<p>We borrowed heavily from the <a href="http://seagl.org/code_of_conduct.html">SeaGL</a> and <a href="https://2018.northbaypython.org/code-of-conduct">North Bay Python</a> Codes of Conduct which are based on <a href="http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy">this template</a> and include many of the <a href="https://us.pycon.org/2018/about/code-of-conduct/">variations used by PyCon</a>, all of which are available under the Creative Commons
<h1 class="page-title">Code of Conduct</h1>
<h2>tl;dr</h2>
<p>FOSSY is dedicated to providing a harassment-free conference experience for everyone; regardless of
gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, national
origin, race, or religion or lack thereof. This code applies to everyone -- including attendees, speakers,
volunteers and staff. We do not tolerate harassment of conference participants in any form.</p>
<h2>Details</h2>
<p>Please do not include sexualized imagery, off-color jokes or other materials that attendees may deem offensive
in your slides or spoken remarks. If you arent sure if something you intend to show or state is potentially offensive,
please contact us for help in reviewing your presentation materials.</p>
<p>Be kind to others. Do not insult or put down other participants. Behave professionally. Remember that sexist,
racist, or exclusionary jokes are not appropriate for FOSSY.</p>
<p>Harassment will not be tolerated at FOSSY. Harassment includes offensive verbal comments related to
gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, national
origin, race, religion or lack thereof, sexual images in public spaces, deliberate intimidation, stalking, following, harassing
photography or recording without permission, sustained disruption of talks or other parts of the event, inappropriate
physical contact, and unwelcome sexual attention.</p>
<p>Just as we will ask any audience member to cease their behavior and to leave if they are not respectful of you,
we will also ask that you stop presenting should there be offensive or inappropriate material in your slides or
presentation. This code applies to everyone -- including attendees, speakers, volunteers and staff.</p>
<p>Participants asked to stop any harassing behavior are expected to comply immediately. If they do not stop
immediately or their behavior constitutes a potential physical danger to other participants, they may be ejected
from the event without a refund. This will be at the discretion of FOSSY's response team.</p>
<p>If you believe that someone is violating the code of conduct during FOSSY, or have any other concerns,
please contact our response team immediately by emailing <a href="mailto:conference@sfconservancy.org">conference@sfconservancy.org</a>.</p>
<p>Conference staff can help you contact emergency services, local police and/or provide an escort to your hotel.</p>
<h2>Credits</h2>
<p>We borrowed heavily from the <a href="http://seagl.org/code_of_conduct.html">SeaGL</a> and <a href="https://2018.northbaypython.org/code-of-conduct">North Bay Python</a> Codes of Conduct which are based on <a href="http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy">this template</a> and include many of the <a href="https://us.pycon.org/2018/about/code-of-conduct/">variations used by PyCon</a>, all of which are available under the Creative Commons
Zero License. Please feel free to use any of this language for your own Code of Conduct.</p>
</div>
</div>

View file

@ -165,46 +165,46 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 class="page-title">Code of Conduct</h1>
<h2>tl;dr</h2>
<p>FOSSY is dedicated to providing a harassment-free conference experience for everyone; regardless of
gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, national
origin, race, or religion or lack thereof. This code applies to everyone -- including attendees, speakers,
volunteers and staff. We do not tolerate harassment of conference participants in any form.</p>
<h2>Details</h2>
<p>Please do not include sexualized imagery, off-color jokes or other materials that attendees may deem offensive
in your slides or spoken remarks. If you arent sure if something you intend to show or state is potentially offensive,
please contact us for help in reviewing your presentation materials.</p>
<p>Be kind to others. Do not insult or put down other participants. Behave professionally. Remember that sexist,
racist, or exclusionary jokes are not appropriate for FOSSY.</p>
<p>Harassment will not be tolerated at FOSSY. Harassment includes offensive verbal comments related to
gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, national
origin, race, religion or lack thereof, sexual images in public spaces, deliberate intimidation, stalking, following, harassing
photography or recording without permission, sustained disruption of talks or other parts of the event, inappropriate
physical contact, and unwelcome sexual attention.</p>
<p>Just as we will ask any audience member to cease their behavior and to leave if they are not respectful of you,
we will also ask that you stop presenting should there be offensive or inappropriate material in your slides or
presentation. This code applies to everyone -- including attendees, speakers, volunteers and staff.</p>
<p>Participants asked to stop any harassing behavior are expected to comply immediately. If they do not stop
immediately or their behavior constitutes a potential physical danger to other participants, they may be ejected
from the event without a refund. This will be at the discretion of FOSSY's response team.</p>
<p>If you believe that someone is violating the code of conduct during FOSSY, or have any other concerns,
please contact our response team immediately by emailing <a href="mailto:conference@sfconservancy.org">conference@sfconservancy.org</a>.</p>
<p>Conference staff can help you contact emergency services, local police and/or provide an escort to your hotel.</p>
<h2>Credits</h2>
<p>We borrowed heavily from the <a href="http://seagl.org/code_of_conduct.html">SeaGL</a> and <a href="https://2018.northbaypython.org/code-of-conduct">North Bay Python</a> Codes of Conduct which are based on <a href="http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy">this template</a> and include many of the <a href="https://us.pycon.org/2018/about/code-of-conduct/">variations used by PyCon</a>, all of which are available under the Creative Commons
<h1 class="page-title">Code of Conduct</h1>
<h2>tl;dr</h2>
<p>FOSSY is dedicated to providing a harassment-free conference experience for everyone; regardless of
gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, national
origin, race, or religion or lack thereof. This code applies to everyone -- including attendees, speakers,
volunteers and staff. We do not tolerate harassment of conference participants in any form.</p>
<h2>Details</h2>
<p>Please do not include sexualized imagery, off-color jokes or other materials that attendees may deem offensive
in your slides or spoken remarks. If you arent sure if something you intend to show or state is potentially offensive,
please contact us for help in reviewing your presentation materials.</p>
<p>Be kind to others. Do not insult or put down other participants. Behave professionally. Remember that sexist,
racist, or exclusionary jokes are not appropriate for FOSSY.</p>
<p>Harassment will not be tolerated at FOSSY. Harassment includes offensive verbal comments related to
gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, national
origin, race, religion or lack thereof, sexual images in public spaces, deliberate intimidation, stalking, following, harassing
photography or recording without permission, sustained disruption of talks or other parts of the event, inappropriate
physical contact, and unwelcome sexual attention.</p>
<p>Just as we will ask any audience member to cease their behavior and to leave if they are not respectful of you,
we will also ask that you stop presenting should there be offensive or inappropriate material in your slides or
presentation. This code applies to everyone -- including attendees, speakers, volunteers and staff.</p>
<p>Participants asked to stop any harassing behavior are expected to comply immediately. If they do not stop
immediately or their behavior constitutes a potential physical danger to other participants, they may be ejected
from the event without a refund. This will be at the discretion of FOSSY's response team.</p>
<p>If you believe that someone is violating the code of conduct during FOSSY, or have any other concerns,
please contact our response team immediately by emailing <a href="mailto:conference@sfconservancy.org">conference@sfconservancy.org</a>.</p>
<p>Conference staff can help you contact emergency services, local police and/or provide an escort to your hotel.</p>
<h2>Credits</h2>
<p>We borrowed heavily from the <a href="http://seagl.org/code_of_conduct.html">SeaGL</a> and <a href="https://2018.northbaypython.org/code-of-conduct">North Bay Python</a> Codes of Conduct which are based on <a href="http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy">this template</a> and include many of the <a href="https://us.pycon.org/2018/about/code-of-conduct/">variations used by PyCon</a>, all of which are available under the Creative Commons
Zero License. Please feel free to use any of this language for your own Code of Conduct.</p>
</div>
</div>

View file

@ -165,30 +165,30 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 class="page-title">FOSSY 2023 Health and Safety Guidelines</h1>
<p>Our attendees' health and safety have been a top priority for us. Our goal with this policy is to balancing our limited resources as a small non-profit while protecting our attendees and their families from COVID-19 and its possible long-term side effects. We are aiming to provide a welcoming and safer environment for people who are immunocompromised, disabled, elderly, have support needs, or are caregivers for children, and those of us who share households with or caretake for people in those groups.</p>
<p>We will provide room for social distancing wherever possible in the venue. Hand sanitizer will be available for all attendees. We will direct people to locations for eating that are as well ventilated or spacious as we can, including providing food in packaging for attendees to take outside if they prefer.</p>
<p>We value all of our attendees and want everyone to feel welcome to participate in any way they can. In turn, we ask that you, as attendees, respect your fellow attendees and do what you can to create an environment that is safe and welcoming to all.</p>
<h3 id="masks">Mask Requirement</h3>
<p>Face coverings will be required of everyone inside the conference venue at FOSSY. We will have attendees from all over the world who have traveled and may have unknowingly been exposed to COVID-19.<br>Exceptions are:<br><ol start="1" class="number"><li>Outdoor spaces</li><li>Indoors while consuming food and while socially distanced from other participants</li><li>While necessary for communicating with someone who is hearing impaired when the ability to see the mouth is essential for communication</li><li>Speakers while presenting</li><li>Those who are unable to wear masks due to a medical condition. Please contact us in advance of the conference and we will provide a badge or lanyard that indicates this.</ol>Masks must be worn over the nose and mouth and must be made of a tight-knit, non-permeable material. N95 or equivalent masks are required. As N95 is an American standard, masks certified by other governments to similar standards (e.g. PM2.5, KN95, and KF94) will also be allowed.<br>We will be distributing masks so long as our supplies last, but attendees should plan to provide their own masks should we run out.</p>
<h3>Rapid Testing</h3>
<p>We highly encourage attendees to do a rapid test before traveling and each day of the event. Unfortunately providing free, rapid onsite testing for all attendees is not feasible, but if purchasing your own tests is a financial hardship, please contact us and we will help you acquire some.</p>
<h3>Badge Indicators</h3>
<p>Attendees will be able to indicate their negative tested status each day on their badge with a sticker that can be picked up at the registration table.<br>We'll also have a way for attendees to indicate what level of social distancing they are most comfortable with.</p>
<h3>Attendance</h3>
<p>Individuals should not attend the event if they are COVID-positive, are exhibiting COVID symptoms (as defined by the CDC), or have been exposed, within 7 days prior to the event, to someone who was COVID-positive or showed COVID symptoms.<br>If you are feeling sick or exhibiting symptoms of COVID-19, or test positive for COVID-19, prior to the start of the conference, or on any day of the conference, please contact us at conference@sfconservancy.org, and we will issue you a refund.</p>
<h1 class="page-title">FOSSY 2023 Health and Safety Guidelines</h1>
<p>Our attendees' health and safety have been a top priority for us. Our goal with this policy is to balancing our limited resources as a small non-profit while protecting our attendees and their families from COVID-19 and its possible long-term side effects. We are aiming to provide a welcoming and safer environment for people who are immunocompromised, disabled, elderly, have support needs, or are caregivers for children, and those of us who share households with or caretake for people in those groups.</p>
<p>We will provide room for social distancing wherever possible in the venue. Hand sanitizer will be available for all attendees. We will direct people to locations for eating that are as well ventilated or spacious as we can, including providing food in packaging for attendees to take outside if they prefer.</p>
<p>We value all of our attendees and want everyone to feel welcome to participate in any way they can. In turn, we ask that you, as attendees, respect your fellow attendees and do what you can to create an environment that is safe and welcoming to all.</p>
<h3 id="masks">Mask Requirement</h3>
<p>Face coverings will be required of everyone inside the conference venue at FOSSY. We will have attendees from all over the world who have traveled and may have unknowingly been exposed to COVID-19.<br>Exceptions are:<br><ol start="1" class="number"><li>Outdoor spaces</li><li>Indoors while consuming food and while socially distanced from other participants</li><li>While necessary for communicating with someone who is hearing impaired when the ability to see the mouth is essential for communication</li><li>Speakers while presenting</li><li>Those who are unable to wear masks due to a medical condition. Please contact us in advance of the conference and we will provide a badge or lanyard that indicates this.</ol>Masks must be worn over the nose and mouth and must be made of a tight-knit, non-permeable material. N95 or equivalent masks are required. As N95 is an American standard, masks certified by other governments to similar standards (e.g. PM2.5, KN95, and KF94) will also be allowed.<br>We will be distributing masks so long as our supplies last, but attendees should plan to provide their own masks should we run out.</p>
<h3>Rapid Testing</h3>
<p>We highly encourage attendees to do a rapid test before traveling and each day of the event. Unfortunately providing free, rapid onsite testing for all attendees is not feasible, but if purchasing your own tests is a financial hardship, please contact us and we will help you acquire some.</p>
<h3>Badge Indicators</h3>
<p>Attendees will be able to indicate their negative tested status each day on their badge with a sticker that can be picked up at the registration table.<br>We'll also have a way for attendees to indicate what level of social distancing they are most comfortable with.</p>
<h3>Attendance</h3>
<p>Individuals should not attend the event if they are COVID-positive, are exhibiting COVID symptoms (as defined by the CDC), or have been exposed, within 7 days prior to the event, to someone who was COVID-positive or showed COVID symptoms.<br>If you are feeling sick or exhibiting symptoms of COVID-19, or test positive for COVID-19, prior to the start of the conference, or on any day of the conference, please contact us at conference@sfconservancy.org, and we will issue you a refund.</p>
<p>These guidelines may change based on health and safety recommendations at the time of the event. We are committing, however, to only make changes in the direction of greater safety.</p>
</div>
</div>

View file

@ -165,81 +165,81 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 class="page-title">Terms and Conditions</h1>
<p><em>This document was forked from the <a href="https://github.com/northbaypython/website/blob/master/pinaxcon/templates/static_pages/terms_and_conditions.md">North Bay Python Terms and Conditions</a>.</em></p>
<p>These Terms and Conditions apply to all attendees who have registered for FOSSY 2023.</p>
<h2>Registration</h2>
<p>Registering for the event does not guarantee your ticket until it has been paid for in full. To secure your ticket, pay the registration invoice as soon as possible.</p>
<h2>Cancellation Policy</h2>
<p><strong>Cancellations made prior to July 6th, 2023</strong>: Incur a cancellation fee of 50% of the ticket cost, which will be deducted from any registration fee paid. The balance will be refunded.</p>
<p><strong>Cancellations made after July 7th, 2023</strong>: No refund.</p>
<h2>Substitutions</h2>
<p>You may substitute another person, however you must contact us with this person's details.</p>
<h2>Privacy Notice</h2>
<p>In the course of registering for the event and related events, personal information will be collected about attendees such as their name, contact details, etc. This information is required to facilitate registration to the event, for catering requirements, and for organizers or their agents to contact particular attendees as and when required in respect of the event. Attendees who do not disclose this personal information will be unable to complete registration at the event and will therefore not be able to attend.</p>
<p>Personal information will only be disclosed to Software Freedom Conservancy and Government agencies where organizers believe disclosure is appropriate for legal compliance and law enforcement; to facilitate court proceedings; to enforce our terms and conditions; or to protect the rights, property, or safety of the event, our attendees, or others. Software Freedom Conservancy will not sell your personal information to third parties and will not use your personal information to send promotional material from any of our affiliated partners and/or sponsors.</p>
<p>From time to time event organizers update their information and website practices. Please regularly review this page for the most recent information about the event privacy practices.</p>
<p>All personal information will be kept private and used only for event registration purposes, statistics for future events, and convenience for future event registration.</p>
<h2>Discrimination and Anti-Social Behavior</h2>
<p>FOSSY is proud to support people from all walks of life, especially underrepresented groups like women and people of color, and will not tolerate in any fashion any intimidation, harassment, and/or any abusive, discriminatory or derogatory behavior by any attendees of the event and/or related events.</p>
<p>Examples of these behaviors and measures the event organizers may take are set out in the <a href="../code-of-conduct.html">Code of Conduct</a>. By registering for and attending FOSSY, you agree to this Code of Conduct.</p>
<h2>Talk Recordings</h2>
<p>Event organizers may provide recordings of talks (audio and/or video) given at the event. This service is provided on a best-effort basis only. Any recordings will be released as and when they are ready, which may be some time after the conclusion of the event, and the recordings may be of varying quality.</p>
<h2>Photography and Audio Video Recording</h2>
<p>This applies to all attendees of FOSSY and related events, including staff who are designated as official photographers and audio and video recorders.</p>
<p>Do not photograph, video or audio record anyone without their express permission.</p>
<p>Attendees will have a way to visibly signal their preference for photography at the conference. You agree to consider and act according to these preferences:</p>
<ul>
<li>Opt-in: Photography always okay</li>
<li>Permission required: Ask before photographing</li>
<li>Opt-out: Photographs are never okay, don't ask</li>
</ul>
<p>Attendees who are not visibly signaling their preference should be asked for permission before photographing. There is no prior opt-in for audio or video recordings. You must always ask before recording.</p>
<p>The event may have one or more staff taking photographs and/or audio or video recordings during the event. These staff will respect attendees' preferences regarding photography and recordings.</p>
<p>The only exception is for recordings of talks given at the event where attendees who ask questions of the presenter may be included in the talk recording.</p>
<p>If Software Freedom Conservancy chooses to publish photographs and recordings taken by event staff, we will publish them under a Creative Commons license. Conservancy further reserves the right to use those photographs and recordings in promotional materials to promote its activities and/or the use of free and open source software.</p>
<p>If there is a violation of this policy, event organizers will request that the photograph be removed from any sites where it was posted and deleted from the devices. In the event that this request is ignored or further violations occur, the participants violating this policy may be sanctioned or expelled from the conference without a refund or banned from future Conservancy events.</p>
<h2>Media</h2>
<p>There are a limited number of Media Passes available to media personnel. Media Passes are free of charge, and entitle media personnel to attend the event with all the entitlements of a Discount registration. Please note, due to the limited numbers of Media Passes available, all Media Passes will need to be approved by the event organizers.</p>
<p>Any media attending the event are required to identify themselves as "media" to attendees prior to speaking on the record with any attendees of the event. It is the responsibility of the media to introduce themselves to the persons they wish to interview and to arrange any interviews with those persons. The event organizers will not make introductions or arrange interviews on behalf of media.</p>
<h2>Smoke-free</h2>
<p>All event venues including the social event venues are smoke-free. If attendees wish to smoke during the event and/or related events, they must do so in signed areas. Please consider others and refrain from smoking directly outside the venues' entrances.</p>
<h2>Health and Safety</h2>
<h1 class="page-title">Terms and Conditions</h1>
<p><em>This document was forked from the <a href="https://github.com/northbaypython/website/blob/master/pinaxcon/templates/static_pages/terms_and_conditions.md">North Bay Python Terms and Conditions</a>.</em></p>
<p>These Terms and Conditions apply to all attendees who have registered for FOSSY 2023.</p>
<h2>Registration</h2>
<p>Registering for the event does not guarantee your ticket until it has been paid for in full. To secure your ticket, pay the registration invoice as soon as possible.</p>
<h2>Cancellation Policy</h2>
<p><strong>Cancellations made prior to July 6th, 2023</strong>: Incur a cancellation fee of 50% of the ticket cost, which will be deducted from any registration fee paid. The balance will be refunded.</p>
<p><strong>Cancellations made after July 7th, 2023</strong>: No refund.</p>
<h2>Substitutions</h2>
<p>You may substitute another person, however you must contact us with this person's details.</p>
<h2>Privacy Notice</h2>
<p>In the course of registering for the event and related events, personal information will be collected about attendees such as their name, contact details, etc. This information is required to facilitate registration to the event, for catering requirements, and for organizers or their agents to contact particular attendees as and when required in respect of the event. Attendees who do not disclose this personal information will be unable to complete registration at the event and will therefore not be able to attend.</p>
<p>Personal information will only be disclosed to Software Freedom Conservancy and Government agencies where organizers believe disclosure is appropriate for legal compliance and law enforcement; to facilitate court proceedings; to enforce our terms and conditions; or to protect the rights, property, or safety of the event, our attendees, or others. Software Freedom Conservancy will not sell your personal information to third parties and will not use your personal information to send promotional material from any of our affiliated partners and/or sponsors.</p>
<p>From time to time event organizers update their information and website practices. Please regularly review this page for the most recent information about the event privacy practices.</p>
<p>All personal information will be kept private and used only for event registration purposes, statistics for future events, and convenience for future event registration.</p>
<h2>Discrimination and Anti-Social Behavior</h2>
<p>FOSSY is proud to support people from all walks of life, especially underrepresented groups like women and people of color, and will not tolerate in any fashion any intimidation, harassment, and/or any abusive, discriminatory or derogatory behavior by any attendees of the event and/or related events.</p>
<p>Examples of these behaviors and measures the event organizers may take are set out in the <a href="../code-of-conduct.html">Code of Conduct</a>. By registering for and attending FOSSY, you agree to this Code of Conduct.</p>
<h2>Talk Recordings</h2>
<p>Event organizers may provide recordings of talks (audio and/or video) given at the event. This service is provided on a best-effort basis only. Any recordings will be released as and when they are ready, which may be some time after the conclusion of the event, and the recordings may be of varying quality.</p>
<h2>Photography and Audio Video Recording</h2>
<p>This applies to all attendees of FOSSY and related events, including staff who are designated as official photographers and audio and video recorders.</p>
<p>Do not photograph, video or audio record anyone without their express permission.</p>
<p>Attendees will have a way to visibly signal their preference for photography at the conference. You agree to consider and act according to these preferences:</p>
<ul>
<li>Opt-in: Photography always okay</li>
<li>Permission required: Ask before photographing</li>
<li>Opt-out: Photographs are never okay, don't ask</li>
</ul>
<p>Attendees who are not visibly signaling their preference should be asked for permission before photographing. There is no prior opt-in for audio or video recordings. You must always ask before recording.</p>
<p>The event may have one or more staff taking photographs and/or audio or video recordings during the event. These staff will respect attendees' preferences regarding photography and recordings.</p>
<p>The only exception is for recordings of talks given at the event where attendees who ask questions of the presenter may be included in the talk recording.</p>
<p>If Software Freedom Conservancy chooses to publish photographs and recordings taken by event staff, we will publish them under a Creative Commons license. Conservancy further reserves the right to use those photographs and recordings in promotional materials to promote its activities and/or the use of free and open source software.</p>
<p>If there is a violation of this policy, event organizers will request that the photograph be removed from any sites where it was posted and deleted from the devices. In the event that this request is ignored or further violations occur, the participants violating this policy may be sanctioned or expelled from the conference without a refund or banned from future Conservancy events.</p>
<h2>Media</h2>
<p>There are a limited number of Media Passes available to media personnel. Media Passes are free of charge, and entitle media personnel to attend the event with all the entitlements of a Discount registration. Please note, due to the limited numbers of Media Passes available, all Media Passes will need to be approved by the event organizers.</p>
<p>Any media attending the event are required to identify themselves as "media" to attendees prior to speaking on the record with any attendees of the event. It is the responsibility of the media to introduce themselves to the persons they wish to interview and to arrange any interviews with those persons. The event organizers will not make introductions or arrange interviews on behalf of media.</p>
<h2>Smoke-free</h2>
<p>All event venues including the social event venues are smoke-free. If attendees wish to smoke during the event and/or related events, they must do so in signed areas. Please consider others and refrain from smoking directly outside the venues' entrances.</p>
<h2>Health and Safety</h2>
<p>Presenters are responsible for ensuring that sessions they lead meet local health and safety requirements.</p>
</div>
</div>

View file

@ -165,33 +165,33 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 class="page-title">Tickets</h1>
<p>Tickets to FOSSY are tiered to be inclusive for all folks. This includes access
to all workshops and talks, lunch for each of the 4 days, and a smile and thank
you from all our conference staff and volunteers!</p>
<p>We are also looking for volunteers to help with registration, guiding
attendees from transit to the venue, and many other opportunities if you'd
like to donate your time instead of money to attend our conference.</p>
<h3>Community Member</h3>
<p><strong>$250</strong> - For all community members</p>
<h3>Professional</h3>
<p><strong>$600</strong> - Your professional status will be indicated with a special lanyard or
other badge indicator</p>
<h3>One for me, one for you</h3>
<p><strong>$1000</strong> - provides admittance for you and donation of a ticket to someone
else</p>
<h3>Reduced fare</h3>
<p><strong>$60</strong> - for anyone for whom money is tight, this price is full attendance but
helps offset the cost of lunch for 3 days</p>
<p>If you have any financial hardship from this ticket price, please reach out to
us at <a href="mailto:conference@sfconservancy.org">conference@sfconservancy.org</a>. Please reach out, even if you are not sure if your situation qualifies as we'd like to help as many people as possible.</p>
<h1 class="page-title">Tickets</h1>
<p>Tickets to FOSSY are tiered to be inclusive for all folks. This includes access
to all workshops and talks, lunch for each of the 4 days, and a smile and thank
you from all our conference staff and volunteers!</p>
<p>We are also looking for volunteers to help with registration, guiding
attendees from transit to the venue, and many other opportunities if you'd
like to donate your time instead of money to attend our conference.</p>
<h3>Community Member</h3>
<p><strong>$250</strong> - For all community members</p>
<h3>Professional</h3>
<p><strong>$600</strong> - Your professional status will be indicated with a special lanyard or
other badge indicator</p>
<h3>One for me, one for you</h3>
<p><strong>$1000</strong> - provides admittance for you and donation of a ticket to someone
else</p>
<h3>Reduced fare</h3>
<p><strong>$60</strong> - for anyone for whom money is tight, this price is full attendance but
helps offset the cost of lunch for 3 days</p>
<p>If you have any financial hardship from this ticket price, please reach out to
us at <a href="mailto:conference@sfconservancy.org">conference@sfconservancy.org</a>. Please reach out, even if you are not sure if your situation qualifies as we'd like to help as many people as possible.</p>
</div>
</div>

View file

@ -165,22 +165,22 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<p>Running FOSSY will take a lot of help from people like you! Volunteers receive free admission and lunch for all 4 days of the conference.</p>
<p>If you are interested in volunteering in some capacity, please make an account on this site and fill out <a href="https://nextcloud.sfconservancy.org/apps/forms/s/GF8gkmQfSFdyHoaNPiTWeCCx">our form</a>.</p>
<p>Here are some areas we need volunteers:</p>
<ul>
<li>Set up</li>
<li>Take down and Cleanup</li>
<li>Room host (assisting speakers in setup, etc)</li>
<li>Registration/welcome table</li>
<li>Attendee assistant (greeting, general help, way finding)</li>
<li>Transit guide (take people to and frome transit destination)</li>
<li>AV (please give level of experience)</li>
<li>Photographer (please give level of experience)</li>
<li>Code of Conduct Team (training required)</li>
<li>Team Leader (run a group of above mentioned volunteers - please list any experience with this)</li>
<li>Any other ideas you might have or want to do!</li>
<p>Running FOSSY will take a lot of help from people like you! Volunteers receive free admission and lunch for all 4 days of the conference.</p>
<p>If you are interested in volunteering in some capacity, please make an account on this site and fill out <a href="https://nextcloud.sfconservancy.org/apps/forms/s/GF8gkmQfSFdyHoaNPiTWeCCx">our form</a>.</p>
<p>Here are some areas we need volunteers:</p>
<ul>
<li>Set up</li>
<li>Take down and Cleanup</li>
<li>Room host (assisting speakers in setup, etc)</li>
<li>Registration/welcome table</li>
<li>Attendee assistant (greeting, general help, way finding)</li>
<li>Transit guide (take people to and frome transit destination)</li>
<li>AV (please give level of experience)</li>
<li>Photographer (please give level of experience)</li>
<li>Code of Conduct Team (training required)</li>
<li>Team Leader (run a group of above mentioned volunteers - please list any experience with this)</li>
<li>Any other ideas you might have or want to do!</li>
</ul>
</div>
</div>

View file

@ -165,37 +165,37 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 class="page-title">Call for Proposals</h1>
<p><strong>Our call for proposals have closed!</strong></p>
<p>We had over 15 tracks proposed by our incredible community, and more than 200 talks! We hope you keep us in mind next year for your talk and we'll see you in a few weeks!</p>
<p>This year's <a href="../pages/tracks.html">tracks</a> are:</p>
<ul>
<li><a href="../pages/tracks.html#arm">AArch64/ARM64 Servers and Open Source- The Who, What, Why, and How</a></li>
<li><a href="../pages/tracks.html#bsd">BSD Unix</a></li>
<li><a href="../pages/tracks.html#community">Community: Open Source in Practice</a></li>
<li><a href="../pages/tracks.html#container">Container Days</a></li>
<li><a href="../pages/tracks.html#copyleft">Copyleft and Compliance</a></li>
<li><a href="../pages/tracks.html#dei">Diversity Equity and Inclusion and FOSS</a></li>
<li><a href="../pages/tracks.html#daily-life">FOSS in Daily Life</a></li>
<li><a href="../pages/tracks.html#play">FOSS at Play: Games, creative development, and open technology</a></li>
<li><a href="../pages/tracks.html#education">FOSS For Education</a></li>
<li><a href="../pages/tracks.html#openwork">Issues in Open Work; Common Challenges and Best Practices in the Open Source Industry, Open Scholarship, and Government</a></li>
<li><a href="../pages/tracks.html#ai-data">Open Source AI + Data</a></li>
<li><a href="../pages/tracks.html#repair">Right to Repair</a></li>
<li><a href="../pages/tracks.html#science">Science of Community</a></li>
<li><a href="../pages/tracks.html#sfc-member-projects">SFC Member Projects</a></li>
<li><a href="../pages/tracks.html#security">Security</a></li>
<li><a href="../pages/tracks.html#business">Sustainable Open Source Business</a></li>
<li><a href="../pages/tracks.html#xmpp">XMPP</a></li>
<li><a href="../pages/tracks.html#wildcard">Wild card</a></li>
<li><a href="../pages/tracks.html#coops">Worker-Owner Co-ops that write and use FOSS</a></li>
</ul>
<h1 class="page-title">Call for Proposals</h1>
<p><strong>Our call for proposals have closed!</strong></p>
<p>We had over 15 tracks proposed by our incredible community, and more than 200 talks! We hope you keep us in mind next year for your talk and we'll see you in a few weeks!</p>
<p>This year's <a href="../pages/tracks.html">tracks</a> are:</p>
<ul>
<li><a href="../pages/tracks.html#arm">AArch64/ARM64 Servers and Open Source- The Who, What, Why, and How</a></li>
<li><a href="../pages/tracks.html#bsd">BSD Unix</a></li>
<li><a href="../pages/tracks.html#community">Community: Open Source in Practice</a></li>
<li><a href="../pages/tracks.html#container">Container Days</a></li>
<li><a href="../pages/tracks.html#copyleft">Copyleft and Compliance</a></li>
<li><a href="../pages/tracks.html#dei">Diversity Equity and Inclusion and FOSS</a></li>
<li><a href="../pages/tracks.html#daily-life">FOSS in Daily Life</a></li>
<li><a href="../pages/tracks.html#play">FOSS at Play: Games, creative development, and open technology</a></li>
<li><a href="../pages/tracks.html#education">FOSS For Education</a></li>
<li><a href="../pages/tracks.html#openwork">Issues in Open Work; Common Challenges and Best Practices in the Open Source Industry, Open Scholarship, and Government</a></li>
<li><a href="../pages/tracks.html#ai-data">Open Source AI + Data</a></li>
<li><a href="../pages/tracks.html#repair">Right to Repair</a></li>
<li><a href="../pages/tracks.html#science">Science of Community</a></li>
<li><a href="../pages/tracks.html#sfc-member-projects">SFC Member Projects</a></li>
<li><a href="../pages/tracks.html#security">Security</a></li>
<li><a href="../pages/tracks.html#business">Sustainable Open Source Business</a></li>
<li><a href="../pages/tracks.html#xmpp">XMPP</a></li>
<li><a href="../pages/tracks.html#wildcard">Wild card</a></li>
<li><a href="../pages/tracks.html#coops">Worker-Owner Co-ops that write and use FOSS</a></li>
</ul>
<p class="mv4"><a href="../speaker/create/index.html"><button type="button" class="btn btn-primary btn-lg">Create a speaker profile</button></a></p>
</div>
</div>

View file

@ -165,30 +165,30 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 class="page-title">Maps of the Oregon Convention Center</h1>
<div>
<figure class="fr pa0 mt4 mt2-ns mr0 ml0 ml4-ns mb4">
<img src="https://sfconservancy.org/img/fossy-map.png" alt="Map of the Oregon Convention Center, labeling transit locations and entrance on the south east side of the building ">
<figcaption class="tc mt2">Map of Oregon Convention Center, Hyatt and Spirit of 77 (CC-BY 2.0)</figcaption>
</figure>
</div>
<div>
<figure class="fr pa0 mt4 mt2-ns mr0 ml0 ml4-ns mb4">
<img src="https://www.oregoncc.org/sites/default/files/styles/slideshow_tabbed/public/OCC-Level-1-Web-Maps-AED.jpg" alt="Map of the inside of the first level of Oregon Convention Center">
<figcaption class="tc mt2">Our area is the block of E rooms and the Pre-Function E Space</figcaption>
</figure>
</div>
<div>
<figure class="fr pa0 mt4 mt2-ns mr0 ml0 ml4-ns mb4">
<img src="https://www.oregoncc.org/sites/default/files/styles/slideshow_tabbed/public/OCC-Level-2-Administrative.jpg" alt="Map of the inside of the second level of Oregon Convention Center">
<figcaption class="tc mt2">Our area is the Ballroom 256/257. Registration will be outside the Portland Ballroom and the keynotes will be taking place inside.</figcaption>
</figure>
<h1 class="page-title">Maps of the Oregon Convention Center</h1>
<div>
<figure class="fr pa0 mt4 mt2-ns mr0 ml0 ml4-ns mb4">
<img src="https://sfconservancy.org/img/fossy-map.png" alt="Map of the Oregon Convention Center, labeling transit locations and entrance on the south east side of the building ">
<figcaption class="tc mt2">Map of Oregon Convention Center, Hyatt and Spirit of 77 (CC-BY 2.0)</figcaption>
</figure>
</div>
<div>
<figure class="fr pa0 mt4 mt2-ns mr0 ml0 ml4-ns mb4">
<img src="https://www.oregoncc.org/sites/default/files/styles/slideshow_tabbed/public/OCC-Level-1-Web-Maps-AED.jpg" alt="Map of the inside of the first level of Oregon Convention Center">
<figcaption class="tc mt2">Our area is the block of E rooms and the Pre-Function E Space</figcaption>
</figure>
</div>
<div>
<figure class="fr pa0 mt4 mt2-ns mr0 ml0 ml4-ns mb4">
<img src="https://www.oregoncc.org/sites/default/files/styles/slideshow_tabbed/public/OCC-Level-2-Administrative.jpg" alt="Map of the inside of the second level of Oregon Convention Center">
<figcaption class="tc mt2">Our area is the Ballroom 256/257. Registration will be outside the Portland Ballroom and the keynotes will be taking place inside.</figcaption>
</figure>
</div>
</div>
</div>

View file

@ -165,11 +165,11 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 class="page-title">Credits</h1>
<h2>This website</h2>
<p>This site is based on Symposion and Registrasion (sic) Django apps, originally created by James Tauber and Chris Neugebauer respectively and extended by many others. The site is based on Linux Australia's <a href="https://gitlab.com/laconfdev/symposion_app">Everything Open codebase</a>. We'd like to thank Joel Addison and Sae Ra Germaine from Linux Australia and Chris Neugebauer for their guidance. See our <a href="https://k.sfconservancy.org/symposion_app">source code</a>.</p>
<h1 class="page-title">Credits</h1>
<h2>This website</h2>
<p>This site is based on Symposion and Registrasion (sic) Django apps, originally created by James Tauber and Chris Neugebauer respectively and extended by many others. The site is based on Linux Australia's <a href="https://gitlab.com/laconfdev/symposion_app">Everything Open codebase</a>. We'd like to thank Joel Addison and Sae Ra Germaine from Linux Australia and Chris Neugebauer for their guidance. See our <a href="https://k.sfconservancy.org/symposion_app">source code</a>.</p>
<p>Software development and operational support by <a href="https://www.sturm.com.au/">Sturm Software Engineering</a>.
</div>
</div>

View file

@ -165,69 +165,69 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 class="page-title">Events</h1>
<h4>SustainOSS meetup</h4>
<b>Wednesday 6:30pm at Hey Love</b>
<p>The SustainOSS community is having a meetup on Wednesday night for early arrivers. You can <a href="https://opencollective.com/sustainoss/events/sustain-fossy-2023-meet-up-c9943596">sign up</a> or show up at Hey Love at 6:30pm. We're looking forward to holding informal conversations on sustaining open source.</p>
</br>
<h4><strong>Official Thursday Night Social</strong></h4>
<p>Thursday 7-10pm at Punch Bowl Social Portland, <a href="https://www.openstreetmap.org/node/7134560577">340 SW Morrison St Suite 4305, Portland, OR 97204</a> which is a quick ~15 minute Max ride from the convention center. All attendees are invited!</p>
<p>We are providing light snacks, and the bar will be open to purchase your choice of beverages. There will be all kind of games like bowling, ping pong, giant Scrabble, darts, shuffle board and karaoke! </p>
<p>There is limited outdoor space, and we'll request people wear masks while not eating and drinking inside. We are trying to be as health conscious as we can be.</p>
<p>Part of the cost of the venue and food was provided by RedHat, thank you!</p>
</br>
<h4><a href="https://calagator.org/events/1250480587">BSD Pizza Night</a></h4>
<p><b>Thursday, July 13, 2023 from 79pm at Sizzle Pie Central Eastside</b>, 624 E Burnside St. Portland, OR.</p>
<p>A meeting of folks interested in BSD operating systems and related technologies to get together, eat pizza, drink beer, and talk about what interesting things have been going on.</p>
</br>
<h4>Apereo Social</h4>
<strong>FOSS For Education Mixer at Spirit77 on Saturday night</strong>
<p>Join Apereo, Virtual Inc., Unicon , and Sakai+ for an evening of FOSS, friends, and fun. Organized by the FOSS for Education track, all are welcome to mix and mingle over your favorite beverages, light snacks--and maybe a bit of edtech shop-talk. Space is limited; tickets available at the Apereo booth during the conference. </p>
<h4 id="crowdsourced">Crowdsourced Respiratory-Friendly Nearby Venues</h4>
<p>(In no particular order. Add others you learn about!)</p>
<ul>
<li>Metropolitan Tavern (diagonal from the Northeast corner of OCC) has a rooftop outdoor patio. Food and drinks. https://mettavern.com/</li>
<li>Pioneer Courthouse Square has lots of places to sit & visit, and a few food carts that are open daytime hours, as well as a Starbucks, and a few street-level food places around the surrounding streets. Get there via MAX on Red, Blue, or Green lines. https://www.thesquarepdx.org/</li>
<li>Departure (diagnoal from Northeast corner of Pioneer Courthouse Square) is rooftop restaurant/bar. Accessible from OCC via MAX Red/Blue/Green lines (Pioneer Courthouse Square stops). https://www.departureportland.com/</li>
<li>Lloyd Center Mall is the next stop east on the MAX Red/Green/Blue lines, on the north side of Holladay Park. It's a nearly-dead mall with a couple food places a few shops including a Barnes & Noble bookstore, and lots of open/quiet indoor space & seating. There are also a few restaurants just outside & to the north of the mall in adjacent/nearby buildings. https://www.lloydcenter.com/</li>
<li>Portland Saturday Market is across the river on the waterfront and has quite a few food carts and outdoor places to sit and eat. (And also lots of shopping.) This used to also be open on Sunday but these days it's pretty much just Saturday lunch. Get there on the MAX Red or Blue lines (Skidmore Fountain stop). https://www.portlandsaturdaymarket.com/</li>
<li>My Father's Place is a dive bar/diner that has several small sidewalk tables. Directly south of the OCC on the Portland Streetcar (Stark stops). https://myfathersplacepdx.com/</li>
<li>Nong's Khao Man Gai, Snappy's Sandwiches, and Kinboshi Ramen share a good amount of outdoor seating along the sidewalk and in a covered space. Just south of the OCC, one-two blocks east of the Portland Streetcar stops @ Burnside. https://khaomangai.com/ https://www.makeitsnappys.com/ and https://www.kinboshiramen.com/ </li>
<li>E-San Thai has a food cart 3 streets east of the north end of the OCC in the small "Oregon Park". Open only for weekday lunches. (no web site)</li>
<li>Hotlips Pizza (by the slice) is on just the other side of the river but easily accessible by taking the Portland Streetcar north from OCC and over the bridge (NW Johnson Street stops). Lots of outdoor (incl. covered) seating and a block from Jamison Square park which has more seating and a fountain to cool off. Several other restaurants with takeaway available are located within a block or two from this park. https://www.hotlipspizza.com/</li>
<li>Voodoo Doughnuts is a famous Portland 24-hour doughnut place on the west side of the river, and (once you get through the often-long queue) has several outdoor tables outside to consume your sugar. From OCC, get there on the MAX Red or Blue lines (Skidmore Fountain stop). https://www.voodoodoughnut.com/</li>
<li>Powell's City of Books is a favorite geek stop in Portland. They don't have anything outdoors, but across Burnside Street from there you'll find lots of outdoor seating for both Shake Shack and Sizzle Pie pizza by-the-slice. It's on basically the other (west) side of the Portland Streetcar A/B loops, using at the Couch Street stops. https://www.powells.com/ </li>
<li>Lardo is a popular sandwich joint with outdoor covered seating, Not so great for vegies or gluten-free options, but near a number of other cafes and restaurants, including the Asylum food carts. 1212 SE Hawthorne Blvd,, Portland, OR (503) 234-7786Daily 11AM - 10PM https://www.lardosandwiches.com </li>
<li>Hawthorne Asylum has very nice selection of food carts, atmosphere, and a selection of seating areas. 1080 SE Madison St Portland, OR 97214. https://www.openstreetmap.org/way/722369995#map=19/45.51272/-122.65521 </li>
<li>food carts : Our food-carts are surprizingly good, and if you go to a pod of them, you get more selection and seating. OpenStreetMaps.org has a longish list of food-cart courtyards or pods. https://www.openstreetmap.org/search?query=food%20carts%20portland%20oregon#map=16/45.5354/-122.6644 </li>
<li>Mirisata. Sri Lankan vegan restaurant, worker co-op; outdoor seating. 2420 SE Belmont St. https://mirisata.com/ https://www.openstreetmap.org/way/368235009</li>
<h1 class="page-title">Events</h1>
<h4>SustainOSS meetup</h4>
<b>Wednesday 6:30pm at Hey Love</b>
<p>The SustainOSS community is having a meetup on Wednesday night for early arrivers. You can <a href="https://opencollective.com/sustainoss/events/sustain-fossy-2023-meet-up-c9943596">sign up</a> or show up at Hey Love at 6:30pm. We're looking forward to holding informal conversations on sustaining open source.</p>
</br>
<h4><strong>Official Thursday Night Social</strong></h4>
<p>Thursday 7-10pm at Punch Bowl Social Portland, <a href="https://www.openstreetmap.org/node/7134560577">340 SW Morrison St Suite 4305, Portland, OR 97204</a> which is a quick ~15 minute Max ride from the convention center. All attendees are invited!</p>
<p>We are providing light snacks, and the bar will be open to purchase your choice of beverages. There will be all kind of games like bowling, ping pong, giant Scrabble, darts, shuffle board and karaoke! </p>
<p>There is limited outdoor space, and we'll request people wear masks while not eating and drinking inside. We are trying to be as health conscious as we can be.</p>
<p>Part of the cost of the venue and food was provided by RedHat, thank you!</p>
</br>
<h4><a href="https://calagator.org/events/1250480587">BSD Pizza Night</a></h4>
<p><b>Thursday, July 13, 2023 from 79pm at Sizzle Pie Central Eastside</b>, 624 E Burnside St. Portland, OR.</p>
<p>A meeting of folks interested in BSD operating systems and related technologies to get together, eat pizza, drink beer, and talk about what interesting things have been going on.</p>
</br>
<h4>Apereo Social</h4>
<strong>FOSS For Education Mixer at Spirit77 on Saturday night</strong>
<p>Join Apereo, Virtual Inc., Unicon , and Sakai+ for an evening of FOSS, friends, and fun. Organized by the FOSS for Education track, all are welcome to mix and mingle over your favorite beverages, light snacks--and maybe a bit of edtech shop-talk. Space is limited; tickets available at the Apereo booth during the conference. </p>
<h4 id="crowdsourced">Crowdsourced Respiratory-Friendly Nearby Venues</h4>
<p>(In no particular order. Add others you learn about!)</p>
<ul>
<li>Metropolitan Tavern (diagonal from the Northeast corner of OCC) has a rooftop outdoor patio. Food and drinks. https://mettavern.com/</li>
<li>Pioneer Courthouse Square has lots of places to sit & visit, and a few food carts that are open daytime hours, as well as a Starbucks, and a few street-level food places around the surrounding streets. Get there via MAX on Red, Blue, or Green lines. https://www.thesquarepdx.org/</li>
<li>Departure (diagnoal from Northeast corner of Pioneer Courthouse Square) is rooftop restaurant/bar. Accessible from OCC via MAX Red/Blue/Green lines (Pioneer Courthouse Square stops). https://www.departureportland.com/</li>
<li>Lloyd Center Mall is the next stop east on the MAX Red/Green/Blue lines, on the north side of Holladay Park. It's a nearly-dead mall with a couple food places a few shops including a Barnes & Noble bookstore, and lots of open/quiet indoor space & seating. There are also a few restaurants just outside & to the north of the mall in adjacent/nearby buildings. https://www.lloydcenter.com/</li>
<li>Portland Saturday Market is across the river on the waterfront and has quite a few food carts and outdoor places to sit and eat. (And also lots of shopping.) This used to also be open on Sunday but these days it's pretty much just Saturday lunch. Get there on the MAX Red or Blue lines (Skidmore Fountain stop). https://www.portlandsaturdaymarket.com/</li>
<li>My Father's Place is a dive bar/diner that has several small sidewalk tables. Directly south of the OCC on the Portland Streetcar (Stark stops). https://myfathersplacepdx.com/</li>
<li>Nong's Khao Man Gai, Snappy's Sandwiches, and Kinboshi Ramen share a good amount of outdoor seating along the sidewalk and in a covered space. Just south of the OCC, one-two blocks east of the Portland Streetcar stops @ Burnside. https://khaomangai.com/ https://www.makeitsnappys.com/ and https://www.kinboshiramen.com/ </li>
<li>E-San Thai has a food cart 3 streets east of the north end of the OCC in the small "Oregon Park". Open only for weekday lunches. (no web site)</li>
<li>Hotlips Pizza (by the slice) is on just the other side of the river but easily accessible by taking the Portland Streetcar north from OCC and over the bridge (NW Johnson Street stops). Lots of outdoor (incl. covered) seating and a block from Jamison Square park which has more seating and a fountain to cool off. Several other restaurants with takeaway available are located within a block or two from this park. https://www.hotlipspizza.com/</li>
<li>Voodoo Doughnuts is a famous Portland 24-hour doughnut place on the west side of the river, and (once you get through the often-long queue) has several outdoor tables outside to consume your sugar. From OCC, get there on the MAX Red or Blue lines (Skidmore Fountain stop). https://www.voodoodoughnut.com/</li>
<li>Powell's City of Books is a favorite geek stop in Portland. They don't have anything outdoors, but across Burnside Street from there you'll find lots of outdoor seating for both Shake Shack and Sizzle Pie pizza by-the-slice. It's on basically the other (west) side of the Portland Streetcar A/B loops, using at the Couch Street stops. https://www.powells.com/ </li>
<li>Lardo is a popular sandwich joint with outdoor covered seating, Not so great for vegies or gluten-free options, but near a number of other cafes and restaurants, including the Asylum food carts. 1212 SE Hawthorne Blvd,, Portland, OR (503) 234-7786Daily 11AM - 10PM https://www.lardosandwiches.com </li>
<li>Hawthorne Asylum has very nice selection of food carts, atmosphere, and a selection of seating areas. 1080 SE Madison St Portland, OR 97214. https://www.openstreetmap.org/way/722369995#map=19/45.51272/-122.65521 </li>
<li>food carts : Our food-carts are surprizingly good, and if you go to a pod of them, you get more selection and seating. OpenStreetMaps.org has a longish list of food-cart courtyards or pods. https://www.openstreetmap.org/search?query=food%20carts%20portland%20oregon#map=16/45.5354/-122.6644 </li>
<li>Mirisata. Sri Lankan vegan restaurant, worker co-op; outdoor seating. 2420 SE Belmont St. https://mirisata.com/ https://www.openstreetmap.org/way/368235009</li>
</ul>
</div>
</div>

View file

@ -165,63 +165,63 @@
<div class="row">
<div class="col-12 content text-page">
<header class="pt2-ns pb4">
<div class="flex-ns center">
<div class="mr4 dark-green sans-serif" style="flex-grow: 1">
<h1 class="f-subheadline f-headline-ns b lh-solid tracked-tight mv0">FOSSY 2023</h1>
<h2 class="f3 f2-ns b lh-solid mt0 mb3">July 13-16th 2023 — Portland, OR</h2>
<h3 class="f4 f4-ns b lh-title mv2 mv3-ns">The first Free and Open Source Software Yearly conference</h3>
</div>
<div class="lh-solid mt4 mt0-ns" style="font-size: 10rem; max-width: 250px;"><img class="db" src="static/build/img/conservancy_logo_tall_mono.svg" style="max-height: 180px" alt="Software Freedom Conservancy"></div>
</div>
<header class="pt2-ns pb4">
<div class="flex-ns center">
<div class="mr4 dark-green sans-serif" style="flex-grow: 1">
<h1 class="f-subheadline f-headline-ns b lh-solid tracked-tight mv0">FOSSY 2023</h1>
<h2 class="f3 f2-ns b lh-solid mt0 mb3">July 13-16th 2023 — Portland, OR</h2>
<h3 class="f4 f4-ns b lh-title mv2 mv3-ns">The first Free and Open Source Software Yearly conference</h3>
</div>
<div class="lh-solid mt4 mt0-ns" style="font-size: 10rem; max-width: 250px;"><img class="db" src="static/build/img/conservancy_logo_tall_mono.svg" style="max-height: 180px" alt="Software Freedom Conservancy"></div>
</div>
<div class="mt4 mt0-ns">
<a href="schedule/index.html" class="mr2"><button type="button" class="btn btn-primary mb2">Explore the schedule</button></a>
</div>
</header>
<section id="content">
<h1 class="f3 mt0 mb4">FOSS is back in Portland, OR at the Oregon Convention Center!!</h1>
<div class="flex-ns">
<div class="mw6">
<p class="f4 mt0">Software Freedom Conservancy is so proud to announce that we are hosting a
community oriented conference this coming summer. FOSSY (Free and Open Source
Yearly) is focused on the creation and impact of free and open source software,
uplifting contributors of all experience.</p>
<p> We are also mindful of having a safe
environment for all. In this new time of conferences, we will be focused on
COVID safety and making sure all attendees feel safe participating as much as
they feel comfortable (please take a look at the <a href="attend/health-and-safety/index.html">policy</a> ).</p>
<p>Taking place in Portland, OR, we hope FOSSY will be a community focused
event that invites local community, as well as the wider internet and global
communites we have formed over the years. Whether you are a long time
contributing member of a free software project, a recent graduate of a
coding bootcamp or university, or just have an interest in the possibilies
that free and open source software bring, FOSSY will have something for
you.</p>
<p>For this first year we are running a conference of this scale, we are having
around 12 tracks with talks over 4 days. With tracks for community building,
development and legal and licensing issues, our conference will provide ample
learning and networking opportunities for contributors of all levels of
experience. There will be hands on workshops, lightning talks and
traditional 50 minute talks.</p>
<p>As we look to the future of conferences, we are excited to focus on using
free software to run a conference and will seek to help reduce the amount of
proprietary software that is treated as default.</p>
<p>If you are interested in sponsoring our conference, please see our <a href="https://sfconservancy.org/docs/Fossy-Prospectus.pdf">Sponsorship Prospectus</a> or contact us at <a href="mailto:conference@sfconservancy.org">conference@sfconservancy.org</a>.</p>
</div>
<div>
<figure class="fr pa0 mt4 mt2-ns mr0 ml0 ml4-ns mb4">
<img src="https://sfconservancy.org/img/fossy-map.png" alt="Map of the Oregon Convention Center, labeling transit locations and entrance on the south east side of the building ">
<figcaption class="tc mt2">Map of Oregon Convention Center, Hyatt and Spirit of 77 (CC-BY 2.0)</figcaption>
</figure>
</div>
</div>
<a href="schedule/index.html" class="mr2"><button type="button" class="btn btn-primary mb2">Explore the schedule</button></a>
</div>
</header>
<section id="content">
<h1 class="f3 mt0 mb4">FOSS is back in Portland, OR at the Oregon Convention Center!!</h1>
<div class="flex-ns">
<div class="mw6">
<p class="f4 mt0">Software Freedom Conservancy is so proud to announce that we are hosting a
community oriented conference this coming summer. FOSSY (Free and Open Source
Yearly) is focused on the creation and impact of free and open source software,
uplifting contributors of all experience.</p>
<p> We are also mindful of having a safe
environment for all. In this new time of conferences, we will be focused on
COVID safety and making sure all attendees feel safe participating as much as
they feel comfortable (please take a look at the <a href="attend/health-and-safety/index.html">policy</a> ).</p>
<p>Taking place in Portland, OR, we hope FOSSY will be a community focused
event that invites local community, as well as the wider internet and global
communites we have formed over the years. Whether you are a long time
contributing member of a free software project, a recent graduate of a
coding bootcamp or university, or just have an interest in the possibilies
that free and open source software bring, FOSSY will have something for
you.</p>
<p>For this first year we are running a conference of this scale, we are having
around 12 tracks with talks over 4 days. With tracks for community building,
development and legal and licensing issues, our conference will provide ample
learning and networking opportunities for contributors of all levels of
experience. There will be hands on workshops, lightning talks and
traditional 50 minute talks.</p>
<p>As we look to the future of conferences, we are excited to focus on using
free software to run a conference and will seek to help reduce the amount of
proprietary software that is treated as default.</p>
<p>If you are interested in sponsoring our conference, please see our <a href="https://sfconservancy.org/docs/Fossy-Prospectus.pdf">Sponsorship Prospectus</a> or contact us at <a href="mailto:conference@sfconservancy.org">conference@sfconservancy.org</a>.</p>
</div>
<div>
<figure class="fr pa0 mt4 mt2-ns mr0 ml0 ml4-ns mb4">
<img src="https://sfconservancy.org/img/fossy-map.png" alt="Map of the Oregon Convention Center, labeling transit locations and entrance on the south east side of the building ">
<figcaption class="tc mt2">Map of Oregon Convention Center, Hyatt and Spirit of 77 (CC-BY 2.0)</figcaption>
</figure>
</div>
</div>
</section>
</div>
</div>

View file

@ -165,269 +165,269 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 class="page-title">Tracks</h1>
<h4 id="arm">AArch64/ARM64 Servers and Open Source- The Who, What, Why, and How</h4>
Organizers:
<ul>
<li>Aaron Williams</li>
<li>Dave Neary</li>
</ul>
<p>ARM64/AArch64 devices are some of the most widely used processors in the world, from small SoC boards like the Raspberry Pi to mobile phones and even Apple's latest M1 and M2 chips powering MacBooks. Their high performance and power efficiency means more performance per watt of energy used, making them ideal for mobile and laptops where performance, battery life, and heat dissipation are important.</p>
<p>These same performance advantages are becoming increasingly important in data centers as well. The aging x86 server technology uses more energy and requires more complicated cooling solutions, limiting the number of servers that can be placed in a rack. Plus, their single threaded cores, mean no noisy neighbor problems, and better high performance and predictable throughput. As a result, all major public clouds, including Azure, GCP, Oracle Cloud, AWS, Bytedance, Alibaba, and Tencent, have started adopting AArch64 servers in their data centers. In fact, the number of AArch64 servers in data centers has grown from 1% in 2019 to 6% today, and it's estimated that they will make up 50% of all servers by 2026. This is why it's crucial for open-source projects to understand these trends to take advantage of them going forward.</p>
<p>In this track, we will introduce DevOps engineers, developers, and architects to the latest trends and technologies in the AArch64 server world. Our sessions will cover:</p>
<ul>
<li>What are AArch64 servers, and how do they perform against x86?</li>
<li>What makes them different from x86?</li>
<li>Who is using them, and what projects are using them?</li>
<li>Why use AArch64 servers, and what are the advantages?</li>
<li>How to get started using AArch64 servers </li>
<li>A comparison of performance between AArch64 and x86 servers, covering topics such as compiling natively versus emulation with QEMU.</li>
</ul>
<p>We believe that this track will provide valuable insights for anyone interested in leveraging AArch64 servers in their work, from small-scale open-source projects to large data centers.</p>
<h4 id="bsd">BSD Unix</h4>
Organizers:
<ul>
<li>Michael Dexter</li>
<li>Andrew Fresh</li>
<li>Alexander Vasarab</li>
</ul>
<p>The BSD Unix track would showcase the BSD family of Unix operating systems, each of which is backed by a public-benefit nonprofit, rather than a for-profit company. We have the BSDs to thank for OpenSSH, mandoc, the Berkeley Packet Filter BPF, the PF packet filter, the IPFW firewall, the bhyve hypervisor, plus countless smaller utilities used throughout the free software ecosystem. The track would statistically focus on FreeBSD and OpenBSD, but would welcome other BSD operating systems such as NetBSD and distant cousin illumos.</p>
<h4 id="community">Community: Open Source in Practice</h4>
Organizers:
<ul>
<li>Josh Simmons</li>
<li>Monica Ayhens-Madon</li>
<li>julia ferraioli</li>
<li>Stephan Micahel Kellat</li>
</ul>
<p>Communities of people are the beating heart of free and open source software, and this track provides a home for sessions covering the many practices involved in building and supporting healthy, productive communities.</p>
<p>In this track, we welcome sessions on topics ranging from community management, communications infrastructure, project governance, sustainability, education, mentorship, and succession planning, contributor experience, event organizing, marketing, research, movement and coalition building, and tackling the interface between communities and corporations with integrity. No matter the topic, we encourage sessions that discuss the how of community as much as the why. Diversity, equity, inclusion, and belonging is a lens we aim to see represented across the board, as a standard of community building.</p>
<p>Any one of these topics could be a track unto itself, but often lack the critical mass to stand alone at conferences and land in the squishy bucket we call “community.” The organizers of this track view this as an antipattern, while also recognizing its a familiar dynamic. We hope, in collaboration with our speakers, to elevate these topics and engender a culture in which these topics are elevated and celebrated.</p>
<p>We welcome proposals from speakers and people who are excited to give their first talk. We want seasoned professionals and volunteers, as well as fresh perspectives from new entrants. Everyone has something of value to share! We are prepared to help with proposals and presentations to make sure everyone is putting their best foot forward.</p>
<p>Beyond the core audience of community professionals and leaders, both paid and volunteer, we treasure cross-pollination and encourage participation from people in other disciplines.</p>
<h4 id="container">Container Days</h4>
Organizers:
<ul>
<li>Josh Berkus</li>
<li>Chris Hoge</li>
<li>Melissa Logan</li>
</ul>
<p>ContainerDaysPDX has returned! Join us for two days of exploration of the latest generation of web and application infrastructure. We'll cover both the basics, and the newer and more esoteric aspects of orchestrated container stacks, including:</p>
<ul>
<li>Moving to containers and Kubernetes without losing your sanity</li>
<li>Desktop development for containerized applications</li>
<li>Developments in Linux: cGroupsv2, seccomp, and more</li>
<li>Containers on alternate platforms (FreeBSD, windows)</li>
<li>Container alternatives like WASM and microVMs</li>
<li>ML and data analysis in container clouds</li>
<li>Alternatives to Kubernetes</li>
<li>Security, networking, and performance for new stacks</li>
<li>Kubernetes + Openstack + OpenInfra: all the layers </li>
</ul>
<p>... and more! ContainerDays will bring exciting technical topics to Portland and FOSSYcon. It will cover not just what's available now, but what free software developers are working on for the future.</p>
<p>Whether you're just getting started with the new container stacks, or have been using Docker since 2014, whether you're an application developer, ops staff, or an infrastructure hacker, we plan to have something for you. </p>
<h4 id="copyleft">Copyleft and Compliance</h4>
<p>Participants from throughout the copyleft world — developers, strategists, enforcement organizations, scholars and critics — will be welcomed for an in-depth, high bandwidth, and expert-level discussion about the day-to-day details of using copyleft licensing, obstacles facing copyleft and the future of copyleft as a strategy to advance and defend software freedom for users and developers around the world.</p>
<h4 id="dei">Diversity Equity and Inclusion and FOSS</h4>
Organizers:
<ul>
<li>Aarti Ramkrishna</li>
<li>Anita Ihuman</li>
<li>Georg Link</li>
<li>Sri Ramkrishna</li>
</ul>
<p>Diversity, Equity, and inclusion are receiving increased attention in the FOSS community, the broader technology industry, and beyond. Since free and open software, hardware, and standards are made by people with very different backgrounds, beliefs, disabilities, nationalities, and identities, it is important to ensure access for these different groups and enable them to participate in a healthy way. This conference track provides a space to discuss diversity, equity, and inclusion challenges and solutions. We invite submissions from practitioners who share their own stories and what strategies they have tried to improve DEI, regardless of whether they succeeded or failed. We invite submission focused on DEI in FOSS, DEI beyond FOSS, and personal DEI experiences.</p>
<p>We look forward to providing a safe and welcoming space for highlighting DEI efforts and experiences from various perspectives, initiatives, and programs. We invite submissions from people who face systemic bias or discrimination in the technology industry of their country. We expressly invite submissions from women (both cis and trans), trans men, non-binary people, and gender queer people to apply. We further invite submissions from allies. </p>
<h4 id="daily-life">FOSS in Daily Life</h4>
Organizers:
<ul>
<li>SFC Staff</li>
</ul>
<p>How are you using FOSS in your "everyday" life? Are there places where you
find it's easier or harder to get the people around you to respect and
appreciate software freedom? What areas of software are we missing in our
pursuit of software freedom for all?</p>
<h4 id="play">FOSS at Play: Games, creative development, and open technology</h4>
Organizers:
<ul>
<li>Paris Buttfield-Addison</li>
<li>Stephen Jacobs</li>
</ul>
<p>The relationship between FOSS and Game Development is a multidisciplinary maze of creative, software, community, legal, and design issues that can very easily make your head spin. This track will help demystify the world of FOSS and Game Development, blending topics around the following pillars:</p>
<ul>
<li>FOSS game engines and tools</li>
<li>Legal or business implications of game development using FOSS</li>
<li>The history of FOSS in games and game development</li>
<li>Best practices in releasing your game as FOSS</li>
<li>FOSS support tools and communities for other games</li>
<li>Improving proprietary game engines with FOSS tooling</li>
<li>Open game hardware and peripherals</li>
<li>Community management and the differences between traditional FOSS communities and games communities</li>
<li>Finding, using, and releasing game assets (art, music, etc.) under free and open licenses</li>
<li>FOSS and board games</li>
</ul>
<p>Our audience is FOSS enthusiasts, software developers, designers, and creatives who are intrigued or interested in games, but are cautious to dive too deep, due to the overwhelmingly proprietary appearance of the industry. Games are nowhere near as proprietary as you may think, and this track will help usher in new users, contributors, and creators to the fantastic collection of FOSS tools, and encourage them to release new games, tools, and creative works.</p>
<h4 id="education">FOSS For Education</h4>
Organizers:
<ul>
<li>Martin Dougiamas, Moodle</li>
<li>Cable Green, Creative Commons</li>
<li>Patrick Masson, Apereo Foundation</li>
</ul>
<p>Educational institutions have a long and impactful history in the development of multiple open initiatives. In addition to free and open source software, colleges and universities have played significant roles in producing and propagating a variety of other open educational resources, for example, open content, textbooks and courses, open access journals, open data, science and research.</p>
<p>Institutions of higher education play an essential role across several free and open source communities. As adopters, campuses occupy a unique space in--and provide a unique perspective for--the use of free and open source software at the enterprise level, often in conjunction with government and research institutions. At the same time, campus constituencies--students, staff, and faculty--provide yet another perspective as independent desktop and mobile end users. </p>
<p>Higher education is also fertile ground for development; educating the next generation of developers while often actively creating and managing their own projects and communities of practice.</p>
<p>The FOSS For Education Community Track would provide sessions dedicated to using, developing, and managing open resources within academic environments, from multi-institutional consortia to departmental projects. The track organizers would emphasize presentations and topics highlighting the common principles, practices, benefits, challenges, and models spanning the variety of open initiatives impacting teaching and learning environments and campus administration.</p>
<h4 id="openwork">Issues in Open Work; Common Challenges and Best Practices in the Open Source Industry, Open Scholarship, and Government</h4>
Organizers:
<ul>
<li>Stephen Jacobs</li>
<li>Michael Nolan</li>
</ul>
<p>We hope to cover:</p>
<ul>
<li>Relevant changes in government policy surrounding open work</li>
<li>Metrics and Analytics across Open Work</li>
<li>Incentivizing organizations and employees to work in the Open</li>
<li>Best Practices in Community Management Across the fields</li>
<li>Government and Private Funders and Open Work</li>
<li>OSPOs in Academia and Governmen</li>
</ul>
<h4 id="ai-data">Open Source AI + Data</h4>
Organizers:
<ul>
<li>Ruth Suehle</li>
<li>Brian Proffitt</li>
</ul>
<p>Free and open source development has proven its criticality, popularity, and success as a method for bringing software to the world. As we forge into the next evolution of technology, led by data and AI, we must consider how to best apply the lessons of free and open source principles, governance, and development and vendor-neutral collaboration. The focus will no longer be on the underlying code, but about data and how we use and appropriately protect it. Weve already seen many successes in open data, but theres still much to do and growth to plan for. The open data ecosystem is vast, including models, tools, and of course, the data itself and how it is acquired, stored, trained, and used. Then, to come full circle, AI-powered tools are changing how software is written. What do licenses for data and models look like? Whose ethics become the ethics of the AI systems we will all eventually depend on? What are the coming security and privacy concerns? Will the systems of governance we understand in open source software change around AI projects?</p>
<h4 id="repair">Right to Repair</h4>
<p>There is significant overlap between the software freedom and right to repair movements. As we see more and more intersection in activism, legislation, and open technology, we hope to foster a more symbiotic relationship between the spaces. If you have expertise in software freedom and would like to apply that to right to repair issues, or vice versa, please submit your talk!</p>
<h4 id="science">FOSS Research for All: Science of Community</h4>
Organizers:
<ul>
<li>Kaylea Champion, Community Data Science Collective and the University of Washington</li>
<li>Molly de Blanc, Community Data Science Collective and Northwestern University</li>
<li>Benjamin Mako Hill, Community Data Science Collective and the University of Washington</li>
<li>Aaron Shaw, Community Data Science Collective and Northwestern University</li>
</ul>
<p>
Although there are literally hundreds of scholarly papers published about FOSS communities each year, much of this work never makes it out of academic journals and conferences and back to the FOSS communities being studied. At the same time, FOSS communities have a range of insights that researchers studying FOSS would benefit enormously from.
<br/>
The goal of this track is to build bridges between FOSS communities and the research conducted with and about FOSS communities. We hope to provide opportunities for community members to hear about exciting results from researchers, opportunities for researchers to learn from the FOSS community members, and spaces for the FOSS community to think together about how to improve FOSS projects by leveraging research insights and research.
<br/>
This track will include opportunities for:
<ol>
<li>researchers to talk with practitioners (about their research)</li>
<li>practitioners to talk with researchers (about their needs)</li>
<li> researchers to talk with other researchers (for learning and collaboration)</li>
</ol>
If this is appealing to you, please consider proposing, perhaps in one of the following formats:
<ul>
<li>Short Talks. Do you have a recent project to share in some depth? A topic that needs time to unpack? Take 20 minutes to present your thoughts.</li>
<li>Lightning Talks. Want to make a focused point, pitch, or problem report to a great audience? Bring your 5-minute talk to our lightning round.</li>
<li>Panelist. We will be facilitating dialogue between researchers and community members. Would you be willing to share your thoughts as a panelist? Let us know your expertise and a few notes on your perspective so that we can develop a diverse and engaging panel.</li>
</ul>
If you have an idea that doesn't fit into these formats, let's chat! You can reach out to Kaylea (kaylea@uw.edu) or submit your idea as a proposal via the form.<br/>
Submissions are non-archival, so we welcome ongoing, completed, and already published work. Non-archival means that presentation of work at FOSSY does not constitute a publication. It's just a way to get your work out there! Work that synthesizes or draws across a body of published papers is particularly welcome. <br/>
What kind of research are you looking to have presented? <br/>
We are interested in any topic related to FOSS research! This might include research from computing (including software engineering, computer security, social computing, HCI), the social sciences (including management, philosophy, law, economics, sociology, communication, and more), information sciences, and much more. <br/>
For example: how to identify undermaintained packages and what to do about it; community growth and how to find success in small communities; effective rule making and enforcement in online communities. <br/>
If it involves FOSS, we'd welcome it! We are eager to help you put your results into the hands of practitioners who can use your findings to inform their own community's practices and policies on social, governance, and technical topics. </p>
<br>
<h4 id="security">Security</h4>
Organizers
<ul>
<li>Kees Cook</li>
</ul>
<p>A track dedicated to FOSS security ideas and how reproducibility and audibility are important for software freedom. With increasing focus on the Software Supply Chain, focusing on the openness of free software will lead to better industry assurances that free software is the correct path.</p>
<h4 id="sfc-member-projects">SFC Member Projects</h4>
Organizers:
<ul>
<li>SFC Staff</li>
</ul>
<p>As a fiscal sponsor for a multitude of important and vital free software projects, Software Freedom Conservancy takes pride in providing alternatives to proprietary software, funding FOSS infrastructure and making sure important FOSS projects have a legal home. Join us to learn about what our projects are up to and how you can get involved.</p>
<h4 id="business">Sustainable Open Source Business</h4>
Organizers:
<ul>
<li>Matt Yonkovit</li>
<li>Avi Press</li>
</ul>
<p>We want to help maintainers, open source devs, and those looking to build a business around open source software build a sustainable community-focused business. We want to talk openly about concepts like funding, bootstrapping a business, ensuring you are doing it in a way that won't hurt the ecosystem, and how to grow and scale a business. We want to giving budding entrepreneurs the proper knowledge and tools to setup a business that will help their projects grow.</p>
<h4 id="xmpp">XMPP</h4>
Organizers:
<ul>
<li>Stephen Paul Weber 'singpolyma'</li>
<li>root</li>
</ul>
<p>XMPP is an extensible, foundational, and libre building block for any sort of federated communication infrastructure. Talks ranging from those new to the idea, setting up chat or social servers for small groups and families and other use cases, to those familiar with the issues such as SPAM and abuse prevention in a federated space, to technical deep dive talks about open source projects in the space and their innovations, would all be something worth covering in this track. We would strive to both appeal to the core XMPP audience and bring them to FOSSY, but also to introduce the projects and ideas to the rest of the FOSS community.</p>
<h4 id="wildcard">Wild card</h4>
Organizers:
<ul>
<li>SFC Staff</li>
</ul>
<p>For any talks that don't fit cleanly into the rest of the tracks. Don't be shy about putting it here if you don't know where it should go, we can always rearrange later!</p>
<h4 id="coops">Worker-Owner Co-ops that write and use FOSS</h4>
Organizers:
<ul>
<li>Valerie Young</li>
<li>Clayton Craft</li>
</ul>
<h1 class="page-title">Tracks</h1>
<h4 id="arm">AArch64/ARM64 Servers and Open Source- The Who, What, Why, and How</h4>
Organizers:
<ul>
<li>Aaron Williams</li>
<li>Dave Neary</li>
</ul>
<p>ARM64/AArch64 devices are some of the most widely used processors in the world, from small SoC boards like the Raspberry Pi to mobile phones and even Apple's latest M1 and M2 chips powering MacBooks. Their high performance and power efficiency means more performance per watt of energy used, making them ideal for mobile and laptops where performance, battery life, and heat dissipation are important.</p>
<p>These same performance advantages are becoming increasingly important in data centers as well. The aging x86 server technology uses more energy and requires more complicated cooling solutions, limiting the number of servers that can be placed in a rack. Plus, their single threaded cores, mean no noisy neighbor problems, and better high performance and predictable throughput. As a result, all major public clouds, including Azure, GCP, Oracle Cloud, AWS, Bytedance, Alibaba, and Tencent, have started adopting AArch64 servers in their data centers. In fact, the number of AArch64 servers in data centers has grown from 1% in 2019 to 6% today, and it's estimated that they will make up 50% of all servers by 2026. This is why it's crucial for open-source projects to understand these trends to take advantage of them going forward.</p>
<p>In this track, we will introduce DevOps engineers, developers, and architects to the latest trends and technologies in the AArch64 server world. Our sessions will cover:</p>
<ul>
<li>What are AArch64 servers, and how do they perform against x86?</li>
<li>What makes them different from x86?</li>
<li>Who is using them, and what projects are using them?</li>
<li>Why use AArch64 servers, and what are the advantages?</li>
<li>How to get started using AArch64 servers </li>
<li>A comparison of performance between AArch64 and x86 servers, covering topics such as compiling natively versus emulation with QEMU.</li>
</ul>
<p>We believe that this track will provide valuable insights for anyone interested in leveraging AArch64 servers in their work, from small-scale open-source projects to large data centers.</p>
<h4 id="bsd">BSD Unix</h4>
Organizers:
<ul>
<li>Michael Dexter</li>
<li>Andrew Fresh</li>
<li>Alexander Vasarab</li>
</ul>
<p>The BSD Unix track would showcase the BSD family of Unix operating systems, each of which is backed by a public-benefit nonprofit, rather than a for-profit company. We have the BSDs to thank for OpenSSH, mandoc, the Berkeley Packet Filter BPF, the PF packet filter, the IPFW firewall, the bhyve hypervisor, plus countless smaller utilities used throughout the free software ecosystem. The track would statistically focus on FreeBSD and OpenBSD, but would welcome other BSD operating systems such as NetBSD and distant cousin illumos.</p>
<h4 id="community">Community: Open Source in Practice</h4>
Organizers:
<ul>
<li>Josh Simmons</li>
<li>Monica Ayhens-Madon</li>
<li>julia ferraioli</li>
<li>Stephan Micahel Kellat</li>
</ul>
<p>Communities of people are the beating heart of free and open source software, and this track provides a home for sessions covering the many practices involved in building and supporting healthy, productive communities.</p>
<p>In this track, we welcome sessions on topics ranging from community management, communications infrastructure, project governance, sustainability, education, mentorship, and succession planning, contributor experience, event organizing, marketing, research, movement and coalition building, and tackling the interface between communities and corporations with integrity. No matter the topic, we encourage sessions that discuss the how of community as much as the why. Diversity, equity, inclusion, and belonging is a lens we aim to see represented across the board, as a standard of community building.</p>
<p>Any one of these topics could be a track unto itself, but often lack the critical mass to stand alone at conferences and land in the squishy bucket we call “community.” The organizers of this track view this as an antipattern, while also recognizing its a familiar dynamic. We hope, in collaboration with our speakers, to elevate these topics and engender a culture in which these topics are elevated and celebrated.</p>
<p>We welcome proposals from speakers and people who are excited to give their first talk. We want seasoned professionals and volunteers, as well as fresh perspectives from new entrants. Everyone has something of value to share! We are prepared to help with proposals and presentations to make sure everyone is putting their best foot forward.</p>
<p>Beyond the core audience of community professionals and leaders, both paid and volunteer, we treasure cross-pollination and encourage participation from people in other disciplines.</p>
<h4 id="container">Container Days</h4>
Organizers:
<ul>
<li>Josh Berkus</li>
<li>Chris Hoge</li>
<li>Melissa Logan</li>
</ul>
<p>ContainerDaysPDX has returned! Join us for two days of exploration of the latest generation of web and application infrastructure. We'll cover both the basics, and the newer and more esoteric aspects of orchestrated container stacks, including:</p>
<ul>
<li>Moving to containers and Kubernetes without losing your sanity</li>
<li>Desktop development for containerized applications</li>
<li>Developments in Linux: cGroupsv2, seccomp, and more</li>
<li>Containers on alternate platforms (FreeBSD, windows)</li>
<li>Container alternatives like WASM and microVMs</li>
<li>ML and data analysis in container clouds</li>
<li>Alternatives to Kubernetes</li>
<li>Security, networking, and performance for new stacks</li>
<li>Kubernetes + Openstack + OpenInfra: all the layers </li>
</ul>
<p>... and more! ContainerDays will bring exciting technical topics to Portland and FOSSYcon. It will cover not just what's available now, but what free software developers are working on for the future.</p>
<p>Whether you're just getting started with the new container stacks, or have been using Docker since 2014, whether you're an application developer, ops staff, or an infrastructure hacker, we plan to have something for you. </p>
<h4 id="copyleft">Copyleft and Compliance</h4>
<p>Participants from throughout the copyleft world — developers, strategists, enforcement organizations, scholars and critics — will be welcomed for an in-depth, high bandwidth, and expert-level discussion about the day-to-day details of using copyleft licensing, obstacles facing copyleft and the future of copyleft as a strategy to advance and defend software freedom for users and developers around the world.</p>
<h4 id="dei">Diversity Equity and Inclusion and FOSS</h4>
Organizers:
<ul>
<li>Aarti Ramkrishna</li>
<li>Anita Ihuman</li>
<li>Georg Link</li>
<li>Sri Ramkrishna</li>
</ul>
<p>Diversity, Equity, and inclusion are receiving increased attention in the FOSS community, the broader technology industry, and beyond. Since free and open software, hardware, and standards are made by people with very different backgrounds, beliefs, disabilities, nationalities, and identities, it is important to ensure access for these different groups and enable them to participate in a healthy way. This conference track provides a space to discuss diversity, equity, and inclusion challenges and solutions. We invite submissions from practitioners who share their own stories and what strategies they have tried to improve DEI, regardless of whether they succeeded or failed. We invite submission focused on DEI in FOSS, DEI beyond FOSS, and personal DEI experiences.</p>
<p>We look forward to providing a safe and welcoming space for highlighting DEI efforts and experiences from various perspectives, initiatives, and programs. We invite submissions from people who face systemic bias or discrimination in the technology industry of their country. We expressly invite submissions from women (both cis and trans), trans men, non-binary people, and gender queer people to apply. We further invite submissions from allies. </p>
<h4 id="daily-life">FOSS in Daily Life</h4>
Organizers:
<ul>
<li>SFC Staff</li>
</ul>
<p>How are you using FOSS in your "everyday" life? Are there places where you
find it's easier or harder to get the people around you to respect and
appreciate software freedom? What areas of software are we missing in our
pursuit of software freedom for all?</p>
<h4 id="play">FOSS at Play: Games, creative development, and open technology</h4>
Organizers:
<ul>
<li>Paris Buttfield-Addison</li>
<li>Stephen Jacobs</li>
</ul>
<p>The relationship between FOSS and Game Development is a multidisciplinary maze of creative, software, community, legal, and design issues that can very easily make your head spin. This track will help demystify the world of FOSS and Game Development, blending topics around the following pillars:</p>
<ul>
<li>FOSS game engines and tools</li>
<li>Legal or business implications of game development using FOSS</li>
<li>The history of FOSS in games and game development</li>
<li>Best practices in releasing your game as FOSS</li>
<li>FOSS support tools and communities for other games</li>
<li>Improving proprietary game engines with FOSS tooling</li>
<li>Open game hardware and peripherals</li>
<li>Community management and the differences between traditional FOSS communities and games communities</li>
<li>Finding, using, and releasing game assets (art, music, etc.) under free and open licenses</li>
<li>FOSS and board games</li>
</ul>
<p>Our audience is FOSS enthusiasts, software developers, designers, and creatives who are intrigued or interested in games, but are cautious to dive too deep, due to the overwhelmingly proprietary appearance of the industry. Games are nowhere near as proprietary as you may think, and this track will help usher in new users, contributors, and creators to the fantastic collection of FOSS tools, and encourage them to release new games, tools, and creative works.</p>
<h4 id="education">FOSS For Education</h4>
Organizers:
<ul>
<li>Martin Dougiamas, Moodle</li>
<li>Cable Green, Creative Commons</li>
<li>Patrick Masson, Apereo Foundation</li>
</ul>
<p>Educational institutions have a long and impactful history in the development of multiple open initiatives. In addition to free and open source software, colleges and universities have played significant roles in producing and propagating a variety of other open educational resources, for example, open content, textbooks and courses, open access journals, open data, science and research.</p>
<p>Institutions of higher education play an essential role across several free and open source communities. As adopters, campuses occupy a unique space in--and provide a unique perspective for--the use of free and open source software at the enterprise level, often in conjunction with government and research institutions. At the same time, campus constituencies--students, staff, and faculty--provide yet another perspective as independent desktop and mobile end users. </p>
<p>Higher education is also fertile ground for development; educating the next generation of developers while often actively creating and managing their own projects and communities of practice.</p>
<p>The FOSS For Education Community Track would provide sessions dedicated to using, developing, and managing open resources within academic environments, from multi-institutional consortia to departmental projects. The track organizers would emphasize presentations and topics highlighting the common principles, practices, benefits, challenges, and models spanning the variety of open initiatives impacting teaching and learning environments and campus administration.</p>
<h4 id="openwork">Issues in Open Work; Common Challenges and Best Practices in the Open Source Industry, Open Scholarship, and Government</h4>
Organizers:
<ul>
<li>Stephen Jacobs</li>
<li>Michael Nolan</li>
</ul>
<p>We hope to cover:</p>
<ul>
<li>Relevant changes in government policy surrounding open work</li>
<li>Metrics and Analytics across Open Work</li>
<li>Incentivizing organizations and employees to work in the Open</li>
<li>Best Practices in Community Management Across the fields</li>
<li>Government and Private Funders and Open Work</li>
<li>OSPOs in Academia and Governmen</li>
</ul>
<h4 id="ai-data">Open Source AI + Data</h4>
Organizers:
<ul>
<li>Ruth Suehle</li>
<li>Brian Proffitt</li>
</ul>
<p>Free and open source development has proven its criticality, popularity, and success as a method for bringing software to the world. As we forge into the next evolution of technology, led by data and AI, we must consider how to best apply the lessons of free and open source principles, governance, and development and vendor-neutral collaboration. The focus will no longer be on the underlying code, but about data and how we use and appropriately protect it. Weve already seen many successes in open data, but theres still much to do and growth to plan for. The open data ecosystem is vast, including models, tools, and of course, the data itself and how it is acquired, stored, trained, and used. Then, to come full circle, AI-powered tools are changing how software is written. What do licenses for data and models look like? Whose ethics become the ethics of the AI systems we will all eventually depend on? What are the coming security and privacy concerns? Will the systems of governance we understand in open source software change around AI projects?</p>
<h4 id="repair">Right to Repair</h4>
<p>There is significant overlap between the software freedom and right to repair movements. As we see more and more intersection in activism, legislation, and open technology, we hope to foster a more symbiotic relationship between the spaces. If you have expertise in software freedom and would like to apply that to right to repair issues, or vice versa, please submit your talk!</p>
<h4 id="science">FOSS Research for All: Science of Community</h4>
Organizers:
<ul>
<li>Kaylea Champion, Community Data Science Collective and the University of Washington</li>
<li>Molly de Blanc, Community Data Science Collective and Northwestern University</li>
<li>Benjamin Mako Hill, Community Data Science Collective and the University of Washington</li>
<li>Aaron Shaw, Community Data Science Collective and Northwestern University</li>
</ul>
<p>
Although there are literally hundreds of scholarly papers published about FOSS communities each year, much of this work never makes it out of academic journals and conferences and back to the FOSS communities being studied. At the same time, FOSS communities have a range of insights that researchers studying FOSS would benefit enormously from.
<br/>
The goal of this track is to build bridges between FOSS communities and the research conducted with and about FOSS communities. We hope to provide opportunities for community members to hear about exciting results from researchers, opportunities for researchers to learn from the FOSS community members, and spaces for the FOSS community to think together about how to improve FOSS projects by leveraging research insights and research.
<br/>
This track will include opportunities for:
<ol>
<li>researchers to talk with practitioners (about their research)</li>
<li>practitioners to talk with researchers (about their needs)</li>
<li> researchers to talk with other researchers (for learning and collaboration)</li>
</ol>
If this is appealing to you, please consider proposing, perhaps in one of the following formats:
<ul>
<li>Short Talks. Do you have a recent project to share in some depth? A topic that needs time to unpack? Take 20 minutes to present your thoughts.</li>
<li>Lightning Talks. Want to make a focused point, pitch, or problem report to a great audience? Bring your 5-minute talk to our lightning round.</li>
<li>Panelist. We will be facilitating dialogue between researchers and community members. Would you be willing to share your thoughts as a panelist? Let us know your expertise and a few notes on your perspective so that we can develop a diverse and engaging panel.</li>
</ul>
If you have an idea that doesn't fit into these formats, let's chat! You can reach out to Kaylea (kaylea@uw.edu) or submit your idea as a proposal via the form.<br/>
Submissions are non-archival, so we welcome ongoing, completed, and already published work. Non-archival means that presentation of work at FOSSY does not constitute a publication. It's just a way to get your work out there! Work that synthesizes or draws across a body of published papers is particularly welcome. <br/>
What kind of research are you looking to have presented? <br/>
We are interested in any topic related to FOSS research! This might include research from computing (including software engineering, computer security, social computing, HCI), the social sciences (including management, philosophy, law, economics, sociology, communication, and more), information sciences, and much more. <br/>
For example: how to identify undermaintained packages and what to do about it; community growth and how to find success in small communities; effective rule making and enforcement in online communities. <br/>
If it involves FOSS, we'd welcome it! We are eager to help you put your results into the hands of practitioners who can use your findings to inform their own community's practices and policies on social, governance, and technical topics. </p>
<br>
<h4 id="security">Security</h4>
Organizers
<ul>
<li>Kees Cook</li>
</ul>
<p>A track dedicated to FOSS security ideas and how reproducibility and audibility are important for software freedom. With increasing focus on the Software Supply Chain, focusing on the openness of free software will lead to better industry assurances that free software is the correct path.</p>
<h4 id="sfc-member-projects">SFC Member Projects</h4>
Organizers:
<ul>
<li>SFC Staff</li>
</ul>
<p>As a fiscal sponsor for a multitude of important and vital free software projects, Software Freedom Conservancy takes pride in providing alternatives to proprietary software, funding FOSS infrastructure and making sure important FOSS projects have a legal home. Join us to learn about what our projects are up to and how you can get involved.</p>
<h4 id="business">Sustainable Open Source Business</h4>
Organizers:
<ul>
<li>Matt Yonkovit</li>
<li>Avi Press</li>
</ul>
<p>We want to help maintainers, open source devs, and those looking to build a business around open source software build a sustainable community-focused business. We want to talk openly about concepts like funding, bootstrapping a business, ensuring you are doing it in a way that won't hurt the ecosystem, and how to grow and scale a business. We want to giving budding entrepreneurs the proper knowledge and tools to setup a business that will help their projects grow.</p>
<h4 id="xmpp">XMPP</h4>
Organizers:
<ul>
<li>Stephen Paul Weber 'singpolyma'</li>
<li>root</li>
</ul>
<p>XMPP is an extensible, foundational, and libre building block for any sort of federated communication infrastructure. Talks ranging from those new to the idea, setting up chat or social servers for small groups and families and other use cases, to those familiar with the issues such as SPAM and abuse prevention in a federated space, to technical deep dive talks about open source projects in the space and their innovations, would all be something worth covering in this track. We would strive to both appeal to the core XMPP audience and bring them to FOSSY, but also to introduce the projects and ideas to the rest of the FOSS community.</p>
<h4 id="wildcard">Wild card</h4>
Organizers:
<ul>
<li>SFC Staff</li>
</ul>
<p>For any talks that don't fit cleanly into the rest of the tracks. Don't be shy about putting it here if you don't know where it should go, we can always rearrange later!</p>
<h4 id="coops">Worker-Owner Co-ops that write and use FOSS</h4>
Organizers:
<ul>
<li>Valerie Young</li>
<li>Clayton Craft</li>
</ul>
<p>This community track will include speakers from worker-owned co-operatives that write or use FOSS. Topics will include which FOSS projects they use, their relationship with the organizations that produce the FOSS they use, their relationship with customers (if they produce FOSS), their co-op's history and structure, and more!</p>
</div>
</div>

View file

@ -165,269 +165,269 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 class="page-title">Tracks</h1>
<h4 id="arm">AArch64/ARM64 Servers and Open Source- The Who, What, Why, and How</h4>
Organizers:
<ul>
<li>Aaron Williams</li>
<li>Dave Neary</li>
</ul>
<p>ARM64/AArch64 devices are some of the most widely used processors in the world, from small SoC boards like the Raspberry Pi to mobile phones and even Apple's latest M1 and M2 chips powering MacBooks. Their high performance and power efficiency means more performance per watt of energy used, making them ideal for mobile and laptops where performance, battery life, and heat dissipation are important.</p>
<p>These same performance advantages are becoming increasingly important in data centers as well. The aging x86 server technology uses more energy and requires more complicated cooling solutions, limiting the number of servers that can be placed in a rack. Plus, their single threaded cores, mean no noisy neighbor problems, and better high performance and predictable throughput. As a result, all major public clouds, including Azure, GCP, Oracle Cloud, AWS, Bytedance, Alibaba, and Tencent, have started adopting AArch64 servers in their data centers. In fact, the number of AArch64 servers in data centers has grown from 1% in 2019 to 6% today, and it's estimated that they will make up 50% of all servers by 2026. This is why it's crucial for open-source projects to understand these trends to take advantage of them going forward.</p>
<p>In this track, we will introduce DevOps engineers, developers, and architects to the latest trends and technologies in the AArch64 server world. Our sessions will cover:</p>
<ul>
<li>What are AArch64 servers, and how do they perform against x86?</li>
<li>What makes them different from x86?</li>
<li>Who is using them, and what projects are using them?</li>
<li>Why use AArch64 servers, and what are the advantages?</li>
<li>How to get started using AArch64 servers </li>
<li>A comparison of performance between AArch64 and x86 servers, covering topics such as compiling natively versus emulation with QEMU.</li>
</ul>
<p>We believe that this track will provide valuable insights for anyone interested in leveraging AArch64 servers in their work, from small-scale open-source projects to large data centers.</p>
<h4 id="bsd">BSD Unix</h4>
Organizers:
<ul>
<li>Michael Dexter</li>
<li>Andrew Fresh</li>
<li>Alexander Vasarab</li>
</ul>
<p>The BSD Unix track would showcase the BSD family of Unix operating systems, each of which is backed by a public-benefit nonprofit, rather than a for-profit company. We have the BSDs to thank for OpenSSH, mandoc, the Berkeley Packet Filter BPF, the PF packet filter, the IPFW firewall, the bhyve hypervisor, plus countless smaller utilities used throughout the free software ecosystem. The track would statistically focus on FreeBSD and OpenBSD, but would welcome other BSD operating systems such as NetBSD and distant cousin illumos.</p>
<h4 id="community">Community: Open Source in Practice</h4>
Organizers:
<ul>
<li>Josh Simmons</li>
<li>Monica Ayhens-Madon</li>
<li>julia ferraioli</li>
<li>Stephan Micahel Kellat</li>
</ul>
<p>Communities of people are the beating heart of free and open source software, and this track provides a home for sessions covering the many practices involved in building and supporting healthy, productive communities.</p>
<p>In this track, we welcome sessions on topics ranging from community management, communications infrastructure, project governance, sustainability, education, mentorship, and succession planning, contributor experience, event organizing, marketing, research, movement and coalition building, and tackling the interface between communities and corporations with integrity. No matter the topic, we encourage sessions that discuss the how of community as much as the why. Diversity, equity, inclusion, and belonging is a lens we aim to see represented across the board, as a standard of community building.</p>
<p>Any one of these topics could be a track unto itself, but often lack the critical mass to stand alone at conferences and land in the squishy bucket we call “community.” The organizers of this track view this as an antipattern, while also recognizing its a familiar dynamic. We hope, in collaboration with our speakers, to elevate these topics and engender a culture in which these topics are elevated and celebrated.</p>
<p>We welcome proposals from speakers and people who are excited to give their first talk. We want seasoned professionals and volunteers, as well as fresh perspectives from new entrants. Everyone has something of value to share! We are prepared to help with proposals and presentations to make sure everyone is putting their best foot forward.</p>
<p>Beyond the core audience of community professionals and leaders, both paid and volunteer, we treasure cross-pollination and encourage participation from people in other disciplines.</p>
<h4 id="container">Container Days</h4>
Organizers:
<ul>
<li>Josh Berkus</li>
<li>Chris Hoge</li>
<li>Melissa Logan</li>
</ul>
<p>ContainerDaysPDX has returned! Join us for two days of exploration of the latest generation of web and application infrastructure. We'll cover both the basics, and the newer and more esoteric aspects of orchestrated container stacks, including:</p>
<ul>
<li>Moving to containers and Kubernetes without losing your sanity</li>
<li>Desktop development for containerized applications</li>
<li>Developments in Linux: cGroupsv2, seccomp, and more</li>
<li>Containers on alternate platforms (FreeBSD, windows)</li>
<li>Container alternatives like WASM and microVMs</li>
<li>ML and data analysis in container clouds</li>
<li>Alternatives to Kubernetes</li>
<li>Security, networking, and performance for new stacks</li>
<li>Kubernetes + Openstack + OpenInfra: all the layers </li>
</ul>
<p>... and more! ContainerDays will bring exciting technical topics to Portland and FOSSYcon. It will cover not just what's available now, but what free software developers are working on for the future.</p>
<p>Whether you're just getting started with the new container stacks, or have been using Docker since 2014, whether you're an application developer, ops staff, or an infrastructure hacker, we plan to have something for you. </p>
<h4 id="copyleft">Copyleft and Compliance</h4>
<p>Participants from throughout the copyleft world — developers, strategists, enforcement organizations, scholars and critics — will be welcomed for an in-depth, high bandwidth, and expert-level discussion about the day-to-day details of using copyleft licensing, obstacles facing copyleft and the future of copyleft as a strategy to advance and defend software freedom for users and developers around the world.</p>
<h4 id="dei">Diversity Equity and Inclusion and FOSS</h4>
Organizers:
<ul>
<li>Aarti Ramkrishna</li>
<li>Anita Ihuman</li>
<li>Georg Link</li>
<li>Sri Ramkrishna</li>
</ul>
<p>Diversity, Equity, and inclusion are receiving increased attention in the FOSS community, the broader technology industry, and beyond. Since free and open software, hardware, and standards are made by people with very different backgrounds, beliefs, disabilities, nationalities, and identities, it is important to ensure access for these different groups and enable them to participate in a healthy way. This conference track provides a space to discuss diversity, equity, and inclusion challenges and solutions. We invite submissions from practitioners who share their own stories and what strategies they have tried to improve DEI, regardless of whether they succeeded or failed. We invite submission focused on DEI in FOSS, DEI beyond FOSS, and personal DEI experiences.</p>
<p>We look forward to providing a safe and welcoming space for highlighting DEI efforts and experiences from various perspectives, initiatives, and programs. We invite submissions from people who face systemic bias or discrimination in the technology industry of their country. We expressly invite submissions from women (both cis and trans), trans men, non-binary people, and gender queer people to apply. We further invite submissions from allies. </p>
<h4 id="daily-life">FOSS in Daily Life</h4>
Organizers:
<ul>
<li>SFC Staff</li>
</ul>
<p>How are you using FOSS in your "everyday" life? Are there places where you
find it's easier or harder to get the people around you to respect and
appreciate software freedom? What areas of software are we missing in our
pursuit of software freedom for all?</p>
<h4 id="play">FOSS at Play: Games, creative development, and open technology</h4>
Organizers:
<ul>
<li>Paris Buttfield-Addison</li>
<li>Stephen Jacobs</li>
</ul>
<p>The relationship between FOSS and Game Development is a multidisciplinary maze of creative, software, community, legal, and design issues that can very easily make your head spin. This track will help demystify the world of FOSS and Game Development, blending topics around the following pillars:</p>
<ul>
<li>FOSS game engines and tools</li>
<li>Legal or business implications of game development using FOSS</li>
<li>The history of FOSS in games and game development</li>
<li>Best practices in releasing your game as FOSS</li>
<li>FOSS support tools and communities for other games</li>
<li>Improving proprietary game engines with FOSS tooling</li>
<li>Open game hardware and peripherals</li>
<li>Community management and the differences between traditional FOSS communities and games communities</li>
<li>Finding, using, and releasing game assets (art, music, etc.) under free and open licenses</li>
<li>FOSS and board games</li>
</ul>
<p>Our audience is FOSS enthusiasts, software developers, designers, and creatives who are intrigued or interested in games, but are cautious to dive too deep, due to the overwhelmingly proprietary appearance of the industry. Games are nowhere near as proprietary as you may think, and this track will help usher in new users, contributors, and creators to the fantastic collection of FOSS tools, and encourage them to release new games, tools, and creative works.</p>
<h4 id="education">FOSS For Education</h4>
Organizers:
<ul>
<li>Martin Dougiamas, Moodle</li>
<li>Cable Green, Creative Commons</li>
<li>Patrick Masson, Apereo Foundation</li>
</ul>
<p>Educational institutions have a long and impactful history in the development of multiple open initiatives. In addition to free and open source software, colleges and universities have played significant roles in producing and propagating a variety of other open educational resources, for example, open content, textbooks and courses, open access journals, open data, science and research.</p>
<p>Institutions of higher education play an essential role across several free and open source communities. As adopters, campuses occupy a unique space in--and provide a unique perspective for--the use of free and open source software at the enterprise level, often in conjunction with government and research institutions. At the same time, campus constituencies--students, staff, and faculty--provide yet another perspective as independent desktop and mobile end users. </p>
<p>Higher education is also fertile ground for development; educating the next generation of developers while often actively creating and managing their own projects and communities of practice.</p>
<p>The FOSS For Education Community Track would provide sessions dedicated to using, developing, and managing open resources within academic environments, from multi-institutional consortia to departmental projects. The track organizers would emphasize presentations and topics highlighting the common principles, practices, benefits, challenges, and models spanning the variety of open initiatives impacting teaching and learning environments and campus administration.</p>
<h4 id="openwork">Issues in Open Work; Common Challenges and Best Practices in the Open Source Industry, Open Scholarship, and Government</h4>
Organizers:
<ul>
<li>Stephen Jacobs</li>
<li>Michael Nolan</li>
</ul>
<p>We hope to cover:</p>
<ul>
<li>Relevant changes in government policy surrounding open work</li>
<li>Metrics and Analytics across Open Work</li>
<li>Incentivizing organizations and employees to work in the Open</li>
<li>Best Practices in Community Management Across the fields</li>
<li>Government and Private Funders and Open Work</li>
<li>OSPOs in Academia and Governmen</li>
</ul>
<h4 id="ai-data">Open Source AI + Data</h4>
Organizers:
<ul>
<li>Ruth Suehle</li>
<li>Brian Proffitt</li>
</ul>
<p>Free and open source development has proven its criticality, popularity, and success as a method for bringing software to the world. As we forge into the next evolution of technology, led by data and AI, we must consider how to best apply the lessons of free and open source principles, governance, and development and vendor-neutral collaboration. The focus will no longer be on the underlying code, but about data and how we use and appropriately protect it. Weve already seen many successes in open data, but theres still much to do and growth to plan for. The open data ecosystem is vast, including models, tools, and of course, the data itself and how it is acquired, stored, trained, and used. Then, to come full circle, AI-powered tools are changing how software is written. What do licenses for data and models look like? Whose ethics become the ethics of the AI systems we will all eventually depend on? What are the coming security and privacy concerns? Will the systems of governance we understand in open source software change around AI projects?</p>
<h4 id="repair">Right to Repair</h4>
<p>There is significant overlap between the software freedom and right to repair movements. As we see more and more intersection in activism, legislation, and open technology, we hope to foster a more symbiotic relationship between the spaces. If you have expertise in software freedom and would like to apply that to right to repair issues, or vice versa, please submit your talk!</p>
<h4 id="science">FOSS Research for All: Science of Community</h4>
Organizers:
<ul>
<li>Kaylea Champion, Community Data Science Collective and the University of Washington</li>
<li>Molly de Blanc, Community Data Science Collective and Northwestern University</li>
<li>Benjamin Mako Hill, Community Data Science Collective and the University of Washington</li>
<li>Aaron Shaw, Community Data Science Collective and Northwestern University</li>
</ul>
<p>
Although there are literally hundreds of scholarly papers published about FOSS communities each year, much of this work never makes it out of academic journals and conferences and back to the FOSS communities being studied. At the same time, FOSS communities have a range of insights that researchers studying FOSS would benefit enormously from.
<br/>
The goal of this track is to build bridges between FOSS communities and the research conducted with and about FOSS communities. We hope to provide opportunities for community members to hear about exciting results from researchers, opportunities for researchers to learn from the FOSS community members, and spaces for the FOSS community to think together about how to improve FOSS projects by leveraging research insights and research.
<br/>
This track will include opportunities for:
<ol>
<li>researchers to talk with practitioners (about their research)</li>
<li>practitioners to talk with researchers (about their needs)</li>
<li> researchers to talk with other researchers (for learning and collaboration)</li>
</ol>
If this is appealing to you, please consider proposing, perhaps in one of the following formats:
<ul>
<li>Short Talks. Do you have a recent project to share in some depth? A topic that needs time to unpack? Take 20 minutes to present your thoughts.</li>
<li>Lightning Talks. Want to make a focused point, pitch, or problem report to a great audience? Bring your 5-minute talk to our lightning round.</li>
<li>Panelist. We will be facilitating dialogue between researchers and community members. Would you be willing to share your thoughts as a panelist? Let us know your expertise and a few notes on your perspective so that we can develop a diverse and engaging panel.</li>
</ul>
If you have an idea that doesn't fit into these formats, let's chat! You can reach out to Kaylea (kaylea@uw.edu) or submit your idea as a proposal via the form.<br/>
Submissions are non-archival, so we welcome ongoing, completed, and already published work. Non-archival means that presentation of work at FOSSY does not constitute a publication. It's just a way to get your work out there! Work that synthesizes or draws across a body of published papers is particularly welcome. <br/>
What kind of research are you looking to have presented? <br/>
We are interested in any topic related to FOSS research! This might include research from computing (including software engineering, computer security, social computing, HCI), the social sciences (including management, philosophy, law, economics, sociology, communication, and more), information sciences, and much more. <br/>
For example: how to identify undermaintained packages and what to do about it; community growth and how to find success in small communities; effective rule making and enforcement in online communities. <br/>
If it involves FOSS, we'd welcome it! We are eager to help you put your results into the hands of practitioners who can use your findings to inform their own community's practices and policies on social, governance, and technical topics. </p>
<br>
<h4 id="security">Security</h4>
Organizers
<ul>
<li>Kees Cook</li>
</ul>
<p>A track dedicated to FOSS security ideas and how reproducibility and audibility are important for software freedom. With increasing focus on the Software Supply Chain, focusing on the openness of free software will lead to better industry assurances that free software is the correct path.</p>
<h4 id="sfc-member-projects">SFC Member Projects</h4>
Organizers:
<ul>
<li>SFC Staff</li>
</ul>
<p>As a fiscal sponsor for a multitude of important and vital free software projects, Software Freedom Conservancy takes pride in providing alternatives to proprietary software, funding FOSS infrastructure and making sure important FOSS projects have a legal home. Join us to learn about what our projects are up to and how you can get involved.</p>
<h4 id="business">Sustainable Open Source Business</h4>
Organizers:
<ul>
<li>Matt Yonkovit</li>
<li>Avi Press</li>
</ul>
<p>We want to help maintainers, open source devs, and those looking to build a business around open source software build a sustainable community-focused business. We want to talk openly about concepts like funding, bootstrapping a business, ensuring you are doing it in a way that won't hurt the ecosystem, and how to grow and scale a business. We want to giving budding entrepreneurs the proper knowledge and tools to setup a business that will help their projects grow.</p>
<h4 id="xmpp">XMPP</h4>
Organizers:
<ul>
<li>Stephen Paul Weber 'singpolyma'</li>
<li>root</li>
</ul>
<p>XMPP is an extensible, foundational, and libre building block for any sort of federated communication infrastructure. Talks ranging from those new to the idea, setting up chat or social servers for small groups and families and other use cases, to those familiar with the issues such as SPAM and abuse prevention in a federated space, to technical deep dive talks about open source projects in the space and their innovations, would all be something worth covering in this track. We would strive to both appeal to the core XMPP audience and bring them to FOSSY, but also to introduce the projects and ideas to the rest of the FOSS community.</p>
<h4 id="wildcard">Wild card</h4>
Organizers:
<ul>
<li>SFC Staff</li>
</ul>
<p>For any talks that don't fit cleanly into the rest of the tracks. Don't be shy about putting it here if you don't know where it should go, we can always rearrange later!</p>
<h4 id="coops">Worker-Owner Co-ops that write and use FOSS</h4>
Organizers:
<ul>
<li>Valerie Young</li>
<li>Clayton Craft</li>
</ul>
<h1 class="page-title">Tracks</h1>
<h4 id="arm">AArch64/ARM64 Servers and Open Source- The Who, What, Why, and How</h4>
Organizers:
<ul>
<li>Aaron Williams</li>
<li>Dave Neary</li>
</ul>
<p>ARM64/AArch64 devices are some of the most widely used processors in the world, from small SoC boards like the Raspberry Pi to mobile phones and even Apple's latest M1 and M2 chips powering MacBooks. Their high performance and power efficiency means more performance per watt of energy used, making them ideal for mobile and laptops where performance, battery life, and heat dissipation are important.</p>
<p>These same performance advantages are becoming increasingly important in data centers as well. The aging x86 server technology uses more energy and requires more complicated cooling solutions, limiting the number of servers that can be placed in a rack. Plus, their single threaded cores, mean no noisy neighbor problems, and better high performance and predictable throughput. As a result, all major public clouds, including Azure, GCP, Oracle Cloud, AWS, Bytedance, Alibaba, and Tencent, have started adopting AArch64 servers in their data centers. In fact, the number of AArch64 servers in data centers has grown from 1% in 2019 to 6% today, and it's estimated that they will make up 50% of all servers by 2026. This is why it's crucial for open-source projects to understand these trends to take advantage of them going forward.</p>
<p>In this track, we will introduce DevOps engineers, developers, and architects to the latest trends and technologies in the AArch64 server world. Our sessions will cover:</p>
<ul>
<li>What are AArch64 servers, and how do they perform against x86?</li>
<li>What makes them different from x86?</li>
<li>Who is using them, and what projects are using them?</li>
<li>Why use AArch64 servers, and what are the advantages?</li>
<li>How to get started using AArch64 servers </li>
<li>A comparison of performance between AArch64 and x86 servers, covering topics such as compiling natively versus emulation with QEMU.</li>
</ul>
<p>We believe that this track will provide valuable insights for anyone interested in leveraging AArch64 servers in their work, from small-scale open-source projects to large data centers.</p>
<h4 id="bsd">BSD Unix</h4>
Organizers:
<ul>
<li>Michael Dexter</li>
<li>Andrew Fresh</li>
<li>Alexander Vasarab</li>
</ul>
<p>The BSD Unix track would showcase the BSD family of Unix operating systems, each of which is backed by a public-benefit nonprofit, rather than a for-profit company. We have the BSDs to thank for OpenSSH, mandoc, the Berkeley Packet Filter BPF, the PF packet filter, the IPFW firewall, the bhyve hypervisor, plus countless smaller utilities used throughout the free software ecosystem. The track would statistically focus on FreeBSD and OpenBSD, but would welcome other BSD operating systems such as NetBSD and distant cousin illumos.</p>
<h4 id="community">Community: Open Source in Practice</h4>
Organizers:
<ul>
<li>Josh Simmons</li>
<li>Monica Ayhens-Madon</li>
<li>julia ferraioli</li>
<li>Stephan Micahel Kellat</li>
</ul>
<p>Communities of people are the beating heart of free and open source software, and this track provides a home for sessions covering the many practices involved in building and supporting healthy, productive communities.</p>
<p>In this track, we welcome sessions on topics ranging from community management, communications infrastructure, project governance, sustainability, education, mentorship, and succession planning, contributor experience, event organizing, marketing, research, movement and coalition building, and tackling the interface between communities and corporations with integrity. No matter the topic, we encourage sessions that discuss the how of community as much as the why. Diversity, equity, inclusion, and belonging is a lens we aim to see represented across the board, as a standard of community building.</p>
<p>Any one of these topics could be a track unto itself, but often lack the critical mass to stand alone at conferences and land in the squishy bucket we call “community.” The organizers of this track view this as an antipattern, while also recognizing its a familiar dynamic. We hope, in collaboration with our speakers, to elevate these topics and engender a culture in which these topics are elevated and celebrated.</p>
<p>We welcome proposals from speakers and people who are excited to give their first talk. We want seasoned professionals and volunteers, as well as fresh perspectives from new entrants. Everyone has something of value to share! We are prepared to help with proposals and presentations to make sure everyone is putting their best foot forward.</p>
<p>Beyond the core audience of community professionals and leaders, both paid and volunteer, we treasure cross-pollination and encourage participation from people in other disciplines.</p>
<h4 id="container">Container Days</h4>
Organizers:
<ul>
<li>Josh Berkus</li>
<li>Chris Hoge</li>
<li>Melissa Logan</li>
</ul>
<p>ContainerDaysPDX has returned! Join us for two days of exploration of the latest generation of web and application infrastructure. We'll cover both the basics, and the newer and more esoteric aspects of orchestrated container stacks, including:</p>
<ul>
<li>Moving to containers and Kubernetes without losing your sanity</li>
<li>Desktop development for containerized applications</li>
<li>Developments in Linux: cGroupsv2, seccomp, and more</li>
<li>Containers on alternate platforms (FreeBSD, windows)</li>
<li>Container alternatives like WASM and microVMs</li>
<li>ML and data analysis in container clouds</li>
<li>Alternatives to Kubernetes</li>
<li>Security, networking, and performance for new stacks</li>
<li>Kubernetes + Openstack + OpenInfra: all the layers </li>
</ul>
<p>... and more! ContainerDays will bring exciting technical topics to Portland and FOSSYcon. It will cover not just what's available now, but what free software developers are working on for the future.</p>
<p>Whether you're just getting started with the new container stacks, or have been using Docker since 2014, whether you're an application developer, ops staff, or an infrastructure hacker, we plan to have something for you. </p>
<h4 id="copyleft">Copyleft and Compliance</h4>
<p>Participants from throughout the copyleft world — developers, strategists, enforcement organizations, scholars and critics — will be welcomed for an in-depth, high bandwidth, and expert-level discussion about the day-to-day details of using copyleft licensing, obstacles facing copyleft and the future of copyleft as a strategy to advance and defend software freedom for users and developers around the world.</p>
<h4 id="dei">Diversity Equity and Inclusion and FOSS</h4>
Organizers:
<ul>
<li>Aarti Ramkrishna</li>
<li>Anita Ihuman</li>
<li>Georg Link</li>
<li>Sri Ramkrishna</li>
</ul>
<p>Diversity, Equity, and inclusion are receiving increased attention in the FOSS community, the broader technology industry, and beyond. Since free and open software, hardware, and standards are made by people with very different backgrounds, beliefs, disabilities, nationalities, and identities, it is important to ensure access for these different groups and enable them to participate in a healthy way. This conference track provides a space to discuss diversity, equity, and inclusion challenges and solutions. We invite submissions from practitioners who share their own stories and what strategies they have tried to improve DEI, regardless of whether they succeeded or failed. We invite submission focused on DEI in FOSS, DEI beyond FOSS, and personal DEI experiences.</p>
<p>We look forward to providing a safe and welcoming space for highlighting DEI efforts and experiences from various perspectives, initiatives, and programs. We invite submissions from people who face systemic bias or discrimination in the technology industry of their country. We expressly invite submissions from women (both cis and trans), trans men, non-binary people, and gender queer people to apply. We further invite submissions from allies. </p>
<h4 id="daily-life">FOSS in Daily Life</h4>
Organizers:
<ul>
<li>SFC Staff</li>
</ul>
<p>How are you using FOSS in your "everyday" life? Are there places where you
find it's easier or harder to get the people around you to respect and
appreciate software freedom? What areas of software are we missing in our
pursuit of software freedom for all?</p>
<h4 id="play">FOSS at Play: Games, creative development, and open technology</h4>
Organizers:
<ul>
<li>Paris Buttfield-Addison</li>
<li>Stephen Jacobs</li>
</ul>
<p>The relationship between FOSS and Game Development is a multidisciplinary maze of creative, software, community, legal, and design issues that can very easily make your head spin. This track will help demystify the world of FOSS and Game Development, blending topics around the following pillars:</p>
<ul>
<li>FOSS game engines and tools</li>
<li>Legal or business implications of game development using FOSS</li>
<li>The history of FOSS in games and game development</li>
<li>Best practices in releasing your game as FOSS</li>
<li>FOSS support tools and communities for other games</li>
<li>Improving proprietary game engines with FOSS tooling</li>
<li>Open game hardware and peripherals</li>
<li>Community management and the differences between traditional FOSS communities and games communities</li>
<li>Finding, using, and releasing game assets (art, music, etc.) under free and open licenses</li>
<li>FOSS and board games</li>
</ul>
<p>Our audience is FOSS enthusiasts, software developers, designers, and creatives who are intrigued or interested in games, but are cautious to dive too deep, due to the overwhelmingly proprietary appearance of the industry. Games are nowhere near as proprietary as you may think, and this track will help usher in new users, contributors, and creators to the fantastic collection of FOSS tools, and encourage them to release new games, tools, and creative works.</p>
<h4 id="education">FOSS For Education</h4>
Organizers:
<ul>
<li>Martin Dougiamas, Moodle</li>
<li>Cable Green, Creative Commons</li>
<li>Patrick Masson, Apereo Foundation</li>
</ul>
<p>Educational institutions have a long and impactful history in the development of multiple open initiatives. In addition to free and open source software, colleges and universities have played significant roles in producing and propagating a variety of other open educational resources, for example, open content, textbooks and courses, open access journals, open data, science and research.</p>
<p>Institutions of higher education play an essential role across several free and open source communities. As adopters, campuses occupy a unique space in--and provide a unique perspective for--the use of free and open source software at the enterprise level, often in conjunction with government and research institutions. At the same time, campus constituencies--students, staff, and faculty--provide yet another perspective as independent desktop and mobile end users. </p>
<p>Higher education is also fertile ground for development; educating the next generation of developers while often actively creating and managing their own projects and communities of practice.</p>
<p>The FOSS For Education Community Track would provide sessions dedicated to using, developing, and managing open resources within academic environments, from multi-institutional consortia to departmental projects. The track organizers would emphasize presentations and topics highlighting the common principles, practices, benefits, challenges, and models spanning the variety of open initiatives impacting teaching and learning environments and campus administration.</p>
<h4 id="openwork">Issues in Open Work; Common Challenges and Best Practices in the Open Source Industry, Open Scholarship, and Government</h4>
Organizers:
<ul>
<li>Stephen Jacobs</li>
<li>Michael Nolan</li>
</ul>
<p>We hope to cover:</p>
<ul>
<li>Relevant changes in government policy surrounding open work</li>
<li>Metrics and Analytics across Open Work</li>
<li>Incentivizing organizations and employees to work in the Open</li>
<li>Best Practices in Community Management Across the fields</li>
<li>Government and Private Funders and Open Work</li>
<li>OSPOs in Academia and Governmen</li>
</ul>
<h4 id="ai-data">Open Source AI + Data</h4>
Organizers:
<ul>
<li>Ruth Suehle</li>
<li>Brian Proffitt</li>
</ul>
<p>Free and open source development has proven its criticality, popularity, and success as a method for bringing software to the world. As we forge into the next evolution of technology, led by data and AI, we must consider how to best apply the lessons of free and open source principles, governance, and development and vendor-neutral collaboration. The focus will no longer be on the underlying code, but about data and how we use and appropriately protect it. Weve already seen many successes in open data, but theres still much to do and growth to plan for. The open data ecosystem is vast, including models, tools, and of course, the data itself and how it is acquired, stored, trained, and used. Then, to come full circle, AI-powered tools are changing how software is written. What do licenses for data and models look like? Whose ethics become the ethics of the AI systems we will all eventually depend on? What are the coming security and privacy concerns? Will the systems of governance we understand in open source software change around AI projects?</p>
<h4 id="repair">Right to Repair</h4>
<p>There is significant overlap between the software freedom and right to repair movements. As we see more and more intersection in activism, legislation, and open technology, we hope to foster a more symbiotic relationship between the spaces. If you have expertise in software freedom and would like to apply that to right to repair issues, or vice versa, please submit your talk!</p>
<h4 id="science">FOSS Research for All: Science of Community</h4>
Organizers:
<ul>
<li>Kaylea Champion, Community Data Science Collective and the University of Washington</li>
<li>Molly de Blanc, Community Data Science Collective and Northwestern University</li>
<li>Benjamin Mako Hill, Community Data Science Collective and the University of Washington</li>
<li>Aaron Shaw, Community Data Science Collective and Northwestern University</li>
</ul>
<p>
Although there are literally hundreds of scholarly papers published about FOSS communities each year, much of this work never makes it out of academic journals and conferences and back to the FOSS communities being studied. At the same time, FOSS communities have a range of insights that researchers studying FOSS would benefit enormously from.
<br/>
The goal of this track is to build bridges between FOSS communities and the research conducted with and about FOSS communities. We hope to provide opportunities for community members to hear about exciting results from researchers, opportunities for researchers to learn from the FOSS community members, and spaces for the FOSS community to think together about how to improve FOSS projects by leveraging research insights and research.
<br/>
This track will include opportunities for:
<ol>
<li>researchers to talk with practitioners (about their research)</li>
<li>practitioners to talk with researchers (about their needs)</li>
<li> researchers to talk with other researchers (for learning and collaboration)</li>
</ol>
If this is appealing to you, please consider proposing, perhaps in one of the following formats:
<ul>
<li>Short Talks. Do you have a recent project to share in some depth? A topic that needs time to unpack? Take 20 minutes to present your thoughts.</li>
<li>Lightning Talks. Want to make a focused point, pitch, or problem report to a great audience? Bring your 5-minute talk to our lightning round.</li>
<li>Panelist. We will be facilitating dialogue between researchers and community members. Would you be willing to share your thoughts as a panelist? Let us know your expertise and a few notes on your perspective so that we can develop a diverse and engaging panel.</li>
</ul>
If you have an idea that doesn't fit into these formats, let's chat! You can reach out to Kaylea (kaylea@uw.edu) or submit your idea as a proposal via the form.<br/>
Submissions are non-archival, so we welcome ongoing, completed, and already published work. Non-archival means that presentation of work at FOSSY does not constitute a publication. It's just a way to get your work out there! Work that synthesizes or draws across a body of published papers is particularly welcome. <br/>
What kind of research are you looking to have presented? <br/>
We are interested in any topic related to FOSS research! This might include research from computing (including software engineering, computer security, social computing, HCI), the social sciences (including management, philosophy, law, economics, sociology, communication, and more), information sciences, and much more. <br/>
For example: how to identify undermaintained packages and what to do about it; community growth and how to find success in small communities; effective rule making and enforcement in online communities. <br/>
If it involves FOSS, we'd welcome it! We are eager to help you put your results into the hands of practitioners who can use your findings to inform their own community's practices and policies on social, governance, and technical topics. </p>
<br>
<h4 id="security">Security</h4>
Organizers
<ul>
<li>Kees Cook</li>
</ul>
<p>A track dedicated to FOSS security ideas and how reproducibility and audibility are important for software freedom. With increasing focus on the Software Supply Chain, focusing on the openness of free software will lead to better industry assurances that free software is the correct path.</p>
<h4 id="sfc-member-projects">SFC Member Projects</h4>
Organizers:
<ul>
<li>SFC Staff</li>
</ul>
<p>As a fiscal sponsor for a multitude of important and vital free software projects, Software Freedom Conservancy takes pride in providing alternatives to proprietary software, funding FOSS infrastructure and making sure important FOSS projects have a legal home. Join us to learn about what our projects are up to and how you can get involved.</p>
<h4 id="business">Sustainable Open Source Business</h4>
Organizers:
<ul>
<li>Matt Yonkovit</li>
<li>Avi Press</li>
</ul>
<p>We want to help maintainers, open source devs, and those looking to build a business around open source software build a sustainable community-focused business. We want to talk openly about concepts like funding, bootstrapping a business, ensuring you are doing it in a way that won't hurt the ecosystem, and how to grow and scale a business. We want to giving budding entrepreneurs the proper knowledge and tools to setup a business that will help their projects grow.</p>
<h4 id="xmpp">XMPP</h4>
Organizers:
<ul>
<li>Stephen Paul Weber 'singpolyma'</li>
<li>root</li>
</ul>
<p>XMPP is an extensible, foundational, and libre building block for any sort of federated communication infrastructure. Talks ranging from those new to the idea, setting up chat or social servers for small groups and families and other use cases, to those familiar with the issues such as SPAM and abuse prevention in a federated space, to technical deep dive talks about open source projects in the space and their innovations, would all be something worth covering in this track. We would strive to both appeal to the core XMPP audience and bring them to FOSSY, but also to introduce the projects and ideas to the rest of the FOSS community.</p>
<h4 id="wildcard">Wild card</h4>
Organizers:
<ul>
<li>SFC Staff</li>
</ul>
<p>For any talks that don't fit cleanly into the rest of the tracks. Don't be shy about putting it here if you don't know where it should go, we can always rearrange later!</p>
<h4 id="coops">Worker-Owner Co-ops that write and use FOSS</h4>
Organizers:
<ul>
<li>Valerie Young</li>
<li>Clayton Craft</li>
</ul>
<p>This community track will include speakers from worker-owned co-operatives that write or use FOSS. Topics will include which FOSS projects they use, their relationship with the organizations that produce the FOSS they use, their relationship with customers (if they produce FOSS), their co-op's history and structure, and more!</p>
</div>
</div>

View file

@ -165,50 +165,50 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 class="page-title">Sponsorship</h1>
<p>If you are interested in sponsoring our conference, please check out our <a href="https://sfconservancy.org/docs/Fossy-Prospectus.pdf">sponsorship prospectus</a>. We are looking for sponsors at a variety of levels, including a sponsor to help us create a fully free WiFi stack for all our attendees.</p>
<h3 id="redwood">Redwood</h3>
<a rel="nofollow" href="https://google.com"><img src="https://sfconservancy.org/img/sponsors/google.png" width="250" alt="logo of Google"></img></a>
</br>
</br>
<a rel="nofollow" href="https://arm.com"><img src="https://sfconservancy.org/img/sponsors/arm.png" alt="logo of ARM" width="250"></img></a>
</br>
</br>
<a rel="nofollow" href="https://intel.com"><img src="https://sfconservancy.org/img/sponsors/intel.png" alt="logo of intel" width="250"></img></a>
</br>
</br>
<a rel="nofollow" href="https://www.mozilla.org/foundation/"><img src="https://sfconservancy.org/img/sponsors/mozilla.png" alt="logo of Mozilla" width="250"></img></a>
<p>
</br>
</br>
<h4 id="coffee">Coffee</h4>
<a rel="nofollow" href="https://fossa.com"><img src="https://sfconservancy.org/img/sponsors/fossa.png" alt="logo of FOSSA" width="250"></img></a>
</br>
</br>
<a rel="nofollow" href="https://www.sakailms.org/"><img src="https://sfconservancy.org/img/sponsors/sakai.png" alt="logo of Sakai " width="250"></img></a>
<p>
</br>
</br>
<h4 id="Benefactors">Benefactors</h4>
<a rel="nofollow" href="https://sentry.io"><img src="https://sfconservancy.org/img/sponsors/sentry.png" alt="logo of Sentry" width="250"></img></a>
</br>
</br>
<a rel="nofollow" href="https://www.alliterativeadvising.com/"><img src="https://sfconservancy.org/img/sponsors/AlliterativeAdvisingLogo400.png" alt="logo of AlliterativeAdvising" width="400"></img></a>
</br>
</br>
<a rel="nofollow" href="https://redhat.com/"><img src="https://www.redhat.com/rhdc/managed-files/Asset-Red_Hat-Logo_page-Logo-RGB.svg" alt="logo of RedHat" width="250"></img></a>
</br>
</br>
<h4 id="Media">Media Sponsor</h4>
<a rel="nofollow" href="https://lwn.net"><img src="https://sfconservancy.org/img/sponsors/lwn.png" alt="logo of LWN" width="250"></img></a>
</br>
</br>
<h1 class="page-title">Sponsorship</h1>
<p>If you are interested in sponsoring our conference, please check out our <a href="https://sfconservancy.org/docs/Fossy-Prospectus.pdf">sponsorship prospectus</a>. We are looking for sponsors at a variety of levels, including a sponsor to help us create a fully free WiFi stack for all our attendees.</p>
<h3 id="redwood">Redwood</h3>
<a rel="nofollow" href="https://google.com"><img src="https://sfconservancy.org/img/sponsors/google.png" width="250" alt="logo of Google"></img></a>
</br>
</br>
<a rel="nofollow" href="https://arm.com"><img src="https://sfconservancy.org/img/sponsors/arm.png" alt="logo of ARM" width="250"></img></a>
</br>
</br>
<a rel="nofollow" href="https://intel.com"><img src="https://sfconservancy.org/img/sponsors/intel.png" alt="logo of intel" width="250"></img></a>
</br>
</br>
<a rel="nofollow" href="https://www.mozilla.org/foundation/"><img src="https://sfconservancy.org/img/sponsors/mozilla.png" alt="logo of Mozilla" width="250"></img></a>
<p>
</br>
</br>
<h4 id="coffee">Coffee</h4>
<a rel="nofollow" href="https://fossa.com"><img src="https://sfconservancy.org/img/sponsors/fossa.png" alt="logo of FOSSA" width="250"></img></a>
</br>
</br>
<a rel="nofollow" href="https://www.sakailms.org/"><img src="https://sfconservancy.org/img/sponsors/sakai.png" alt="logo of Sakai " width="250"></img></a>
<p>
</br>
</br>
<h4 id="Benefactors">Benefactors</h4>
<a rel="nofollow" href="https://sentry.io"><img src="https://sfconservancy.org/img/sponsors/sentry.png" alt="logo of Sentry" width="250"></img></a>
</br>
</br>
<a rel="nofollow" href="https://www.alliterativeadvising.com/"><img src="https://sfconservancy.org/img/sponsors/AlliterativeAdvisingLogo400.png" alt="logo of AlliterativeAdvising" width="400"></img></a>
</br>
</br>
<a rel="nofollow" href="https://redhat.com/"><img src="https://www.redhat.com/rhdc/managed-files/Asset-Red_Hat-Logo_page-Logo-RGB.svg" alt="logo of RedHat" width="250"></img></a>
</br>
</br>
<h4 id="Media">Media Sponsor</h4>
<a rel="nofollow" href="https://lwn.net"><img src="https://sfconservancy.org/img/sponsors/lwn.png" alt="logo of LWN" width="250"></img></a>
</br>
</br>
<a rel="nofollow" href="https://sustainoss.org/"><img src="https://sfconservancy.org/img/sponsors/sustainoss.png" alt="logo of SustainOSS" width="250"></img></a>
</div>
</div>

View file

@ -165,35 +165,35 @@
<div class="row">
<div class="col-12 content text-page" style="max-width: 45rem">
<h1 id="page-title">Travel and Lodging</h1>
<p>July is a fantastic time to visit the Pacific Northwest. Portland in the middle of July is a gorgeous city with plenty of greenery and a lack of humidity that will keep you comfortable. There is plenty of lodging around the city but we are contracting with the Hyatt across the street from the Oregon Convention Center to provide a block of rooms.</p>
<p>The Oregon Convention Center is a centrally located and easy to reach venue with plenty of space (and air conditioning!) for our conference. With accessible entrances and elevators, conveniently located for transit and walking.</p>
<p>777 NE Martin Luther King Jr Blvd, Portland, OR 97232</p>
<h4>Getting to and around Portland</h4>
<p>Portland International Airport (PDX) is a convenient and well connected airport that we assume most of our attendees will come through. It's also only a (very beautiful) 3 hour train ride to Seattle, so you could consider flying to SeaTac if you want to do some sight seeing.</p>
<p>Max/ TriMet - The Red Line Max connects from the airport to the Convention Center, very convenient. Local public transit is great and generally very safe and well timed. Let us know if you have any concerns or needs we can advise you on when using transit.</p>
<h4 id="hotels">Hotels</h4>
<p>There are 2 conference hotels, the Hyatt is across the street and the Kex is a short walk away. We've linked to the room block with group rate discount codes applied here, so please click the links if you are going to book with one of those hotels. If you have other lodging needs, Portland transit should be robust enough to get to and from where you need to be.</p>
<b><a href="https://www.hyatt.com/en-US/group-booking/PDXRP/G-SFCC">Hyatt Regency Portland</a></b> at the Oregon Convention Center<br/>
375 NE Holladay Street<br/>
Portland, Oregon 97232</p>
<p>We have a a group rates starting at $219 a night.</p>
<p id="kex"><b><a href="https://be.synxis.com/?adult=1&arrive=2023-07-12&chain=28097&child=0&currency=USD&depart=2023-07-16&hotel=30809&level=hotel&locale=en-US&promo=FOSSY23&rooms=1">Kex</a></b><br/>
100 NE Martin Luther King Jr Blvd<br/>
Portland, Oregon 97232</p>
<h1 id="page-title">Travel and Lodging</h1>
<p>July is a fantastic time to visit the Pacific Northwest. Portland in the middle of July is a gorgeous city with plenty of greenery and a lack of humidity that will keep you comfortable. There is plenty of lodging around the city but we are contracting with the Hyatt across the street from the Oregon Convention Center to provide a block of rooms.</p>
<p>The Oregon Convention Center is a centrally located and easy to reach venue with plenty of space (and air conditioning!) for our conference. With accessible entrances and elevators, conveniently located for transit and walking.</p>
<p>777 NE Martin Luther King Jr Blvd, Portland, OR 97232</p>
<h4>Getting to and around Portland</h4>
<p>Portland International Airport (PDX) is a convenient and well connected airport that we assume most of our attendees will come through. It's also only a (very beautiful) 3 hour train ride to Seattle, so you could consider flying to SeaTac if you want to do some sight seeing.</p>
<p>Max/ TriMet - The Red Line Max connects from the airport to the Convention Center, very convenient. Local public transit is great and generally very safe and well timed. Let us know if you have any concerns or needs we can advise you on when using transit.</p>
<h4 id="hotels">Hotels</h4>
<p>There are 2 conference hotels, the Hyatt is across the street and the Kex is a short walk away. We've linked to the room block with group rate discount codes applied here, so please click the links if you are going to book with one of those hotels. If you have other lodging needs, Portland transit should be robust enough to get to and from where you need to be.</p>
<b><a href="https://www.hyatt.com/en-US/group-booking/PDXRP/G-SFCC">Hyatt Regency Portland</a></b> at the Oregon Convention Center<br/>
375 NE Holladay Street<br/>
Portland, Oregon 97232</p>
<p>We have a a group rates starting at $219 a night.</p>
<p id="kex"><b><a href="https://be.synxis.com/?adult=1&arrive=2023-07-12&chain=28097&child=0&currency=USD&depart=2023-07-16&hotel=30809&level=hotel&locale=en-US&promo=FOSSY23&rooms=1">Kex</a></b><br/>
100 NE Martin Luther King Jr Blvd<br/>
Portland, Oregon 97232</p>
<p>Our promo code <b>FOSSY23</b> is a 20% discount to any private room. There are also shared bunk spaces available without the coupon code as the rate is quite low already. Rates for a bunk room start at $50 and singles start at $179 a night.</p>
</div>
</div>