plc4x-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Hutcheson <ben.hut...@gmail.com>
Subject Re: [DISCUSS] Start having a regular PLC4X community call?
Date Thu, 29 Oct 2020 00:52:17 GMT
Hi,

I'm in favour of a call every so often.

+1 for announcing it to the wider community.

Ben

On Wed, Oct 28, 2020 at 12:17 PM Lukas Ott <ott.lukas.14@gmail.com> wrote:

> Hi Chris,
>
> I personally would really appreciate such a meeting. As it helps to form a
> community and also increases transparency on the current stuff we are
> working on.
>
> Just because of time and effort in my humble opinion quarterly would be
> sufficient as most of the active developers are chatting on Slack anyways
> on our current topics.
>
> + We could announce these meetings via Twitter as well to make it visible
> and more transparent for others to be able to join and get in contact with
> us as well
>
> so +1 for starting such a thing.
>
> Lukas
>
> Am Mi., 28. Okt. 2020 um 17:06 Uhr schrieb Christofer Dutz <
> christofer.dutz@c-ware.de>:
>
> > Hi all,
> >
> > yesterdays the Mahout project started announcing to start having regular
> > community calls where anyone can join in.
> > These calls would sort of be used for chatting with the community and
> > perhaps exchanging where people need help, and generally exchanging
> > information.
> >
> > I know finding a time where everyone can participate will be impossible,
> I
> > would suggest doing it in the evening (Germany) so the folks in the
> > US/Canada can participate (morning)
> > Right now we definitely have more people actively working on plc4x if we
> > go West (EU and US) than going east (EU and Australia) … and this way we
> > can have a beer while at it ;-)
> >
> > I would propose a Wednesday 19:00 CET … and perhaps doing it every
> > (first/second/third/fourth) Wednesday of the month … (I’d prefer first or
> > second)
> >
> > What do you think? Should we start such a thing?
> >
> > Chris
> >
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message