[Owncloud] default reply to owncloud at kde.org header

[Jan-Christoph Borchardt]

What are we discussing here?

It’s honestly ridiculous to have such a big discussion about petty things
like a default reply-to header, on the list of a project which is concerned
with solving actual problems, for many people. If you have time to kill,
please look at ownCloud’s current issues and help us fix them:
https://github.com/owncloud/core/issues?state=open – thank you!

Regarding the original discussion – if it should be changed, please just
contact the mailing list manager and they will decide if it makes sense, no
need for bikeshedding on here. Then again, I think the mailing list manager
is Frank, and he’s swamped doing actual work on the release, so please
don’t bother now.

Sorry for the harsh tone, but we’re close to releasing ownCloud 5 and all
of you people’s time is better spent testing and fixing it rather than in
this thread. If you want to be awesome, help out!




On Mon, Feb 18, 2013 at 4:51 PM, MJ Ray <mjr at phonecoop.coop> wrote:

> Diederik de Haas <didi.debian at cknow.org>
> > Even though my mail client supports reply-to-list perfectly, I (too)
> think it's
> > a good suggestion.
> > What is the downside of setting this header?
>
> It punishes people who have fully-working email software.  Consider
> the potential damage in the intended use cases:
>
> With Reply-To overwritten:
>
> A1. if Reply-To set and the mail client supports List-Post =>
> list-reply command works but the direct-reply command is broken and
> does the same as list-reply, no way to recover an off-list reply
> command except manual editing, so some private messages will become
> public.
>
> A2. if Reply-To set and the mail client ignores List-Post => reply
> goes to list, no way to recover off-list reply command except manual
> editing, so some private messages will become public.
>
> Leaving Reply-To alone:
>
> B1. if the mail client supports List-Post => list-reply command
> works, reply command works fully.  No problems.
>
> B2. if the mail client ignores List-Post => reply goes direct, user of
> incomplete client has to use Reply-All or edit the recipients, but
> some list messages will go privately.
>
> What's the bigger danger? Private messages being published (maybe
> embarrasing or worse), or people who use buggy mail clients having to
> resend a few accidentally-unpublished messages?
>
> And why should users of list-RFC-supporting clients be punished by their
> private messages going public if they overlook the overwriting, just
> so users of worse clients don't risk public messages going private?
> Shouldn't we reward people who use standards-supporting software?
>
> If a mail client doesn't support List-Post properly, report the bug -
> and fix it if you can (it's free and open source software, right?)
>
> Hope that informs,
>
> --
> MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op.
> http://koha-community.org supporter, web and library systems developer.
> In My Opinion Only: see http://mjr.towers.org.uk/email.html
> Available for hire (including development) at http://www.software.coop/
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/owncloud/attachments/20130218/04a02e48/attachment.html>