<div dir="ltr"><div>+1 to a time change, that regular time slot has been getting hit by some of my rotating meetings -- this is new for 2022!</div><div><br></div><div>How do folks feel about the 2:00PM Eastern / 1:00PM Central / Noon Mountain / 11:00AM Pacific timeslot?<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jan 28, 2022 at 1:12 PM TC Haddad <<a href="mailto:tchaddad@gmail.com">tchaddad@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>If the question is primarily between Slack and Discord, I'd prefer Slack, if nothing else, primarily for consolidation purposes. I've used Discord, but it doesn't run as well on all my devices, so I'd prefer not to deal with those inconsistencies, among other reasons.</div><div><br></div><div>I don't mind continuing the meetings on IRC, and will be careful to not miss the reminders in future months. I wonder if we should reconsider the time slot - maybe moving it yet another half hour later would work out better? it's a little odd to start a meeting on the half-hour (causes me to have a lot of 1/2 hour conflicts). But maybe that is just me...<br></div><div><br></div><div>Like Jim, I do like the fact that referencing the list archives is a good form of project memory, and there really isn't another equivalent to that particular function. That doesn't necessarily mean that we have to have all discussions there - we would just need to have an intentional practice where, if a discussion topic blows up on Slack, we make a point to copy the main points back to the email list for any final votes or long term outcomes to be captured and agreed on. I see other communities struggle with this a little bit, but it could be as simple as checking once a month, before a PSC meeting, if anything significant happened and needs to be cross-posted.</div><div><br></div><div>Tanya<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jan 28, 2022 at 5:41 AM Dan Little <<a href="mailto:theduckylittle@gmail.com" target="_blank">theduckylittle@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Any one have thoughts on using something like Slack or Discord? <br></div><div><br></div><div>Con:</div><div>- Not full open source managed.</div><div>- Not necessarily "universal" in the same as IRC.</div><div><br></div><div>Pro:</div><div>- Logging</div><div>- Web based client</div><div>- Data "take away" tools.</div><div><br></div><div>After the kurfluffle with freenode, I'm not sure there is much distance in politics between something like Discord or Slack and IRC.</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 26, 2022 at 10:24 AM Jim Klassen <<a href="mailto:klassen.js@gmail.com" target="_blank">klassen.js@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
I agree, I prefer meeting live on IRC. I added my comments, but I
wasn't really sure where to respond to various points in this
format.<br>
<br>
<div>On 1/26/22 09:56, Eli Adam wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">Hi Dan and all,<br>
<input name="virtru-metadata" type="hidden" value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"enableNoauth":false,"persistentProtection":false,"expandedWatermarking":false,"expires":false,"isManaged":false},"attachments":{},"compose-id":"1","compose-window":{"secure":false}}">
<div><br>
</div>
<div>I added some comments to the wiki. </div>
<div><br>
</div>
<div>Generally I don't like the asynchronous meeting style. I
find myself tediously commenting on points that would be a
rapid discussion. I am a big fan of *preparation* in
advance of a meeting and think we could do more of that to
make our discussion more rapid and productive. </div>
<div><br>
</div>
<div>We should probably start our next meeting by running
through these points for discussion. Maybe preparing for
the meeting in advance as well. </div>
<div><br>
</div>
<div>Best regards, Eli</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Jan 25, 2022 at 4:32
AM Dan Little <<a href="mailto:theduckylittle@gmail.com" target="_blank">theduckylittle@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Hey Folks!</div>
<div><br>
</div>
<div>Please add your comments and that you've reviewed
last week's PSC meeting notes:<br>
</div>
<div><br>
</div>
<div>- <a href="https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2022-01-21" target="_blank">https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2022-01-21</a></div>
<div><br>
</div>
<div>Cheers!<br>
</div>
</div>
_______________________________________________<br>
geomoose-psc mailing list<br>
<a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
</blockquote>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
geomoose-psc mailing list
<a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
geomoose-psc mailing list<br>
<a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
</blockquote></div>
_______________________________________________<br>
geomoose-psc mailing list<br>
<a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
</blockquote></div>
_______________________________________________<br>
geomoose-psc mailing list<br>
<a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
</blockquote></div>