[clug] Member Moderation - Bryan Kilgallin

[Michael Still]

Well in that case, I would like to propose that during next months junk
code session I could perhaps present...

A HIGHLY TECHNICAL talk about REVERSE ENGINEERING the Aussie Broadband
customer portal to explore their REST API, with the ultimate outcome being
implementing a python library which talks the API and is available on pip.
The whole talk should take about five minutes.

No acronyms will be explained. Dumb questions will receive dumb answers.

Michael


On Thu, Jul 4, 2019 at 2:30 PM Bob Edwards via linux <linux at lists.samba.org>
wrote:

> On 4/7/19 12:19 pm, Michael Still via linux wrote:
> > As someone who stopped attending CLUG because of Bryan, I think this is a
> > good first step and I appreciate the efforts of those who have done the
> > hard yards instead of running away like me.
> >
> > However, it doesn't resolve the other main issue -- I wont go to a CLUG
> > meeting if Bryan is there because I am unwilling to be in a room where
> > speakers are treated the way he treats them.
> >
> > Michael
>
> Hi Michael,
>
> My general observation is that the word "Technical" in the talk
> description seems to be sufficient to deter Bryan from attending
> CLUG meetings. "Highly technical" might work even better.
>
> So, let me encourage you to tempt fate and attend CLUG meetings
> listed as being "Technical" and you should be good... (we miss you!)
>
> We should still run "non-technical" talks/sessions at CLUG as I
> know there are many who appreciate those talks as well.
>
> cheers,
> Bob Edwards.
>
> >
> > On Thu, Jul 4, 2019 at 12:15 AM Steve Walsh via linux <
> linux at lists.samba.org>
> > wrote:
> >
> >> Hello Everyone
> >>
> >> We've had an unfortunate few days on the list, so in an effort to move
> >> forward with a more Linux-related discussion, I have requested the
> >> mailing list admins apply a moderation flag to Bryan Kilgallin's email
> >> address. Emails from Bryan will be held in a queue, and where the post
> >> positively contributes to an ongoing discussion, they will be released
> >> through to the list.
> >>
> >> To be balanced in this effort,  I have also sought volunteers from a
> >> selection of active list members to assist with the moderation of the
> >> email list.
> >>
> >> To help limit this from re-occurring in future, I've also done a first
> >> pass at a Code of Conduct for CLUG. This can be found online at
> >> https://gitlab.com/clug-au/code-of-conduct/blob/master/CodeOfConduct,
> >> and feedback is welcome.
> >>
> >> This document  is not an attempt to exclude people from meetings. It is,
> >> however, a guide that everyone can use to gauge what is acceptable
> >> behavior, both on the list and in our monthly face to face meetings.
> >>
> >> It is intended to be a living document and in an effort to be as open
> >> around this process as we can be, please send any edit suggestions to
> >> the list for discussion, and if the general consensus is they positively
> >> contribute to the CoC document and to the community, they'll be
> >> incorporated.
> >>
> >> Many thanks
> >>
> >> Steve
> >>
> >>
> >> --
> >> linux mailing list
> >> linux at lists.samba.org
> >> https://lists.samba.org/mailman/listinfo/linux
> >>
>
>
> --
> linux mailing list
> linux at lists.samba.org
> https://lists.samba.org/mailman/listinfo/linux
>