vmbrasseur

Open Source Summit NA 2024 Proposal Template

To help you plan your OSSNA 2024 conference proposals.

https://sessionize.com/ossna2024/

Session title

Description (max 1200 characters)

vmbrasseur

Finding & Interacting with Mentors

These tips come from my experience, but they also owe a large debt to the mentoring panel I was on and that was put together by Erik Riedel & Nithya Ruff for Open Source Leadership Summit 2019.

One-off mentoring

You have something you want to learn more about or you need experienced advice with. You just need answers and then you're not likely to take up the mentor's time much again.

• Figure out what you need help with. This is key. Do this now before you do anything else.
• Come up with a specific, well-bounded question expressing that.

vmbrasseur

Google Summer of Code advice for projects

On 2019-01-09, Software Freedom Conservancy ran a Google Summer of Code (GSoC) advice session for projects. The session occurred in the #conservancy channel on Freenode IRC.

Below is a summary of the advice followed by a complete transcript of the advice session.

Ideas list

• This list is very important for the committee selecting projects to participate in GSoC.
• Things to consider while building the list:

vmbrasseur

LFN Project CLA Processes

To help Tungsten Fabric settle on the CLA administration process it should use, I've reviewed the CLA processes of the other LFN member projects. I was specifically looking for documentation about how each administers their CLAs (if they use them at all; several do not), but I found no such docs. Instead, below find the summary each project's requirements for contribution as well as my own notes from this research process.

Overall, this is an area where all projects (including TF) can do a better job, both in setting up expectations for the contributors and in documenting the various processes involved. Some projects did not even have contributor guides, for instance, and for others I had to dig into their technical charters to find any mention at all of contribution requirements with regard to intellectual property.

FD.io

Searched for contributor docs or mention of CLA. Didn't find anything.

vmbrasseur

Bisara (Tunisian fava bean stew with merguez lamb sausage)

I've discovered that dried split favas and merguez each are surprisingly hard to find in Portland, but since you have a car you may have better luck. Olympia Provisions sometimes has merguez, as does my Whole Foods on NE Fremont (and they'll make it to order if you give them enough days notice). The favas sometimes can be found at Ethiopian shops (sometimes called "ful"), or at Fubonn or 99 Ranch. I think they may also be available at World Foods on NW Everett, but I haven't confirmed that recently.

Recipe originally from "Beans" by Aliza Green (0-7624-1931-8), but the below is my particular version of it, evolved over years of making and loving the dish.

I usually serve it with a simple salad of some sort of assertive green (arugula is nice), dressed with a fairly peppy homemade vinaigrette.

This is a whole pound of beans plus a pound of sausage, so be prepared for plenty of leftovers. It freezes very well, as most bean stews seem to.

vmbrasseur

This method is from the Tartine Bread Book, which is a lovely piece of work. I use this method all the time with their dough but the logic and science behind it should work well for any good dough. I haven't tried it for a machine dough but I don't see why it wouldn't work. It forms a nice round loaf with a good proper crust.

The logic/science of it is that the dutch oven forms a hot, moist environment at a crucial time of crust formation. This allows the crust to expand while heating up enough to cook through more than it would in a bread machine or loaf pan.

Equipment:

• 4-5.5 quart cast iron covered dutch oven. The top is very important and must also be oven-safe.
• Dough, before its final rise; Method below assumes as much dough as you'd get out of your bread machine.
• A kitchen towel for the dough bowl
• Flour for the towel (a 50-50 flour of rice and white wheat flour is particularly good)

vmbrasseur

Keybase proof

I hereby claim:

• I am vmbrasseur on github.
• I am vmbrasseur (https://keybase.io/vmbrasseur) on keybase.
• I have a public key ASA46UYmENS7UVLb7erHlWfw1xIszcdBktprxImohEb69Ao

To claim this, I am signing this object:

vmbrasseur

In VM (aka Vicky)'s nearly 20 years in the tech industry she has been an analyst, programmer, product manager, software engineering manager, director of software engineering, and C-level technical business and open source strategy consultant. Vicky is the winner of the Perl White Camel Award (2014) and the O'Reilly Open Source Award (2016).

Vicky occasionally blogs at http://anonymoushash.vmbrasseur.com, often writes and is a community moderator for opensource.com, and frequently tweets at @vmbrasseur.

vmbrasseur

Goal

• decomission a legacy bespoke PHP application
  • replace it with an open source ETL where it makes sense to do that
  • transition it's functions into other things where it doesn't

Moving parts

So the bits which jump out immediately:

vmbrasseur

Community Summit

Data-Driven Community Management

• Data-driven CM bores people
• So let's talk about fire
  • Post-fire, they try to figure out why it happened
    • Can they improve anything?
    • Was it a crime?
• If something can be improved, is that actually done?