Hey there, team!
I’m working on an article for FOSSlife, essentially converting my drive-thru contributors talk into an article. When I last did that talk (way back in 2017…wow, time flies), Cauldron wasn’t a thing. Now it is!
To be clear, here’s the explanation of drive-thru contributor that I’m using in the article:
When you go to a fast-food drive-thru, you show up, get what you need out of the transaction, and then leave to go about your life. The same is true of drive-thru contributors in FOSS projects. These people show up to the project, make a single contribution, and then leave, never to contribute there again. The majority of these contributions are “itch scratches”: the contributor has a bug they need fixed, a feature they need added, or just had a quick edit to make in the documentation. Once the contributor has solved their particular problem, they move on to continue what they were doing before.
It would be really helpful to be able to give people some really brief pointers on how to track/visualise this type of contributor using Cauldron. This has to be something Cauldron can do, right? I mean, it has all the data right there…but I don’t know how to do it. I suspect it might involve the Kibana stuff?
Anyway, I figured I’d ask the pros (that’s you) for a hand, because it’s gonna be a heckuva lot faster than my flailing at figuring it out myself.
A snag: If I want to have a weekend (spoiler alert: I do), I need to get this article into my editor tomorrow (Friday, 23OCT). Because of course I’m doing this at the last minute. I’m only human.
I plan to mention/link to Cauldron in the article regardless, but if you were able to give me some info about how to manage this exact task then I can include a screenshot as well.
What do you think? Can you help, given the short deadline? “No time now” is a totally valid answer, of course. I appreciate that I’m popping this on y’all at the last moment.