Hi folks!! Reminder that the monthly Pants develop...
# development
h
Hi folks!! Reminder that the monthly Pants development meeting is tomorrow at 9 AM Pacific Time. If you're interested in the development roadmap of Pants itself, you're welcome to join! DM me to be added to the calendar event, or just hop on the huddle in this channel. Also reply to this post (or DM me) if you have any agenda items to add. See you tomorrow!
f
Add to the agenda ▪︎ seeking development guidance : desire to add a generic string returning build file alias
read_file_contents(sources=[...],[regex=...])
b
Proposal/request for discussion: have the meeting time rotate to allow me (in Australia) / other people on this side of the world to attend. I think one can only schedule reasonable times for at most two of Asia/Oceania, Americas, Europe/Africa, and the current slot seems to be good for Americas + Europe/Africa: it's currently at 3am for me (and similarly late night for a good chunk of Asia), and while I like Pants, not quite that much 😅 Some ideas: 1. alternate between the existing Americas + Europe/Africa slot and an Americas + Asia/Oceania one 2. rotate between three slots, so also cover Europe/Africa + Asia/Oceania 3. do something more complicated than alternating (e.g. a cycle of 3: 2 in the existing slot, 1 in a new one) My sense is most of the community is in the US, so maybe 1 is appropriate? For convenience of a selection of timezones around the world: https://www.worldtimebuddy.com/?pl=1&lid=5391959,5128581,100,2950159,1261481,1850147,2147714&h=2147714&date=3/12/2024%7C2&hf=1 After 2pm in SF would work for me (= 8am for me now, but 7am from April - September, due to daylight savings).
h
Thanks for bringing this up - yeah, this is far from ideal.
If we moved this to 2 PM in SF, that would be 7 AM Australia, which is early but maybe not prohibitvely so? and 11 PM central Europe, which is late but maybe not prohibitively so?
It would be great if we could find some sliver of time that allows everyone to just about make it
We could alternate that with 10 PM PST (7 AM central europe, 3 PM Australia)
But either way, yes, we definitely should recognize the international nature of the team and choose meeting times appropriately
👍 1
@fresh-continent-76371 did you mention you're in Australia? I wouldn't expect you to attend at 3 AM... we can find another way to get feedback on your idea and help find a path forward
b
Happy for it to be discussed amongst the group, but some specific notes I'd like to be considered in my absence: • I'm personally happy with 7am - (finishing at) 10pm, although could do probably manage 6am or finishing at 11pm if nothing else worked. • Northern/Southern hemispheres do DST opposite => meeting times shift 2 hours through the year => a time reasonable for June might not be great for January and vice versa
n
Had been wondering this also - never got around to attending while I was in the UK. I'm also now in Australia and 7 am is fine.
f
@broad-processor-92400 I'm in Sydney- Australia
@happy-kitchen-89482 yes I'm Australia. For this one off where the lion share of expertise is on a call at 3am. Not a problem :-) (worked for a silicon Valley co for 18 months ) Keen to see a rotation of time also :-) 😀
c
Suggested topic: 3rdparty update consistency, or rather is it worth perusing any consistency/standardization on this: • When adding a new X.Y release, do we add just the latest Y for every release since? • When do we change the default? • Do we ever remove old versions?