On the way back from a function, might be a touch late for the Meetup

I'll dial in from the car for the first bit

Hey folks, apologies again but I’m going to miss the maintainers catch up this week (family gathering) A couple of updates: 1. I’m working on the retro items from the past 2. I’ve been looking at socialising feedback around an update to our documentation (a restructure into a diataxis format, with some assistance from Tech Writers at SmartBear)

I also wont be avail, as ill be in NY talking about all things contract testing

Hey folks, not sure if the maintainer catch up is on tonight but I’m smoked - I also need to wrap up a few things at work before I clock off. i’ll give tonight a miss, that is

All good buddy, me and Jo wrapping up some bits and bobs

oh shoot - was it 50 mins ago?! facepalm

Yeah, me and Jo got confused and thought it was an hour earlier than that as well 😅

But we also discussed canning it, and getting some comms out with the community about how they want to interact with us. Maybe some calendly time. We’re working on finalising some comms pieces today. • Pact Foundation org members ◦ Thank you’s and do you still want to be part of the org ◦ Aim: Review members and set up appropriate groups / permissions, and ensure we have bots rather than users for automations • Pact Community at large ◦ How can we meet you where we are, maybe survey ◦ Aim: Find better aligned ways to communicate with our user base, • Pact Repo Usage Survey ◦ For each repo, have a issue/discussion around current usage / feedback / maintainer and/or contributor participation. ◦ Aim: Try and archive repos that are not used, or do not serve the community well, to reduce cognitive load and sunken costs, when reviewing viability of our tooling. ◦ Secondary Aim: Try and find a maintainer, or group of maintainers/contributors who actively want to maintain/shepherd each repo

@rholshausen I was speaking with Yousaf and Jo the other day and I mentioned how you were rebuilding the JVM release pipelines as the current stack is being shutdown. Is this a good opportunity to re-think automating the release process from GitHub? Also, a reminder for any secrets/credentials to pop them into the Pact Foundation’s 1Password in case you win the lottery and disappear to Mallorca

Is this a good opportunity to re-think automating the release process from GitHub?

Probably, but I couldn't be bothered doing it

I don't gamble, so you don't have to worry about me winning any lotteries

Do you travel on public transport?

Just clarifying - what time is our maintainer meet tonight? I think 8pm AEST / 12pm CET / 6am ET?

In 1 hour from now?

haha thanks all 👋

What's on the agenda for tonight? I'm still behind on my actions and need to get some other urgent stuff done if nothing pressing

FYI I think Yousaf and Jo are at a conference. I could use the time tonight to work on my commitments (retro follow up and progressing the JS PR)vif we don't have much to discuss? I'm also likely to be slightly late (kids)

i’ll be about. we don’t head off till later this eve. all good if you want to get your head down buddy

Ah cool. I'll aim to be there. Initiating bed time routine in 3-2-1...

I would like a new version for pact-protobuf-plugin and pact-ffi, can you release them for me @rholshausen?

Hey all, Welcome @Kevin Vaz who recently joined the PactFlow team and will be helping triage and work on some issues in the Pact-Python space. alongside @Joshua Ellis who has been doing awesome work. I’ve created a pact-python-triagers team and added kevin into it, rather than full maintainer/admin rights. Josh feel free to amend to suit.

Sorry folks, I need to skip on tonight’s meeting. I need to get something done tonight (insert MS Powerpoint emoji!)

blobwave On Friday, some CLI tooling changes were merged to to help the migration/adoption of our rust based tooling, over our ruby tooling. All rust cli tooling is now available in a consolidated docker image and standalone package, these are additions to the existing ruby consolidated cli packages. To support this 1. pact-ruby-cli has been renamed to pact-docker-cli 2. pact-ruby-standalone has been renamed to pact-standalone Ruby packages have been marked as legacy in cli docs, with exception of the pact_broker-client. • https://github.com/pact-foundation/pact-docker-cli/pull/135 • https://github.com/pact-foundation/pact-standalone/pull/146 Updated docs / repo links • https://docs.pact.io/implementation_guides/overview

Hey folks, I’ll be there tonight (albeit will need to drop a little earlier to get to another call). Looking forward to seeing you 👋

I’ve dropped these crate owners (pact) a message to see if we can claim it as they have renamed to codas and have a notice in place about transferring https://crates.io/crates/pact

this is also unfortunate 😅 i might drop them a message whilst I am at it https://crates.io/crates/pact-cli

Sorry folks, I realised the maintainer invite dropped out of my calendar. I wouldn’t have made last week anyway as I was on leave. I should be right for next Wednesday

someone trying to add pact_broker-client as pact-cli to homebrew-core https://github.com/pact-foundation/pact_broker-client/pull/195 kind of nice to have it in homebrew-core, but without having a live url to update, it makes it more awkward to use to update (an extra hope out of our control), plus those type of package managers don’t usually like have meta cli packages that bundle up many clis ( I got grief from scoop about it when looking to create listed packages for there)

I asked some questions to see if we be viable to be the core,, but to also address some concerns about the meta cli