I enjoy making zines. I especially enjoy making zines about Jewish topics. When I saw that the Jewish Zine Archive was planning to hold a Jewish Zine Fest, I obviously got excited. I got so excited, in fact, that I signed up to host a pop-up event in Portland.
Since this event is my first time hosting an in-person event since the beginning of the pandemic, I figured I’d write up my experiences, along with what I’d do differently if I were immediately running another similar event.
I signed up to host a little late, on July 12. As a result, I had 30 days to get everything set up. As a result, I wanted to keep things as simple as possible: I figured just getting a chance to hang out, share zines, and maybe make a few new zines would be both fun and manageable, provided I could get the right location.
Books with Pictures, at 1401 SE Division Street, was my first choice. The store is one of my favorite places in Portland, not just one of my favorite comic shops. As it happens, the Eisner Awards agree with me and named Books with Pictures the best comic shop in the world while I was prepping for this event.
As far as event planning goes, Books with Pictures has a lot going for it:
an inclusive vibe that makes most people feel comfortable
good COVID-19 safety practices, including requiring masks within the shop
an outdoor garden space, along with a food cart pod and eating area
a space I’ve already seen folks navigate with a variety of mobility devices
Books with Pictures also stocks zines, so I figured the location would be a good opportunity for zine makers to connect with a stockist, if that was something any attendees wanted to do. People could also pick up more zines without anyone needing to schlep along a bunch of projects. Luckily, the garden was available for this event!
I received a few comments from attendees on the decision to use a space that isn’t explicitly Jewish (like a synagogue or a Jewish community center). The comments were positive and I think they are emblematic of a larger discussion of changes happening within Judaism right now. We need more great Jewish events and spaces that are outside of institutional Judaism.
I already had Books in Pictures in mind when I agreed to organize a pop-up, in part because I personally value being Jewish outside of buildings set aside for that purpose. I also chose Books with Pictures because I wanted a space that not only has an existing connection to zine communities, but also because zines are about accessibility and often appeal to communities that have been othered. Books with Pictures’ whole shtick is creating inviting spaces for folks who have been othered by the standing comics community.
I was also aware from the get-go that some of the discussions I hoped to have at the pop-up wouldn’t be the best fit for most of the Jewish institutions around Portland. Like many other Jewish institutions, a lot of Portland’s synagogues and other Jewish organizations are committed to Israel and Zionism. Even mentioning Israeli nationalism or oppression of Palestinians is off the table in those sorts of spaces. That’s a problem, especially for me since some of my own Jewish zines focus on dismantling nationalism. So I wanted a space that allowed for discussions that just wouldn’t happen in more official Jewish spaces.
I prioritize making events as accessible as possible. For this event, my biggest concerns were
ensuring COVID-safety for attendees who are high risk, including immunocompromised folks
keeping the costs of attending as low as possible
guaranteeing access for folks using mobility aids, because outdoor spaces can be harder to navigate
Of course, providing access in one way can limit other kinds of accessibility. I know that there are probably people who didn’t feel they could participate in an outside event — there’s no way to control factors ranging from outside allergens to high levels of sensory input. However, I feel that focusing on the aspects of access listed above ensured as many people as possible would be comfortable at the event.
I described access efforts in the event landing page, as well as when discussing the event. I also included contact information for folks who needed access options beyond what I initially set up.
Attendees were required to wear masks at the event, which was outside. Working with Books with Pictures was easy, as the store requires shoppers to wear masks and advocate for mask use even at their outside events. They’ve held a bunch of events in their outside spaces, including their garden and on the sidewalks around the business, so they’ve got practice with the steps necessary to make outdoor spaces accessible (like making sure folks can get to the indoor bathrooms without too much hassle). That made ensuring mobility access much easier for me.
All attendees wore masks and no one shared any complaints. All I needed to do was set out spare masks where folks could grab them, and remind a few folks to mask up as they arrived. While I didn’t specifically ask attendees their thoughts, I do know at least a few folks came who are even more cautious than I am. That makes me feel like I hit my goals. From what other event organizers have shared on social media, I think a lot of people are willing to mask up, provided they’re asked to do so.
Zine events are typically inexpensive to participate in. Zine culture revolves around making and sharing work that costs a fraction of the cost of professionally produced work. But even a free event can cost money to participate in — expenses like transportation to get to and from a location or copying zines to swap can make some folks feel like they can’t participate.
With that in mind, I decided to offer a few stipends of $25, structured to be as low-effort as possible (both for me and for folks requesting the stipend). The application was a form asking for name, contact information, and payment options. I limited the payment options to methods that were easy on me (Venmo, CashApp, or cash at the event).
One person requested a stipend and I was able to provide them with funds before the event. In my experience, small stipends make a big difference to the folks who request them. I’ve had minimal issues with requests from people who may not actually need stipends, though that may be due to the relatively low dollar amount of this sort of stipend.
I’ve done enough work enforcing community codes of conduct that I plan for worst case scenarios for even the smallest of events. I tweaked the code of conduct template I use for meetups. One tweak I prioritized was ensuring that I’d be able to address anyone responding to support for Palestinians with accusations of anti-Jewish bias.
Speaking of anti-Jewish bias, one of my concerns about running this event is the growing bias and violence against Jews in this country. I didn’t think that a zine meetup presented a huge risk, but I wanted to make sure to mitigate that risk as much as I could. I reviewed social media thoroughly for potential issues (including checking up on prospective attendees) and planned for contingencies.
In the end, we had no reported problems with attendees’ conduct or problems from outside sources.
Even though I haven’t been running events lately, I still maintain a stash of certain supplies. I found three separate containers of name tags when I was preparing. I also have a fair amount of zine-making supplies on hand at any time. However, I did make a trip to Scrap in order to bulk up my supplies — and also to have a good excuse for visiting Scrap. I got a wealth of different kinds of paper (including two full reams of printer paper, one pink and one green) and didn’t break the $20 mark.
I did make some swag for the event — I haven’t had an excuse to pull out my button maker in a minute, so I had to make pins! I also made a mini-zine of relevant resources, as well as a short version of the event’s land acknowledgement and code of conduct. Of course, I printed the minizine on some of the pink paper I scored at Scrap. Here’s the mini-zine, if you’d like to check it out!
Here’s what I took with to the event in terms of supplies:
Event logistics: Name tags, sharpies, extra masks, extra phone chargers, and a spare battery
Zine-making supplies: A variety of types of paper, scissors, stapler, glue, stickers, colored pencils, crayons
Swag: Pins and mini-zines
My own zines to swap and share (as well as a few zines in my collection I wanted to show off)
All told, I spent under $50 to run the event. Of course, someone without a stash of event supplies or with more stipend requests might need to spend a bit more to run an equivalent event.
The Portland Jewish Zine Pop-Up was a resounding success. I was expecting a turnout of perhaps 15 people, but we had more than 35 attendees! I think everyone had a good time and got to engage in a way that worked for them.
A few highlights that really excited me:
A kid made their first ever zine!
Three people came from Seattle!
Eight people have asked me when the next Jewish zine meetup is!
Interestingly, only a handful of attendees were also going to the Jewish Zine Fest — the rest of the attendees were just present to hang out with other folks interested in Jewish zines.
I haven’t yet decided on whether to host a second Jewish zine pop-up, despite the requests to do so. If I were to do another one, I definitely want at least one co-organizer! I’m pretty sure that this event was relatively easy to run because of my excitement — a follow up event may be a little harder to put together.
But I am already thinking about what I might change for a follow-up event. Here are a few of the things I’m thinking about:
Signage — I somehow forgot all about signage during my prep work. Putting up some signs to suggest people wear name tags or direct folks to the restroom is just good sense.
Land acknowledgement — I always feel awkward about land acknowledgements. They’re important, but since I’m not Indigenous, I worry about getting land acknowledgements right. Jewish spaces add an extra layer of complication and I want to do more research and think more about how to improve on the land acknowledgement I offered.
Cold weather space options — Books with Pictures’ garden is an amazing space, but it will likely be a little less perfect during winter months.
I gave a 25ish-minute talk at PyCascades 2022 covering a Django app that Jamey Sharp built and I supported for the Portland GDC. My script and slides are below. Please note that this is not an exact script; I had to cut some material from my talk during recording to get it closer to the time limit that I’ve left in this version of the script. Consider it a little bonus material! You can watch a video of the talk on YouTube or below:
I’m here to talk about my experiences doing bail and legal support for protestors arrested in 2020 and 2021 during the George Floyd Uprising. Since I’m White and I’m talking about supporting people arrested while asking for racial justice, I need to say that I’m only talking about the specific project I worked on. I didn’t organize or lead protests or anything like that. Please consider this a report back on the small chunk of mutual aid that I worked and nothing more. Furthermore, I did not do this work alone. This talk covers the efforts of dozens of people who I am proud to work alongside.
This talk covers technical topics, but it also includes discussions of institutionalized racism and police violence. If you’re not in a place where you can hear about these topics, please consider stepping away for the moment. You can always watch the recording later.
On May 25th, 2020, George Floyd went to a grocery store in Minneapolis and made a purchase. Thirty-one minutes later, he was dead at the hands of a police officer.
On May 26th, hundreds of protestors took to the streets in Minneapolis, demanding accountability for Floyd’s death — and the long list of other deaths of Black people at the hands of police officers.
On May 27th, a small group of Black and Indigenous women gathered in Portland at the Multnomah County Justice Center to hold space in memory of Floyd.
On May 28th, around 100 people gathered at the same building, with some people sitting in the doorways. Riot police violently pushed people away from the building.
On May 29th, over 1,000 people gathered at Peninsula Park in North Portland and marched into downtown to gather again at the Justice Center. Portland police officers arrested 13 people.
The Portland General Defense Committee immediately started posting bail for protestors who were arrested. The GDC started as a legal defense organization for union organizers and workers. Members of the Industrial Workers of the World founded the GDC in 1917. The Portland branch started in 2017 and has provided jail and legal support to protestors since its start. We did the same things for folks arrested on May 29 that we did for past protests: We made a spreadsheet of people arrested and started figuring out who needed bail money, including prioritizing arrestees by relative risks at the jail. Those risks included whether the person arrested was Black or Indigenous, LGBTQ, or had health risks.
Dealing with thirteen arrests at once was a stretch for us. At that point, we were used to two or three arrests at one event and supporting maybe two people with ongoing cases at any given time. We were able to pull together bail funds from members and friends, but we knew we would need to raise money to cover legal costs and reduce the bail burden we’d already taken on. Prior to 2020, the Portland GDC had a budget of a few thousand dollars per year. I put up a GoFundMe early on May 30th. By the end of that day, police had arrested 64 people.
Protests continued every night into January 2021. I’ve heard estimates that 70,000 people participated over those eight months. Portland still sees several protests and rallies around racial justice every month. Local police and federal law enforcement agents made over 1,000 arrests at protests in Portland. They beat, gassed, and otherwise hurt countless protestors and journalists.
As you can guess, gathering and managing information on who had been arrested, who needed bail money, and where each person was in the legal process outgrew a single spreadsheet rapidly. On June 6th, 2020, I contacted on Jamey Sharp, who I knew from various tech-related things here in Portland and asked for help. I was deep in the weeds at that point and basically gave Jamey free rein to figure out how to replace this terrible spreadsheet with something that could manage information better. We were not in a position to pay Jamey and I am eternally grateful he was able to help us. The Portland GDC still has minimal resources beyond dedicated volunteers and some funds earmarked for legal expenses. While we eventually raised over a million dollars, that money is all for to bail and legal expenses and therefore not available for administrative costs like building software applications.
One of the reasons I reached out to Jamey is because of his experience scraping all kinds of websites. He was unable to speak at this event, but I encourage you to check out his project Comic Rocket at comic-rocket.com, which is one of the places he got that experience. I figured Jamey would be able to automate some of our information gathering, letting volunteers focus on things technology can’t do. Jamey’s experience meant that he had the first iteration of our app up and running on June 12, with all the notes in our terrible spreadsheet imported and ready for us to work on.
As the summer of 2020 wore on, we added users and functionality and scaled up a little just about every day. The Portland GDC’s workflow constantly changed based on capacity and the growing number of arrests. This was not a situation where a developer got to make nice neat little upgrades and slowly roll them out to users. This was duct-taping steering to an airplane that was already in flight and occasionally doing barrel rolls.
The web app we use for the Portland GDC’s work can be thought of as two key pieces. Most people only ever see an interface to a database, listing people who were arrested with a bunch of fields about their contact information, the status of their court case, and various other details. It’s an amped-up, search-friendly spreadsheet.
But the app also pulls in information from several sources, automatically prepopulating many of those fields and providing updates to volunteers. Those sources generally don’t have APIs, so the app scrapes them. The sources include Oregon state court records and jail records from the Multnomah County Sheriff’s Office. MCSO is responsible for processing anyone arrested on state charges and many of those arrested on federal charges in Multnomah County (which includes the majority of the city of Portland).
The information we need to do our work comes in an absurd variety of formats, with an equally absurd set of access requirements. For instance, a lot of court information is in PDFs that are scans of printed documents, often with important handwritten notes like “Dropped” to indicate a suspended charge.
Federal courts work differently than state courts. and have less public information that can be scraped. Federal court cases go through PACER, which is an app that charges 10 cents per page when you access a document, as well as fees for search results and non-case specific reports. 18F, the federal government’s in-house technical consultancy, has looked at upgrading the system but their report is best summarized as no one knows how PACER works, it’s unmaintainable, and we need something entirely new and built from scratch.
Important information also disappears regularly. MCSO’s arrest information will change with no warning and no record if someone at the jail updates information, including during the booking process. Records of arrests drop off the site entirely after a few weeks. There’s also no listing of citations — incidents where protestors are charged with a crime, usually a misdemeanor, but not arrested. And the information is available is often full of errors. Information collected during arrests is the worst. We’ve known for a long time that law enforcement agents will “tweak” certain information they collect to make their own stats look better. But the data we saw from protests made those changes much more obvious. Police record the races of people arrested incorrectly constantly. In particular, we’ve seen glaring errors around the race of people of color, which have allowed the Portland Police Bureau and other agencies to claim that almost all protestors arrested in Portland are White. We’ve also seen names, genders, physical descriptions, and more recorded incorrectly.
We’ve had to figure out the meanings of certain data through trial and error because there’s not any documentation available. MCSO also uses different terms and definitions for specific charges than the Oregon court system uses, to the point that our app only grabs the statute number a person is charged under and maps it to correct charge information in our database.
This system is especially infuriating when you realize that it’s on the people who are arrested to correct any errors. Since errors can have consequences that include being kept in jail, they can be impossible to correct without expert legal help. People who are arrested are also expected to stay up to date on their cases, without any of the modern notification systems you might expect. If someone’s charges are suspended, that person is instructed to call the district attorney’s office at least monthly to check if their charges have been reinstated for at least the next two years. If they don’t, they’ll likely miss a court case which will result in a warrant being issued for their arrest and other terrible outcomes. COVID has also meant that policies change constantly, often without online notice. Even before the pandemic, details around court hearings routinely changed on the day of, but as things moved online, everything about legal processes got more complicated.
These websites are also delicate. Some were constructed by contractors trying to keep costs down, while others are built by companies that know that they can take advantage of people who are incarcerated without anyone important caring.
Django and Python were the logical choices for this project for a few reasons: First, Jamey had already built Django apps and was pretty familiar with the framework. And while I haven’t built a whole Django app by myself, I’ve gone through some workshops. Second, Django’s built-in admin interface makes managing a bunch of structured data really easy. The user interface enables anyone to edit that data without tons of training. Jamey was also already familiar with Scrapy, a Python scraping framework, so he could get that set up with a Django-based app quickly.
One of the pieces of information we need to grab automatically are upcoming court dates. The Oregon court calendar site is particularly irksome. Jamey jumped through lots of programmatic hoops to get that scraper running: the site limits search to 550 results, without offering any “next page” button. The scraper can’t just grab all calendar entries over the next 3 months without hammering the site harder than we want to. So the solution is a little complicated: the scraper looks at the specific case numbers we care about, then groups all the cases with the same starting numbers, trimming off the last two digits. When the court calendar is queried with those truncated group numbers, there are a max of 100 active cases returned. By batching together cases, the scraper minimizes the number of queries — though Jamey has pointed out that if whoever designed the court calendar site had just limited to search results to 1,000 rows instead of 550, he could have cut the number of queries even further.
Of course, there’s still plenty of work that requires a human touch. We have to audit our data regularly, adding in pieces that MCSO missed or that come from conversations with the protestors we’re supporting. Django has made those audits relatively simple, even though they still require a lot of reading through information for the humans involved. We can use tags for indicating the specific categories that need auditing at a given time, as well as sort and filter information in a variety of ways.
The Portland GDC is not a large organization, even now. We’re also not an especially technical group. We recruited volunteers to work on legal support in July and August of 2020, and more volunteers have joined since then.
All onboarding, and all other work for that matter, happens remotely. Django’s user interface is reasonably simple right out of the box and while we’ve tweaked the user experience lightly, Django uses a visual language in interfaces that is very similar to what’s considered “standard” on the internet.
I created our technical onboarding process. Another person was responsible for walking new folks through specific support situations, communication norms, and our policies, so I was able to focus just on getting people on to the app.
I do a video call with each new user that includes a 30-minute walk through of the app. We actually don’t always need the full 30 minutes, but we set up user accounts during that session and getting folks through their first time logging in was often hard — in fact, it was the point our users struggled with the most. That’s because some of our account setup emails wind up in spam. So I built in time to search around for emails. I also limited onboarding sessions to a max of three new users because I only have enough patience to go through three people’s spam folders at a time.
During the walk through session, we go through each section of the app as well as our documentation. Our documentation is a shared Google Doc with screenshots and written descriptions — it’s not fancy, but it does contain answers to basically every question anyone has asked me about the app.
We tweaked the app as users asked questions and needed more features. Jamey wisely pushed back every so often and reminded us of our options, even deleting certain features when they were no longer needed. If Jamey hadn’t provided a technical voice of reason, we’d probably have a full-featured CRM at this point, even though that’s not what we need.
And when I checked in with our users while getting ready to give this talk, they told me that the app was intuitive, friendly, hard to break, and empowering. Users felt empowered to work with data, even if they didn’t come in knowing tech, legal proceedings, or activism. Some features still don’t get used as much as possible. But volunteers say this is more about the time available to do work, not due to difficulties with the app. People also like that they don’t feel beholden to the app and that it’s not judgmental about unfilled fields. One person even said that using the app reminds them of using a message board because they can see the notes and work of other volunteers, which helps them stay connected through all this remote work.
We realized early on that we were sitting on a pile of valuable information. While most of what we pulled together was publicly available, it wasn’t combined in this way anywhere else. Between what we scrape and the information we add from the people we’re supporting, we created a doxxer’s paradise. Not only do we have data like physical addresses and phone numbers, but we also have notes on who needs what kinds of help. The risks of holding this information are massive. If someone with bad intentions got access, they’d be able to easily harass people both online and offline. We have an ethical obligation to mitigate every risk we can and to protect this information. The alternative is compounding the harm legal systems are already doing to folks.
We also faced a lesser risk of losing access to the sources where we pull information from. That did happen several times — not only does MCSO remove information from their arrest records, but the Oregon court system stopped allowing access by anything with an IP address located outside of the US, which coincidentally enough included us at the time. Jamey found us work-arounds, but I’m always waiting for the next time one of these systems changes their access controls. We also faced concerted attacks on any tool we publicly use: we dealt with numerous malicious reports to GoFundMe, Twitter, our email provider, and more.
We reduced our risks in several ways. First off: we obviously didn’t go around telling people about this app. After all, if someone is attacking your email, they’ll attack every other system they can find related to your organization. We’re facing less attention online now, so talking about the app here is a calculated risk that we’re comfortable with — but I’m not telling you who hosts the app or other important details to keep those risks to a minimum.
We also look closely at everyone who gets access to the app. Our due-diligence process for volunteers includes an in-depth internet background search and confirmation of the information we find with shared connections where possible. Jamey was also able to set up multiple types of user accounts so that we could limit each volunteer’s access to information they actually need to do their work. If, for instance, someone is writing letters of support to people who are currently incarcerated, they can only see those people in the system who they’re writing to. Those volunteers don’t get much more than an address and some biographical information.
Technical security is, of course, an aspect of risk mitigation. Django has good security features out of the box, assuming you use them. By using Django, we could use built-in security options and also access documentation that we could adapt to explain what was going on behind the scenes to volunteers. But the most important step to managing our security concerns was our effort to avoid collecting information that we didn’t feel we could protect — and that policy would have been the same no matter what framework or language the app was written in. No technology choice is as important as defining what data you’ll collect and how it will be handled.
One of our biggest ongoing issues was burn out. Basically everyone burnt out over the course of 2020 and 2021 — doing legal support just made us burn out faster. We’ve had higher turnover among volunteers than I’d like, but this is hard work. Even though we don’t need to worry too much about gathering and processing data, we’re dealing with emotional situations and even the best outcomes for the people we’re working with involve lots of time dealing with an adversarial legal system.
The only way to handle the fluctuations in capacity is to document EVERYTHING. Everything that happens in an individual case gets recorded in the app. Everything about the app gets documented, too. Our documentation isn’t fancy: it’s a document that I add questions and answers to whenever an app user asked me something. I lifted some pieces out of the Django documentation and reworded them a bit to ensure our users understood how to handle a problem even if they didn’t come in with a ton of technical experience. And any time an edge case came up, I took tons of notes.
I did worry a lot about what would happen when Jamey and I burned out, however. We both managed to hang on until the app was basically stable and there hadn’t been any new features needed in a while. I did want to make sure that someone had enough knowledge to at least decide if a situation was an emergency and to have someone who could step up if such an emergency came to pass. Luckily, our most technical volunteers reached a point with the app where they seemed capable of handling questions and I drafted a back-up developer who would be willing to handle emergencies before I had to take a break.
I think the work I’ve done with the Portland GDC over the past two years is some of the most important work I have done or will do. We put together legal support for hundreds of protestors out of Django, duct tape, and donations from strangers. We did our part to ensure that protestors could be in the streets for months on end and reduced the risks they faced. One of the most meaningful measures of our work, at least for me, is that Rodney Floyd, George Floyd’s brother, thanked Portland protestors specifically last April. He said the support of protestors meant so much to their family and that staying in the streets helped ensure his brother’s killers faced justice.
So here’s where everything stands as of February 2022: Mike Schmidt, the district attorney here, suspended most protest-related charges. That’s not the same thing as dropping charges entirely. Instead of dropping charges, he’s just not currently prosecuting charges. The DA has the option to reinstate suspended charges for years to come. He’s already reinstated a few. By suspending charges, rather than dropping them, the state also gets to hold on to bail money and evidence until the charges age out. And since almost $700,000 of the money the Portland GDC raised went to posting bail for hundreds of protestors, that money is not available for legal fees or bail for future protests for an indeterminate amount of time. Schmidt is considered a very progressive DA and he’s still chosen to hold protest-related charges over protestors’ heads for years to come.
The federal district attorney, Scott Asphaug, hasn’t been so nice. Several protestors are facing federal charges, with Black and Indigenous folks facing the harshest penalties. There are at least three such cases which will be going to court in the next few weeks with each defendant facing years in jail. It’s also worth noting that Asphaug previously worked for the Portland police union to get police officers out of trouble during internal investigations and the U.S. Department of Justice does not consider that relationship a conflict of interest.
The city of Portland, as well as several federal agencies, are facing lawsuits from many of the protestors who police attacked. Residents of Portland who were not involved with protests but were teargassed or otherwise harmed are also bringing their own lawsuits. While a few cases have already been settled with payouts by the relevant government agency, many seem to be going to court.
While Portlanders are no longer protesting in the streets every night, cases related to the George Floyd Uprising won’t be over for months, perhaps even longer. The Portland GDC is still doing legal support and expects to be doing prison support for folks unjustly incarcerated over these protests for years to come.
I hope you found this talk valuable, both in terms of learning about launching a Django app with minimal resources and even less time and in terms of understanding the amount of work it takes to support protestors through arrests and court cases. The Portland GDC continues to support people arrested at protests in 2020 and 2021 and if you’re able to, please consider donating to help cover the legal costs that many protestors are still dealing with. You can donate through CashApp, Venmo, or by mail to PDX GDC, 2249 East Burnside Street, Portland, OR 97214.
I’ve launched a new project that I’m excited to share with all of you.
PDX.Vote rounds up news related to the 2022 elections taking place here in Portland, Oregon. It also publishes long-form articles about specific aspects of Portland’s politics. Please support this work financially.
If you’re interested in my thoughts behind this site and my plans for its future, keep reading!
Why a news site focused on elections?
I’ve always followed local politics pretty closely. One of my first paid blogging gigs was covering the 2008 presidential election, which really helped me understand that local politics impact our day-to-day lives more than most things happening in Washington, D.C. I was also an election judge in Maryland and saw first hand how hard voting was for some folks.
I also think that a lot of the media covering local news just aren’t covering local elections in any real depth. That’s partially due to the financial constraints on a lot of news media. But there’s also a sense that nonpartisan groups like the League of Women Voters write great voters guides that provide enough information for most voters to make their decisions. Now, I read the Portland League of Women Voters’ guides cover to cover and think they’re a great resource — but those guides are put together by folks who are trying hard not to influence the outcome of the races they’re covering.
Local elections decide matters of life and death importance here in Oregon, from the oversight of police forces and the violence they enact to the budgets for supportive services for folks without stable housing. But a nonpartisan report doesn’t tell voters whose policies are likely to increase deaths or save lives. We deserve better information.
I’ve already soft-launched PDX.Vote with three key types of coverage:
Digests of news related to the current election cycle
Weekly calendars rounding up important meetings, deadlines, and other dates relevant to local politics
Articles that go deeper into specific races, as well as important context for upcoming elections
At the moment, I’m doing all of the writing for the site. But with the official launch of PDX.Vote, I’m accepting pitches for articles. I’m also actively reaching out to people who are able to talk about political issues in ways I can’t. I’m privileged enough to be able to fund my startup costs and an initial writers budget so that I can pay for these contributions. My goal is to share election coverage from as diverse a group of contributors as possible. In terms of numbers, the first metric I’m measuring is the percentage of contributors from different racial backgrounds than my own, which I plan to report back on quarterly. It’s not a perfect metric, of course, but it’s one that I’m confident I can track as the only administrative staff for the site, as well as one that will give a top-level view of how well I’m doing at recruiting writers with different experiences. If you’re interested in writing for PDX.Vote, please contact me.
While I can cover the initial costs of setting up the site, I do need community support to publish this coverage. My first financial priority is covering the expenses of running the site, including the media insurance policy I needed to feel safe doing this work. My second financial priority is paying contributors. It would be nice to be eventually rewarded for my labor, but that’s much farther down the list.
So how can you support PDX.Vote? Currently, you can give us direct financial support. The current options are a one-time payment of $10 or a recurring monthly payment of $10. I’ll be making other options, such as printed voter guides, available later on. However, I will neither be accepting advertising on the site for the foreseeable future nor putting up a paywall in front of content. Both options make me feel uncomfortable when we’re talking about election coverage: Every resident (including non-voters) should be able to access information about the governments under which they must live, without paying for that information. And advertising tends to affect what news media publish, even without any explicit expectations. While I’m happy to discuss financial support in larger amounts, I do want the site to be primarily funded by the people I hope will most benefit from having free coverage available — people who can afford to throw $10 towards PDX.Vote, rather than people who can afford to spend thousands of dollars a year on multiple newspaper subscriptions.
Because I’m talking about elections and political power, I think it’s important to be as transparent as possible, especially about finances. I’m making the site’s financials available on a monthly basis. I’ve also included a transparency section on the ‘About’ page, including my own donations to candidates and political committees. I’ll be asking contributors about their connections to candidates and political committees and adding that information as I deem appropriate and safe. I’m also explicitly talking about my own biases and the site’s slant as a whole: I’m a leftist and you should expect PDX.Vote’s coverage to lean left as well. Furthermore, I am critical of even leftist elected officials — rather than being invested in maintaining a status quo, I want us to rethink what governance looks like and limit the harm the state can cause to each of us.
What are my long-term plans?
Well, a lot depends on how many folks find PDX.Vote a useful resource. While I’m confident I can put together regular updates through the November 2022 election, I’m not yet sure if I’ll continue the site after that time. Financial sustainability and reader interest will probably be the determining factors.
I would love to continue to build on the site’s coverage long-term if I can. I’m already working with a few contributors for one-off pieces and I want the opportunity to bring in some folks as regular contributors if I can afford to pay them for their work. I see two key areas of expansion: first, geographic coverage and, second, linguistic coverage. Currently, PDX.Vote covers Multnomah County elections, because that’s the county that covers the largest chunk of the city of Portland. It’s also the county I live in. I’m working on coverage of Washington and Clackamas Counties because they’re part of Metro, along with Multnomah County. It’s hard to cover Metro races without having at least a working knowledge of Washington and Clackamas Counties. I’d like to eventually cover all seven counties that include Portland and its suburbs, but that’s beyond what I can do without regular contributors. Bringing on folks to cover these additional counties will require finding reporters already living in each county, so that we can read coverage from folks actually impacted by county politics. And I have to admit that expanding coverage to Clark County (and Vancouver, Washington) will probably be low on the list. Clark County is important to understanding Portland politics, but it’s in Washington State and therefore plays by a different set of rules. Adding Clark County coverage to PDX.Vote will take more work than adding another Oregon county.
I also believe that expanding coverage outside of the English language is crucial. Portland residents speak a wealth of languages and deserve news in languages they understand. Translation is expensive and I don’t expect to be able to publish every article in multiple languages right away, but that’s my ultimate goal. Currently, I see Spanish, Vietnamese, and Chinuk Wawa translations as priorities. While the community of Chinuk Wawa speakers in Portland is smaller than the communities that speak several other languages, Portland sits on land that rightfully belongs to Indigenous tribes, including Chinookan tribes. Chinuk Wawa is a jargon used by many tribes. While I’m not Indigenous, I believe in the Land Back movement. Providing news in Chinuk Wawa seems like a tangible step towards respecting Indigenous sovereignty that goes deeper than a simple land acknowledgement.
I’m not sure how much I’ll be able to accomplish until I see what sort of financial support community members are prepared to provide. But I will do everything I can afford to do that will make local political information more widely available here in Portland. I’ll keep y’all updated.
Content warnings: Discussions of death, genocide, state violence
I made a short zine exploring new ways to observe Tu B’Shvat, which you can read on my Twitter or grab as a PDF. There are both print and screen-friendly copies of the PDF at that link. Please note that I wrote this recently enough that I have not been able to run it past a sensitivity reader yet — all errors are my own and I fully expect to have a new version in time for Tu B’Shvat 5683.
If you’re interested in reading further on the topics I mention in the zine, here is a list of websites, articles, and videos that I recommend, broken down by topics. The sources I used to create my zine are included here, along with those covering details I couldn’t fit into just eight pages.
“Tu B’Shvat and Malida” (video) — This short video from the Institute of Jewish Experience covers the Bene Israel custom of making malida (a sweet treat made of pressed rice and fruit) for Tu B’Shvat, as well as a summary of the history of the Bene Israel community in India.
“Tu B’Shvat? Why Not?” (article) — Linda Gritz, from the Boston Workmen’s Circle, documented the process of creating a secular observance of Tu B’Shvat.
“Tu B’Shevat in the Age of Ecofeminism” (article) — This article includes several ways to observe Tu B’Shevat while considering both climate change and feminism. Writer Steph Black highlights options like a Reverse Tashlich ceremony to clean up rivers.
“Tu Bi’Shevat” (website) — Ritualwell has an entire section of their website devoted to meditations, liturgy, and other suggestions for observing Tu B’Shvat.
Resources on Indigenous land return
“Remothering the Land” (video) — Patagonia produced this 10-minute film to discuss the concept of ‘rematriation’ (or ‘remothering’ the land) using sustainable agriculture techniques with William Smith, land steward of the Village of Huchiun, and Nazshonnii Brown-Almaweri, land team member of the Sogorea Te’ Land Trust.
“#LandBack is Climate Justice” (article) — Restoring stolen lands to Indigenous sovereignty counteracts climate change, as documented by the Lakota People’s Law Project.
Braiding Sweatgrass (book) — Robin Wall Kimmerer’s collection of essays on Indigenous ecological knowledge provides a foundational guide. At the time of compiling this list, I haven’t finished reading Braiding Sweatgrass but I already find it informative enough to recommend.
Landback U (website) — The Landback Movement created a series of courses on land struggles in different locations to build a foundation of knowledge about Indigenous sovereignty. The organization accepts donations to continue their work.
“Tu Bishvat: Dish with One Spoon” (article) — Mazon Canada published this article on the Haudenosaunee concept of ‘the Dish with One Spoon,’ a way to discuss the interconnected relationship between humans and land. The article also links to a video where historian Richard Hill covers some aspects of Haudenosaunee culture and history that’s worth watching.
“Planting the Promised Landscape: Zionism, Nature, and Resistance in Israel/Palestine” (article, PDF) — This academic article is long at 50 pages, but author Irus Braverman provides important insights into the ways that Jewish campaigns to plant pine trees in Israel have been used to remove Palestinian presences from the land and are iconic to the Zionist experience. Pine trees are not native to Israel and act as a method to make the land more comfortable to Ashkenzai settlers.
“Why I no longer donate to the Jewish National Fund” (article) — This short article touches on some of the topics covered in more depth in the source above. Writer Matthew Gindin looks at the militarism and greenwashing associated with the JNF, the leading organization planting pine trees in Israel.
“Cultivating Resilience: Growing Olives in Palestine” (article) — Emily Baron Cadloff’s article on how Palestinian olive farmers have been forced to watch their trees systematically destroyed (along with their livelihoods) is a difficult but necessary read for American Jews.
“Trees for Life 2021 Report” (report, PDF) — The Palestine Fair Trade Association’s annual report on its Trees for Life program describes the organization’s work distributing more than 37,800 seedlings of native trees to more than 350 Palestinian farmers. The organization also educates farmers on regenerative farming and the use of native seeds.
Rooting Resistance (donation page) — For U.S. donors interested in contributing to the PFTA’s Trees for Life program, the U.S. Campaign for Palestinian Rights offers a donation process that doesn’t require you to figure out international payment processors. Every $25 donated equals one tree sapling planted. Guidestar has reviewed the organization.
Resources for working in nature, including agriculture
Cultivating Culture 2022 (conference) — This upcoming conference includes sessions on Jewish relationships to agriculture and food. Tickets start at $36.
Friends of Trees (website) — Friends of Trees plants trees in the Portland metro area (as well as other parts of Oregon) and have streamlined the process. If you’re considering planting trees here, working with Friends of Trees is the easiest option. I’ve used their services in the past. And if you’re not in a position to plant a tree yourself this year, you can donate to the organization to help plant trees elsewhere in the city.
Native Plants and Trees of Oregon (brochure, PDF) — This list of trees native to Oregon offers options to consider if you plan to plant trees locally to observe Tu B’Shvat.
“Approved Street Tree Planting Lists” (article) — The government of Portland requires trees planted in the city to be permitted and be on the approved list of trees. This article covers their requirements.
Palestinian Products: Olive Oil and Medjool Dates (retail page) — Equal Exchange is a co-op that sells Fair Trade products in the U.S, which has partnered with the Palestinian Agricultural Committee to sell olive oil and Medjool dates grown by small-scale Palestinian farmers. Wholesale purchasing is also available.
Willamette River Cleanup (website) — The Willamette River Cleanup organization works to clean up the Portland Harbor, along with the rest of the Willamette River. Consider signing up for updates and donating to their work.
“Portland Harbor Superfund Site” (article) — As part of the effort to clean up the Portland Harbor Superfund Site, the EPA created a resource documenting the history of Portland Harbor, the impacts of its pollution on marginalized communities, and the work necessary to fix the site.
Here are 20 works I read in 2020 and 2021 that I am still thinking about. I’ve divided the list into fiction and nonfiction, but that’s the only organizing principle at work here. Please note that while I read these works in the last two years, not all were published during that time. I’m including 2020 in this year’s round up because time is made up and I’m not entirely sure 2020 ever ended.
Harrow the Ninth by Tamsyn Muir (novel, purchase) — I included Gideon the Ninth, the first book in the Locked Tomb Series, in my 2019 recommended reading. Harrow the Ninth is Muir’s follow up and I loved it just as much as Gideon. The series is about lesbian space necromancers with feelings, which feels like it should be an easy sell. I have heard, however, that some folks didn’t enjoy Harrow quite as much as Gideon, possibly due to some really interesting structural decisions. Personally, I nerded out about Muir’s unusual approach to structure, but your mileage may vary. I’d also like to add a special shoutout for “The Mysterious Study of Doctor Sex,” a short story that takes place between Gideon and Harrow. If nothing else, it’s hilarious to read because one character is named Doctor Sex due to numerically-based naming systems rather than due to any reference to sexy times. Content notes: death, body horror, mental illness, and gaslighting.
“Earthquake relief. Mexico. 2051.” by Malka Older (short story, free) — I’ve loved Older’s novels, especially Infomocracy, for years. She combines a lot of really interesting political ideas with characters who I’d like to hang out with. Older wrote this short story for The New Humanitarian, which covers emergency response, and it was the first piece of fiction the site ever published. It’s a really thoughtful take on what emergency response could like in the future and an argument for completely reassessing how we deal with problems on municipal and global levels. Content notes: natural disasters.
“Hibiscus Tacos” by Ire’ne Lara Silva (short story, free) — I think about this short story regularly. Silva pulls together threads of food, love, death, and immortality in a way that feels more like poetry than most short stories. That’s no accident, given Silva is a poet with four collections under her belt. Content notes: Food and eating, death, suicide, medical procedures, and hospice care.
Bitter Root by David F. Walker, Chuck Brown, and Sanford Greene (comic, purchase) – I picked up this collection of the first five issues of Bitter Root based on the recommendation of the staff at my local comic shop (who consistently hand me comics that I absolutely have to read). The comic follows the Sangerye family through Harlem in the 1920s, as they fight monsters using traditional rootcraft and conjurings. Volume 2 and Volume 3 are now available, though I haven’t picked up a copy of the third volume yet. Content notes: Racism, family separation, and body horror.
“(emet)” by Lauren Ring (novelette, temporarily free) — Ring’s story of a programmer struggling with how her work endangers people rings so true for me. There’s an air of magical realism, drawing on Jewish folktales of golems, which adds a layer of meaning that I’ve had to sit with. Ring never mentions the ways that technology companies enabled efforts to wipe out Jews but her storytelling drips with that deeper meaning. Content notes: Surveillance and parental death.
Elatsoe by Darcie Little Badger (novel, purchase) — Little Badger is a Lipan Apache, as is the protagonist of Elatsoe. Drawing on her own culture, Little Badger created a version of the U.S. full of Indigenous monsters and magic (as well as some supernatural colonizers). The titular main character, nicknamed Ellie, is a teenager with the power to raise ghosts who seeks justice for a family member. Elatsoe is Little Badger’s first novel and I can’t wait to read more long-form work from her. Content notes: Racism, death (including murder), colonization, and horror elements.
“Lena” by qntm (short story, free) — This short story is a little difficult to describe, but “Lena” is a fast read. I’ll try to do it justice, but take a chance on reading it even if it doesn’t sound like quite your thing. The story is structured like a Wikipedia article and discusses the technical process of creating digital versions of an individual’s personality. Hints of the ethical and psychological concerns appear throughout discussions of workloads and intellectual property. Content notes: Death, dementia, and exploitation.
Lore Olympus by Rachel Smythe (comic, free) — This webcomic is a reimagining of Greek mythology with both modern and historical elements, told through exquisitely illustrated panels. I could write thousands of words just on Smythe’s color palettes. Lore Olympus follows Persephone and Hades from the very beginnings of their romance, while exploring themes of consent and sexual assault. Interestingly, Smythe chose to eliminate concerns around consent present in myths about Persephone and Hades, instead looking at other gods and how their social positions could impact relationships and be used harmfully. Smythe is very good about providing warnings about potentially triggering comics. The story is on-going and is closing in on 200 ‘episodes’ (which I would compare to individual comic issues in length). If you prefer to read your comics in dead tree format, the first 25 episodes are available in print and future volumes are planned. Content notes: Sexual assault, consent, child abuse, murder, and legal repression.
Salvage by Muffinlance (novel, free) — Yes, this a 127,175 word fanfic based on Avatar: The Last Airbender. Yes, I am recommending that you should read the whole thing (assuming you’re already familiar with ATLA). Yes, I possess no shame about my reading habits. I watched ATLA for the first time in 2020 and really enjoyed the storytelling. I read a lot of ATLA fan fiction after finishing the television series, and Muffinlance quickly became one of my favorite authors. I’m not the only one — Salvage is the top-ranked work for ATLA on Archive Of Our Own. Content notes: discussions of child abuse and death on the same level as the original television series.
“Lies I Never Told You” by Jaxton Kimble (short story, free) — Stories of everyday magical powers have a special place in my heart. Kimble’s short story hit that spot, with a character who writes out true statements, including predictions and personal insights. The result is a quick exploration of a teen’s coming of age and exploration of her own identity that somehow has the weight of a much longer piece. Content notes: Parental death, homophobia, and transphobia.
Submergence by Arula Ratnakar (novella, free) — Ratnakar’s novella follows a scientist searching for a cure to an incurable plague, fighting to maintain their personal ethics — but only after that scientist has already died. Their memories are implanted into the mind of an investigator. While Submergence is a fascinating story of questioning just how far science should go, Ratnakar’s world building is even more enthralling. She sets the stage of a near-future still facing climate change and explores tactics youth-led movements might use to combat that change in a way that reminds me of the efforts of the Sunrise Movement. Content notes: Climate change, pandemics, death, exploitation, privacy, and medical procedures.
“Handcuffed and Unhoused” by Meli Lewis (radio episode with transcript, free) — While technically a podcast episode, “Handcuffed and Unhoused” is incredibly important reporting on the criminalization of homelessness in Portland, Oregon. Lewis spent over two years collecting data, conducting interviews, and examining the failures of local efforts to address homelessness. Her reporting even uncovered concerning comments by Portland officials regarding their desires to further criminalize people without access to stable housing. Content notes: Homelessness, legal repression, police violence (including a recording of a police killing), and classism.
The Next Supper by Corey Mintz (book, purchase) — Mintz’s exploration of the future of the restaurant industry is fascinating, especially in light of COVID-19’s impact on restaurants’ ability to safely function. The book covers topics like sustainability, employee rights, and immigration. I wrote a longer review, contextualized for Portland, Oregon. Content notes: Food, racism, pandemics, abusive behavior (including sexual abuse).
“Ministry of Violence” by Tal Lavin (article series, free) — This three-part series is a hard read, but worth it. Lavin created this three-part series to examine corporal punishment in evangelical Christian households. I’m not Christian, but as I live in a Christianized society, I’ve seen some impacts of the sort of corporal punishment Lavin describes. But it’s very hard to understand how culturally ingrained these sorts of punishments are and to stop ignoring the reality that these punishments are essentially child abuse. Lavin created a definitive piece that provides insight for those outside evangelical Christian culture (and maybe those inside it, as well). Content notes: Child abuse, abusive relationships (including romantic relationships), and PTSD.
Weird Jewish Digest by Meli (weekly newsletter, free) — Meli’s weekly newsletter is ‘just’ a round up of links and events connected to Judaism. But it’s one of the most inclusive round-ups I’ve found and I look forward to every email (including the cute photos of Jewish pets at the end of each week’s newsletter). Meli includes tough topics and avoids unthinking approval of certain nations that typifies many Jewish publications. I strongly recommend a sign-up if Judaism is part of your identity in any way. Content notes: Sometimes includes links discussing anti-Jewishness and other difficult topics. Meli includes specific content warnings on each email.
“The Myth of a Wilderness Without Humans” by Mark Dowie (article, free) — Part of a longer book which I have not yet read (Conservation Refugees: The Hundred-Year Conflict Between Global Conservation and Native Peoples), Dowie’s article looks at what many people think they know about the history of national parks and other nature preserves. U.S. history is often taught in a way that erases Indigenous presences and the history of natural spaces is no different. Places like Yosemite National Park are marketed as untouched nature, despite millennia of presence by residents like the Miwok tribe. Dowie further discusses how the Miwok and other tribes actually created and tended the spaces that later became national parks, during which process the U.S. military forcibly removed Indigenous people from these lands. Content notes: Racism and colonization.
“Image Conscious” by Jasmine Sanders (article, free) — Sanders provided a bittersweet look at Black Romantic art, based on her familial experiences with selling art through home parties and other direct sales methods. Combining art by Black artists with discussion of the businesses that connected those artists with buyers, this article introduced me to several artists I quickly came to love. Sanders also examines the ways structural oppression has played out in art markets. Content notes: Racism and structural oppression.
“Why Frida Kahlo Still Isn’t a Great Woman Artist According to the Market” by Hall Rockefeller — I am a Frida Kahlo fan and, as such, I’m easily persuaded to read just about anything about Kahlo or her work. Rockefeller’s article is a standout piece, however, because of its examination of how Kahlo is perceived by curators, collectors, and other ‘experts.’ I recommend paring this article with Sanders’ “Image Conscious” (above) and then angrily making art of your own. Content notes: Misogyny.
“Jean and Jorts: the extended metaphor for workplace accommodations nobody asked for” by Fiona Robertson — Jean and Jorts took the internet by storm while I was in the process of writing this post. The story of these two cats originally appeared as an “Am I the Asshole?” post on reddit, which I recommend reading, along with this update posted later. The original poster asked for advice about whether they were perpetuating stereotypes about orange cats’ relative intelligence. The internet has gone wiled for Jorts, the orange cat in question, as well as Jean, Jorts’ kind companion. One response in particular caught my attention: Robertson’s discussion of Jorts and Jean as a metaphor for workplace accommodations. This write-up rings so true to my own experiences and provides a more accessible explanation of accommodations than the others I’ve read. My only complaint is that we have to talk about animals to get humans to take each other’s needs seriously. Content notes: Ableism.
“The State of Portland News” by Thursday Bram (article series, free) — I wrote this article, but this is my list and I make the rules, so I’m including it. I’ve referred back to this piece several times since posting it and I’m still pleased by how it turned out. Published in two parts, this piece covers who pays for and consumes news in the Portland area (Part One) and who owns publications and decides what to cover (Part Two). Content notes: Structural oppression, legal repression, and online harassment.
Just a head’s up: I’ve included links to Bookshop that will provide me with a small affiliate commission if you click through and make a purchase. However, I’d recommend any of these reads even without affiliate commissions — if you borrow books from the library or acquire them through other non-purchasing methods, I think that’s awesome.
Content notes: Discussions of deaths due to COVID-19, abusive behavior (including sexual abuse), racism
I read The Next Supper by Corey Mintz recently and it’s been stuck in my brain. I tweeted about the book, hoping that someone would write a review of The Next Supper, contextualizing the information it contains for Portland, Oregon. And then I remembered that sometimes you just have to write the article you want to see out in the world. So this review is kind of that, with the caveat that I’m not a food journalist and haven’t really set foot in a restaurant in almost two years. Another caveat worth noting is that I received a free copy of the book through NetGalley. I don’t think that influenced this review — but if you are at all worried, please note that the link above goes to the WorldCat entry for The Next Supper. You should be able to find a library near you with a copy rather than spending money based on my potentially biased opinion.
I found The Next Supper very readable, especially for a book telling me that everything about how we eat is probably bad. Mintz shares anecdotes showing that he’s not judging other eaters. He has committed the same sins as the rest of us — including eating at Taco Bell.
It’s comforting to know that none of us are alone in struggling to eat in a way that goes beyond stuffing the nearest calories down our gullets. I know I have terrible eating habits, but I’m not the only one. I’m trying to cut back on takeout after basically living on it for the last few years. I’ve been wondering how other people eat without relying on picking up prepared food from restaurants. Turns out that I’m part of a trend! The Next Supper documents a massive trend in relying on restaurants (as well as other sources of prepared foods, like supermarkets) — in 2018, US consumers spent more money on dining out than on groceries.
In The Next Supper, Mintz planned to cover the future of restaurants — and he did so, but not in the way he planned. Mintz began writing the book before the COVID-19 pandemic, during which the restaurant industry crumbled. From Mintz’s research, it’s clear that key trends around staffing, sustainability, and finances were dramatically escalated by pandemic lockdowns.
Key Topics in Context
Mintz covers a lot of ground in The Next Supper and I certainly don’t want to just repeat what he’s written. But Mintz wrote about national numbers (and international in many cases, given that he covers the restaurant industry in both Canada and the US). Since I live in Portland, Oregon, a city known for its food culture and wealth of local restaurants, I’m interested in what The Next Supper implies for the restaurants around here. To that end, I’m going to cover a couple of key topics from the book.
One fact stood out to me: Mintz says that there are far more restaurants in the US than can be supported by the number of diners. Partially due to big brands constantly pushing growth, the US had roughly one restaurant per 500 people before COVID. There’s just no way that consumers can support that many restaurants based on math Mintz presents. Portland’s restaurants tend to be independent, but the numbers are even more extreme here. I’m not sure how many restaurants are in Portland, but OpenTable currently lists over 5,000 restaurants in this city. That number is definitely low since there are plenty of restaurants that don’t use that site. Portland’s metro-area population in the last census was roughly 2.5 million. With just the 5,000 restaurants on Open Table, we already hit the level of one restaurant per 500 people. If we had a comprehensive list of restaurants in the Portland metro area, I bet we’d actually find that Portland’s ratio is closer to one restaurant per 300 people. That’s unsustainable unless we dramatically transform the relationship between consumers and restaurants.
Wages and Tipping
Staffing is a thread that runs throughout The Next Supper through sections on tipping, wages, abuse, and immigration. Portland-area restaurant staffing is a little different than what you may see in other cities. Oregon requires that restaurants pay full minimum wage of $12 per hour to servers, rather than allowing bullshit like paying a server $2.13 and counting on tips to bring that rate up to something someone might be able to live on. Furthermore, Portland itself has a higher minimum wage than surrounding areas, with a rate of $14 per hour.
Tipping is still common here (although I think it’s past time for us to find a way to eliminate tipping and actually pay everyone a fair wage). Mintz’s inclusion of Michael Lynn’s research on tipping caught my eye, especially given the racism built into Oregon’s governance from the first state constitution onward. Lynn’s research has demonstrated racial disparities in the tips diners give to servers. The disparity hits the point that forcing servers to rely on tips feels like an actionable civil rights violation. I’m not a lawyer, of course, but I doubt we’ll see substantial changes to tipping culture without that kind of in-depth examination and refutation.
Of course, tipping is only one way restaurant employees are compensated for their labor. As I browsed through job listings for restaurant staff here in Portland, I noticed that the listings didn’t quite match up with Mintz’s discussion. Many of these jobs list benefits like paid-time off and offer hourly rates above minimum wage. That’s a good sign for local food culture, although what job listings offer often doesn’t match the reality of working for a given restaurant. It’s easy to find lots of posts like this one about applying to multiple jobs offering one wage and then actually offering significantly less to new hires. Bait-and-switch techniques are common in hiring restaurant staff right now. There’s also a long history of wage theft in the form of unpaid training, paying day rates (rather than hourly wages), unpaid overtime, etc. in the restaurant industry, which Mintz goes into in more depth.
These problems are compounded by a variety of larger social issues. There’s an underlying misogyny that enables business owners to sexually assault staff members, an underlying racism that allows business owners to take advantage of undocumented workers, and an underlying devotion to capitalism that makes wage theft a standard business practice.
Personally, I’m unconvinced that call-out posts will reform these problems at an industry-level. Collective action, such as unionization, is the only strategy that I’ve seen work. Unionizing both independent restaurants and local chains is likely the most useful strategy, and one that Portland may be able to rely on. With the recognition of the Burgerville Workers Union, we have the first unionized fast food chain in the country. We just need to build on that success.
Third-Party Delivery Apps
Third-party delivery apps — which around here includes Uber Eats, Postmates (owned by Uber), DoorDash, and Caviar (owned by DoorDash) — are notoriously bad for restaurants and delivery drivers alike. There are plenty of examples, from pocketing delivery drivers’ tips to charging fees to restaurants for orders that don’t go through the apps. Independent restaurants get the worst deals, as big brands like Applebees negotiate with delivery providers to keep costs down. The Next Supper points out venture capitalists with long-term plans fund these apps. They subsidize the cost of destroying other delivery options as well as keeping prices down long enough to get consumers reliant on these apps. Third-party apps can afford lobbying efforts or they can punish users with local fees when local governments are willing to push back against their practices.
Communities (including restaurants, delivery staff, and diners) need to plan for the long term. We need plans for both minimizing how capitalistic interests can mix extra costs into our food budgets and for building better systems for getting food in the hands of hungry people. I see organizations like CCC PDX as a start to that discussion. Local bicyclists formed a collective to deliver food and other products in partnerships with local restaurants and retailers. A logical next step might be building an app that handles handles local deliveries for local brands. It could offer equitable splits of both expenses and profits without sending money outside the Portland ecosystem. I don’t think that’s enough, long term, but the conversation has to start somewhere. Only once we’re actively talking about these issues will we be able to bring up options like collective purchasing, neighborhood-based food systems, and other options that move us towards radical change.
McDonald’s — which I learned is the world’s largest buyer of beef, pork, potatoes, lettuce, and tomatoes during my reading — has a variety of mechanisms for auditing their supply chain for reducing harm. There are also a variety of NGOs that work to hold McDonald’s and other large chains accountable. But there’s virtually nothing in place for smaller businesses. Mintz catalogues different ways restaurants can lie or stretch the truth about the sources of their ingredients. As we look at our local dining options, we are responsible for deciding who we trust. But, frankly, none of us have the resources to check whether a given restaurant might be lying. There’s no easy solution to this problem and it will only grow as climate change advances and diminishes the quality of certain crops.
Ultimately, many of the problems with the restaurant industry grow out of problems with ownership, especially of large chains that can make decisions that move the market for everyone else. It’s tempting to ignore problems with big chains if you live inside Portland’s city limits: Red Lobster and Outback Steakhouse are only in the suburbs (due in part to minimum wage laws), so there’s a sense that their problems are better dealt with by the residents and governments of Beaverton, Lake Oswego, or Vancouver. But these big companies make plenty of decisions that impact folks inside city limits and we need to pay attention.
While the problems Mintz discusses are national or even international, few of us have the resources to work on that level. But we can work on those issues on a local level, improving Portland’s share of the restaurant industry. One key step is encouraging local food journalism that goes beyond restaurant reviews. If we have local food media that covers supply chains, staffing, and other facets of the restaurant business, individuals don’t need to try to figure out those details on our own. Of course, local journalism has issues of its own. Eater PDX’s staff works hard, as do the writers in charge of covering food at publications like the Portland Mercury and Portland Monthly, but those publications all have clear goals that don’t prioritize critiquing the restaurant industry. We need something closer to the Racist Sandwich podcast, with a more explicit focus on Portland. (Fingers crossed for another season of Racist Sandwich soon.)
Getting good information is only part of the equation. We need to act on that information. We all want to make good choices about what we eat, including choosing restaurants that minimize harm. Mintz sees the need for more action, telling us “Don’t just vote with your fork, vote with your vote.” We need collective action, which can include voting for local candidates as well as unionization drives at restaurants, getting off of third-party delivery apps, and believing folks about sexual harassment and other abuses they’ve experienced. The problems within the restaurant industry are the same problems we see throughout society — perhaps written small enough that we can create real change on a practical timeline.
In closing, I found The Next Supper to provide a good lens on the restaurant industry, including some of the changes wrought by COVID. I’ve only covered a small chunk of the material in the book and how it relates to Portland’s restaurants — to cover it all would take, well, a full book.
Some of you may remember that in the before times, I ran an email list covering sponsorship opportunities around tech conferences and other events related to tech here in Portland. I haven’t updated it since 2019, given the large number of cancellations and postponements in the last two years.
Both running and sponsoring events look dramatically different today than they did in 2017, when I started the newsletter. Personally, I don’t feel comfortable attending big events in person and I don’t see that changing any time soon. My work has also moved away from the tech industry, so I’m not really tracking tech events very closely at this point.
As a result, I’ve decided to formally shut down the mailing list. After this post goes live, I’ll delete the mailing list, including subscriber emails. If someone wants to start something similar in the future, you have my blessing. And if you want my templates and notes, let me know — we can work out an equitable arrangement.
I’m already working on some coverage of the 2022 primary and general elections. In the meanwhile, though, I wanted to collect the resources I’ve made over the past several years into one place.
Prior to moving to Portland, I also wrote about elections (including a stint blogging professionally about the 2008 election). I don’t really recommend my political writing prior to about ten years ago; I have learned a lot since then and developed personal politics that I feel a lot better about.
As someone who regularly submits talks to technical conferences that aren’t really focused on technology, I found the feedback from this proposal especially helpful for future talks. Here’s one highlight that has convinced me to double-down on writing lengthier proposals in order to get my idea across:
We especially liked the ‘audience’ section. The description of whom the tutorial was aimed at was excellent.
Most of our favorite proposals include clear learning goals (showing us what the audience will learn, and giving them motivation to attend). This one provides additional details, unique to the format of the tutorial itself:
“Attendees will have at least one writing sample they can share and will be better equipped to write and test their own materials, as well as evaluate others’ writing. They’ll also know about opportunities to share their writing with other pythonistas.”
I hope these materials serve as an inspiration for Python speakers, especially anyone considering putting in a talk that focuses less on the programming language itself and more on the context in which we use it.
And if you need ideas for topics that would make great talks in 2022, here are a list of ideas pulled from various Twitter threads I’ve posted over the years and updated as needed (2021, 2020, 2019, 2018). These talk ideas are, of course, not vetted by PyCon staff and are just talks I want to watch.
Most of us have spent almost two years thinking about COVID vaccines almost constantly. Some places have done well at distribution, some are struggling. If you’re building or using Python tools to help with the vaccination effort, tell the rest of us. If there’s still work to be done, tell us about it so we can help.
If you have any scripts or tools that make living a socially-distanced life easier, I think a lot of people are still looking for ways to make remote everything easier.
A talk about writing Python with minimal internet access or writing programs for users with minimal internet access may seem like a counterintuitive idea. But many folks have precarious internet access, and the continuing pandemic leaves those folks with fewer opportunities to go elsewhere for better access.
I’m not sure what the highest number of types of pythons you can reference in one talk, but I’ve seen some herpetology tools written in Python and there’s a giant prehistoric snake with the taxonomic name _Montypythonoides riversleighensis_. There’s a lot of material there.
Was there some nuance about Python you struggled with this year? Write up an explanation — I promise that if you struggled with a Python concept, some other Pythonista has too!
Are you working on one of the many elections happening in 2022? Empower your fellow Python programmers to take their skills and get involved in the political process.
We need to talk about prisontech and how much technology works goes into maintaining white supremacy if we want to have even a chance of reducing structural racism.
Las PyCon Charlas será un track de charlas en español abierto a toda la comunidad que tendrá lugar en la PyCon US. Si hablas español, ¿por qué no envías una propuesta de charla?
With the current wave of unionization at a variety of tech companies, it’s time to talk about organizing in tech communities. Some folks may be starting out with collective action, so both introductory talks and more advanced materials are good.
This is more a general topic for programmers, rather than just Pythonistas, but how about a talk on dealing with old computer hardware. Programs like Portland’s Free Geek do phenomenal work getting technology in the hands of those who need it, like students going to school remotely.
As responsible consumers of data, why do we not talk more about how we dispose of data? Storage space may not be an issue, but privacy definitely is!
Programmers need more education on how to mitigate climate change factors. Honestly, all I know off the top of my head is that Bitcoin produces more carbon emissions than the entire country of Argentina.
What do you do if you discover that your employer provides, say, a connected thermostat to a client you don’t like, for instance, ICE? Holding employers to ethical standards is a skill set every programmer needs.
There are Python newsletters, podcasts, blogs, books, and other media. Maybe it’s time to start talking about the Python media ecosystem. What would this talk look like? a guided tour through what’s out there? a discussion on how the different bits interact? There are so many options!
Based on unfortunate mistakes that were made, possibly at my desk, I’d love to hear more from experienced folks on how to interact with other people’s projects in ways that won’t overwhelm a server or break other stuff. i.e. how to use an API run by a nonprofit with an all volunteer tech team.
Fundraising for open source projects has changed dramatically in the last two years. PyCon, for instance, is usually the PSF’s main fundraiser. If you’ve successfully raised money for an open source project in the last year, we’d all appreciate you sharing with the rest of us.
I have a dream of PyCon hosting its own fashion show some day. We deserve it. And Nina Zakharenko’s earrings deserve to be on the runway.
What’s the absolute weirdest hardware you’ve gotten Python to run on? Currently, I think the Furby is a standout but I bet y’all can surprise me.
If you struggled to learn any concept related to Python, consider giving a talk about that concept — I can guarantee that if you struggled with something, other folks in the Python community struggled too!
I’ve seen dozens of tarot and astrology apps at this point. Getting a developer’s perspective of building systems that (I assume) need to work in an element of chance or intuition world make for an amazing talk.
I’m getting kind of tired of talks on automation scripts for businesses. How about some household automation scripts? Did you write a script for generating a shopping list or managing chores?
Have you tweaked Python IDEs & other programming tools to make programming in Python accessible? In the past, talks covered tools for programmers with low vision and teaching Python in ASL, but there must be other accessibility hacks worth sharing.
I have seen some truly amazing Python-driven sensors for temperature, moisture, and other environmental factors. I have to believe someone has put them all together into an amazing gardening system. If you are that person, you should tell the rest of us how to do the same!
I’ve heard more than once that Python is used on every continent, but what exactly are Antarctic Python users up to? That’s a talk I’d listen to, for sure!
I think every conference organizer has seen several versions of “How to make your first contribution to open source”, so it’s time for talks about how to make your second, or third, or hundredth contribution to open source. Tell us what comes next.
There are plenty of talks out there about programming with security in mind, but it’s a struggle to find anything about programming with privacy in mind. We have a responsibility to keep users’ information private, so we need tools and techniques to ensure that privacy.
Finding data sets to train machine learning projects on can have unintended consequences. Any ML enthusiasts out there who can explain what to look for when choosing data sets?
If we’re honest, we could all probably use a talk on how to create bug reports that will actually result in fixes.
We clearly need a Python game arcade during the conference. I will happily bring a bunch of quarters if someone brings the games.
Python has been deployed to help during several recent emergencies. What’s it like to use Python in those scenarios? Is there anything you’d do differently or wish you had in your toolbox?
There’s one poster that I would love to see: a guide to what Python programmers are expected to know at different experience levels, at least in terms of what hiring managers are looking for.
Building a Python app can be a matter of hours — but scaling that same app could take the rest of your life. If you’ve gone through the process, please let the rest of us learn from your experience.
IoT / connected devices have enabled a lot of people to customize their homes to better suit their needs, like by using lights to create visual warnings for folks who can’t afford fully accessible alarms. Talk us through what that sort of project entails.
Given Python’s educational usage, we may need to spend more time on Python’s user experience. I’m not sure if this topic would be best as a talk or as an open space.
Several open source communities have experienced controversies over limiting the use of their work based on ethical concerns. It seems worth discussing what ethical concerns Python contributors have, as well as what Pythonic ethics might look like.
Using Python to change your online browsing experience (i.e., filtering out abusive content on reddit) could make for a great talk.
I would love to know how to effectively assess libraries and frameworks when choosing how to build a project. How do you vet tools so you avoid components that won’t be supported a year from now?
Can someone demo some hiring exercises that don’t require whiteboarding? Ideally those exercises can actually show an applicant’s Python skills without asking for an unreasonable amount of work, but I don’t want to be, you know, too optimistic.
We have about a decade left to make meaningful progress on climate change. Are there any projects out there that require Pythonic assistance? Talk us through the onboarding process and then maybe set up a sprint on that project.
I continue to maintain that not enough programmers are terrified by the words “intercalary periods.” Time zones aren’t anywhere near the only difficulties in implementing time into code worthy of a talk.
How we got to Python 3: I don’t think I’m the only one who likes a good code archaeology talk, so an overview of how Python has evolved over the past 20 odd years could be awesome.
Python for writers (fiction and otherwise) could be an awesome talk. I could see coming at this topic from a couple of different ways, like dissecting some of the scripts writers have shared on GitHub.
How to improve search in your projects, especially when you’ve scrapped a giant pile of websites, PDFs, or other data and that pile is just sitting there, silently judging you for not already working with it.
I’m sure someone out there is going to be running 2.7 for years to come, so talks about maintaining and using legacy code are great. If you’ve got any particularly well-aged code still in production, tell us about what it takes to keep that code working. (I have literally written a short story about the consequences of running 2.7 for far too long, so I’m obviously thinking about this topic a lot.)
Could someone with experience in anonymizing data sit us all down and talk about how to anonymize data and what potential issues we need to look out for?
Okay, I’m pretty sure that most conferences don’t want talks about gambling, but I did read an interesting paper about predictive modeling for horse racing and there’s definitely a talk in there. Maybe stay away from talking about betting and focus on the math and horses.
How to triage and understand Python code bases someone else wrote. Honestly, I could probably use some advice about understanding the code Past Me wrote, too.
How to do due diligence on an open source project before using it: There are definitely security factors we need to think about, but we also need to talk more about project sustainability and deciding if it’s worth supporting projects with questionable approaches to inclusion.
While a lot of us use GitHub, there are other version control apps out there (including other git-based options). When does it make sense to use other options for Python projects and is it important to reduce reliance on a single app?
Python in a hurry: what tools and techniques can help get something / anything into production? But you’ll also want to cover the tradeoffs and technical debt accrued along the way.
There are some serious pros and cons to doing genetic testing through 23andme and similar tools, so maybe it’s time to talk about how to do our own analysis of our genetic history (including using some of the Python tools that already exist in this area).
I know NASA uses Python and I just want to say that I am here for *any* talk about using Python to launch stuff into space. (Non-NASA space talks are also super cool.)
What’s the life cycle of a Python library? What should we know before we decide to create new libraries? (Bonus points if your slide deck illustrates concepts using the life cycle of a python!)
Benchmarking the different hosting options for Python-based projects would make a great poster session topic (and I would probably ask for a copy of that poster for my office).
Software testing on a shoestring budget would be great. There have been a lot of “Python for activism!” talks lately, but one of the results have been some projects thrown over the wall without any testing, because testing seems hard and expensive.
Another technology archeology idea: what old hardware can you get running with a more modernish interface? And let’s go old-school: if you have access to, say, a Jacquard loom, what can you do with it with a modern programming language?
Building local mapping systems, especially in ways where data can be shared. As a for instance, being able to map warming shelters (especially the informal ones, like churches) as they open and close in real time would be so useful during freezing temperatures.
Anyone with a generative art project should write it up, in my opinion. First, because all conferences need more art. Second, because there is some AMAZING art coming out of human / tech combos right now.
Augmented reality is a thing right now. There are amazing museum installations (more art!), accessibility upgrades, etc. out there that we’re not seeing a lot of in talks yet. (I’ve seen several “I made an app for other techbros!” talks, so anything else really would be nice.)
One take on the standard “make your API actually useable” talk I’d love to watch: how to prep your API to work with platforms like IFTTT or Zapier. What does it entail behind the scenes and how many different ways do users find to break things?
Building Python tools for non-programmers would be a useful talk. I’ve seen a couple of great PyQt walkthroughs, for instance, that could really be followed up with another talk on how people actually use GUIs after they’re built, necessary upgrades, unexpected edge cases etc.
Oooh, someone could totally do a talk on code review best practices, especially around what parts can be automated and what bits a human needs to do. If you’ve got some ideas for adding empathy to code reviews (especially for the bits that are automated), that would be great!
There’s some really interesting technology built around religious needs (often with Python). For instance, some Orthodox Jewish business owners take down their websites for the length of the Sabbath. Kosher technology is fascinating and talk-worthy.
I’m so here for data spelunking talks, especially from data journalists. Had to go to absurd lengths with a FOIA request, munge together data sets from old scans, or otherwise work with dubious data? What’s your workflow?
Would someone please give a talk with “How to Teach Your Daughter to Code” as the first slide and “Exactly the way you’d teach your other children to code” as the second? You could follow it up with an actual talk or submit it as a lightning talk.
I’m not sure what the oldest Python code still in use is, but if anyone’s running software using, say, Python 2.0, what does it take to keep that kind of well-aged software up? Even better if you didn’t write the code initially and had to read the previous programmer’s mind.
There are tons of talks on building tools to track and improve health, but very few on tracking and improving mental health. I don’t believe for a minute that none of y’all are tracking mental health data on yourselves, so put in a talk if you’re comfortable talking about it.
If anyone is hardening systems using Python to prepare for natural disasters (or man-made disasters, as the case may be), that’s definitely a thing you should put in a talk on.
I’m always in favor of community-specific trainings about how to work with the community’s code of conduct. Ally and bystander training around PyCon’s Code of Conduct would be particularly nice.
Python has impacted how a bunch of other programming languages have evolved. A talk on those impacts in other languages, along with an exploration of anything those languages have improved upon would be super interesting.
There are entire series of books dedicated to using what you know about one programming language to learn another. What about a talk that uses the same approach to introduce a couple of Python frameworks? What do they have in common? How do they work differently?
How about an intro to building linters? Maybe some best practices, tips on making linters more accessible, that sort of thing?
An annotated discussion of all the Monty Python jokes in the Python language, especially for everyone who did not grow up with the antics of said comedians.
So you have 75 ideas to get you started and roughly a month to write your proposal. What are you waiting for?