From ryan at rfk.id.au  Sun May  3 04:39:29 2015
From: ryan at rfk.id.au (Ryan Kelly)
Date: Sun, 03 May 2015 12:39:29 +1000
Subject: [melbourne-pug] Python Meetup, Monday 4th of May at 6pm
Message-ID: <55458A61.4080901@rfk.id.au>


Hi All,


After taking a break in April for Easter, the Melbourne Python Users
Group will be meeting again this Monday evening from 6pm.

  What?    Melbourne Python Meetup
  When?    Monday 4th of May, from 6pm
  Where?   Inspire9, 1/41 Stewart Street, Richmond

We've got two talks planned so far:

  * Juan Nunez-Iglesias will present on streaming data analysis.
  * Ryan Kelly will give a quick talk about PyCon Australia

There's still plenty of scope for an extra talk of two, so if you've got
something you'd like to share, let us know!

According to the Meetup page we've got at least 44 people who plan to be
there, so it should be a fun evening:

  http://www.meetup.com/Melbourne-Python-Meetup-Group/events/220301612/


Hope to see you there.


  Cheers,

    Ryan

From jni.soma at gmail.com  Mon May  4 15:52:53 2015
From: jni.soma at gmail.com (Juan Nunez-Iglesias)
Date: Mon, 04 May 2015 13:52:53 +0000
Subject: [melbourne-pug] Notes from today's talk
Message-ID: <CA+JHcKQ87fdPWLZhk-UrX7A3fAdgDsGKF3Sgy9fapPSXPZtPbg@mail.gmail.com>

Hi everyone,

Thanks for listening to my overly-long talk earlier today! I've cleaned up
my notes a bit:

https://github.com/jni/streaming-talk

The README contains info about the contents of that repo.

Some longer/more complete answers/stuff I forgot about for questions at the
end of the talk:
https://github.com/jni/streaming-talk/blob/master/notes.markdown#notes-for-follow-up-email-based-on-in-person-questions

Feel free to email me (or tweet at me) with follow-up questions, or
suggestions on how to improve the talk! I think there was a fair point that
some of my examples are a bit overboard with the toolz-ing. I wouldn't mind
if we had a competition for clarity/conciseness for those examples! =)

Juan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150504/d1b7b803/attachment.html>

From robertlayton at gmail.com  Tue May  5 14:01:53 2015
From: robertlayton at gmail.com (Robert Layton)
Date: Tue, 5 May 2015 22:01:53 +1000
Subject: [melbourne-pug]  Notes from today's talk
Message-ID: <CALcD8sgDgdqLAC0YvOjC66mvoGik7HyitfbrZkaz279CujrNkA@mail.gmail.com>

Great, thank you Juan!

On 5 May 2015 at 20:00, <melbourne-pug-request at python.org> wrote:

> Date: Mon, 04 May 2015 13:52:53 +0000
> From: Juan Nunez-Iglesias <jni.soma at gmail.com>
> To: Melbourne Python Users Group <melbourne-pug at python.org>
> Subject: [melbourne-pug] Notes from today's talk
> Message-ID:
>         <
> CA+JHcKQ87fdPWLZhk-UrX7A3fAdgDsGKF3Sgy9fapPSXPZtPbg at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi everyone,
>
> Thanks for listening to my overly-long talk earlier today! I've cleaned up
> my notes a bit:
>
> https://github.com/jni/streaming-talk
>
> The README contains info about the contents of that repo.
>
> Some longer/more complete answers/stuff I forgot about for questions at the
> end of the talk:
>
> https://github.com/jni/streaming-talk/blob/master/notes.markdown#notes-for-follow-up-email-based-on-in-person-questions
>
> Feel free to email me (or tweet at me) with follow-up questions, or
> suggestions on how to improve the talk! I think there was a fair point that
> some of my examples are a bit overboard with the toolz-ing. I wouldn't mind
> if we had a competition for clarity/conciseness for those examples! =)
>
> Juan.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150505/9dade5e0/attachment.html>

From gcross at fastmail.fm  Tue May 12 08:41:30 2015
From: gcross at fastmail.fm (Graeme Cross)
Date: Tue, 12 May 2015 16:41:30 +1000
Subject: [melbourne-pug] Fwd: [luv-announce] LUV Main June 2015 Meeting:
 Using deep mutational scanning to understand protein function / Drupal8 out
 of the box
Message-ID: <1431412890.3333308.266361065.2C771021@webmail.messagingengine.com>

Hi all.

The talk on "deep mutational scanning" might be of interest to some of
the people on this list given the Python connection.

Regards,
Graeme


----- Original message -----
From: Andrew Pam <andrew at sericyb.com.au>
To: luv-announce at luv.asn.au
Subject: [luv-announce] LUV Main June 2015 Meeting: Using deep
mutational scanning to understand protein function / Drupal8 out of the
box
Date: Tue, 12 May 2015 15:36:01 +1000

Start: Jun 2 2015 19:00
End: Jun 2 2015 21:00
Location: The Buzzard Lecture Theatre. Evan Burge Building, Trinity
College, Melbourne University Main Campus, Parkville.
Link: http://luv.asn.au/meetings/map

Speakers:

? Alan Rubin: Using deep mutational scanning to understand protein
function
? Donna Benjamin: Drupal8 out of the box


Alan Rubin: Using deep mutational scanning to understand protein
function

High-throughput DNA sequencing enables researchers to identify normal
and disease-associated genetic variation faster than ever before.
However, the functional consequences of most mutations are unknown. Deep
mutational scanning is a method for directly measuring the activity of
hundreds of thousands of variants of a protein quickly, easily, and
cheaply. This allows researchers to analyze huge quantities of data and
identify interesting targets for further research in a variety of
contexts, from aiding the assessment of clinical variants to guiding
protein engineering.

Alan will describe a typical deep mutational scanning experiment, and
give examples of applications for this technology. He will also present
Enrich 2, a Python-based software package that makes deep mutational
scanning data analysis accessible to experimental biologists while
providing an extensible framework for bioinformaticians manipulating
these large datasets.

Alan Rubin is a computational biologist at The Walter and Eliza Hall
Insitute of Medical Research, where he works in the labs of Tony
Papenfuss and Terry Speed in the Bioinformatics division. He joined the
institute in February of 2014 after completing his PhD with Phil Green
in the Department of Genome Sciences at the University of Washington.
His primary research interests are functional genomics and genomic
technology development.


Donna Benjamin: Drupal8 out of the box

Drupal 8 has been in development for over 4 years. Now in Beta, the
community is working hard to resolve the remaining release blockers.
Even so, Drupal 8 is a huge step forward.

With the WYSIWYG CKeditor and Views module now in core Drupal 8 is a
very capable and easy to use content management platform. The new
configuration management system and approach to web services will make
life easier for Devops and integrations.

Donna will outline the 8 big changes in Drupal 8 and demo what it can do
out of the box.

Donna Benjamin runs a small business called Creative Contingencies, sits
on the board of the Drupal Association and chairs the Drupal Community
Working Group. She also served as President of LUV from 2008 to 2010.


The Buzzard Lecture Theatre, Evan Burge Building, Trinity College Main
Campus Parkville Melways Map: 2B C5

Notes: Trinity College's Main Campus is located off Royal Parade. The
Evan Burge Building is located near the Tennis Courts. See our Map of
Trinity College. Additional maps of Trinity and the surrounding area
(including its relation to the city) can be found at
http://www.trinity.unimelb.edu.au/about/location/map

Parking can be found along or near Royal Parade, Grattan Street,
Swanston Street and College Crescent. Parking within Trinity College is
unfortunately only available to staff.

For those coming via Public Transport, the number 19 tram (North Coburg
- City) passes by the main entrance of Trinity College (Get off at
Morrah St, Stop 12). This tram departs from the Elizabeth Street tram
terminus (Flinders Street end) and goes past Melbourne Central
Timetables can be found on-line at:

http://www.metlinkmelbourne.com.au/route/view/725

Before and/or after each meeting those who are interested are welcome to
join other members for dinner. We are open to suggestions for a good
place to eat near our venue. Maria's on Peel Street in North Melbourne
is currently the most popular place to eat after meetings.

LUV would like to acknowledge Red Hat for their help in obtaining the
Buzzard Lecture Theatre venue and VPAC for hosting.

Linux Users of Victoria Inc. is an incorporated association,
registration number A0040056C.
_______________________________________________
luv-announce mailing list
luv-announce at luv.asn.au
http://lists.luv.asn.au/listinfo/luv-announce

From alec at lookahead.com.au  Tue May 19 23:24:24 2015
From: alec at lookahead.com.au (Alec Sloman - Lookahead Search)
Date: Wed, 20 May 2015 07:24:24 +1000
Subject: [melbourne-pug] Hello from Alec @ Lookahead
Message-ID: <555BAA08.8070709@lookahead.com.au>

Hello friends,

My name is Alec Sloman. I?m a technical recruiter at Lookahead Search.

Now, before you get out the pitchforks and chase me off, please let me 
explain.

Yes, I have a job to post here. No. I am not the hiring company itself. 
I read the rules, and decided to ask for forgiveness rather than 
permission, because I think it?s an interesting role.

So you?ve heard of Powershop perhaps?

Yes, well they are currently seeking a Python/Django developer to work 
on their internal Australian energy market intelligence systems.

Basically, their analysts have a tool that was developed by contractors 
that now needs a full-time maintainer / feature developer.

ATM it?s a Django app that queries a whole bunch of energy market DBs 
and provides a nice bootstrappy interface.

Pretty sure it?s hosted on physical machines on premise, ATM, so anyone 
who is comfortable rolling that into the cloud, that could be step 1.

Step 2 would be to have lots of discussions with their energy market 
analysts and help them make the tool even more useful.

As I?m sure you know, the Australian energy market is kinda? bonkers? 
and they?re trying to get a handle on it. This tool is all about 
intelligence in that space.

And they?ve got /a lot/ of data to work with.

So other things that are important include:

  * SQL (writing lotsa queries)
  * Postgres (they maybe want to migrate from MySQL, actually they do ;) )
  * R
  * General Python-based tooling
  * Setup continuous deploy to cloud

If any of that sounds like you, and you are interested to know more, 
please email me on alec at lookahead.com.au

I?m @alec_sloman on Twitter, too.

And by the way LARS YENCKEN, if you?re reading this? have a great time 
in Stockholm.

I?ll be waiting patiently for you return :?)

Best regards,
Alec

?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150520/a277ce08/attachment.html>

From tleeuwenburg at gmail.com  Thu May 21 04:24:04 2015
From: tleeuwenburg at gmail.com (Tennessee Leeuwenburg)
Date: Thu, 21 May 2015 12:24:04 +1000
Subject: [melbourne-pug] Position vacant at Bureau of Meteorology
Message-ID: <CADhgxgccmry5h9YMQhf+zCOcR9x81LPpV0h80-sFMszL0g4FLA@mail.gmail.com>

Hi all,

I wanted to share information about a position which has opened on my team
at the Bureau of Meteorology.

http://tinyurl.com/my3e4u4

The linked web page contains all the relevant information regarding the
job, pay and process. The "Full job details" contain the technical detail,
the web page provides the overview.

Regards,
-Tennessee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150521/621a3294/attachment.html>

From brian at microcomaustralia.com.au  Mon May 25 01:54:34 2015
From: brian at microcomaustralia.com.au (Brian May)
Date: Sun, 24 May 2015 23:54:34 +0000
Subject: [melbourne-pug] Hello from Alec @ Lookahead
In-Reply-To: <555BAA08.8070709@lookahead.com.au>
References: <555BAA08.8070709@lookahead.com.au>
Message-ID: <CAA0ZO6Cmtr1cLt9ps-BMpBAwqj=1x-utwMTvhoiviubL5SonNQ@mail.gmail.com>

On Wed, 20 May 2015 at 11:37 Alec Sloman - Lookahead Search <
alec at lookahead.com.au> wrote:

>  So other things that are important include:
>
>    - SQL (writing lotsa queries)
>    - Postgres (they maybe want to migrate from MySQL, actually they do ;)
>    )
>    - R
>    - General Python-based tooling
>    - Setup continuous deploy to cloud
>
> If any of that sounds like you, and you are interested to know more,
> please email me on alec at lookahead.com.au
>
> I?m @alec_sloman on Twitter, too.
>

Hello,

I am interested in the above position, and believe I have the majority of
the above skills. I am currently the lead developer in Karaage <
https://github.com/Karaage-Cluster/>, and as I result I am experienced in
Python2, Python3, Mysql, Postgresql, Django, Continuous Integration, etc. I
am also a Debian developer and hold a PhD in computer authentication
techniques.

Where is this work located?

Apologies for the late response; I only found out last Friday that my
current position at VPAC is being made redundant (4 weeks notice) due to
poor financial status. As as I result, I still need to update my resume.

Regards.
Brian May

PS. Sorry, I don't seem to have a pitchfork handy :-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150524/f485a551/attachment.html>

From brian at microcomaustralia.com.au  Mon May 25 04:51:30 2015
From: brian at microcomaustralia.com.au (Brian May)
Date: Mon, 25 May 2015 02:51:30 +0000
Subject: [melbourne-pug] last post
Message-ID: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>

Apologies for the last post - assuming it got through, it was suppose to be
a private reply, but I failed to notice in time that this mailing list sets
the reply-to header, and as such the private reply was redirected back to
the list[1].

I don't think there was anything actually private in my email, however
apologies for breaking mailing list etiquette.

[1] This is the reason I fall into the "mailing list automatically setting
reply-to header is bad" camp.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150525/15c4d67e/attachment.html>

From noonslists at gmail.com  Mon May 25 08:06:08 2015
From: noonslists at gmail.com (Noon Silk)
Date: Mon, 25 May 2015 16:06:08 +1000
Subject: [melbourne-pug] last post
In-Reply-To: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>
References: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>
Message-ID: <CADt_azZKuj8RcvRd=hP8rnB=fvGJw1hH=c3mo6WAD-T-gMoTcw@mail.gmail.com>

> [1] This is the reason I fall into the "mailing list automatically
setting reply-to header is bad" camp.

Yeah, I think I kind of agree actually.

--
Noon


On Mon, May 25, 2015 at 12:51 PM, Brian May <brian at microcomaustralia.com.au>
wrote:

> Apologies for the last post - assuming it got through, it was suppose to
> be a private reply, but I failed to notice in time that this mailing list
> sets the reply-to header, and as such the private reply was redirected back
> to the list[1].
>
> I don't think there was anything actually private in my email, however
> apologies for breaking mailing list etiquette.
>
> [1] This is the reason I fall into the "mailing list automatically setting
> reply-to header is bad" camp.
>
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> https://mail.python.org/mailman/listinfo/melbourne-pug
>
>


-- 
Noon Silk, ?

https://sites.google.com/site/noonsilk/

"Every morning when I wake up, I experience an exquisite joy ? the joy
of being this signature."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150525/adc13c55/attachment.html>

From tleeuwenburg at gmail.com  Mon May 25 08:37:19 2015
From: tleeuwenburg at gmail.com (Tennessee Leeuwenburg)
Date: Mon, 25 May 2015 16:37:19 +1000
Subject: [melbourne-pug] last post
In-Reply-To: <CADt_azZKuj8RcvRd=hP8rnB=fvGJw1hH=c3mo6WAD-T-gMoTcw@mail.gmail.com>
References: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>
 <CADt_azZKuj8RcvRd=hP8rnB=fvGJw1hH=c3mo6WAD-T-gMoTcw@mail.gmail.com>
Message-ID: <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>

Six of one, half a dozen of the other. I've never found a 'best' setting,
you just have to choose your preferred set of hassles.

I'll change it if 70% of people agree and at least ten people express an
opinion. That's because I value stability at 25% but I can't have half a
person if only ten people vote :).

Cheers,
-T

On 25 May 2015 at 16:06, Noon Silk <noonslists at gmail.com> wrote:

> > [1] This is the reason I fall into the "mailing list automatically
> setting reply-to header is bad" camp.
>
> Yeah, I think I kind of agree actually.
>
> --
> Noon
>
>
> On Mon, May 25, 2015 at 12:51 PM, Brian May <
> brian at microcomaustralia.com.au> wrote:
>
>> Apologies for the last post - assuming it got through, it was suppose to
>> be a private reply, but I failed to notice in time that this mailing list
>> sets the reply-to header, and as such the private reply was redirected back
>> to the list[1].
>>
>> I don't think there was anything actually private in my email, however
>> apologies for breaking mailing list etiquette.
>>
>> [1] This is the reason I fall into the "mailing list automatically
>> setting reply-to header is bad" camp.
>>
>> _______________________________________________
>> melbourne-pug mailing list
>> melbourne-pug at python.org
>> https://mail.python.org/mailman/listinfo/melbourne-pug
>>
>>
>
>
> --
> Noon Silk, ?
>
> https://sites.google.com/site/noonsilk/
>
> "Every morning when I wake up, I experience an exquisite joy ? the joy
> of being this signature."
>
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> https://mail.python.org/mailman/listinfo/melbourne-pug
>
>


-- 
--------------------------------------------------
Tennessee Leeuwenburg
http://myownhat.blogspot.com/
"Don't believe everything you think"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150525/b6f4eecd/attachment-0001.html>

From jni.soma at gmail.com  Mon May 25 09:10:49 2015
From: jni.soma at gmail.com (Juan Nunez-Iglesias)
Date: Mon, 25 May 2015 00:10:49 -0700 (PDT)
Subject: [melbourne-pug] last post
In-Reply-To: <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
References: <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
Message-ID: <1432537848987.abde6983@Nodemailer>

I vote against changing. The default interaction with a mailing list is to write back to the list. And Reply-all ends up polluting people's inboxes who might have otherwise not wanted to stay on that thread.

On Mon, May 25, 2015 at 4:37 PM, Tennessee Leeuwenburg
<tleeuwenburg at gmail.com> wrote:

> Six of one, half a dozen of the other. I've never found a 'best' setting,
> you just have to choose your preferred set of hassles.
> I'll change it if 70% of people agree and at least ten people express an
> opinion. That's because I value stability at 25% but I can't have half a
> person if only ten people vote :).
> Cheers,
> -T
> On 25 May 2015 at 16:06, Noon Silk <noonslists at gmail.com> wrote:
>> > [1] This is the reason I fall into the "mailing list automatically
>> setting reply-to header is bad" camp.
>>
>> Yeah, I think I kind of agree actually.
>>
>> --
>> Noon
>>
>>
>> On Mon, May 25, 2015 at 12:51 PM, Brian May <
>> brian at microcomaustralia.com.au> wrote:
>>
>>> Apologies for the last post - assuming it got through, it was suppose to
>>> be a private reply, but I failed to notice in time that this mailing list
>>> sets the reply-to header, and as such the private reply was redirected back
>>> to the list[1].
>>>
>>> I don't think there was anything actually private in my email, however
>>> apologies for breaking mailing list etiquette.
>>>
>>> [1] This is the reason I fall into the "mailing list automatically
>>> setting reply-to header is bad" camp.
>>>
>>> _______________________________________________
>>> melbourne-pug mailing list
>>> melbourne-pug at python.org
>>> https://mail.python.org/mailman/listinfo/melbourne-pug
>>>
>>>
>>
>>
>> --
>> Noon Silk, ?
>>
>> https://sites.google.com/site/noonsilk/
>>
>> "Every morning when I wake up, I experience an exquisite joy ? the joy
>> of being this signature."
>>
>> _______________________________________________
>> melbourne-pug mailing list
>> melbourne-pug at python.org
>> https://mail.python.org/mailman/listinfo/melbourne-pug
>>
>>
> -- 
> --------------------------------------------------
> Tennessee Leeuwenburg
> http://myownhat.blogspot.com/
> "Don't believe everything you think"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150525/b5ba1f31/attachment.html>

From william.leslie.ttg at gmail.com  Mon May 25 10:02:16 2015
From: william.leslie.ttg at gmail.com (William ML Leslie)
Date: Mon, 25 May 2015 18:02:16 +1000
Subject: [melbourne-pug] last post
In-Reply-To: <1432537848987.abde6983@Nodemailer>
References: <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
 <1432537848987.abde6983@Nodemailer>
Message-ID: <CAHgd1hHOAgukmM0+vnsCOfduo3ZYr9kiNFw6NvFiQyyLfnaJbQ@mail.gmail.com>

On 25 May 2015 at 17:10, Juan Nunez-Iglesias <jni.soma at gmail.com> wrote:

> I vote against changing. The default interaction with a mailing list is to
> write back to the list. And Reply-all ends up polluting people's inboxes
> who might have otherwise not wanted to stay on that thread.


+1 for the list being the default reply-to.

It's frustrating either way, but reply-to list usually what you mean to
do.  pypy-dev is an example that does not do this, and every time I use
that list I forget, and email someone privately, messing up the entire
conversation.

Barring a permanent set of coffee-goggles that force you to swear an
undying oath that you really really want to reply to that one user (or
everyone, or the list), and/or a way to configure it in your personal
account in mailman, `reply-to: mpug` is the thing.

-- 
William Leslie

Notice:
Likely much of this email is, by the nature of copyright, covered under
copyright law.  You absolutely MAY reproduce any part of it in accordance
with the copyright law of the nation you are reading this in.  Any attempt
to DENY YOU THOSE RIGHTS would be illegal without prior contractual
agreement.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150525/6f5ab511/attachment.html>

From h.dashnow at gmail.com  Mon May 25 09:21:45 2015
From: h.dashnow at gmail.com (Harriet Dashnow)
Date: Mon, 25 May 2015 17:21:45 +1000
Subject: [melbourne-pug] last post
In-Reply-To: <1432537848987.abde6983@Nodemailer>
References: <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
 <1432537848987.abde6983@Nodemailer>
Message-ID: <CAKouk=QU6fNu8FWG2sG9tXNFbJYS8gZgGu=GndiZNJbPSnLBeg@mail.gmail.com>

I like it as-is. You have to deliberately go off-list.

On Mon, May 25, 2015 at 5:10 PM, Juan Nunez-Iglesias <jni.soma at gmail.com>
wrote:

> I vote against changing. The default interaction with a mailing list is to
> write back to the list. And Reply-all ends up polluting people's inboxes
> who might have otherwise not wanted to stay on that thread.
>
>
>
>
> On Mon, May 25, 2015 at 4:37 PM, Tennessee Leeuwenburg <
> tleeuwenburg at gmail.com> wrote:
>
>> Six of one, half a dozen of the other. I've never found a 'best' setting,
>> you just have to choose your preferred set of hassles.
>>
>> I'll change it if 70% of people agree and at least ten people express an
>> opinion. That's because I value stability at 25% but I can't have half a
>> person if only ten people vote :).
>>
>> Cheers,
>> -T
>>
>> On 25 May 2015 at 16:06, Noon Silk <noonslists at gmail.com> wrote:
>>
>>>  > [1] This is the reason I fall into the "mailing list automatically
>>> setting reply-to header is bad" camp.
>>>
>>> Yeah, I think I kind of agree actually.
>>>
>>> --
>>> Noon
>>>
>>>
>>> On Mon, May 25, 2015 at 12:51 PM, Brian May <
>>> brian at microcomaustralia.com.au> wrote:
>>>
>>>>  Apologies for the last post - assuming it got through, it was suppose
>>>> to be a private reply, but I failed to notice in time that this mailing
>>>> list sets the reply-to header, and as such the private reply was redirected
>>>> back to the list[1].
>>>>
>>>> I don't think there was anything actually private in my email, however
>>>> apologies for breaking mailing list etiquette.
>>>>
>>>> [1] This is the reason I fall into the "mailing list automatically
>>>> setting reply-to header is bad" camp.
>>>>
>>>> _______________________________________________
>>>> melbourne-pug mailing list
>>>> melbourne-pug at python.org
>>>> https://mail.python.org/mailman/listinfo/melbourne-pug
>>>>
>>>>
>>>
>>>
>>> --
>>> Noon Silk, ?
>>>
>>> https://sites.google.com/site/noonsilk/
>>>
>>> "Every morning when I wake up, I experience an exquisite joy ? the joy
>>> of being this signature."
>>>
>>> _______________________________________________
>>> melbourne-pug mailing list
>>> melbourne-pug at python.org
>>> https://mail.python.org/mailman/listinfo/melbourne-pug
>>>
>>>
>>
>>
>> --
>> --------------------------------------------------
>> Tennessee Leeuwenburg
>> http://myownhat.blogspot.com/
>> "Don't believe everything you think"
>>
>
>
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> https://mail.python.org/mailman/listinfo/melbourne-pug
>
>


-- 
Harriet Dashnow
BSc, BA, MSc (Bioinformatics), PhD candidate
au.linkedin.com/in/hdashnow
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150525/aafc7d13/attachment-0001.html>

From n6151h at gmail.com  Mon May 25 10:36:09 2015
From: n6151h at gmail.com (N6151H)
Date: Mon, 25 May 2015 18:36:09 +1000
Subject: [melbourne-pug] last post
In-Reply-To: <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
References: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>
 <CADt_azZKuj8RcvRd=hP8rnB=fvGJw1hH=c3mo6WAD-T-gMoTcw@mail.gmail.com>
 <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
Message-ID: <CALz4+LLERLrXuiVEXFj814T8fGWoqnZFz5zA09-g=pR4AV7Dwg@mail.gmail.com>

I vote leave it as-is.

Nick

On Mon, May 25, 2015 at 4:37 PM, Tennessee Leeuwenburg <
tleeuwenburg at gmail.com> wrote:

> Six of one, half a dozen of the other. I've never found a 'best' setting,
> you just have to choose your preferred set of hassles.
>
> I'll change it if 70% of people agree and at least ten people express an
> opinion. That's because I value stability at 25% but I can't have half a
> person if only ten people vote :).
>
> Cheers,
> -T
>
> On 25 May 2015 at 16:06, Noon Silk <noonslists at gmail.com> wrote:
>
>> > [1] This is the reason I fall into the "mailing list automatically
>> setting reply-to header is bad" camp.
>>
>> Yeah, I think I kind of agree actually.
>>
>> --
>> Noon
>>
>>
>> On Mon, May 25, 2015 at 12:51 PM, Brian May <
>> brian at microcomaustralia.com.au> wrote:
>>
>>> Apologies for the last post - assuming it got through, it was suppose to
>>> be a private reply, but I failed to notice in time that this mailing list
>>> sets the reply-to header, and as such the private reply was redirected back
>>> to the list[1].
>>>
>>> I don't think there was anything actually private in my email, however
>>> apologies for breaking mailing list etiquette.
>>>
>>> [1] This is the reason I fall into the "mailing list automatically
>>> setting reply-to header is bad" camp.
>>>
>>> _______________________________________________
>>> melbourne-pug mailing list
>>> melbourne-pug at python.org
>>> https://mail.python.org/mailman/listinfo/melbourne-pug
>>>
>>>
>>
>>
>> --
>> Noon Silk, ?
>>
>> https://sites.google.com/site/noonsilk/
>>
>> "Every morning when I wake up, I experience an exquisite joy ? the joy
>> of being this signature."
>>
>> _______________________________________________
>> melbourne-pug mailing list
>> melbourne-pug at python.org
>> https://mail.python.org/mailman/listinfo/melbourne-pug
>>
>>
>
>
> --
> --------------------------------------------------
> Tennessee Leeuwenburg
> http://myownhat.blogspot.com/
> "Don't believe everything you think"
>
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> https://mail.python.org/mailman/listinfo/melbourne-pug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150525/c1085c06/attachment.html>

From ben+python at benfinney.id.au  Mon May 25 20:32:47 2015
From: ben+python at benfinney.id.au (Ben Finney)
Date: Tue, 26 May 2015 04:32:47 +1000
Subject: [melbourne-pug] last post
References: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>
 <CADt_azZKuj8RcvRd=hP8rnB=fvGJw1hH=c3mo6WAD-T-gMoTcw@mail.gmail.com>
 <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
Message-ID: <85vbfgwlrk.fsf@benfinney.id.au>

Tennessee Leeuwenburg <tleeuwenburg at gmail.com> writes:

> Six of one, half a dozen of the other.

It really isn't, though. Setting ?Reply-To? to the mailing list is
significantly more harmful than leaving that field alone.

* The failure mode of ?don't do anything with Reply-To? is that
  sometimes people send a message to an individual, that they *intended*
  to go more public.

* The failure mode of ?set Reply-To to the mailing list? is that
  sometimes people send a message publicly, that they *intended* to be
  private to an individual.

Which failure is easier to recover?

The former is hardly any damage at all; recovery simply requires sending
the message again to the correct address.

The latter is unrecoverable. Once a message has been sent more publicly
than intended, it cannot be un-sent.

Setting ?Reply-To? to the list is much more troublesome for those who
run afoul of it.

> I've never found a 'best' setting, you just have to choose your
> preferred set of hassles.

So it's not merely a matter of preference. One mode is clearly more
damaging than the other.

> I'll change it if 70% of people agree and at least ten people express
> an opinion. That's because I value stability at 25% but I can't have
> half a person if only ten people vote :).

Because the failure mode of ?don't do anything with Reply-To? is
harmless and easily recovered, I vote for that.

This shouldn't be decided by vote, though. It should be decided by doing
the least harm.

-- 
 \                ?Room service? Send up a larger room.? ?Groucho Marx |
  `\                                                                   |
_o__)                                                                  |
Ben Finney


From marek at kuziel.info  Mon May 25 13:21:20 2015
From: marek at kuziel.info (Marek Kuziel)
Date: Mon, 25 May 2015 23:21:20 +1200
Subject: [melbourne-pug] Kiwi PyCon 2015 - Call for Proposals!
Message-ID: <CANMeXfuDZXNZoh0vdEPaawkVEJ+kVWyOSUpMfzcm26_kT=zevw@mail.gmail.com>

Dear Pythonistas,

The New Zealand Python User Group and the Kiwi PyCon 2015 committee are
pleased to announce the opening of the Call for Proposals for this year's
Kiwi PyCon.

Kiwi PyCon is an independent, community-run and not-for-profit conference
dedicated to the Python programming language. Kiwi PyCon 2015 will be held
on the 4th, 5th and 6th of September.

The venue for this year are the Central Lecture Theatres of The University
of Canterbury in Riccarton, just 30 minutes walk from what is left of the
Christchurch CBD.

The submission deadline for proposals is Monday the 22th of June, 2015.
That's four weeks away, so get your thinking caps on!

More on the conference can be found at:

        http://kiwi.pycon.org

and the details for the Call for Proposals can be perused at:

        http://kiwi.pycon.org/call-for-proposals/

We're looking for talks, tutorials and posters on all aspects of Python.

We especially welcome first-time speakers; we are a community conference
and are eager to hear about your experience. If you have friends or
colleagues who have something to contribute, please twist their arm
(gently!) to talk about it!

If you have the seed of an idea, head over to http://kiwi.pycon.org/ and
create a user account. Fill in some details, and submit your talk. We're
looking forward to hearing about it!

Marek Kuziel, on behalf of the New Zealand Python User Group
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150525/48ce8b36/attachment.html>

From n6151h at gmail.com  Tue May 26 01:17:36 2015
From: n6151h at gmail.com (N6151H)
Date: Tue, 26 May 2015 09:17:36 +1000
Subject: [melbourne-pug] last post
In-Reply-To: <85vbfgwlrk.fsf@benfinney.id.au>
References: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>
 <CADt_azZKuj8RcvRd=hP8rnB=fvGJw1hH=c3mo6WAD-T-gMoTcw@mail.gmail.com>
 <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
 <85vbfgwlrk.fsf@benfinney.id.au>
Message-ID: <CALz4+LJXc=qC9Pk=yXR9eKDuzy4R0iEGzfc-jAik6N_kFJJFyw@mail.gmail.com>

"Harm"?

Really?

Nick

On Tue, May 26, 2015 at 4:32 AM, Ben Finney <ben+python at benfinney.id.au>
wrote:

> Tennessee Leeuwenburg <tleeuwenburg at gmail.com> writes:
>
> > Six of one, half a dozen of the other.
>
> It really isn't, though. Setting ?Reply-To? to the mailing list is
> significantly more harmful than leaving that field alone.
>
> * The failure mode of ?don't do anything with Reply-To? is that
>   sometimes people send a message to an individual, that they *intended*
>   to go more public.
>
> * The failure mode of ?set Reply-To to the mailing list? is that
>   sometimes people send a message publicly, that they *intended* to be
>   private to an individual.
>
> Which failure is easier to recover?
>
> The former is hardly any damage at all; recovery simply requires sending
> the message again to the correct address.
>
> The latter is unrecoverable. Once a message has been sent more publicly
> than intended, it cannot be un-sent.
>
> Setting ?Reply-To? to the list is much more troublesome for those who
> run afoul of it.
>
> > I've never found a 'best' setting, you just have to choose your
> > preferred set of hassles.
>
> So it's not merely a matter of preference. One mode is clearly more
> damaging than the other.
>
> > I'll change it if 70% of people agree and at least ten people express
> > an opinion. That's because I value stability at 25% but I can't have
> > half a person if only ten people vote :).
>
> Because the failure mode of ?don't do anything with Reply-To? is
> harmless and easily recovered, I vote for that.
>
> This shouldn't be decided by vote, though. It should be decided by doing
> the least harm.
>
> --
>  \                ?Room service? Send up a larger room.? ?Groucho Marx |
>   `\                                                                   |
> _o__)                                                                  |
> Ben Finney
>
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> https://mail.python.org/mailman/listinfo/melbourne-pug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150526/e93d2aa2/attachment.html>

From brian at microcomaustralia.com.au  Tue May 26 02:07:28 2015
From: brian at microcomaustralia.com.au (Brian May)
Date: Tue, 26 May 2015 00:07:28 +0000
Subject: [melbourne-pug] last post
In-Reply-To: <CALz4+LJXc=qC9Pk=yXR9eKDuzy4R0iEGzfc-jAik6N_kFJJFyw@mail.gmail.com>
References: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>
 <CADt_azZKuj8RcvRd=hP8rnB=fvGJw1hH=c3mo6WAD-T-gMoTcw@mail.gmail.com>
 <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
 <85vbfgwlrk.fsf@benfinney.id.au>
 <CALz4+LJXc=qC9Pk=yXR9eKDuzy4R0iEGzfc-jAik6N_kFJJFyw@mail.gmail.com>
Message-ID: <CAA0ZO6DONPQi+ykaJ7qGHBxYgy19Jh0kGuZsnTwYHzrDwQ72cA@mail.gmail.com>

On Tue, 26 May 2015 at 09:25 N6151H <n6151h at gmail.com> wrote:

> * The failure mode of ?don't do anything with Reply-To? is that
>>   sometimes people send a message to an individual, that they *intended*
>>   to go more public.
>>
>> * The failure mode of ?set Reply-To to the mailing list? is that
>>   sometimes people send a message publicly, that they *intended* to be
>>   private to an individual.
>>
>> Which failure is easier to recover?
>>
>> The former is hardly any damage at all; recovery simply requires sending
>> the message again to the correct address.
>>
>
I agree 100% with this line of reasoning. In my situation there was no harm
done by my email, my manager fully supports me looking for new work.

In another situation however if my management found out I was looking for
more work that could place my current position in serious jeopardy.

Or if I sent a response to an email saying "I don't like XYZ, he has
totally stuffed up package ZYX" and XYZ saw the message this could be
equally as damaging, with no possibility of correcting it.

Sure it is annoying to accidentally have a public message become private,
however it is easy to rectify. Also it is generally speaking easy to filter
out duplicate emails, if you don't like people CCing you.

At the very least, we should have information somewhere about posting job
advertisements to this list (I thought there was something already, but
can't find it), and recommend that all job advertisements have Reply-To:
preset - I believe mailman will see that Reply-To is already set and not
change it (do we need to double check this?).

Having said that, this is one mistake I personally am not likely to make
again in a hurry.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150526/fd6d9938/attachment-0001.html>

From miked at dewhirst.com.au  Tue May 26 04:21:21 2015
From: miked at dewhirst.com.au (Mike Dewhirst)
Date: Tue, 26 May 2015 12:21:21 +1000
Subject: [melbourne-pug] last post
In-Reply-To: <CAA0ZO6DONPQi+ykaJ7qGHBxYgy19Jh0kGuZsnTwYHzrDwQ72cA@mail.gmail.com>
References: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>
 <CADt_azZKuj8RcvRd=hP8rnB=fvGJw1hH=c3mo6WAD-T-gMoTcw@mail.gmail.com>
 <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
 <85vbfgwlrk.fsf@benfinney.id.au>
 <CALz4+LJXc=qC9Pk=yXR9eKDuzy4R0iEGzfc-jAik6N_kFJJFyw@mail.gmail.com>
 <CAA0ZO6DONPQi+ykaJ7qGHBxYgy19Jh0kGuZsnTwYHzrDwQ72cA@mail.gmail.com>
Message-ID: <5563D8A1.3030400@dewhirst.com.au>

On 26/05/2015 10:07 AM, Brian May wrote:
> On Tue, 26 May 2015 at 09:25 N6151H <n6151h at gmail.com
> <mailto:n6151h at gmail.com>> wrote:
>
>         * The failure mode of ???don't do anything with Reply-To??? is that
>         ?  sometimes people send a message to an individual, that they
>         *intended*
>         ?  to go more public.
>
>         * The failure mode of ???set Reply-To to the mailing list??? is that
>         ?  sometimes people send a message publicly, that they
>         *intended* to be
>         ?  private to an individual.
>
>         Which failure is easier to recover?
>
>         The former is hardly any damage at all; recovery simply requires
>         sending
>         the message again to the correct address.
>
>
> I agree 100% with this line of reasoning. In my situation there was no
> harm done by my email, my manager fully supports me looking for new work.

I disagree 75%

I believe the only sensible approach to email - and most other internet 
based communication channels - is to assume *nothing* is private. One 
way or another, sooner or later, it will reveal itself.

In that circumstance, the concept of "harm" must be regarded as 
self-inflicted.

So I vote for convenience for the majority trumping self-inflicted 
"harm" for the minority.

That "convenience" is 100% normal for the younger generation. And it 
seems there is more of them as each day passes!

It is not normal for the oldies who grew up with vanilla aliases serving 
as mailing lists and therefore required a Reply-all to include the list. 
We oldies just need to get over it.

I still use some alias-style "lists" hence my 75% disagreement. Bottom 
line is that we should always engage brain before dropping the clutch.

Cheers

Mike

>
> In another situation however if my management found out I was looking
> for more work that could place my current position in serious jeopardy.
>
> Or if I sent a response to an email saying "I don't like XYZ, he has
> totally stuffed up package ZYX" and XYZ saw the message this could be
> equally as damaging, with no possibility of correcting it.
>
> Sure it is annoying to accidentally have a public message become
> private, however it is easy to rectify. Also it is generally speaking
> easy to filter out duplicate emails, if you don't like people CCing you.
>
> At the very least, we should have information somewhere about posting
> job advertisements to this list (I thought there was something already,
> but can't find it), and recommend that all job advertisements have
> Reply-To: preset - I believe mailman will see that Reply-To is already
> set and not change it (do we need to double check this?).
>
> Having said that, this is one mistake I personally am not likely to make
> again in a hurry.
>
>
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> https://mail.python.org/mailman/listinfo/melbourne-pug
>


From miked at dewhirst.com.au  Tue May 26 05:06:05 2015
From: miked at dewhirst.com.au (Mike Dewhirst)
Date: Tue, 26 May 2015 13:06:05 +1000
Subject: [melbourne-pug] last post
In-Reply-To: <CAA0ZO6DONPQi+ykaJ7qGHBxYgy19Jh0kGuZsnTwYHzrDwQ72cA@mail.gmail.com>
References: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>
 <CADt_azZKuj8RcvRd=hP8rnB=fvGJw1hH=c3mo6WAD-T-gMoTcw@mail.gmail.com>
 <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
 <85vbfgwlrk.fsf@benfinney.id.au>
 <CALz4+LJXc=qC9Pk=yXR9eKDuzy4R0iEGzfc-jAik6N_kFJJFyw@mail.gmail.com>
 <CAA0ZO6DONPQi+ykaJ7qGHBxYgy19Jh0kGuZsnTwYHzrDwQ72cA@mail.gmail.com>
Message-ID: <5563E31D.1020908@dewhirst.com.au>

On 26/05/2015 10:07 AM, Brian May wrote:
> In another situation however if my management found out I was looking
> for more work that could place my current position in serious jeopardy.

Or more hopefully, prompt management to take a good hard look at 
themselves! And if they aren't that sort of management, that's probably 
why you would be looking elsewhere.

M

From anthony.briggs at gmail.com  Tue May 26 05:29:12 2015
From: anthony.briggs at gmail.com (Anthony Briggs)
Date: Tue, 26 May 2015 13:29:12 +1000
Subject: [melbourne-pug] last post
In-Reply-To: <5563D8A1.3030400@dewhirst.com.au>
References: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>
 <CADt_azZKuj8RcvRd=hP8rnB=fvGJw1hH=c3mo6WAD-T-gMoTcw@mail.gmail.com>
 <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
 <85vbfgwlrk.fsf@benfinney.id.au>
 <CALz4+LJXc=qC9Pk=yXR9eKDuzy4R0iEGzfc-jAik6N_kFJJFyw@mail.gmail.com>
 <CAA0ZO6DONPQi+ykaJ7qGHBxYgy19Jh0kGuZsnTwYHzrDwQ72cA@mail.gmail.com>
 <5563D8A1.3030400@dewhirst.com.au>
Message-ID: <CAO4-389Yteh5p25NqH+6f=0P-3bWwsEEACi9oBHfG6wA2PWPYA@mail.gmail.com>

My 2c: It's a mailing list; it's a public space.

In that context, public replies make perfect sense, and as the most common
(90+%?) case, should be the easiest option. Replying to someone privately
is more like pulling them aside at a party - it shouldn't be default.

(Having to do slightly more work to gossip about other people on the list
seems ok to me too...)

Anthony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150526/eaff690d/attachment.html>

From cjlmac at gmail.com  Tue May 26 06:56:52 2015
From: cjlmac at gmail.com (Chris Maclachlan)
Date: Tue, 26 May 2015 14:56:52 +1000
Subject: [melbourne-pug] last post
In-Reply-To: <CAO4-389Yteh5p25NqH+6f=0P-3bWwsEEACi9oBHfG6wA2PWPYA@mail.gmail.com>
References: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>
 <CADt_azZKuj8RcvRd=hP8rnB=fvGJw1hH=c3mo6WAD-T-gMoTcw@mail.gmail.com>
 <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
 <85vbfgwlrk.fsf@benfinney.id.au>
 <CALz4+LJXc=qC9Pk=yXR9eKDuzy4R0iEGzfc-jAik6N_kFJJFyw@mail.gmail.com>
 <CAA0ZO6DONPQi+ykaJ7qGHBxYgy19Jh0kGuZsnTwYHzrDwQ72cA@mail.gmail.com>
 <5563D8A1.3030400@dewhirst.com.au>
 <CAO4-389Yteh5p25NqH+6f=0P-3bWwsEEACi9oBHfG6wA2PWPYA@mail.gmail.com>
Message-ID: <CAD2FDiOeNBf5bpCiR8q76CVvapV_Bfp+c0g-wemdSR0yj=asZA@mail.gmail.com>

Hear, hear. A mailing list of IT professionals should be able to cope with
checking where their replies are going on a mailing list.

Yes, mistakes sometimes happen - but breaking the implicit default behavior
of facilitating collaboration for the sake of a couple of edge cases feels
a bit silly.

I would attach $0.02 if the bank still issued them.

Cheers

Chris
On 26 May 2015 1:34 pm, "Anthony Briggs" <anthony.briggs at gmail.com> wrote:

> My 2c: It's a mailing list; it's a public space.
>
> In that context, public replies make perfect sense, and as the most common
> (90+%?) case, should be the easiest option. Replying to someone privately
> is more like pulling them aside at a party - it shouldn't be default.
>
> (Having to do slightly more work to gossip about other people on the list
> seems ok to me too...)
>
> Anthony
>
>
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> https://mail.python.org/mailman/listinfo/melbourne-pug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150526/98a0316d/attachment.html>

From victa.ooi at gmail.com  Tue May 26 07:26:51 2015
From: victa.ooi at gmail.com (Victor Ooi)
Date: Tue, 26 May 2015 15:26:51 +1000
Subject: [melbourne-pug] last post
In-Reply-To: <CAD2FDiOeNBf5bpCiR8q76CVvapV_Bfp+c0g-wemdSR0yj=asZA@mail.gmail.com>
References: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>
 <CADt_azZKuj8RcvRd=hP8rnB=fvGJw1hH=c3mo6WAD-T-gMoTcw@mail.gmail.com>
 <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
 <85vbfgwlrk.fsf@benfinney.id.au>
 <CALz4+LJXc=qC9Pk=yXR9eKDuzy4R0iEGzfc-jAik6N_kFJJFyw@mail.gmail.com>
 <CAA0ZO6DONPQi+ykaJ7qGHBxYgy19Jh0kGuZsnTwYHzrDwQ72cA@mail.gmail.com>
 <5563D8A1.3030400@dewhirst.com.au>
 <CAO4-389Yteh5p25NqH+6f=0P-3bWwsEEACi9oBHfG6wA2PWPYA@mail.gmail.com>
 <CAD2FDiOeNBf5bpCiR8q76CVvapV_Bfp+c0g-wemdSR0yj=asZA@mail.gmail.com>
Message-ID: <C2F9A6DE-26FC-447A-81B1-B245512B92AD@gmail.com>

I have to agree. There's always going to be mistakes made. 

If the intention is to send a private reply it is the responsibility of the individual to check correct addressing. 




> On 26 May 2015, at 2:56 pm, Chris Maclachlan <cjlmac at gmail.com> wrote:
> 
> Hear, hear. A mailing list of IT professionals should be able to cope with checking where their replies are going on a mailing list.
> 
> Yes, mistakes sometimes happen - but breaking the implicit default behavior of facilitating collaboration for the sake of a couple of edge cases feels a bit silly.
> 
> I would attach $0.02 if the bank still issued them.
> 
> Cheers
> 
> Chris
> 
>> On 26 May 2015 1:34 pm, "Anthony Briggs" <anthony.briggs at gmail.com> wrote:
>> My 2c: It's a mailing list; it's a public space.
>> 
>> In that context, public replies make perfect sense, and as the most common (90+%?) case, should be the easiest option. Replying to someone privately is more like pulling them aside at a party - it shouldn't be default.
>> 
>> (Having to do slightly more work to gossip about other people on the list seems ok to me too...)
>> 
>> Anthony
>> 
>> 
>> _______________________________________________
>> melbourne-pug mailing list
>> melbourne-pug at python.org
>> https://mail.python.org/mailman/listinfo/melbourne-pug
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> https://mail.python.org/mailman/listinfo/melbourne-pug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20150526/634e9245/attachment-0001.html>

From deeprave at gmail.com  Tue May 26 14:20:02 2015
From: deeprave at gmail.com (David Nugent)
Date: Tue, 26 May 2015 22:20:02 +1000
Subject: [melbourne-pug] last post
In-Reply-To: <85vbfgwlrk.fsf@benfinney.id.au>
References: <CAA0ZO6BiY3wPkHe2ueO33JgC9J-CzER3PbbBCZ6b_kS-SQToBw@mail.gmail.com>
 <CADt_azZKuj8RcvRd=hP8rnB=fvGJw1hH=c3mo6WAD-T-gMoTcw@mail.gmail.com>
 <CADhgxgdbVVu7NMEB+hyaL4zW3Kbwoz7YHroYFogRtTdG=3APxA@mail.gmail.com>
 <85vbfgwlrk.fsf@benfinney.id.au>
Message-ID: <03E8F28E-3A57-4511-BF40-3BECB80851C7@gmail.com>

> On 26 May 2015, at 4:32 am, Ben Finney <ben+python at benfinney.id.au> wrote:
> 
> Tennessee Leeuwenburg <tleeuwenburg at gmail.com> writes:
> 
>> Six of one, half a dozen of the other.
> 
> It really isn't, though. Setting ?Reply-To? to the mailing list is
> significantly more harmful than leaving that field alone.


^^ This.


> * The failure mode of ?don't do anything with Reply-To? is that
>  sometimes people send a message to an individual, that they *intended*
>  to go more public.
> 
> * The failure mode of ?set Reply-To to the mailing list? is that
>  sometimes people send a message publicly, that they *intended* to be
>  private to an individual.

Adding:

* Changing a Reply-To also overwrites the original author?s Reply-To, which may be contrary to the purpose of setting it (admittedly doing so in a ?public? mailing list is kinda silly and you?d expect it would not work as it should). Still, i?m old school enough to maintain the view that when it comes to email headers, correctness is important - anything else quickly leads to non-standard behaviour. Kinda like complaining after the horse has bolted (20+ years on! :-)). Old, old argument in any case, and status quo is probably a good idea.

Good luck Brian, btw. Might be in the same position myself soon...

Cheers,
/d