<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><br></div><div>Am 22.01.2016 um 01:16 schrieb Jordan Rose <<a href="mailto:jordan_rose@apple.com">jordan_rose@apple.com</a>>:<br><br></div><blockquote type="cite"><div><span>My reaction was mostly "eh" because many mail clients thread responses, making it not too hard to jump back to the first message in a thread. That's not always where a proposal link lives, but usually it is.</span></div></blockquote><div><br></div><div><br></div><blockquote type="cite"><div><span>I don't usually look through a response message to find a proposal link in the first place.</span><br><span></span><br></div></blockquote><div><br></div><div>That's true therefore it should be a separated section at the top.</div><br><blockquote type="cite"><div><span>I don't have objections to this. I know I'll forget to do it, but that's true of any new practice, so I can learn.</span><br><span></span><br></div></blockquote><div><br></div><div>That's also true. So maybe <b><u>only the proposer</u></b> should do that in order to keep the responses relatively clean.</div><div><br></div><div>- Maximilian</div><div><br></div><div>PS:</div><div>Was this the right way/place to make such a proposal?</div><div>I also want to propose better organized mailing list archives in order to make proposals (better) searchable and avoid too many duplicate suggestions. Should I do it on this mailing list?</div><br><blockquote type="cite"><div><span>Jordan</span><br><span></span><br><blockquote type="cite"><span>On Jan 21, 2016, at 11:21, Maximilian Hünenberger via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Any opinions?</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>Am 19.01.2016 um 22:48 schrieb Maximilian Hünenberger via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>>:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I'm sorry if this is not the proper way to propose a convention for the actual mailing list.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Having a very long Email thread links to proposals are almost always at the bottom of the mail or in a different one.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>So I propose a convention to leave the link to the main proposal (if there is one; if not use "_") always on top for quick access.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Design:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> Proposal link:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> <a href="http://linktoproposal">http://linkToProposal</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span> Reply text</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span> Other replies</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>It adds some work to making a reply but I think it pays off.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Best regards</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>- Maximilian</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>_______________________________________________</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>swift-evolution mailing list</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></blockquote></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>swift-evolution mailing list</span><br></blockquote><blockquote type="cite"><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br></blockquote><blockquote type="cite"><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></blockquote><span></span><br></div></blockquote></body></html>