[geomoose-psc] Please add comments to last weeks agenda

Eli Adam eadam at co.lincoln.or.us
Mon Jan 31 07:47:25 PST 2022 

I can give 1pm Central (11am Pacific) a try.  Usually the beginning of the
day works better for me but I'll see how this goes.

Best regards, Eli

On Mon, Jan 31, 2022 at 7:21 AM James Klassen <klassen.js at gmail.com> wrote:

> 1pm central works for me
>
> > On Jan 31, 2022, at 08:22, Jeff McKenna <jmckenna at gatewaygeomatics.com>
> wrote:
> >
> > That timeslot could work for me (3pm Atlantic).  Since the PSC meetings
> are the 3rd Friday of the month (correct me if I'm wrong) that means Friday
> at 3pm to 4pm here.  (productivity does decrease for the later Friday
> meetings though, ha)
> >
> > I'd prefer IRC, as Libera chat is very stable (zero issues since it was
> created).  Also, I've been saving and posting the log online for the
> MapServer PSC meetings, I could do the same for the #geomoose meetings.
> >
> > I also prefer the scheduled monthly meetings, rather than unplanned ad
> hoc discussions, that are harder to follow.
> >
> > -jeff
> >
> >
> >
> >
> >
> >> On 2022-01-29 9:59 a.m., Dan Little wrote:
> >> +1 to a time change, that regular time slot has been getting hit by
> some of my rotating meetings -- this is new for 2022!
> >> How do folks feel about the 2:00PM Eastern / 1:00PM Central / Noon
> Mountain / 11:00AM Pacific timeslot?
> >> On Fri, Jan 28, 2022 at 1:12 PM TC Haddad <tchaddad at gmail.com <mailto:
> tchaddad at gmail.com>> wrote:
> >>    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.
> >>    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...
> >>    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.
> >>    Tanya
> >>    On Fri, Jan 28, 2022 at 5:41 AM Dan Little <theduckylittle at gmail.com
> >>    <mailto:theduckylittle at gmail.com>> wrote:
> >>        Any one have thoughts on using something like Slack or Discord?
> >>        Con:
> >>        - Not full open source managed.
> >>        - Not necessarily "universal" in the same as IRC.
> >>        Pro:
> >>        - Logging
> >>        - Web based client
> >>        - Data "take away" tools.
> >>        After the kurfluffle with freenode, I'm not sure there is much
> >>        distance in politics between something like Discord or Slack and
> >>        IRC.
> >>        On Wed, Jan 26, 2022 at 10:24 AM Jim Klassen
> >>        <klassen.js at gmail.com <mailto:klassen.js at gmail.com>> wrote:
> >>            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.
> >>>            On 1/26/22 09:56, Eli Adam wrote:
> >>>            Hi Dan and all,
> >>>
> >>>            I added some comments to the wiki.
> >>>
> >>>            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.
> >>>
> >>>            We should probably start our next meeting by running
> >>>            through these points for discussion.  Maybe preparing for
> >>>            the meeting in advance as well.
> >>>
> >>>            Best regards, Eli
> >>>
> >>>            On Tue, Jan 25, 2022 at 4:32 AM Dan Little
> >>>            <theduckylittle at gmail.com
> >>>            <mailto:theduckylittle at gmail.com>> wrote:
> >>>
> >>>                Hey Folks!
> >>>
> >>>                Please add your comments and that you've reviewed last
> >>>                week's PSC meeting notes:
> >>>
> >>>                -
> >>>
> https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2022-01-21
> >>>                <
> https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2022-01-21>
> >>>
> >>>                Cheers!
> >>>                _______________________________________________
> >>>                geomoose-psc mailing list
> >>>                geomoose-psc at lists.osgeo.org
> >>>                <mailto:geomoose-psc at lists.osgeo.org>
> >>>                https://lists.osgeo.org/mailman/listinfo/geomoose-psc
> >>>                <https://lists.osgeo.org/mailman/listinfo/geomoose-psc>
> >>>
> >>>
> >>>            _______________________________________________
> >>>            geomoose-psc mailing list
> >>>            geomoose-psc at lists.osgeo.org  <mailto:
> geomoose-psc at lists.osgeo.org>
> >>>            https://lists.osgeo.org/mailman/listinfo/geomoose-psc  <
> https://lists.osgeo.org/mailman/listinfo/geomoose-psc>
> >>            _______________________________________________
> >>            geomoose-psc mailing list
> >>            geomoose-psc at lists.osgeo.org
> >>            <mailto:geomoose-psc at lists.osgeo.org>
> >>            https://lists.osgeo.org/mailman/listinfo/geomoose-psc
> >>            <https://lists.osgeo.org/mailman/listinfo/geomoose-psc>
> >>        _______________________________________________
> >>        geomoose-psc mailing list
> >>        geomoose-psc at lists.osgeo.org <mailto:
> geomoose-psc at lists.osgeo.org>
> >>        https://lists.osgeo.org/mailman/listinfo/geomoose-psc
> >>        <https://lists.osgeo.org/mailman/listinfo/geomoose-psc>
> >>    _______________________________________________
> >>    geomoose-psc mailing list
> >>    geomoose-psc at lists.osgeo.org <mailto:geomoose-psc at lists.osgeo.org>
> >>    https://lists.osgeo.org/mailman/listinfo/geomoose-psc
> >>    <https://lists.osgeo.org/mailman/listinfo/geomoose-psc>
> >> _______________________________________________
> >> geomoose-psc mailing list
> >> geomoose-psc at lists.osgeo.org
> >> https://lists.osgeo.org/mailman/listinfo/geomoose-psc
> >
> >
> > --
> > Jeff McKenna
> > GatewayGeo: Developers of MS4W, MapServer Consulting and Training
> > co-founder of FOSS4G
> > http://gatewaygeo.com/
> > _______________________________________________
> > geomoose-psc mailing list
> > geomoose-psc at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/geomoose-psc
> _______________________________________________
> geomoose-psc mailing list
> geomoose-psc at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geomoose-psc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20220131/81c18c7b/attachment-0001.html>

More information about the geomoose-psc mailing list