Ben Sturmfels
e15fd51e3b
Ran: wget --mirror --convert-links --adjust-extension --page-requisites --no-parent https://2024.fossy.us/
2546 lines
120 KiB
Text
2546 lines
120 KiB
Text
BEGIN:VCALENDAR
|
||
VERSION:2.0
|
||
PRODID:-//2024.fossy.us/schedule//EN
|
||
CALSCALE:GREGORIAN
|
||
METHOD:PUBLISH
|
||
X-WR-CALDESC:FOSSY 2024
|
||
X-WR-TIMEZONE:US/Pacific
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Coffee/tea break
|
||
DTSTART;TZID=US/Pacific:20240804T091500
|
||
DTEND;TZID=US/Pacific:20240804T094500
|
||
DTSTAMP:20240723T165415Z
|
||
UID:234@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Breakfast and coffee break
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Coffee/tea break
|
||
DTSTART;TZID=US/Pacific:20240802T091500
|
||
DTEND;TZID=US/Pacific:20240802T094500
|
||
DTSTAMP:20240723T165415Z
|
||
UID:232@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Breakfast and coffee break
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Coffee/tea break
|
||
DTSTART;TZID=US/Pacific:20240803T091500
|
||
DTEND;TZID=US/Pacific:20240803T094500
|
||
DTSTAMP:20240723T165415Z
|
||
UID:233@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Breakfast and coffee break
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Keynote Session
|
||
DTSTART;TZID=US/Pacific:20240804T094500
|
||
DTEND;TZID=US/Pacific:20240804T103000
|
||
DTSTAMP:20240723T165415Z
|
||
UID:231@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Keynote Session: Corporations and FOSS
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240803T094500
|
||
DTEND;TZID=US/Pacific:20240803T103000
|
||
DTSTAMP:20240723T165415Z
|
||
UID:230@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Keynote Panel: Open Source and AI
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:20+ years of the OSU Open Source Lab
|
||
DTSTART;TZID=US/Pacific:20240802T094500
|
||
DTEND;TZID=US/Pacific:20240802T103000
|
||
DTSTAMP:20240723T165415Z
|
||
UID:229@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Lance Albertson\nThe OSU Open Source Lab is a free ve
|
||
ndor-neutral colocation hosting facility that provides a variety of hostin
|
||
g services for FOSS projects from around the world since 2003. This sessio
|
||
n will cover the current status of what the lab has been up to and other n
|
||
ew services we’re planning on releasing soon. Some of the interesting te
|
||
chnologies we’ve been working with include OpenStack\, OpenPOWER\, ARM64
|
||
\, RISC-V\, Ceph storage and Chef to name a few.\n\nIf you’ve ever wonde
|
||
red about all the services we provide and what we do\, this is the session
|
||
for you. We’ve been improving our services quite a bit and also have be
|
||
en expanding on a few other fronts as well. In addition\, we’ll cover ho
|
||
w we hire and mentor students who work at the lab and where they end up af
|
||
ter graduating. In addition\, we’ll cover some other ways we try and men
|
||
tor other students beyond those who work at the lab.
|
||
URL:http://2024.fossy.us/schedule/presentation/274/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Registration
|
||
DTSTART;TZID=US/Pacific:20240801T101500
|
||
DTEND;TZID=US/Pacific:20240801T131500
|
||
DTSTAMP:20240723T165415Z
|
||
UID:239@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Registration Open
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:From Data to Action: Using Metrics to Improve FOSS Communities
|
||
DTSTART;TZID=US/Pacific:20240802T104500
|
||
DTEND;TZID=US/Pacific:20240802T113000
|
||
DTSTAMP:20240723T165415Z
|
||
UID:327@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Dawn Foster\nSustaining FOSS projects and communities
|
||
over the long-term can be a challenge. Project leaders and contributors a
|
||
re busy people who don’t always have the time or experience to focus on
|
||
growing a community and maintaining their software. Using metrics is one w
|
||
ay to help FOSS projects identify potential issues and identify areas wher
|
||
e they can improve their community to make it more sustainable over the lo
|
||
ng-term. Being proactive about improving sustainability before it becomes
|
||
a crisis can help make our software more sustainable and reliable for all
|
||
of us. However\, not everyone has the experience or skills required to kno
|
||
w how to interpret their metrics and use what they learn to make improveme
|
||
nts within their community.\n\nThe CHAOSS project has been creating a seri
|
||
es of MIT licensed Practitioner Guides focused on helping bridge the gap b
|
||
etween research and practice to improve the sustainability of our software
|
||
and communities. The guides are designed to make it easier for people to
|
||
draw meaningful and actionable insights using community metrics\, even whe
|
||
n those people do not necessarily have a deep background in data analysis
|
||
or much experience working within FOSS communities.\n\nThis talk will iden
|
||
tify several categories of metrics from the Practitioner Guide Series (e.g
|
||
.\, responsiveness\, contributor sustainability\, organizational participa
|
||
tion)\, discuss how to interpret the metrics\, and provide ideas for impro
|
||
ving in areas identified using the metrics. The audience will walk away wi
|
||
th a better understanding of how to use metrics to proactively improve the
|
||
long-term sustainability of their FOSS projects and communities.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/253/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240802T104500
|
||
DTEND;TZID=US/Pacific:20240802T113000
|
||
DTSTAMP:20240723T165415Z
|
||
UID:297@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Steadfast Self-Hosting Workshop
|
||
DTSTART;TZID=US/Pacific:20240803T104500
|
||
DTEND;TZID=US/Pacific:20240803T113000
|
||
DTSTAMP:20240723T165415Z
|
||
UID:338@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Adam Monsen\nJoin in a hands-on workshop all about se
|
||
lf-hosting! Bring your experiences and curiosity\, leave with inspiration
|
||
and ideas to try out. Together we'll help each other get unblocked whereve
|
||
r we're at\, from thinking about self-hosting to improving smooth-running
|
||
servers and services. This workshop will focus on fundamental concepts\, t
|
||
ools\, and techniques from the FOSS book Steadfast Self-Hosting\, although
|
||
having and having read the book is not required.
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us/schedule/presentation/219/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240804T104500
|
||
DTEND;TZID=US/Pacific:20240804T113000
|
||
DTSTAMP:20240723T165415Z
|
||
UID:374@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240803T104500
|
||
DTEND;TZID=US/Pacific:20240803T113000
|
||
DTSTAMP:20240723T165415Z
|
||
UID:347@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Open source training for reproducibility\, collaboration\, and com
|
||
munity in academic research
|
||
DTSTART;TZID=US/Pacific:20240802T104500
|
||
DTEND;TZID=US/Pacific:20240802T113000
|
||
DTSTAMP:20240723T165415Z
|
||
UID:307@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Alex Marden\nResearch-focused data and software train
|
||
ing outside of the standard academic curriculum can play a crucial role in
|
||
university environments. Reproducibility and collaboration are fundamenta
|
||
l aspects of research\, creating an opportunity to incorporate open source
|
||
software development strategies and techniques into training workshops.\n
|
||
\nThe University of Texas at Austin Open Source Program Office (UT-OSPO) h
|
||
as co-sponsored numerous workshops that emphasize the interplay among open
|
||
source software\, reproducibility\, and collaboration. A key focus is eng
|
||
aging researchers across diverse use-case scenarios along the open source
|
||
participation pathway – from introducing participants to the benefits of
|
||
using open source software to managing collaborative open source software
|
||
ecosystems.\n\nThis session will explore the UT-OSPO’s cross-department
|
||
al initiative\, integrating open source software training into research wo
|
||
rkshops and events. We will discuss pedagogical and administrative strateg
|
||
ies for appealing to a wide range of researchers and fostering an open sou
|
||
rce community within a large university.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/204/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Things I've Learned as a Linux Kernel Maintainer
|
||
DTSTART;TZID=US/Pacific:20240803T104500
|
||
DTEND;TZID=US/Pacific:20240803T113000
|
||
DTSTAMP:20240723T165415Z
|
||
UID:331@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Darrick J. Wong\nI spent seven years serving as the m
|
||
aintainer of the XFS filesystem and iomap filesystem library in the Linux
|
||
kernel. Whilst on that journey\, I learned a lot about steering technical
|
||
direction of those two projects\, but also the limitations of managing a
|
||
community without authority. I intend this talk to be most helpful for pe
|
||
ople who are current FOSS maintainers or are mid to senior level developer
|
||
s contemplating taking on such roles.\n\nThese are the six skills that I f
|
||
ound most helpful and grew the most in those seven years:\n * Concocting a
|
||
strategy from which to build a development roadmap\n * Defining roles for
|
||
people to take on\n * Negotiating staffing and budgets with managers\n *
|
||
Coaching people who are trying to get their efforts across the finish line
|
||
\n * Dealing with external shocks in as principled a manner as possible\n
|
||
* Steering your way out of burnout\, aka Replacing Yourself\n\nFor each of
|
||
these areas\, I'll share how that skill fits into the Linux community (th
|
||
ey didn't always fit well!) and what happened when I tried to make things
|
||
happen in those areas. I will target spending about 4-5 minutes talking a
|
||
bout each of those points and leave 20-25 minutes at the end for an audien
|
||
ce discussion.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/246/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Thinking Beyond 0's and 1's
|
||
DTSTART;TZID=US/Pacific:20240803T104500
|
||
DTEND;TZID=US/Pacific:20240803T113000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:353@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Nisha Kumar\nOpen Source won. We see it in the large
|
||
number of software projects created and used by other software projects. M
|
||
ost of our modern day software\, including AI\, runs on a large number of
|
||
open source software projects. Working in a cloud company that produces an
|
||
d deploys software at scale\, I see a lot of phenomenon that look very muc
|
||
h like what I used to see when I worked in semiconductor manufacturing an
|
||
age ago. Examples of these are drift from the norm\, heisenbugs\, emergent
|
||
properties\, and just ¯\\_(ツ)_/¯ things.\n\nThe physical world is ful
|
||
l of these types of phenomenon. We deal with it by using probability and s
|
||
tatistics - accepting that we can't give a "true" or "false" answer\, but
|
||
settling for a continuous "maybe". This is a talk about looking at softwar
|
||
e production at a larger scale than just the single artisanal "app". We wi
|
||
ll apply probability and statistics to open source software at scale\, and
|
||
use some "Machine Learning" to get some insights into how the single app
|
||
is the product of\, and part of a somewhat unknowable whole.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/266/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:A truly community-based Open Source LLM and what it can do for you
|
||
r business and the open community
|
||
DTSTART;TZID=US/Pacific:20240804T104500
|
||
DTEND;TZID=US/Pacific:20240804T113000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:360@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: JJ Asghar\nWhat if I told you the way we're distribut
|
||
ing AI models is fundamentally broken? The majority of people out there le
|
||
verage the ChatGPTs of the world and just ask it for some simple tasks le
|
||
veraging Prompt Engineering. That's all well and good\, but when you want
|
||
to bring AI into your business processes\, do you really want to give your
|
||
secret sauce to another company to train their own models? Probably not.\
|
||
n\nBuilt by IBM and Red Hat from the get-go\, InstructLab is an open sourc
|
||
e project that lets you stay in control of your AI by creating some easy-t
|
||
o-use tuning for a base model. Today we’ll talk about what it can do for
|
||
you as an engineer and how much it can do to improve your business proces
|
||
ses. If you’re thinking that you need a trusted AI system that’s truly
|
||
open source and lets you track back what is put into the tuned data set\,
|
||
we’ve got you covered.\n\nThis talk will prime you to be able to check
|
||
it out and learn to use it in 45 minutes or less. \nKeeping you in complet
|
||
e control of your AI story code\, and making sure your company knowledge i
|
||
s in a place that you find secure.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/238/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:An ideal education with Open Source\, a Recent Grad's Perspective.
|
||
DTSTART;TZID=US/Pacific:20240803T104500
|
||
DTEND;TZID=US/Pacific:20240803T113000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:314@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Onexi\nThe open source world is one filled with oppor
|
||
tunity\, for collaboration\, for learning\, and brimming with experiences.
|
||
It allows for ideas and communities to come about regardless of backgroun
|
||
d\, for the sake of a common goal. If only I knew about it sooner. I learn
|
||
ed of open source in my last semester of college\, and I believe it can tr
|
||
ansform our education as it is now.\n\nLet’s propose a thought experimen
|
||
t. Suppose that you are back in college and open source is a widespread co
|
||
ncept in education\, not as it is right now\, but as widely known as the i
|
||
dea of internships\, for example. Opportunities for open source projects w
|
||
ould exist for every discipline\, allowing for the collaboration among stu
|
||
dents from art\, literature\, business\, engineering\, and more. Open sour
|
||
ce would be more diverse\, allowing for other disciplines to pick up the w
|
||
ork where another may falter. A developer might be too clear cut to write
|
||
out friendly documentation for newcomers to a project\, and a writer might
|
||
be too non-technical to explain certain technologies in depth\, but both
|
||
people collaborating could create great documentation. If it sounds famili
|
||
ar in any way\, it is essentially how people work in the real world\, at a
|
||
company. Meaning\, that if you had open source in your education you coul
|
||
d adapt to working with other disciplines that are not studying the same t
|
||
hing as you\, on a project that can have a real world impact.\n\nCollege s
|
||
tudents would trick themselves into creating their own company\, a pseudo
|
||
startup. Many ideas flourish in young minds\, but never come to fruition\,
|
||
maybe due to lack of resources\, or not having the right people around. A
|
||
lot of times\, given a lack of knowledge\, or the overwhelming feeling of
|
||
doing lots of work that could have no impact\, they never see the light.
|
||
College is a place filled with diversity of knowledge and experiences\, li
|
||
ke open source. If a school club existed which allowed any major to join\,
|
||
bundle together\, and create an open source project of their choosing whi
|
||
le leaving each student a piece of the puzzle to fulfill\, it would essent
|
||
ially have the same structure as a real company\, more or less. Think abou
|
||
t the many app/company ideas that have crossed your mind. Would you have t
|
||
ried to make them if you had open source? \n\nStudents can experience the
|
||
real world and create a real project\, from the comfort of their home. Peo
|
||
ple have different circumstances\, and many students fail to gain experien
|
||
ce in their field right out of college. Whether it be personal circumstanc
|
||
es\, failing to get chosen for internships\, or not having the time to do
|
||
extracurriculars\, there are many reasons why students fail to learn what
|
||
real world work is like. Open source projects would allow a student to app
|
||
ly their skills regardless of time frame or location\, given that they hav
|
||
e a laptop on hand. Moreover\, these skills can be directly applicable int
|
||
o the real world\, as you work with people with different backgrounds towa
|
||
rds a common goal.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/205/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Co-Designing Sustainable Prosocial Digital Infrastructure
|
||
DTSTART;TZID=US/Pacific:20240804T104500
|
||
DTEND;TZID=US/Pacific:20240804T113000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:364@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: LX Cast\nTo build social tech infrastructure that sup
|
||
ports our collective well-being\, we need to include decentralized\, open
|
||
source\, and slow-growth options. However\, these approaches have historic
|
||
ally fallen outside traditional tech funding mechanisms. \n\nTech that sup
|
||
ports collective well-being should meet real needs\, solve real problems\,
|
||
be usable\, and be purpose-built\, not seeing people as an exploitable re
|
||
source or means to extract. So how can projects like these be sustainable\
|
||
, secure\, and built in collaboration with communities? We think that peop
|
||
le putting money into projects should be part of the project design team\,
|
||
so that their expertise\, experience\, and motivations can be both repres
|
||
ented and explicitly weighed in the context of the problem the technology
|
||
hopes to solve. \n\nIn other words\, we need to co-design our financial mo
|
||
dels to find strategies that support the holistic goals of the makers\, co
|
||
mmunity\, and capital suppliers. In this workshop\, we will explore some o
|
||
f the mechanisms that might lead to co-design frameworks\, and surface str
|
||
ategies from participants. We will learn from one another what has worked
|
||
and what hasn’t\, and re-imagine how people putting money into FOSS migh
|
||
t be collaborators with us and the communities we’re designing and build
|
||
ing with.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/223/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240804T104500
|
||
DTEND;TZID=US/Pacific:20240804T113000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:369@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:News Flash! You Are Enough. Let's Talk About Amplifying Your Value
|
||
& Authenticiy
|
||
DTSTART;TZID=US/Pacific:20240804T104500
|
||
DTEND;TZID=US/Pacific:20240804T113000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:345@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Shannon Rasimas\nHaving talked with 100's of people a
|
||
bout their careers\, whether it be a transition into something new or grow
|
||
th from within\, the default seems to be to focus on what you don't know o
|
||
r who you need to morph into to get to where you want to go. You don't nee
|
||
d to learn 5 new languages\, refactor all your code\, earn 3 new skills\,
|
||
and build 2 websites and an API to show you are good enough. Guess what\,
|
||
you already are enough. You also don't need to transform yourself into so
|
||
mebody you think you should be in order to fit in or find acceptance. You
|
||
are amazing just as you are. This is all hard work looking a little more d
|
||
eeply at ourselves\, but let's find strategies to elevate the way we think
|
||
and talk about ourselves\, connect to our why\, and be comfortable sharin
|
||
g the true essence of who we are. In a time where loneliness is at an all
|
||
time high\, how can we also build meaningful community and create spaces\,
|
||
interview practices\, and culture for everyone to find safety in bringing
|
||
their authentic selves\, connect to purpose\, and be valued. And finally\
|
||
, why are we doing any of this if we can't find the joy in it. This talk i
|
||
s meant to inspire you to tap into the leadership qualities and value you
|
||
already have instead of focusing on the deficits\, and for all of us\, esp
|
||
ecially those with the power to do so\, to start building better spaces fo
|
||
r for all of us to exist in and start creating better community all around
|
||
. We all can use a little more belonging these days.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/244/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FreeBSD on ARM64
|
||
DTSTART;TZID=US/Pacific:20240802T104500
|
||
DTEND;TZID=US/Pacific:20240802T113000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:285@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Michael Dexter\nFreeBSD is a compelling operating sys
|
||
tem for the ARM64 platform with its recent addition of bhyve ("beehive") h
|
||
ypervisor support and its traditional tightly-integrated features includin
|
||
g OpenZFS\, Jail\, DTrace\, Packet Filter\, and pkg.\n\nThis talk will pro
|
||
vide an authoritative introduction to FreeBSD features and uses with a foc
|
||
us on the ARM64 platform.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/194/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Why FOSS Must Be Discrimination Free
|
||
DTSTART;TZID=US/Pacific:20240802T104500
|
||
DTEND;TZID=US/Pacific:20240802T113000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:291@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Josh Berkus\nWhy are the non-discriminatory clauses (
|
||
5 and 6) part of the Open Source Definition? Why does anyone care? Why s
|
||
houldn't project owners be able to limit where the software can be used or
|
||
prevent bad people from using the software?\n\nThese two clauses are the
|
||
most poorly understood parts of the Open Source Definition\, and the ones
|
||
that would-be license writers most frequently want to compromise. They ar
|
||
e not a moral requirement\; instead\, they are compulsive in order to sust
|
||
ain how FOSS is packaged\, distributed\, and used. An Open Source Initiat
|
||
ive board member will explain\, in developer-friendly terms\, why you shou
|
||
ld care about OSD5 and OSD6.\n\nAttendees will learn why to retain these f
|
||
reedoms in their own license-writing\, and why the are important when cons
|
||
uming other people's projects.
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us/schedule/presentation/263/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Break
|
||
DTSTART;TZID=US/Pacific:20240804T113000
|
||
DTEND;TZID=US/Pacific:20240804T114500
|
||
DTSTAMP:20240723T165416Z
|
||
UID:271@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Break
|
||
DTSTART;TZID=US/Pacific:20240802T113000
|
||
DTEND;TZID=US/Pacific:20240802T114500
|
||
DTSTAMP:20240723T165416Z
|
||
UID:269@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Break
|
||
DTSTART;TZID=US/Pacific:20240803T113000
|
||
DTEND;TZID=US/Pacific:20240803T114500
|
||
DTSTAMP:20240723T165416Z
|
||
UID:270@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Workshop: Developing Your First Nextcloud App
|
||
DTSTART;TZID=US/Pacific:20240803T114500
|
||
DTEND;TZID=US/Pacific:20240803T123000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:354@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Edward Ly\nNextcloud is an on-premises\, free softwar
|
||
e alternative to Google \nWorkspace and Microsoft 365 that puts user data
|
||
back into the hands of \nthe people. Whether it be getting a handle on you
|
||
r photos\, your budget\, \nor your recipe collection\, Nextcloud is your o
|
||
ne-stop solution for \nde-Googling your digital life. But as much as the a
|
||
pp ecosystem may have \ngrown since Nextcloud was founded in 2016\, it is
|
||
impossible to cover the \nunique needs of every single user. That is why N
|
||
extcloud offers you the \nbasics upon which you can build your own app. In
|
||
this workshop\, we will \ndemonstrate how you can quickly get started dev
|
||
eloping your first \nNextcloud app.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/273/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240803T114500
|
||
DTEND;TZID=US/Pacific:20240803T123000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:326@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240802T114500
|
||
DTEND;TZID=US/Pacific:20240802T123000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:292@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Maps as Art using FOSS
|
||
DTSTART;TZID=US/Pacific:20240803T114500
|
||
DTEND;TZID=US/Pacific:20240803T123000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:337@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Tracy Homer\nTracy will show several different artist
|
||
ic maps she has made\, and go through the different software tools used to
|
||
make them. She will discuss what datasets and formats work for each type
|
||
of map and how you can make your own artistic maps using freely licensed s
|
||
oftware.
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us/schedule/presentation/187/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240804T114500
|
||
DTEND;TZID=US/Pacific:20240804T123000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:370@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240804T114500
|
||
DTEND;TZID=US/Pacific:20240804T123000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:375@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Development of a Nation-wide Research Data Management Platform Le
|
||
veraged by Open Science Framework
|
||
DTSTART;TZID=US/Pacific:20240803T114500
|
||
DTEND;TZID=US/Pacific:20240803T123000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:306@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Shoji Kajita\nThis session shares our experiences on
|
||
a nation-wide Research Data Management (RDM) platform in Japan by using Op
|
||
en Science Framework developed by Center for Open Science in U.S.A. The su
|
||
rrounding contexts of RDM like Open Science and Research Integrity have be
|
||
en quickly changing and the supporting technologies of RDM have been drama
|
||
tically changing due to the speed of Dog Year for digital technologies. To
|
||
tackle these situations\, National Institute of Infomatics (NII) has been
|
||
developing and operating a nation-wide RDM platform "Gakunin RDM" for the
|
||
entire Japanese higher educational institutions. Currently over 100 insti
|
||
tutions have been using Gakunin RDM since 2022. Through the course\, sever
|
||
al challenges are emerging due to the major customizations requested by in
|
||
stitutional users. These are common to any Open Source projects. In this t
|
||
alk\, we will introduce the challenges by the following three parts:\n1. W
|
||
hat is Open Science Framework\n2. Current status of Gakunin RDM\n3. Curren
|
||
t major challenges
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/206/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240802T114500
|
||
DTEND;TZID=US/Pacific:20240802T123000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:305@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Java Performance on ARM64 and Ampere
|
||
DTSTART;TZID=US/Pacific:20240802T114500
|
||
DTEND;TZID=US/Pacific:20240802T123000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:286@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Mikael Vidstedt\nFor close to three decades the Java
|
||
technology stack has been powering the world\, running everything from edg
|
||
e device to enterprise server-side workloads. The Java Platform Group at O
|
||
racle is heavily investing in ARM64\, working closely with Ampere to ensur
|
||
e that current and future applications run securely and with high performa
|
||
nce. In addition to designing and implementing new features to leverage th
|
||
e natural strengths of the hardware\, the team has also delivered a long l
|
||
ist of performance enhancements to future and existing versions of Java th
|
||
rough OpenJDK. This session will cover key projects and features in the Ja
|
||
va platform\, how they relate to ARM64\, and showcase the performance impr
|
||
ovements they have resulted in.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/193/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:How to Chart your own Career Path in Open Source - A Panel Discuss
|
||
ion
|
||
DTSTART;TZID=US/Pacific:20240802T114500
|
||
DTEND;TZID=US/Pacific:20240802T123000
|
||
DTSTAMP:20240723T165416Z
|
||
UID:298@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Ray Paik\nThere isn’t one way to build your career
|
||
in open source as there are a variety of roles beyond writing code and man
|
||
y different routes into those roles. It’s also important for individuals
|
||
to chart their own path that aligns with their unique experience and inte
|
||
rest.\n\nIn this panel discussion\, panelists will share how they got star
|
||
ted in their career and their journey over the past two decades. For peopl
|
||
e looking for jobs in open source\, we’ll discuss what we look for in ca
|
||
ndidates and why it’s not necessary to check all the boxes in job descri
|
||
ptions. We’ll also discuss challenges in balancing your day jobs vs. ope
|
||
n source activities during your career.\n\nIn addition\, we’ll also delv
|
||
e into other challenges and opportunities of an open source career that ra
|
||
nge from dealing with the impostor syndrome\, DEI (Diversity\, Equity\, an
|
||
d Inclusion) challenges\, exploring open source communities for self growt
|
||
h\, and more.\n\nThe goal of this session is to help attendees feel more c
|
||
omfortable exploring opportunities in open source and be confident in char
|
||
ting their own path. Our panel members will share what contributed to thei
|
||
r success and the lessons learned throughout their extensive experience in
|
||
open source. This session is meant to be interactive\, and we’ll encour
|
||
age attendees to ask questions and engage in the conversation.
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us/schedule/presentation/224/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Getting ML Right in a Complex Data World
|
||
DTSTART;TZID=US/Pacific:20240804T114500
|
||
DTEND;TZID=US/Pacific:20240804T123000
|
||
DTSTAMP:20240723T165417Z
|
||
UID:361@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Oz Katz\nMachine learning workflows are iterative & r
|
||
epetitive to and from multiple steps including data labeling\, data clean
|
||
ing\, preprocessing and feature selection methods during model training\,
|
||
just to arrive at an accurate model.\n\nQuality ML at scale is only possib
|
||
le when we can reproduce a specific iteration of the ML experiment–and t
|
||
his is where data is key. This means: capturing the version of training da
|
||
ta\, ML code and model artifacts at each iteration is mandatory. However\,
|
||
to efficiently version ML experiments without duplicating code\, data and
|
||
models\, data versioning tools are required. Open source tools like lakeF
|
||
S make it possible to version all components of ML experiments without the
|
||
need to keep multiple copies\, and as an added benefit\, save you storage
|
||
costs as well.\n\nIn this talk\, you will learn how to use a data version
|
||
ing engine to intuitively and easily version your ML experiments and repro
|
||
duce any specific iteration of the experiment.\n\nThis talk will demo thro
|
||
ugh a live code example:\n• Creating a basic ML experimentation framewor
|
||
k with lakeFS (on Jupyter notebook)\n• Reproducing ML components from a
|
||
specific iteration of an experiment\n• Building intuitive\, zero-mainten
|
||
ance experiments infrastructure\n\nAll with common OSS data engineering st
|
||
acks & open source tooling.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/237/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:How do FOSS projects actually use new README documents?
|
||
DTSTART;TZID=US/Pacific:20240802T114500
|
||
DTEND;TZID=US/Pacific:20240802T123000
|
||
DTSTAMP:20240723T165417Z
|
||
UID:325@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Matt Gaughan\nWithout safeguards or redundancies\, FO
|
||
SS maintainers can find themselves unsupported in the upkeep of projects\;
|
||
this can concentrate risk\, jeopardizing project health and software secu
|
||
rity. The suggestions for better community governance are often the same:
|
||
grow documentation\, recruit new maintainers\, expand what it means to be
|
||
a contributor. But does this common advice actually work? What impact do
|
||
these prescriptions actually have in growing the project's maintainer comm
|
||
unity?\n\nStudying over 2\,000 FOSS projects packaged in the Debian distri
|
||
bution\, we test how the popular recommendations of publishing README and
|
||
CONTRIBUTING files actually impact project contribution activity and the r
|
||
ecruitment of maintainers. Our work finds that\, contrary to popular recom
|
||
mendations\, governance files are often newly published in response to inc
|
||
reased project activity and that the benefit of this new documentation is
|
||
not always immediate. Further descriptive analysis of initial governance d
|
||
ocuments show a wide range of content and forms across projects as communi
|
||
ties adopt standards and formats from different traditions. \n\nIn this ta
|
||
lk\, we will discuss our results and what they might mean for maintainers.
|
||
We hope that maintainers will share their own experiences around communi
|
||
ty governance\, project documentation\, and FOSS evolution. Our empirical
|
||
results are the starting point of a community conversation around the util
|
||
ity of governance files and how projects can better employ these documents
|
||
for project health\; we look forward to this talk opening a broader discu
|
||
ssion about project organization and presentation.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/254/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240803T114500
|
||
DTEND;TZID=US/Pacific:20240803T123000
|
||
DTSTAMP:20240723T165417Z
|
||
UID:348@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Making new tools for open source graphics software
|
||
DTSTART;TZID=US/Pacific:20240804T114500
|
||
DTEND;TZID=US/Pacific:20240804T121500
|
||
DTSTAMP:20240723T165417Z
|
||
UID:344@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Tom Lechner\nLet's discuss various ways that tools su
|
||
ch as Godot\, Blender\, Inkscape\, and Krita let you extend them\, such as
|
||
non-destructive procedural generation from Blender's Geometry Nodes\, cus
|
||
tom utilities with Inkscape extensions\, or hacking right in source code f
|
||
or crazier things. We will also talk about the importance of open standard
|
||
s for art resources\, to be able to share resources across different softw
|
||
are that might otherwise have very different internals and purposes.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/242/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:The State of FOSS Funding
|
||
DTSTART;TZID=US/Pacific:20240804T114500
|
||
DTEND;TZID=US/Pacific:20240804T123000
|
||
DTSTAMP:20240723T165417Z
|
||
UID:365@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Kara Sowles\nJoin me in taking a look at the current
|
||
state of free and open source software funding\, what the potential paths
|
||
to financial sustainability currently look like for maintainers\, and what
|
||
new models are being explored. \n\n- What options do projects have when l
|
||
ooking to be financially sustainable long-term?\n- What organizations are
|
||
funding free and open source software\, and how do they allocate it?\n- Wh
|
||
at does it looks like to have funding that isn't subject to unstable corpo
|
||
rate budgets and interests? \n- What’s missing from our current models o
|
||
f funding? \n\nI’ll include info from some of the top Open Source Progra
|
||
m Offices currently funding corporate dependencies\; government-funded ini
|
||
tiatives aimed at sustaining digital public goods we all rely on\; and use
|
||
r-sustained projects that rely on the goodwill of individuals. We’ll tou
|
||
ch on what place Accelerators and Grants have in this\, and peeling away t
|
||
he growth-curve expectations from investors who may\, or may not\, underst
|
||
and the needs of free and open source. \n\nIt's essential we ask ourselves
|
||
: how do we ensure the software our societies depend on is sustainable lon
|
||
g-term?
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/222/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Lunch break
|
||
DTSTART;TZID=US/Pacific:20240802T123000
|
||
DTEND;TZID=US/Pacific:20240802T140000
|
||
DTSTAMP:20240723T165417Z
|
||
UID:224@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:<em>Lunch</em>
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Lunch break
|
||
DTSTART;TZID=US/Pacific:20240803T123000
|
||
DTEND;TZID=US/Pacific:20240803T140000
|
||
DTSTAMP:20240723T165417Z
|
||
UID:225@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:<em>Lunch</em>
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Lunch break
|
||
DTSTART;TZID=US/Pacific:20240804T123000
|
||
DTEND;TZID=US/Pacific:20240804T140000
|
||
DTSTAMP:20240723T165417Z
|
||
UID:226@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:<em>Lunch</em>
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Opening Remarks
|
||
DTSTART;TZID=US/Pacific:20240801T134500
|
||
DTEND;TZID=US/Pacific:20240801T140000
|
||
DTSTAMP:20240723T165417Z
|
||
UID:227@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Opening Remarks
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240801T140000
|
||
DTEND;TZID=US/Pacific:20240801T144500
|
||
DTSTAMP:20240723T165417Z
|
||
UID:315@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Your FOSS Productive Life! - The Vibrant Ecosystem around Applicat
|
||
ions
|
||
DTSTART;TZID=US/Pacific:20240803T140000
|
||
DTEND;TZID=US/Pacific:20240803T144500
|
||
DTSTAMP:20240723T165417Z
|
||
UID:339@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Sriram Ramkrishna\nFree and Open Source Software ecos
|
||
ystems evolve in curious ways. In the beginning\, when we thought about op
|
||
en source software\, we limited ourselves to applying it to the desktop an
|
||
d the web. \n\nKernel\, user-space\, and application frameworks worked tog
|
||
ether closely to recreate the user experience that we\, as nerds\, grew up
|
||
on. Over time as the utility of open source software became a part of ent
|
||
erprise and business\, we moved away from the desktop into the data center
|
||
. Then\, came the myriad of technologies... from databases to containers..
|
||
..we are all familiar with today. The Linux-based desktop was relegated to
|
||
the tinkerer\, the curious\, and the nostalgic. Developers moved to MacOS
|
||
as the serious developer tool of choice. As investment moved away from th
|
||
e desktop and application ecosystem\, it seemed that the bright light of t
|
||
his ecosystem had been diminished.\n\n Away from center stage\, amazing th
|
||
ings are happening in the app ecosystem. A greater sense of collaboration
|
||
prevails\, and this not quite hidden from view ecosystem is flourishing.\n
|
||
\nThe Flathub App store has 2600 apps and is adding 40 new apps a month.
|
||
By the end of 2024\, it’s projected that Flathub will have over 3000 app
|
||
s ranging from developer oriented apps to apps on the go. Let's look at ho
|
||
w this ecosystem is thriving and ushering in a renaissance. Expect to hear
|
||
a short history lesson on the app ecosystem's influence on the Linux plat
|
||
form before focusing on the apps and where we are today.
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us/schedule/presentation/218/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240804T140000
|
||
DTEND;TZID=US/Pacific:20240804T144500
|
||
DTSTAMP:20240723T165417Z
|
||
UID:371@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:GNU/Linux Loves All: Free Software in Music
|
||
DTSTART;TZID=US/Pacific:20240804T140000
|
||
DTEND;TZID=US/Pacific:20240804T144500
|
||
DTSTAMP:20240723T165417Z
|
||
UID:342@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Timmy James Barnett\nThe music industry is cluttered
|
||
with proprietary software and hardware. Musicians get locked into non-free
|
||
technologies. There is even a professional pressure to use proprietary to
|
||
ols as though it is just part of making music in today's modern society. A
|
||
pple computers are even seen by many as a default for beginner and profess
|
||
ional musicians. When someone says they don't regularly use MacOS\, Window
|
||
s is assumed. But you can make great music without compromising Human Tech
|
||
Rights by using Free Software and GNU/Linux\, a far superior operating sy
|
||
stem to proprietary alternatives.\n\nTechnology is such a great tool for m
|
||
usic. The development of technology supports the development of music. Thi
|
||
s is why musicians should be using Free Software and supporting a Free com
|
||
munity. Philosophers\, mathematicians\, music performers and theorists hav
|
||
e been coming up with many different ways of how to tune instruments for t
|
||
housands of years. With the Internet\, musicians can find out so much of w
|
||
hat has been done in the past as well as what is possible now. The world o
|
||
f tuning keeps coming up with exciting new and innovative ways to organize
|
||
possible pitches. \n\nHowever\, even with something as exciting as new mo
|
||
dern instruments and software that can inspire so much great music\, we se
|
||
e so many new things that are proprietary. This world of proprietary puts
|
||
unnecessary restrictions on what should be an open and creative process th
|
||
at is inviting for both amateurs and professionals. Why are companies maki
|
||
ng non-free software tools just for users to be able to even experience th
|
||
e sounds of notes that are decades\, centuries or millennia old? Why shoul
|
||
d we have restrictions on the great notes both historic and modern from Af
|
||
rica\, India\, and the Middle East\, that are not found on standard Wester
|
||
n instruments in the local Western music store? We have such a great tool
|
||
all around us\, the computer. Computers should come to our aid in a way th
|
||
at inspires more music and community on a global scale. \n\nThis talk show
|
||
s some great Free technologies\, instruments and software. All software is
|
||
run on a GNU/Linux Laptop.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/243/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Mentoring youth: The FOSS strategy we've been looking for
|
||
DTSTART;TZID=US/Pacific:20240803T140000
|
||
DTEND;TZID=US/Pacific:20240803T144500
|
||
DTSTAMP:20240723T165417Z
|
||
UID:310@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Devin Ulibarri\nFree software enthusiasts are eager f
|
||
or the day to come when digital sovereignty is the norm. However\, how do
|
||
we get there from where we are now?\n\nWhile installing GNU/Linux onto you
|
||
r own computer and avoiding proprietary software may be helpful for your p
|
||
ersonal freedom\, these actions fail to persuade others to change their de
|
||
ep-seeded habits. Informing friends and family about software freedom is c
|
||
ertainly important\, but folks have an understandably hard time transition
|
||
ing. So what are we to do about it?\n\nMentoring youth interested in techn
|
||
ology to be contributing members of the free software projects can have a
|
||
lasting impact. Youth are more amenable to change\, and they have more tim
|
||
e to learn and try new things. Moreover\, youth who are able to not only u
|
||
nderstand the *philosophy* of software freedom -- but to *exercise* those
|
||
freedoms -- stand ready to make a significant and lasting impact\, both fo
|
||
r themselves and those around them.\n\nAt Sugar Labs\, we create tools for
|
||
learning. The tools are FOSS. The source code published\, even during dev
|
||
elopment. We invite youth to contribute to our software\, solving issues u
|
||
nder community mentorship and developing their skills. Plus\, many of our
|
||
tools help students to learn programming\, which helps our youngest learne
|
||
rs prepare for their next steps (at Sugar Labs or elsewhere). As a result\
|
||
, we have some repositories with over two-hundred contributors\, many of w
|
||
hom are in high school or college. Moreover\, students who have stayed wit
|
||
h us for a sustained period have reported their successes in later FOSS en
|
||
deavors.\n\nThis talk will examine education and mentorship as a strategy
|
||
to bring free software into the mainstream\, both because it helps give yo
|
||
uth the experience they need to better understand the implications of soft
|
||
ware freedom as well as helps to guide youth into free software communitie
|
||
s where they can continue to make a lasting positive impact.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/202/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Update on Recent Copyleft Litigation and the State of Copyleft
|
||
DTSTART;TZID=US/Pacific:20240802T140000
|
||
DTEND;TZID=US/Pacific:20240802T144500
|
||
DTSTAMP:20240723T165417Z
|
||
UID:293@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Bradley M. Kuhn\nSo much has happened recently with e
|
||
nforcement of copyleft licenses\, such as the GPL and LGPL. This session
|
||
will give you an update on all that's happened in the last year regarding
|
||
GPL compliance and enforcement.
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us/schedule/presentation/257/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:You've been laid off. Now what?
|
||
DTSTART;TZID=US/Pacific:20240803T140000
|
||
DTEND;TZID=US/Pacific:20240803T142500
|
||
DTSTAMP:20240723T165417Z
|
||
UID:355@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Mike Jang\nI've survived two layoffs. I've also found
|
||
jobs while employed. While I've announced my availability\, I've never us
|
||
ed the LinkedIn "Open for Work" banner. After my last layoff (March of 202
|
||
4)\, I submitted 15 serious applications in under 40 days and had a 40% su
|
||
ccess rate getting interviews. Too many of us in tech are not working. So
|
||
many more of us are at risk.\n\nI want to share my lessons learned\, "Best
|
||
practices after a layoff." I've split this talk into the following sectio
|
||
ns:\n\n• Negotiate your layoff terms\n• Apply for unemployment\n• Re
|
||
gain focus (avoid anger)\n• Don't just ask for help (Tell potential futu
|
||
re employers what you can do for them)\n• Find hiring managers in your n
|
||
etwork\n• Customize your application (and cover letter\, and thank you n
|
||
ote\, etc.)\n• Share your schedule\n• Extra work (demonstrate what you
|
||
can do for your target company)\n• Prepare for your interview (spoiler:
|
||
prepare a "closing statement")\n• Follow up\n• The offer\n\nFor the r
|
||
ecord\, I'm happy where I'm working now\, and I hope to stay there for man
|
||
y years into the future. This is a difficult economy. While my methods may
|
||
not work for everyone\, I hope they can help people who need a different
|
||
approach to their job searches.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/268/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Report from the AI-Assisted Programming and Copyleft Committee
|
||
DTSTART;TZID=US/Pacific:20240804T140000
|
||
DTEND;TZID=US/Pacific:20240804T144500
|
||
DTSTAMP:20240723T165417Z
|
||
UID:362@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Stefano Zacchiroli\nAt the onset of AI-assisted progr
|
||
amming\, Software Freedom Conservancy convened a committee to investigate
|
||
the implications of such assistance \nfor copyleft and software freedom mo
|
||
re broadly. \nIn this session\, members of the committee will report back
|
||
to the FOSSY audience about their work and discuss recommendations for the
|
||
use and development of AI assistants that are compatible with free softwa
|
||
re goals.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/236/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:30 Years and Counting: Secrets to enduring user groups
|
||
DTSTART;TZID=US/Pacific:20240801T140000
|
||
DTEND;TZID=US/Pacific:20240801T144500
|
||
DTSTAMP:20240723T165417Z
|
||
UID:277@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Michael Dexter\nWhy do some user groups endure for de
|
||
cades while others do not? What organizational structures and personalitie
|
||
s are needed to maintain interest\, attendance and participation? The Port
|
||
land Linux/Unix Group was founded over 30 years ago and is still going str
|
||
ong\, hosting some of the top open source speakers in the world including
|
||
Linus Torvalds\, Kelsey Hightower and Bradley M. Kuhn.
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us/schedule/presentation/213/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Open source mentorship programs: what’s in it for you as a mento
|
||
r\, maintainer\, or mentee? (panel)
|
||
DTSTART;TZID=US/Pacific:20240802T140000
|
||
DTEND;TZID=US/Pacific:20240802T144500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:308@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Emily Lovell\nMentorship can be a powerful tool for c
|
||
ultivating a more diverse\, equitable\, and inclusive tech pipeline. For m
|
||
entors and maintainers\, investing in these relationships can help to grow
|
||
and sustain their technical communities. Meanwhile\, mentees can benefit
|
||
from a sense of belonging\, alongside technical learning and professional
|
||
development.\n\nJoin us for a conversation about four mentorship initiativ
|
||
es serving as onramps to open source\, especially for those minoritized in
|
||
tech\; these include a variety of models for bridging community colleges\
|
||
, research universities\, and HBCUs with industry open source. We’ll dis
|
||
cuss how these collaborations have been beneficial to everyone involved\,
|
||
and how such efforts can be beneficial to you as a potential mentor\, main
|
||
tainer\, or mentee. We’ll then open up the floor to questions and conver
|
||
sation about mentorship in open source — and how you can get involved.\n
|
||
\nSession takeaways:\n- Key considerations for launching a new mentorship
|
||
initiative within your own project\, organization\, or community\n- Existi
|
||
ng programs you might engage with as a mentor or apply to as a mentee\n- A
|
||
n invitation to join a growing cross-sector interest group on this topic
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/196/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240804T140000
|
||
DTEND;TZID=US/Pacific:20240804T144500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:376@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Empowering FOSS projects on ARM64 at the OSUOSL
|
||
DTSTART;TZID=US/Pacific:20240801T140000
|
||
DTEND;TZID=US/Pacific:20240801T144500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:281@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Lance Albertson\nAt the OSU Open Source Lab\, we prov
|
||
ide a variety of services\, including access to ARM64 for FOSS projects. T
|
||
his session will discuss what we can provide to FOSS projects\, how the in
|
||
frastructure underneath is setup and some user stories from some of our ho
|
||
sted projects. This will also include some brief discussion about the nuis
|
||
ances of hosting ARM64 hardware in a data center.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/192/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Setting Up A Simple XMPP Server
|
||
DTSTART;TZID=US/Pacific:20240801T140000
|
||
DTEND;TZID=US/Pacific:20240801T144500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:240@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Root\nThis talk will showcase the simplicity and ease
|
||
of setting up your own XMPP server using the Snikket software\, walking s
|
||
tep-by-step through the process using slides. The end result will be a ful
|
||
ly functioning XMPP server that can be used throughout the remainder of th
|
||
e conference between all attendees. There will be a demonstration of the f
|
||
eatures available to a Snikket Instance including\, but not limited to\, i
|
||
nviting others to join your server\, group chats that are private or publi
|
||
c\, adding contacts\, managing and updating the instance as the admin\, cr
|
||
eating limited accounts for kids\, and steps for more secure end-to-end en
|
||
cryption. This talk will also dive into some personal privacy\, security\,
|
||
and persona considerations and how they will be affected by your threat m
|
||
odel.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/233/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Video Encoding on Arm64
|
||
DTSTART;TZID=US/Pacific:20240802T140000
|
||
DTEND;TZID=US/Pacific:20240802T144500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:287@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: John J. O'Neill\, Ph.D.\nThis session provides a brie
|
||
f overview on video encoding and why it's critically important due to the
|
||
exponential increase in online video. Video encoding on Arm64 processors
|
||
provide outstanding performance and are very power efficient. The talk wi
|
||
ll compare running video encoding on Arm64 with legacy x86 processors as w
|
||
ell as hardware-based Video Processing Units (VPU). The Arm64 video encod
|
||
ing ecosystem is very active and recent performance improvements will be h
|
||
ighlighted. Future directions in Arm64 based video processing ecosystem w
|
||
ill also be discussed.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/256/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240803T140000
|
||
DTEND;TZID=US/Pacific:20240803T144500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:349@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Private Equity companies only want one thing and it's.......
|
||
DTSTART;TZID=US/Pacific:20240802T140000
|
||
DTEND;TZID=US/Pacific:20240802T144500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:332@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Ben Ford\nThe experience of being acquired by a priva
|
||
te equity company is often traumatic. There are layoffs and reorgs and can
|
||
celed projects and nobody knows who's working on what and the back office
|
||
suite always changes so you're off balance to begin with and... and the co
|
||
mmunity. Who's keeping the community engaged through the process? How do y
|
||
ou even keep a community alive\, when all the metrics seem to be up in the
|
||
air and nobody seems to care about what's important? Complaints are pilin
|
||
g up\, community members feel unappreciated\, and we keep stepping on them
|
||
. Don't they know that community is what built this company?\n\nIt doesn't
|
||
have to end here. This talk will go through our experiences with this sit
|
||
uation and how we learned from it and are coming through the other side. I
|
||
will talk about how we learned to communicate our business value and how
|
||
we had to reset some of our expectations. Most importantly\, I'll talk abo
|
||
ut how we taught the new company to look at our community\, not with greed
|
||
\, but with appreciation.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/245/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240803T140000
|
||
DTEND;TZID=US/Pacific:20240803T144500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:333@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:"The Power of Belonging: go beyond DEI "
|
||
DTSTART;TZID=US/Pacific:20240802T140000
|
||
DTEND;TZID=US/Pacific:20240802T144500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:299@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Aarti Ramkrishna\nOpen source communities have long b
|
||
een heralded as the bastions of innovation\, collaboration\, and shared pr
|
||
ogress. These communities thrive on the contributions of individuals from
|
||
all walks of life\, bringing a plethora of ideas and perspectives to the t
|
||
able. However\, the reality of achieving genuine diversity\, equity\, and
|
||
inclusion (DEI) within these spaces remains elusive.\n\nAarti Ramkrishna\,
|
||
an educator from the global majority and a dedicated equity advocate\, in
|
||
vites you to a compelling and transformative discussion on how we can cult
|
||
ivate a culture of belonging in open source environments. Drawing on her e
|
||
xtensive background in education administration\, curriculum development\,
|
||
and DEI\, Aarti offers a deeply personal and professional insight into th
|
||
e intricacies of fostering inclusive communities.\n\nIn her journey as an
|
||
instructional leader and equity facilitator\, Aarti has consistently champ
|
||
ioned the importance of diversity and inclusion. Her work in developing cu
|
||
lturally responsive curricula and facilitating professional development ha
|
||
s significantly enhanced educational outcomes and fostered a more inclusiv
|
||
e learning environment. She brings this wealth of experience to the open s
|
||
ource arena\, highlighting the parallels and unique challenges faced by th
|
||
ese communities.\n\nDuring this talk\, Aarti will delve into the importanc
|
||
e of recognizing and addressing implicit biases\, creating equitable parti
|
||
cipation opportunities\, and ensuring that every contributor feels seen an
|
||
d valued. She will share practical strategies and tools that open source e
|
||
ngineers can use to embed DEI principles into their projects\, from the in
|
||
itial stages of development to ongoing community engagement.\n\nThrough vi
|
||
vid storytelling and real-world examples\, Aarti will illustrate the trans
|
||
formative power of belonging. Attendees will leave with a deeper understan
|
||
ding of how to bridge gaps within their communities\, promote fairness\, a
|
||
nd cultivate an environment where innovation and inclusivity go hand in ha
|
||
nd.\n\nThis talk is a powerful call to action for all members of the open
|
||
source community. By committing to DEI\, we not only enrich our projects b
|
||
ut also ensure that the future of technology is shaped by a truly diverse
|
||
and inclusive set of voices. Join us in this crucial conversation and be p
|
||
art of the movement to build a more inclusive and innovative open source e
|
||
cosystem.
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us/schedule/presentation/228/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Toward an Economy of Open Abundance: Why FLO funding needs donor c
|
||
oordination and how to do it
|
||
DTSTART;TZID=US/Pacific:20240804T140000
|
||
DTEND;TZID=US/Pacific:20240804T144500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:366@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Aaron Wolf\nThere are four categories of economic goo
|
||
ds: private goods\, club goods\, commons\, and public goods. FLO (Free/Lib
|
||
re/Open) software and other similarly-licensed digital works are public go
|
||
ods — meaning they are open and abundant. So\, they don't fit our market
|
||
economy which relies on the opposite — scarcity and exclusion. Forcing
|
||
software into the standard economic system leads to reliance on paywalls a
|
||
nd ads. Can we do better?\n\nIn the first part of this talk\, Aaron will p
|
||
rovide an updated understanding of the economic dilemmas with public goods
|
||
. He will explain how standard language and models of economics make assum
|
||
ptions that work against the goals of software freedom. From there\, we ca
|
||
n see how to frame a new economic understanding of sharing and abundance.\
|
||
n\nTo get the key concepts\, we need to distinguish between goods and serv
|
||
ices\, exclusive vs open\, and scarce vs abundant. We can see these as tra
|
||
its on continuums (between clearly open and clearly exclusive are examples
|
||
of partly-open). With these core ideas in mind\, we can more easily see t
|
||
he issues with FLO projects today (along with many related parts of the ec
|
||
onomy).\n\nIn the second part of the talk\, Michael will argue that crowdf
|
||
unding for FLO projects is not effective enough as is. That's why we see a
|
||
ppeals to donate often couched in terms of merely buying someone a coffee
|
||
and similar. To become a game-changing economic force for good\, we need t
|
||
o improve one critical feature: donor coordination.\n\nWe believe that man
|
||
y more people would happily donate modest amounts to support FLO projects
|
||
whose works they use and value — if only they could be confident that it
|
||
would make a real difference. Most of us cannot give enough individually
|
||
to change the game\, but if large numbers of individuals can coordinate an
|
||
d donate together\, the collective funding power could have a massive impa
|
||
ct and even ultimately change the nature of our economy.\n\nThe basic prin
|
||
ciple of donor coordination is simple — what you donate can be tied to w
|
||
hat others donate. But exactly how best to do it is not a simple question.
|
||
There are many ways it can be approached\, each with different pros and c
|
||
ons. Michael will present the key "how" variables\, discuss their signific
|
||
ance\, and outline some of the pros and cons of each. And he'll describe t
|
||
he work he and others are doing to develop usable platforms to test these
|
||
coordination ideas with real funding.\n\nThe panel following this talk at
|
||
3pm will provide an opportunity to explore these ideas further in interact
|
||
ive discussion.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/272/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240801T140000
|
||
DTEND;TZID=US/Pacific:20240801T144500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:319@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Down But Not Out: How I'm Continuing to Serve as a Tech Lead 3 Yea
|
||
rs Unemployed
|
||
DTSTART;TZID=US/Pacific:20240803T142500
|
||
DTEND;TZID=US/Pacific:20240803T144500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:380@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Jordan Hewitt\nWhen my freelancing "side gig" took of
|
||
f in 2020\, I was finally able to quit my stop gap retail job and take on
|
||
2 to 3 clients at a time. However\, I soon found around 2021 the market wa
|
||
s shifting\, and\, lacking the knowledge on how it was changing\, I ended
|
||
up losing all my clients and starting from square one--unemployed. I hadn'
|
||
t built any notoriety with any major clients yet\, so I was basically a no
|
||
body. I was naive early on: after all\, I have 12 years software developme
|
||
nt experience--someone's bound to want me! But it became clear that it was
|
||
now a cutthroat job market. After thousands of job applications\, hundred
|
||
s of ghostings\, and many reimaginings of my brand I could have given up\,
|
||
but I've never stopped serving the tech community\, despite not getting p
|
||
aid for it. In this talk\, I'll share what what's working\, what's not\, a
|
||
nd how the tech community can help not only me\, but thousands of other hi
|
||
ghly-skilled tech workers to not only find a job\, but thrive in their car
|
||
eer.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/264/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Break
|
||
DTSTART;TZID=US/Pacific:20240801T144500
|
||
DTEND;TZID=US/Pacific:20240801T150000
|
||
DTSTAMP:20240723T165418Z
|
||
UID:244@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Break
|
||
DTSTART;TZID=US/Pacific:20240802T144500
|
||
DTEND;TZID=US/Pacific:20240802T150000
|
||
DTSTAMP:20240723T165418Z
|
||
UID:245@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Break
|
||
DTSTART;TZID=US/Pacific:20240804T144500
|
||
DTEND;TZID=US/Pacific:20240804T150000
|
||
DTSTAMP:20240723T165418Z
|
||
UID:247@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Break
|
||
DTSTART;TZID=US/Pacific:20240803T144500
|
||
DTEND;TZID=US/Pacific:20240803T150000
|
||
DTSTAMP:20240723T165418Z
|
||
UID:246@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FLO funding: A panel discussion of challenges\, incentives\, and p
|
||
ossibilities
|
||
DTSTART;TZID=US/Pacific:20240804T150000
|
||
DTEND;TZID=US/Pacific:20240804T154500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:367@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Wm Salt Hale\nSeveral panelists will discuss\, with o
|
||
pportunities for audience participation\, the challenges\, incentives\, an
|
||
d possibilities around funding free/libre/open (FLO) projects.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/271/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Survival is an Achievement: Tactical ways to keep user groups aliv
|
||
e under strain
|
||
DTSTART;TZID=US/Pacific:20240801T150000
|
||
DTEND;TZID=US/Pacific:20240801T154500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:278@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Emily Soward\nThis talk focuses solely on how to help
|
||
a user group community survive under duress and what individuals can do t
|
||
o help in a practical way if they aren’t experts in community developmen
|
||
t and stewardship. We will discuss tactical\, teachable tips for sustainin
|
||
g community under challenging times for those who are not community manage
|
||
ment experts. We will discuss 1/ what good enough looks like for community
|
||
management and how to stabilize a user group using COVID-19 disruptions t
|
||
o AWS User Groups as a case study\, 2/ how to identify what makes your use
|
||
r group community unique and build acceptably detailed community managemen
|
||
t strategies and documentation to get you through the next month\, quarter
|
||
\, or year 3/ how to know when your community needs intervention and who m
|
||
ight help you\, and 4/ how to be kind to yourself when you need a break to
|
||
make sure you and your community stay safe.\n\nNo community management sk
|
||
ills or experience needed\; this talk is all about lessons learned and tac
|
||
tics that are within reach for beginners and helpers.
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us/schedule/presentation/214/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240803T150000
|
||
DTEND;TZID=US/Pacific:20240803T154500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:350@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240804T150000
|
||
DTEND;TZID=US/Pacific:20240804T154500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:372@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240804T150000
|
||
DTEND;TZID=US/Pacific:20240804T154500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:377@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:My Neighbour in Open Source
|
||
DTSTART;TZID=US/Pacific:20240802T150000
|
||
DTEND;TZID=US/Pacific:20240802T154500
|
||
DTSTAMP:20240723T165418Z
|
||
UID:300@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Harmony Elendu\n"My Neighbour in Open Source"\nIn a w
|
||
orld that is increasingly connected yet paradoxically divided\, the concep
|
||
t of "My Neighbour in Open Source" stands as a testament to the potential
|
||
of communal living. This speech and presentation delve deeply into how we
|
||
can foster inclusivity and diversity within the global open-source communi
|
||
ty through both visible and subtle means. It emphasises that\, much like n
|
||
eighbours in a physical community\, individuals in the open-source sphere
|
||
can come together to build diverse products and initiatives that transcend
|
||
boundaries of color\, language\, personal challenges\, geographical origi
|
||
ns\, and varying personalities.\n\nAt the heart of "My Neighbour in Open S
|
||
ource" is the idea that the open-source community mirrors the dynamics of
|
||
a thriving neighborhood. In any given neighbourhood\, residents work colla
|
||
boratively to enhance their living conditions\, ensuring that every member
|
||
feels included and valued. This analogy is powerful in the context of ope
|
||
n-source because it underscores the importance of collective effort and mu
|
||
tual support in achieving common goals. Just as neighbors come together fo
|
||
r community clean-ups\, block parties\, and local projects\, contributors
|
||
to open-source projects unite to solve problems\, innovate\, and push the
|
||
boundaries of what is possible with technology.\n\nOne of the key aspects
|
||
of fostering inclusivity and diversity in open-source is recognizing and v
|
||
aluing the unique contributions of every individual. Diversity in this con
|
||
text is not merely about representation across different demographics\, bu
|
||
t also about the inclusion of diverse perspectives and ideas. Open-source
|
||
projects benefit immensely from the varied experiences and viewpoints that
|
||
contributors bring. This diversity of thought leads to more robust and cr
|
||
eative solutions\, as it encourages out-of-the-box thinking and problem-so
|
||
lving approaches that might not emerge in a more homogeneous group.\n\nThe
|
||
speech highlights practical ways to promote inclusivity within the open-s
|
||
ource community. These include creating welcoming and accessible documenta
|
||
tion\, establishing mentorship programs\, and actively reaching out to und
|
||
errepresented groups. Accessible documentation ensures that new contributo
|
||
rs\, regardless of their background\, can easily understand and get involv
|
||
ed in projects. Mentorship programs provide guidance and support to newcom
|
||
ers\, helping them navigate the complexities of open-source contribution a
|
||
nd develop their skills. Outreach initiatives aim to break down barriers t
|
||
o entry by providing resources and opportunities to those who might otherw
|
||
ise be excluded.\n\nFurthermore\, "My Neighbour in Open Source" addresses
|
||
the importance of creating safe and respectful spaces where all contributo
|
||
rs feel valued. This involves implementing and enforcing codes of conduct
|
||
that prohibit discriminatory behavior and harassment. By fostering a cultu
|
||
re of respect and inclusion\, open-source communities can ensure that ever
|
||
y participant feels safe to express their ideas and collaborate freely. Th
|
||
is\, in turn\, enhances the overall quality and innovation within projects
|
||
.\nThe presentation also explores the invisible ways in which inclusivity
|
||
can be promoted. These include fostering an inclusive mindset among existi
|
||
ng contributors and leaders\, who must be aware of their own biases and wo
|
||
rk actively to counteract them. It is crucial for leaders in the open-sour
|
||
ce community to set an example by embracing and promoting diversity in all
|
||
its forms. This can involve highlighting the contributions of diverse ind
|
||
ividuals\, celebrating cultural differences\, and encouraging open dialogu
|
||
e about inclusivity.\n\nIn practice\, achieving the vision of "My Neighbor
|
||
in Open Source" means that everyone\, from project maintainers to casual
|
||
contributors\, plays a role in building an inclusive community. It require
|
||
s a commitment to continuous learning and improvement\, as well as a willi
|
||
ngness to listen and adapt to the needs of the community. This collective
|
||
effort mirrors the dynamics of a successful neighbourhood\, where the well
|
||
being of each member contributes to the overall health and vibrancy of the
|
||
community.\n\nUltimately\, "My Neighbour in Open Source" is a call to act
|
||
ion. It invites every member of the open-source community to reflect on th
|
||
eir role in fostering inclusivity and to take proactive steps towards crea
|
||
ting a more welcoming and diverse environment. By working together as neig
|
||
hbors\, we can ensure that the open-source community not only thrives but
|
||
also serves as a model for collaborative and inclusive innovation in the b
|
||
roader tech industry and beyond
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us/schedule/presentation/226/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Teaching Young Children About Software Freedom
|
||
DTSTART;TZID=US/Pacific:20240803T150000
|
||
DTEND;TZID=US/Pacific:20240803T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:311@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Aaron Wolf\nKids today grow up in a world dominated b
|
||
y computers. And yet the only education they normally get\, if any\, focus
|
||
es on basic computer use or on programming. Where topics of power and ethi
|
||
cs do come up\, they focus on issues like privilege\, bigotry\, and social
|
||
-media. How can young people learn about the inherent issues with software
|
||
freedom at the foundations of the tech that surrounds them?\n\nThinking a
|
||
bout this dilemma\, I first asked others for their ideas. Mostly\, the res
|
||
ponses mentioned pseudo-educational games or other fun-computer-things for
|
||
kids that are FLO. Few were great\, and none taught free/libre/open conce
|
||
pts as an emphasis itself.\n\nInstead of games and spectacles\, I decided
|
||
to set up a computer for my then-6-year-old focusing on a basic terminal.
|
||
We started by playing with silly commands like espeak TTS saying funny th
|
||
ings or gibberish. Over time\, it evolved into his own first program: Cowm
|
||
ath — a Bash script in which cowsay and espeak in combination quiz the u
|
||
ser on random math questions.\n\nAll along\, I emphasized how our experien
|
||
ces fit into larger context. We use FLO software to do this\, and when we
|
||
share our code for others to use\, study\, and adapt\, we become part of c
|
||
ontinuing that process. We talked about licensing and community and other
|
||
topics. And we now hope to get others to join us in expanding the FLO-firs
|
||
t educational curriculum we have started (in-progress at codeberg.org/FLO
|
||
-Conscience/FLO-kids ).\n\nWe presented the first time remotely for LibreP
|
||
lanet in March 2023. Then\, we presented in-person at SeaGL in November 20
|
||
23. Rowan loved meeting others who actually understand and care about soft
|
||
ware-freedom\, and he's eager to get other kids his age also understand an
|
||
d share his concerns and interests here. In this presentation we will shar
|
||
e our story\, recent updates\, and our ideas about how more parents and te
|
||
achers can bring these ideas to more kids.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/188/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:The Art of Asking
|
||
DTSTART;TZID=US/Pacific:20240802T150000
|
||
DTEND;TZID=US/Pacific:20240802T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:329@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Paige Cruz\nWhen joining a new organization or projec
|
||
t we’re often told “There are no bad questions - ask away!” and I fu
|
||
lly endorse stoking your curiosity and connecting with others for help. I
|
||
do believe that there are no bad questions but that there can be badly phr
|
||
ased questions. If you’ve ever had your questions go unanswered in onlin
|
||
e forums or are tired of hearing “it depends” time and time again this
|
||
session is for you! \n\nBetween instant messaging platforms\, mailing lis
|
||
ts\, social media accounts\, wikis\, repos\, and meetups there are a lot o
|
||
f ways to connect and engage with an open source community/project and who
|
||
you ask\, when you ask\, where and how can all affect the answers you get
|
||
. \n\nWe will unpack what it takes to craft questions that get answered by
|
||
reviewing several case studies of questions posed about OpenTelemetry acr
|
||
oss various channels. Finishing with a simple guide you can put into pract
|
||
ice to master the art of asking to get answers.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/248/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Why rewrite OpenBSD's fw_update(8)?
|
||
DTSTART;TZID=US/Pacific:20240803T150000
|
||
DTEND;TZID=US/Pacific:20240803T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:340@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Andrew Hewus Fresh\nOpenBSD provides the utility fw_u
|
||
pdate(8) to handle firmware loading for hardware from manufacturers whose
|
||
licensing isn't compatible with our base system. We will take a trip into
|
||
the history of fw_update(8)\, its structure and why it exists. A recent re
|
||
write provides an illustration of the value OpenBSD places on simplicity a
|
||
nd user experience.
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us/schedule/presentation/217/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Apache Mahout's Quantum Computing Interface
|
||
DTSTART;TZID=US/Pacific:20240804T150000
|
||
DTEND;TZID=US/Pacific:20240804T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:363@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Andrew Musselman\nApache Mahout (https://mahout.apach
|
||
e.org) is a linear algebra library for building machine learning solutions
|
||
\, and up until this year focused on compute back-ends such as Spark and F
|
||
link for processing training data into predictions. More recently the proj
|
||
ect has adopted quantum compute back-ends as well. The Qumat (https://gith
|
||
ub.com/apache/mahout?tab=readme-ov-file#qumat) library is a Python-based i
|
||
nterface to multiple quantum computing systems\, starting with IBM's Qiski
|
||
t\, which allows researchers and developers to assemble quantum logic gate
|
||
s into circuits that can run on simulators as well as utility-scale quantu
|
||
m computers. This talk will provide a brief introduction to quantum comput
|
||
ing\, including the data structures used along with some basic logic gates
|
||
(https://github.com/apache/mahout/blob/main/docs/basic_gates.md)\, and wi
|
||
ll demo Qumat software running in a notebook that will be shared after the
|
||
talk.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/265/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Mitigating MITMs in XMPP
|
||
DTSTART;TZID=US/Pacific:20240801T150000
|
||
DTEND;TZID=US/Pacific:20240801T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:248@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Amolith\nIn October 2023\, Jabber.ru\, “the largest
|
||
Russian XMPP messaging service”\, discovered that both Hetzner and Lino
|
||
de had been targetting them with Machine-In-The-Middle (MITM) attacks for
|
||
up to 6 months. This talk covers the basics of MITM attacks in general\, s
|
||
ome specifics of the attack against Jabber.ru\, and a very effective mitig
|
||
ation strategy for admins to implement and both admins and users to monito
|
||
r.\n\nThis talk assumes little prior knowledge beyond “XMPP is an open a
|
||
nd extensible communication protocol that facilitates messaging\, calling\
|
||
, and more”.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/232/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Unlocking containers on ARM64: A story of runtime and image suppor
|
||
t
|
||
DTSTART;TZID=US/Pacific:20240801T150000
|
||
DTEND;TZID=US/Pacific:20240801T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:282@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Phil Estes\nContainer runtimes like Docker and contai
|
||
nerd are the core software components that enable the adoption of containe
|
||
r technology\, whether in cloud orchestrator systems like Kubernetes or in
|
||
edge and embedded compute scenarios. Similarly\, the Open Container Initi
|
||
ative (OCI) has standardized the concepts around containers\, like the ima
|
||
ge and runtime specifications\, so that all runtime implementations are in
|
||
teroperable. \n\nIn both these worlds\, the adoption of multi-platform sup
|
||
port has made steady progress for the last 6-8 years. While progress has b
|
||
een slow at times\, the ecosystem has now fully unlocked the advantages of
|
||
ARM64 as one of the key platforms supported directly by runtimes and enco
|
||
ded into the specifications of the OCI.\n\nIn this talk we'll walk through
|
||
this history of the adoption of ARM64\, including a focus on the CNCF con
|
||
tainerd project as a shining example of the adoption of multi-platform sup
|
||
port\, and specifically the enablement of the containerd project to build\
|
||
, test\, and release official support on ARM64. We'll look at example use
|
||
cases and where the industry is using this support today to enable product
|
||
ion workloads on ARM64.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/189/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240801T150000
|
||
DTEND;TZID=US/Pacific:20240801T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:320@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:AMA: Building Autonomous Self Healing Computer Systems
|
||
DTSTART;TZID=US/Pacific:20240804T150000
|
||
DTEND;TZID=US/Pacific:20240804T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:346@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Darrick J. Wong\nDoes your data management system go
|
||
bonkers? Would you like it to fix itself for you? Or possibly just grow
|
||
weird new parts on demand? I recently finished construction on an autonom
|
||
ous self healing filesystem for Linux 6.10 and would love to share how it
|
||
works with everyone. Many people who I've shown this off to think this is
|
||
magic\, but it's really not:\n\nDo you have record sets that you need to
|
||
index? While the system is running? What if I showed you several techniq
|
||
ue for doing that\, along with some discussion of the strengths and weakne
|
||
sses of each?\n\nHow about analyzing the structure of graph structured dat
|
||
a? By relaxing some constraints and tightening others\, it's possible to
|
||
determine if you've got a proper tree ... or whatever it is that directory
|
||
trees actually are. Eventual consistency is key here.\n\nOh\, and did I
|
||
mention that this is XFS? So I'll also talk about how do to this in a res
|
||
ource and functionality-constrained environment like the operating system!
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/239/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Q&A: Unemployed or Underemployed? How to get through.
|
||
DTSTART;TZID=US/Pacific:20240803T150000
|
||
DTEND;TZID=US/Pacific:20240803T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:356@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Mike Jang\nMike Jang and Jordan Hewitt will take this
|
||
time to take questions and discuss strategies more in specifics. This dis
|
||
cussion will be directly related to the previous talks\, You've been laid
|
||
off. Now what? (Mike Jang)\, and Down But Not Out: How I'm Continuing to S
|
||
erve as a Tech Lead 3 Years Unemployed (Jordan Hewitt)
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/269/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Using Open Source Software to power the Sustainable Cloud
|
||
DTSTART;TZID=US/Pacific:20240802T150000
|
||
DTEND;TZID=US/Pacific:20240802T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:288@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Dan Kalowsky\nThis session will introduce how Ampere
|
||
Computing has leveraged Open Source Software and standards for powering it
|
||
's line of custom designed Arm based servers. We'll briefly cover what it
|
||
means to be an Arm based Neoverse design\, and then dive into how Open So
|
||
urce software drives the platform through firmware development\, booting\,
|
||
and daily operations. The talk will touch upon some of the benefits and
|
||
challenges encountered along the way that relate to multiple project devel
|
||
opment and open source software development.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/191/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:How do you really do GPL enforcement? (aka Bringing software right
|
||
-to-repair to the masses)
|
||
DTSTART;TZID=US/Pacific:20240802T150000
|
||
DTEND;TZID=US/Pacific:20240802T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:294@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Denver Gingerich\nEnforcing the General Public Licens
|
||
e (GPL) to bring real software freedom to people can be very challenging i
|
||
n practice\, but many of the steps in the process are straight-forward. A
|
||
s the only organization enforcing the GPL for Linux\, Software Freedom Con
|
||
servancy (SFC) receives a huge quantity of GPL violation reports\, and nee
|
||
ds to triage each one as the beginning of our process. The next step is c
|
||
alled the "CCS check" (complete corresponding source check)\, a crucial bu
|
||
t barely known activity that determines whether some candidate source code
|
||
actually corresponds to the device/binaries that the candidate was provid
|
||
ed for. We will discuss the CCS check in detail\, providing examples and
|
||
tips for doing your own checks.\n\nLastly\, we'll cover the offer check\,
|
||
something everyone can do to help in SFC's efforts to bring real software
|
||
right-to-repair to every device running Linux. Whether you want to check
|
||
offers for source code\, review a CCS candidate\, or go even further with
|
||
additional GPL enforcement work of your own\, this talk will set you up fo
|
||
r success.
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us/schedule/presentation/261/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Developing Accessible\, Multimodal Interactive STEM Simulations wi
|
||
th SceneryStack
|
||
DTSTART;TZID=US/Pacific:20240802T150000
|
||
DTEND;TZID=US/Pacific:20240802T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:309@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Brett Fiedler\nSceneryStack is a recently created ope
|
||
n-source community built around a [collection of HTML5/TypeScript develop
|
||
ment libraries](https://scenerystack.github.io/community/guides/scenerysta
|
||
ck_list/) in the Model-View-Controller framework that can be used **toge
|
||
ther or separately** to create multimodal and accessible\, web interactiv
|
||
es. SceneryStack libraries are used to create PhET Interactive Simulations
|
||
\, free and open-source science and math simulations with hundreds of mill
|
||
ions of uses worldwide\, as well as their growing set of Inclusive Feature
|
||
s. SceneryStack includes support for robust accessibility features like dy
|
||
namic and navigable screen-reader descriptions\, dynamic and customizable
|
||
descriptions through browser text-to-speech\, sounds and sonifications\, p
|
||
an and zoom\, alternative input\, and more. SceneryStack offers libraries
|
||
specifically tailored to interactive\, educational simulation development\
|
||
, in addition to being suitable for general web interactive development. T
|
||
he goals of SceneryStack are to create more accessible and enjoyable STEM
|
||
learning interactives\, as well as supporting developers to create more in
|
||
clusive dynamic web content broadly. We share about the motivation to crea
|
||
te SceneryStack\, propelled by teacher-developers\, and the vision for the
|
||
future of the open-source community.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/203/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240801T150000
|
||
DTEND;TZID=US/Pacific:20240801T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:316@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:A review of valuation models and their application to open source
|
||
models
|
||
DTSTART;TZID=US/Pacific:20240803T150000
|
||
DTEND;TZID=US/Pacific:20240803T154500
|
||
DTSTAMP:20240723T165419Z
|
||
UID:334@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Sophia Vargas\nCollectively\, we struggle to consiste
|
||
ntly define the value of open source and work supporting open source proje
|
||
cts. Without clear value attributed to open source projects and developmen
|
||
t\, it can be difficult to justify investment in open source projects\, es
|
||
pecially as many continue to rely on open source solutions as a source of
|
||
cost savings. This talk will discuss longstanding and novel economic\, soc
|
||
ial and operational models and whether or not they can be an effective met
|
||
hod to measure the value of open source projects and contributions. Our go
|
||
al is to further our collective ability to articulate the value of open so
|
||
urce.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/262/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Coffee/tea break
|
||
DTSTART;TZID=US/Pacific:20240801T154500
|
||
DTEND;TZID=US/Pacific:20240801T163000
|
||
DTSTAMP:20240723T165419Z
|
||
UID:235@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Coffee\, tea\, and snack break
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Coffee/tea break
|
||
DTSTART;TZID=US/Pacific:20240803T154500
|
||
DTEND;TZID=US/Pacific:20240803T163000
|
||
DTSTAMP:20240723T165419Z
|
||
UID:237@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Coffee\, tea\, and snack break
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Coffee/tea break
|
||
DTSTART;TZID=US/Pacific:20240804T154500
|
||
DTEND;TZID=US/Pacific:20240804T163000
|
||
DTSTAMP:20240723T165419Z
|
||
UID:238@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Coffee\, tea\, and snack break
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Coffee/tea break
|
||
DTSTART;TZID=US/Pacific:20240802T154500
|
||
DTEND;TZID=US/Pacific:20240802T163000
|
||
DTSTAMP:20240723T165419Z
|
||
UID:236@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Coffee\, tea\, and snack break
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Case Studies of Exploitation in Open Source
|
||
DTSTART;TZID=US/Pacific:20240804T163000
|
||
DTEND;TZID=US/Pacific:20240804T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:368@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Watson\nOpen Source funding is inextricably related t
|
||
o how it is governed. Open source governance of mature projects can be sp
|
||
lit into four components: the project itself\, the services company surrou
|
||
nding the project\, the foundation associated with the project\, and its c
|
||
ommunity of users.\n\nContrary to popular belief\, open source has “riva
|
||
l” assets in the form of social capital (attention\, trust\, a sense of
|
||
belonging) and traditional assets (trademarks\, donations\, certification
|
||
proceeds\, conference proceeds). Both of these asset types need ethical g
|
||
overnance in order to avoid exploitation. \n\nTraditionally\, donations f
|
||
or open source projects were in the form of direct participation e.g. code
|
||
or in fiat money. More recently\, open source projects such as Bitcoin\,
|
||
Ethereum\, and Solana “mint” and issue “tokens” that can be redee
|
||
mable in fiat money. This opens the door to new opportunities (non fungib
|
||
le ownership of digital assets\, i.e. web 3.0) and new methods of exploita
|
||
tion (rug pulls). \n\nWe will present a case study on three open source i
|
||
nitiatives with various sizes of projects\, non profit foundations\, open
|
||
source services companies\, communities\, and funding styles. These initi
|
||
atives are the CNF Test Suite\, the Fedora project\, and XRP. We will con
|
||
clude with an analysis of the funding styles\, stemming from the governanc
|
||
e structure of the open source project. \n\nThe attendee will walk away w
|
||
ith a useful model for critiquing open source funding which can be used fo
|
||
r traditional as well as web 3.0 open source projects.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/220/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Discussion: Scalability Through Open Source Hygiene
|
||
DTSTART;TZID=US/Pacific:20240802T163000
|
||
DTEND;TZID=US/Pacific:20240802T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:295@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Ria Farrell Schalnat\nThere are many processes within
|
||
an organization dealing with open source including licensing reviews & co
|
||
mpliance\, export compliance\, product security\, contractual obligations\
|
||
, and sustainability. These operate against the backdrop of ongoing devel
|
||
opment in technology\, case law and newer legal requirements such as the E
|
||
O 14028 in the United States and the European Union’s Cyber Resiliency A
|
||
ct (EU-CRA). All of them depend on inventories to understand the scope o
|
||
f obligations\, risks and opportunities. They also require simple\, scala
|
||
ble runbooks to achieve the underlying goals. Come to this session for an
|
||
interactive discussion on practices and how to leverage projects within t
|
||
he Linux Foundation to super-charge your company’s open source practices
|
||
.
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us/schedule/presentation/260/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240801T163000
|
||
DTEND;TZID=US/Pacific:20240801T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:317@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240802T163000
|
||
DTEND;TZID=US/Pacific:20240802T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:289@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240804T163000
|
||
DTEND;TZID=US/Pacific:20240804T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:378@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Anatomy of a Cross-platform Chat SDK
|
||
DTSTART;TZID=US/Pacific:20240801T163000
|
||
DTEND;TZID=US/Pacific:20240801T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:252@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Stephen Paul Weber\nA lot of XMPP developers spend mu
|
||
ch of their time re-implementing the same basic protocol features. While g
|
||
ood low-level libraries for protocol establishment are not hard to find\,
|
||
what would it look like to model at a higher level\, so that developers ca
|
||
n focus on building a great user experience and not have to worry about wh
|
||
at a "XEP" is? I have been exploring this space and will report on my find
|
||
ings\, demo a prototype\, and solicit feedback about what would make your
|
||
chat or real-time development experience smoother.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/231/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Fostering Diversity and Sustainability: A Call to Empower Outreach
|
||
y
|
||
DTSTART;TZID=US/Pacific:20240802T163000
|
||
DTEND;TZID=US/Pacific:20240802T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:301@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Omotola Eunice OMOTAYO\nIn today's rapidly evolving t
|
||
ech landscape\, fostering diversity and promoting sustainability are not j
|
||
ust ethical imperatives but crucial elements for innovation and long-term
|
||
societal impact. Outreachy\, a successful diversity program and one of the
|
||
main projects of SFC\, exemplifies these principles aimed at supporting u
|
||
nderrepresented groups in open source and tech communities worldwide. \n\n
|
||
This talk proposes to explore the pivotal role of Outreachy in advancing d
|
||
iversity and sustainability while advocating for increased support and emp
|
||
owerment towards the sustainability of the program.\n\nThe discussion poin
|
||
ts will include the following: \n1) The significance of diversity in drivi
|
||
ng innovation and creativity within tech companies and open-source communi
|
||
ties.\nPresenting statistical evidence and case studies that highlight the
|
||
tangible benefits of diverse teams in problem-solving and product develop
|
||
ment.\n2) Exploring how Outreachy's focus on sustainability aligns with gl
|
||
obal efforts towards environmental stewardship in technology.\nShowcasing
|
||
projects within Outreachy that exemplify sustainable tech solutions\, such
|
||
as renewable energy monitoring systems and eco-friendly software developm
|
||
ent practices\,.\n3) Addressing the challenges faced by Outreachy in scali
|
||
ng its impact and ensuring the long-term sustainability of its programs.\n
|
||
Proposing strategies for enhancing collaboration with tech companies\, edu
|
||
cational institutions\, and funding partners to broaden Outreachy's reach
|
||
and support.\n\nCall to Action:\nThis session will urge stakeholders in th
|
||
e tech industry\, including corporations\, nonprofits\, and individuals\,
|
||
to actively support Outreachy's mission through sponsorship\, mentorship\,
|
||
and advocacy. Emphasizing the role of collective action in creating an in
|
||
clusive and sustainable tech ecosystem that benefits everyone.\n\nIn concl
|
||
usion\, this talk aims to inspire and mobilize the audience to champion di
|
||
versity and sustainability in tech by supporting Outreachy. By amplifying
|
||
Outreachy's impact through increased awareness and resources\, we can crea
|
||
te a future where opportunities are accessible to all and technological ad
|
||
vancements are driven by diverse perspectives and ethical considerations.\
|
||
n\nAttendees will gain insights into the transformative power of Outreachy
|
||
in fostering diversity and sustainability within tech\, along with action
|
||
able steps to contribute to its success. This talk seeks to ignite a conve
|
||
rsation on the pivotal role of inclusive initiatives like Outreachy in sha
|
||
ping the future of technology and society as a whole.
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us/schedule/presentation/229/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:You say you want a (web) revolution?
|
||
DTSTART;TZID=US/Pacific:20240803T163000
|
||
DTEND;TZID=US/Pacific:20240803T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:313@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Bryan T Ollendyke\nThrough web standards\, we have gi
|
||
ven developers the tools to build powerful web experiences. \nThrough web
|
||
standards\, we have given corporations the tools to build powerful custome
|
||
r bases.\nThrough web standards\, we have given the richest .0001% of plan
|
||
et earth the knowledge to make the money printing machine go brrrrr.\n\n"W
|
||
e'd all love to see the plan" as the song goes.. So let's try the statemen
|
||
t again.\n\nThrough web standards\, we can build amazing things\, but the
|
||
web is too hard for a 99.99% of earth to be creative with it. At least not
|
||
on their own without 3rd party\, proprietary systems (social media\, web
|
||
site tonight companies\, etc) that push high quality UX in exchange for ow
|
||
ning user-data and locking them into these solutions.\n\nHAX The Web seeks
|
||
to attack the problems of web creation\, portability\, sustainability\, a
|
||
nd complexity to lower barriers to participation for the common-person. HA
|
||
X\, short for Headless Authoring eXperience\, is an ecosystem of highly pe
|
||
rformant W3C spec Web Components\, 100s of them. These highly semantic tag
|
||
s for things like < video - player > or < multiple - choice > allow users
|
||
to add engaging experiences to the web in a sustainable format that is pla
|
||
tform free.\n\nWe can't just create tags and walk away though\, we must bu
|
||
ild better authoring experiences or these semantic tags will lay in the ha
|
||
nds of the few. That's why we built the < h-a-x > tag\, a series of web co
|
||
mponents that work anywhere that inject a powerful drag and drop authoring
|
||
experience that is able to understand the definition of other web compone
|
||
nts to allow users to place them on the page.\n\nBut what's an editor with
|
||
out a place to store that content? < haxcms-site-builder > is a headless C
|
||
MS that has PHP and NodeJS compatible back-ends but writes everything to s
|
||
tatic .html files and a site.json "database" for relationship data. You ca
|
||
n build HAXsites\, download them as a zip\, drop on any web server and the
|
||
y JustWork (TM).\n\n"You say you got a real solution"\n\nReasons people ra
|
||
ve about our ecosystem:\n- Migrate a HAX site by pointing to the URL\n- Cr
|
||
eate a new HAXsite from the headings / contents of a .docx file\n- Migrate
|
||
to HAX from gitbook / notion / other sources by pointing to the repo\n- "
|
||
Magic script" that detects undefined web components and automatically hydr
|
||
ates their definitions at run time\n- CDN mirrors that automatically hydra
|
||
te sites that lack the local JS files\n- As it's all static and cached in
|
||
an unbundled fashion so its high scale\, data / power saving\, easy to tin
|
||
ker with\n- 100% open source\n\nLearn about our ecosystem\, how Penn State
|
||
has integrated it into the classroom to have students contribute to the p
|
||
roject\, how it powers online courses\, blogs and websites\, and most impo
|
||
rtantly: how to get involved!\n\nWe seek Ubiquity for web content and expe
|
||
riences. We seek a revolution in web publishing. We seek to "HAX" The way
|
||
we Web.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/198/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240804T163000
|
||
DTEND;TZID=US/Pacific:20240804T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:343@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240804T163000
|
||
DTEND;TZID=US/Pacific:20240804T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:373@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240803T163000
|
||
DTEND;TZID=US/Pacific:20240803T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:341@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:How a hardware company supports arm64 open source software develop
|
||
ment
|
||
DTSTART;TZID=US/Pacific:20240801T163000
|
||
DTEND;TZID=US/Pacific:20240801T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:283@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Edward Vielmetti\nEquinix is not a typical contributo
|
||
r to the world of open\nsource software. Organized as a real estate invest
|
||
ment\ntrust\, it operates digital infrastructure around the globe\,\nkeepi
|
||
ng computing systems powered on and cooled in\noer 250 data centers.\n\nEd
|
||
will describe the current Equinix open source program's origins at \nPack
|
||
et\, an infrastructure-as-a-service company acquired\nby Equinix in 2020.
|
||
The pioneering Works on Arm program\nbrought bare metal access to the then
|
||
-new arm64 server\nplatform\, and welcomed developers to port their softwa
|
||
re\nand tools to that architecture at a time when these servers\nwere scar
|
||
ce.\n\nThe talk will cover lessons learned from a multi-year bootstrapping
|
||
\nprocess to bring arm64 to the data center. From programming\nlanguages t
|
||
o build tools to optimization techniques\, Ed will\ndiscuss the crucial ro
|
||
le that access to bare metal hardware at\nscale makes in enabling software
|
||
development to succeed.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/195/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Navigating Dependency Abandonment
|
||
DTSTART;TZID=US/Pacific:20240803T163000
|
||
DTEND;TZID=US/Pacific:20240803T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:335@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Bogdan Vasilescu\nMany developers relying on open-sou
|
||
rce digital infrastructure expect continuous maintenance\, but even the mo
|
||
st critical packages can become unmaintained. Despite this\, there is litt
|
||
le understanding of the prevalence of abandonment of widely-used packages\
|
||
, of subsequent exposure\, and of reactions to abandonment in practice\, o
|
||
r the factors that influence them. We did two research studies to address
|
||
this gap.\n\nFirst\, we interviewed 33 developers who have experienced dep
|
||
endency abandonment\, and learned that many felt they had little to no sup
|
||
port or guidance when facing abandonment\, leaving them to figure out what
|
||
to do through a trial-and-error process on their own. Often\, people used
|
||
multiple strategies to cope with abandonment\, for example\, first reachi
|
||
ng out to the community to find potential alternatives\, then switching to
|
||
a community-accepted alternative if one exists.\n\nSecond\, we quantitati
|
||
vely analyzed all widely-used npm packages and found that abandonment is c
|
||
ommon among them\, that abandonment exposes many projects which often do n
|
||
ot respond\, that responses correlate with other dependency management pra
|
||
ctices\, and that removal is significantly faster when a projects end-of-l
|
||
ife status is explicitly stated. \n\nThis talk reviews the results of thes
|
||
e two studies\, and ends with recommendations to both researchers and prac
|
||
titioners who are facing dependency abandonment or are sunsetting projects
|
||
\, such as opportunities for low-effort transparency mechanisms to help ex
|
||
posed projects make better\, more informed decisions.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/255/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:The University of California OSPO Network: Building a Multi-Campus
|
||
Efforts to Promote Open Source th
|
||
DTSTART;TZID=US/Pacific:20240802T163000
|
||
DTEND;TZID=US/Pacific:20240802T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:312@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Stephanie Lieggi\nThe growth of Open Source Program O
|
||
ffices (OSPOs) in institutions of higher education has helped advance the
|
||
development\, use and long-term stewardship of open source software and pr
|
||
actice. This new movement is also enabling new and unique pathways to furt
|
||
her the impact of university research and improving the educational opport
|
||
unities for the next generation of open source leaders. Since 2020\, more
|
||
than a dozen universities in the US\, as well as a number in Europe\, have
|
||
piloted OSPO efforts on their campuses with promising results. One of the
|
||
first OSPOs in a public university was at the University of California\,
|
||
Santa Cruz (UCSC). Building on the experience gained at UCSC\, in May 202
|
||
4\, six out of the ten University of California (UC) campuses began workin
|
||
g to build the first of its kind systemwide OSPO network. This ambitious e
|
||
ffort\, funded through the Alfred P Sloan Foundation\, allows each campus
|
||
to develop infrastructure that promotes individual areas of excellence whi
|
||
le leveraging the expertise of the entire network. \n\nThis presentation w
|
||
ill showcase the foundational work of UCSC in building an OSPO over the pa
|
||
st three years and will discuss the early work of the other campuses in wo
|
||
rking together to build the first of its kind\, systemwide OSPO. It will
|
||
also provide an initial blueprint for other educators looking to work coll
|
||
aboratively to promote open source approaches in academia. Participants wi
|
||
ll learn the benefits of creating a networked set of OSPOs as well as hear
|
||
about methodologies the UC network plans to employ for creating and maint
|
||
aining a system-wide open source community of practice.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/200/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Research Says.....Insights on Building\, Leading\, and Sustaining
|
||
Open Source
|
||
DTSTART;TZID=US/Pacific:20240802T163000
|
||
DTEND;TZID=US/Pacific:20240802T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:330@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Kaylea Champion\nHow do we know when a project is str
|
||
uggling? How can we build communities to sustain open source projects? \n\
|
||
nIn this beginner-friendly talk\, I will describe recent research findings
|
||
about successfully sustaining an open source project and the lifecycles o
|
||
f these projects. We know that open source software is fundamental to glob
|
||
al communication\, business\, education\, and more. This software is often
|
||
produced and maintained through dynamic organizations in which we have a
|
||
great deal of flexibility to choose our own tasks. But what we choose to w
|
||
ork on and what the global public most needs are not always in alignment.
|
||
What organizational structures\, governance practices\, and technology cho
|
||
ices are associated with increased risk? And given these circumstances\, h
|
||
ow might we work together to improve software quality and security? Let's
|
||
look at what we know about signs of trouble and strategies for success\, a
|
||
nd then discuss how the research community can better serve the needs of o
|
||
pen source.\n\nYou'll walk away with:\n* new ideas for taking action perso
|
||
nally and inside organizations\n* specific data-driven insights into how p
|
||
rojects evolve over time
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/247/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Balancing Innovation and Safety: Navigating the Dilemma of Open-So
|
||
urcing AI Models
|
||
DTSTART;TZID=US/Pacific:20240804T163000
|
||
DTEND;TZID=US/Pacific:20240804T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:359@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Abhishek Gupta\nThe recent trend of leading AI labs e
|
||
ither open-sourcing their models or restricting access has ignited a criti
|
||
cal debate: How should we share increasingly capable AI models? Open-sourc
|
||
ing\, the practice of making model architecture and weights freely accessi
|
||
ble\, has been a cornerstone of software and AI development\, fostering ex
|
||
ternal oversight\, accelerating progress\, and decentralizing control. Yet
|
||
\, as AI models become more powerful\, the risks of misuse and unintended
|
||
consequences escalate.\n\nThis talk scrutinizes the delicate balance betwe
|
||
en the benefits and risks of open-sourcing highly capable foundation model
|
||
s. While open-sourcing has historically been a boon\, we contend that for
|
||
certain future models\, the potential dangers may outweigh the advantages.
|
||
We propose that such models should not be open-sourced\, at least initial
|
||
ly\, to mitigate these risks.\n\nExploring alternative strategies\, we del
|
||
ve into non-open-source model sharing options that could safeguard the ben
|
||
efits of open-source while minimizing potential harms. Our recommendations
|
||
aim to guide developers\, standard-setting bodies\, and governments in es
|
||
tablishing safe and responsible model sharing practices\, ensuring that th
|
||
e progress of AI remains both open and secure.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/240/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240803T163000
|
||
DTEND;TZID=US/Pacific:20240803T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:351@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240803T163000
|
||
DTEND;TZID=US/Pacific:20240803T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:357@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Embracing your weird: Community Building through Fun & Play
|
||
DTSTART;TZID=US/Pacific:20240801T163000
|
||
DTEND;TZID=US/Pacific:20240801T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:279@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Tom "spot" Callaway\nI believe that the community tha
|
||
t plays together\, stays together. It sounds cliche (and it is)\, but the
|
||
first rule of community building is to remember that communities are made
|
||
of people\, not code. Over the last 15 years\, I've been experimenting wit
|
||
h creating opportunities for the communities that I am a part participated
|
||
in to play and have fun\, at first subconsciously\, but later\, mindfully
|
||
and intentionally. In this talk\, I will share some of the ideas I have t
|
||
ried\, along with some efforts that I have seen done in other communities.
|
||
I hope to try to convince you to invest in creating opportunities for you
|
||
r communities to connect as people through laughter and play\, and critica
|
||
lly\, and how that can help in growing the size\, resiliency\, and sustain
|
||
ability of open source communities.
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us/schedule/presentation/212/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240801T163000
|
||
DTEND;TZID=US/Pacific:20240801T171500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:321@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Break
|
||
DTSTART;TZID=US/Pacific:20240801T171500
|
||
DTEND;TZID=US/Pacific:20240801T173000
|
||
DTSTAMP:20240723T165420Z
|
||
UID:256@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Break
|
||
DTSTART;TZID=US/Pacific:20240802T171500
|
||
DTEND;TZID=US/Pacific:20240802T173000
|
||
DTSTAMP:20240723T165420Z
|
||
UID:257@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Break
|
||
DTSTART;TZID=US/Pacific:20240804T171500
|
||
DTEND;TZID=US/Pacific:20240804T173000
|
||
DTSTAMP:20240723T165420Z
|
||
UID:259@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Break
|
||
DTSTART;TZID=US/Pacific:20240803T171500
|
||
DTEND;TZID=US/Pacific:20240803T173000
|
||
DTSTAMP:20240723T165420Z
|
||
UID:258@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240801T173000
|
||
DTEND;TZID=US/Pacific:20240801T181500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:318@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240802T173000
|
||
DTEND;TZID=US/Pacific:20240802T181500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:302@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240801T173000
|
||
DTEND;TZID=US/Pacific:20240801T181500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:322@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Opening Remarks
|
||
DTSTART;TZID=US/Pacific:20240804T173000
|
||
DTEND;TZID=US/Pacific:20240804T183000
|
||
DTSTAMP:20240723T165420Z
|
||
UID:228@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Closing Remarks
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240801T173000
|
||
DTEND;TZID=US/Pacific:20240801T181500
|
||
DTSTAMP:20240723T165420Z
|
||
UID:260@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Protecting users against confusing licensing
|
||
DTSTART;TZID=US/Pacific:20240802T173000
|
||
DTEND;TZID=US/Pacific:20240802T181500
|
||
DTSTAMP:20240723T165421Z
|
||
UID:296@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Craig Topham\nThe Free Software Foundation's (FSF) GN
|
||
U family of General Public Licenses (GPL) is renowned for protecting user
|
||
freedom. It's concerning and confusing that some people alter licenses wit
|
||
h restrictions that attempt to render software nonfree. The GPLs v3.0 Sect
|
||
ion 7 allows the removal of unauthorized restrictions. The FSF may also en
|
||
force its copyrights and trademarks to stop unauthorized alterations to FS
|
||
F's licenses. This presentation covers the operation of Sec.7 and how FSF'
|
||
s copyright and trademark rights can help to protect against confusing use
|
||
of the GPL.\n\nThere are some great features in GPLv3/AGPLv3 Section 7\,
|
||
including the ability\nto create Additional Permissions — this allows li
|
||
censors to use the v3\nlicenses to create fine-tuned weaker copylefts: eve
|
||
n LGPLv3 itself is an\nAdditional Permission set applied to GPLv3. The li
|
||
censes also permit removal\nof “further restrictions” that take away u
|
||
sers' rights.\n\nWe've faced however a complex confluence of events relate
|
||
d to Section 7. The community of\ncopyleft experts are discussing and cons
|
||
idering what to do. Specifically\, we\nhave seen more than once vendors c
|
||
onfusing their users: by adding further\nrestrictions to GPLv3/AGPLv3 in a
|
||
way that confuses users about their right to\nremove those “further res
|
||
trictions” and the right to exercise their full\nsoftware freedom.
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us/schedule/presentation/259/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240801T173000
|
||
DTEND;TZID=US/Pacific:20240801T181500
|
||
DTSTAMP:20240723T165421Z
|
||
UID:280@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240802T173000
|
||
DTEND;TZID=US/Pacific:20240802T181500
|
||
DTSTAMP:20240723T165421Z
|
||
UID:290@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240803T173000
|
||
DTEND;TZID=US/Pacific:20240803T181500
|
||
DTSTAMP:20240723T165421Z
|
||
UID:358@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Leveraging open source softwares to incorporate open assignments i
|
||
n courses.
|
||
DTSTART;TZID=US/Pacific:20240802T173000
|
||
DTEND;TZID=US/Pacific:20240802T181500
|
||
DTSTAMP:20240723T165421Z
|
||
UID:303@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Rie Namba\nAt the University of British Columbia\, we
|
||
host a variety of open source software platforms to support instructors i
|
||
n adopting various teaching practices. This session will specifically focu
|
||
s on MediaWiki\, WordPress\, and H5P as tools for instructors interested i
|
||
n incorporating open practices into their courses and projects. We will go
|
||
over use cases\, and discuss the challenges and considerations we encount
|
||
er in supporting both instructors and students.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/197/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240803T173000
|
||
DTEND;TZID=US/Pacific:20240803T181500
|
||
DTSTAMP:20240723T165421Z
|
||
UID:352@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:333
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Why is Python Packaging
|
||
DTSTART;TZID=US/Pacific:20240803T173000
|
||
DTEND;TZID=US/Pacific:20240803T181500
|
||
DTSTAMP:20240723T165421Z
|
||
UID:336@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Moshe Zadka\n"Python packaging is a problem" is a mem
|
||
e. What is Python packaging? What is being packaged\, where is it sent fro
|
||
m\, and where is its destination? Why\, oh why\, can't I just produce a lo
|
||
ckfile?\nLet's dive into the details of Python packaging: the past\, the p
|
||
resent\, the challenges ahead\, and the proposed solutions.
|
||
LOCATION:329
|
||
URL:http://2024.fossy.us/schedule/presentation/216/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Talk
|
||
DTSTART;TZID=US/Pacific:20240803T173000
|
||
DTEND;TZID=US/Pacific:20240803T181500
|
||
DTSTAMP:20240723T165421Z
|
||
UID:324@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:No description
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Community governance models on small-to-mid-size Mastodon servers
|
||
DTSTART;TZID=US/Pacific:20240802T173000
|
||
DTEND;TZID=US/Pacific:20240802T181500
|
||
DTSTAMP:20240723T165421Z
|
||
UID:323@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Darius Kazemi\nDecentralized social media's rapid exp
|
||
ansion\, notably via the Fediverse and FOSS project Mastodon\, brings both
|
||
opportunities and multifaceted risks. For the first half of 2024\, indepe
|
||
ndent researchers and Fediverse denizens Erin Kissane and Darius Kazemi sp
|
||
oke to the admins and moderation teams of about a dozen Fediverse servers.
|
||
The research sought to identify current server administrators’ most pro
|
||
mising models for mitigating those risks and outline the biggest and most
|
||
important gaps in risk mitigation\, with the aim of helping the broader Fe
|
||
diverse level up governance quickly\, safely\, and collaboratively.\n\nThi
|
||
s presentation will cover what we found when we spoke to the people on the
|
||
ground whose job it is to govern social media servers of about 100 to 2\,
|
||
000 active users. We'll discuss the risks we identified in detail\, a set
|
||
of best practices for risk mitigation that have emerged on various servers
|
||
in our sample\, and discuss a set of variously intense interventions to a
|
||
ddress currently unmet needs and unmitigated risks to successful Fediverse
|
||
governance. We will also discuss the role of FOSS tooling and where the F
|
||
OSS community can step up to fill in the gaps in some of these needs.
|
||
LOCATION:328
|
||
URL:http://2024.fossy.us/schedule/presentation/250/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:GitHub Actions & Arm64: Enabling the world’s software to build o
|
||
n ARM
|
||
DTSTART;TZID=US/Pacific:20240801T173000
|
||
DTEND;TZID=US/Pacific:20240801T181500
|
||
DTSTAMP:20240723T165421Z
|
||
UID:284@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Larissa Fortuna\nTravel through GitHub’s journey to
|
||
supporting arm64 in GitHub Actions natively\, enabling the world’s deve
|
||
lopers to build\, test and deploy on Arm.\nWe will cover: \n-GitHub’s jo
|
||
urney to supporting Arm\n-Arm64 growth and presence in Azure\n-How the hos
|
||
ted arm64 runners work \n-Benefits for the OSS community\n-Sustainability
|
||
gains\n\nGitHub has long been the home for open source\, with GitHub Actio
|
||
ns being well-loved by the developer community. Driven largely by the voic
|
||
e of that community\, GitHub began supporting arm as a platform via self-h
|
||
osted runners first\, leading to the recent release of arm hosted runners.
|
||
Arm-based hosted runners mean that developers can build natively on Arm w
|
||
ithin GitHub\, removing the need for a cumbersome emulation layer. Without
|
||
the OSS community leading the charge\, the largescale movement to the arm
|
||
platform would not be possible. The growing popularity of the aarch64 pla
|
||
tform has caused large cloud providers to jump on the arm train as well\,
|
||
with Azure announcing arm chips in 2022. This talk will cover how the new
|
||
arm runners work\, how OSS can build on Arm within GitHub today and in th
|
||
e future\, as well as how arm processors can help individuals and companie
|
||
s reduce their impact on the environment.
|
||
LOCATION:327
|
||
URL:http://2024.fossy.us/schedule/presentation/190/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:Voluntarily Excellent When It Comes To Accessibility: A New Review
|
||
er-Friendly VPAT
|
||
DTSTART;TZID=US/Pacific:20240803T173000
|
||
DTEND;TZID=US/Pacific:20240803T181500
|
||
DTSTAMP:20240723T165421Z
|
||
UID:304@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Speaker: Chris Knapp\nVPAT and HECVAT (Higher Education Commun
|
||
ity Vendor Assessment Toolkit) are a partial solution to the problem of de
|
||
termining what competing products show better compliance with standards. T
|
||
hey are also good instruments for planning how to equitably roll out an ad
|
||
option with full understanding of the compliance gaps of the chosen produc
|
||
t. \nBut standard compliance information cannot tell the whole story. It i
|
||
s a snapshot in time that does not speak to the culture of the vendor\, wh
|
||
ere the product has been\, and more importantly\, where it is going. In th
|
||
is session\, we will detail Sakai’s multi-year effort to develop and imp
|
||
lement a community-sourced accessibility strategy\, that eventually led us
|
||
to produce our own VPAT\, and the steps we took to reimagine the standard
|
||
VPAT format with the VPAT reviewer audience in mind.
|
||
LOCATION:338
|
||
URL:http://2024.fossy.us/schedule/presentation/199/
|
||
END:VEVENT
|
||
BEGIN:VEVENT
|
||
SUMMARY:FOSSY 2024: Social Event
|
||
DTSTART;TZID=US/Pacific:20240801T190000
|
||
DTEND;TZID=US/Pacific:20240801T220000
|
||
DTSTAMP:20240723T165421Z
|
||
UID:379@2024.fossy.us
|
||
CATEGORIES:
|
||
DESCRIPTION:Official Thursday Night Event at Punch Bowl Social\n\n340 SW M
|
||
orrison St Suite 4305\, Portland\, OR 97204\nJust quick ~15 minute Max rid
|
||
e from PSU. All attendees are invited!
|
||
URL:http://2024.fossy.us
|
||
END:VEVENT
|
||
END:VCALENDAR
|