erlend_sh | 2016-08-05 14:46:27 UTC | #1 ### Problem statement Some web-users strongly prefer communicating via e-mail, others have no other medium at their disposal due to lack of up-to-date technology or a fast enough internet connection. [With this MOSS grant](http://blog.discourse.org/2015/12/discourse-selected-for-mozilla-open-source-support-program/) we aim to enhance Discourse with several individual-but-related features that will make the software easier to use via e-mail, effectively enhancing accessibility and engagement for the segment of users to whom the web-based (JavaScript) interface is not an ideal option. The Discourse company will hire one or more developers on behalf of the MOSS grant to work on these enhancements in conjunction with the core team. We expect all critical tasks on our roadmap to be completed by July 2016, coinciding with the release of Discourse v1.6. With all assignments successfully completed, Discourse will be on-par-with or surpass the feature set of mailing list programs such as GNU Mailman or PHPlist. A user should be able to join, participate and leave group discussions run through Discourse without ever having to log in to the Discourse web interface. ### How is solving this problem going to help Discourse? Improving online discussions is our bread and butter. See: http://blog.codinghorror.com/civilized-discourse-construction-kit/ Mailing lists in particular is a form of communication that we consider outdated. Not much more can be said about mailing lists that hasn’t already been said. In short, they don’t scale well with growing communities, and as a result they can significantly hamper the adoption of new technologies that ought to have touched thousands or even millions of people instead of just a few hundred. Also, they’re generally not very export-friendly, which is not good practice for the modern, open web. We acknowledge the fact that for some people e-mail is still their most effective workflow, but instead of limiting our communications platform to e-mail we want e-mail to be one among several equally valid workflows (e-mail, browser, and - should someone ever choose to make them - native apps). ### TODOs (Do note that not that some features listed below would become stretch goals rather than hard targets) :white_check_mark: = Done :hammer: = WIP :thought_balloon: = Tentative :no_entry_sign: = Discarded (for the time being) **Mailing list feature parity:** - :white_check_mark: Easier unsubscribe options https://meta.discourse.org/t/improved-unsubscribe-workflow/45931?u=erlend_sh - :white_check_mark: Email styling (finished just prior to MOSS) https://meta.discourse.org/t/customizable-email-templates/35818 - :white_check_mark: Better email context https://meta.discourse.org/t/forcing-email-context-input-requested/25577/67 - :white_check_mark: Use display name for email https://meta.discourse.org/t/use-display-name-for-email-if-possible/34474 - :white_check_mark: Get notified by new topics only https://meta.discourse.org/t/get-notified-of-new-topics-but-not-posts/12809/60 - :white_check_mark: Improved inbound parsing - :white_check_mark: Attachments support - :white_check_mark: Threaded replies by e-mail https://discourse.chef.io/t/thread-detection-when-responding-via-email/7329 - :hammer: Read-only web archive of active mailing list. https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/9 - :thought_balloon: Subscribe to topics/categories by e-mail without signing in Just like “Email updates to me” in Google Groups. - :thought_balloon: More context in e-mail message body: “You received this message because…” https://meta.discourse.org/t/subscription-emails-should-carry-more-context-in-message-body/21820/2 - :thought_balloon: Queue up bounced e-mails instead of dismissing them https://meta.discourse.org/t/moderate-emails-which-would-normally-bounce/30331 - :thought_balloon: Option for plain text e-mail **Increased engagement:** - :white_check_mark: Support abridged e-mails https://meta.discourse.org/t/more-granular-mailing-list-mode/38107 https://meta.discourse.org/t/looking-for-an-abridged-email-to-recap-all-activity-since-the-last-email/33239 - :white_check_mark: Send email notifications in user's preferred language https://meta.discourse.org/t/variable-default-interface-language-for-new-users/33741 - :white_check_mark: Interactive e-mails: Let users Like content via their mail (see WooThemes example) https://meta.discourse.org/t/ability-to-like-1-a-post-via-email-reply/24135 - :hammer: Improved “Weekly Summaries” (maybe including significant badges etc.) https://meta.discourse.org/t/what-are-some-simple-ways-to-improve-digest-emails/33224 https://meta.discourse.org/t/newsletter-per-individual-tripadvisor-style/27713 - :thought_balloon: Custom e-mail footers https://meta.discourse.org/t/customize-email-notification-header-and-footer/27927 https://meta.discourse.org/t/per-category-email-footers/33886 https://meta.discourse.org/t/email-footer-support/27381 General bug fixing - :white_check_mark: E-mail signature not being stripped out properly (finished just prior to MOSS) https://meta.discourse.org/t/html-email-signature-not-being-stripped-out-of-notification-reply/21351 Further reading: - https://meta.discourse.org/t/convince-me-to-transition-over-from-google-groups/31221 - https://meta.discourse.org/t/feedback-from-a-community-about-mailing-list-feature/27695 - https://coderanger.net/chef-mailing-list/ ------------------------- codinghorror | 2015-12-11 01:34:34 UTC | #3 I think @zogstrip is getting to some of these as part of the current work around email support portal. Can you cross off any items that you complete here Régis? ------------------------- modius | 2015-12-11 02:52:32 UTC | #4 [quote="erlend_sh, post:1, topic:36432"] With this MOSS grant we aim to enhance Discourse with several individual-but-related features that will make the software easier to use via e-mail, effectively enhancing accessibility and engagement for the segment of users to whom the web-based (JavaScript) interface is not an ideal option. [/quote] What is a MOSS grant? ------------------------- codinghorror | 2015-12-11 02:56:36 UTC | #5 I will add a link back to the blog entry there. ------------------------- erlend_sh | 2016-04-22 10:55:32 UTC | #6 ### Want to work on some of these features? @plugin_authors & contributors, if you feel comfortable with one or more of the tasks listed above, send a message to @erlend_sh to let us know you're interested and we can sort out the details from there. We're only taking on 1 or 2 part time developers for this, but just knowing you're looking for the occasional freelance work means we'll keep you on our radar for future gigs ;) ------------------------- techAPJ | 2015-12-11 14:43:48 UTC | #7 I just crossed off one bug that was fixed by my [recent change](https://meta.discourse.org/t/better-email-reply-parsing-email/36495?u=techapj). :blush: ------------------------- wesochuck | 2015-12-15 14:49:58 UTC | #8 - Are there still issues with inline replies that need worked out? - https://meta.discourse.org/t/reply-by-email-requires-reply-at-top/16983/27 - or https://meta.discourse.org/t/text-of-forwarded-emails-dont-show-up-in-posts/23155/14 - [Cross posting to multiple "lists"](https://meta.discourse.org/t/why-cant-a-topic-be-placed-into-multiple-categories/1883) on the same "instance" is also something I've seen many mail communities do. So you may want to consider if that should be on the MOSS feature list. - When using category mailing list, provide an option to [notify the sender when their message is posted](https://meta.discourse.org/t/send-me-an-email-for-every-new-post-also-notifies-for-self-posts/27209). - I think this is really important for folks that are used to old school style mailing lists. If they don't see an email for the message they sent to the list, then they assume that it never got posted. - Not totally on topic, but I think some option to [email notify on new topics those who are tracking categories](https://meta.discourse.org/t/watching-for-first-messages-only/35143/10?u=wesochuck) should also be considered. ------------------------- sam | 2015-12-16 09:27:34 UTC | #9 One feature I would like us to work on is having Discourse act as a "web archive" for an active mailing list. This simplifies migration off mailing lists and allows us to live side by side with existing software and help many open source projects out there. For example: Say we could simply run a simple script to download all the mbox files here: http://www.postgresql.org/list/pgsql-general/ and then import into a Discourse instance. http://www.postgresql.org/list/pgsql-general/ could simply become a readonly Discourse forum. Then all we would need to do is add a mode where every post to the mailing list is also added to Discourse. Even though a lot of the lego is in place to achieve this, it lacks a lot of polish. It would be super awesome for this kind of task to be both well documented and simple to enable. Imagine if you could just enter a single web address into your Discourse instance (pointing at mailman archives) and it took care of all of the magic for you. ------------------------- carlokok | 2015-12-16 09:44:07 UTC | #10 Isn't that more of a feature that could better fit in a plugin than core discourse? ------------------------- sam | 2015-12-16 09:48:43 UTC | #11 Importers are all core, see https://github.com/discourse/discourse/tree/master/script/import_scripts similarly a bridge or bridging scripts can live in core. Entering a URL to magically make everything work may not be core, I am not sure, but most of the code in my above "imagineering" session would live in core. ------------------------- codinghorror | 2015-12-16 11:32:41 UTC | #12 Even as a partial import this is hugely important and helpful in seeding a new Discourse with users and content.. just forward a few giant email threads in and bam: - you have a bunch of staged users ready for people to join and take ownership of their accounts (via email address) - you have a bunch of useful, real, content on the site ------------------------- carlokok | 2015-12-16 12:21:21 UTC | #13 ah. That makes sense now. ------------------------- almereyda | 2015-12-23 20:05:53 UTC | #14 @thoka Should we document the current adaptation to any of these currently missing features by linking dummy/robot discourse users to mailing lists, thus enabling targeted notifications? @all Does this also involve diff messages of edited postings as HackPad sends them? ------------------------- tobiaseigen | 2015-12-23 20:25:02 UTC | #15 I had a recipe back in the day for doing this by importing mailman-generated mbox archives into fudforum. It worked incredibly well, just as you describe. A quick google search turmed up an oldish stackoverflow topic about it that explains it reasonably well. https://stackoverflow.com/questions/616772/is-there-a-good-way-to-migrate-from-a-mailman-list-to-an-web-forum I also am very interested in the staged users concept - is this discussed anywhere in any detail already on meta? Saw a mention of it in the below topic but when I tested it a few weeks back I saw no sign of staged users or an explanation of how it would work. https://meta.discourse.org/t/discourse-as-a-private-email-support-portal/34444?u=tobiaseigen Seems to me that, if staged accounts were to work, then we're not far away from making this happen. w00t! ------------------------- modius | 2016-01-02 20:25:42 UTC | #16 [quote="sam, post:11, topic:36432"] Importers are all core, see https://github.com/discourse/discourse/tree/master/script/import_scripts similarly a bridge or bridging scripts can live in core. [/quote] Would love to see an importer for Google Groups mailing lists too, but scraping out Groups content looks to be a bit messy. There is [a bash script for generating an mbox from a Google Group](https://github.com/icy/google-group-crawler) which works with a bit of fiddling (need a cookie file to get emails). It also has options for picking up new posts which helps in mirroring, though i haven't tried it. Perhaps that would be an approach if mbox imports were rock solid and repeatable. Also, would the mbox approach allow for importing into an existing forum? Something that might be of interest to our community is merging our existing Discourse forum, with an existing Google Group. ------------------------- amirmc | 2016-01-03 21:17:42 UTC | #17 Being able to merge multiple mailing lists into one Discourse forum would be interesting too. For example, importing (or even mirroring?) them as different categories. ------------------------- tobiaseigen | 2016-02-12 19:16:37 UTC | #19 I got this feedback from a member today relating to discourse and attachments: > Tobias, is there a different way to attach docs on discourse? this function only allows me to save the document, not open it....For a couple of Vivek's e-mails, I've saved the document, and then gotten pulled away, ans then never opened it... can there be an "open in another tab" option? Or even a kind of attachment like in google, where the pop up box would have an "open" option? We use gmail, and I am assuming she's hoping for something more gmail-like. The first request here I think is for "mailing list mode" to actually attach the file to the message. I hope this can be added to the roadmap, at least as an admin setting. The second is more of a "wondering". Is there not a way to indicate in the mailing that a link is to an attachment, which email clients can then use to offer different ways to access said attachment? https://20somethingkidsand1kookyteacher.files.wordpress.com/2012/09/img330.jpg ------------------------- codinghorror | 2016-02-12 21:04:27 UTC | #20 I am not clear what you're talking about here. Can you be more specific? What's being attached? Images? ------------------------- tobiaseigen | 2016-02-12 21:13:39 UTC | #21 usually it's .doc files and other work-related documents. sorry, i just included the picture for fun. :blush: ------------------------- codinghorror | 2016-02-12 21:17:21 UTC | #22 I don't really see a practical use for the request -- if the user can't figure out how to open a downloaded file, they are going to be in a world of hurt sooner or later.. they need to learn how to do that. ------------------------- tobiaseigen | 2016-02-12 21:23:32 UTC | #23 I think she's just hoping the functionality can be made more equivalent to what she's used to. That would happen if the file were actually attached to the message and not provided as a link. She really is a candidate for mailing list mode in a big way - she does not log into our discourse at all and, even now after a year, misses the google groups we replaced. ------------------------- erlend_sh | 2016-04-06 18:40:22 UTC | #24 ### Update - 6. April, 2016 - Major enhancement of [incoming emails](https://meta.discourse.org/t/setup-incoming-emails-e-mail/42026). This work effected a whole *bunch* of email improvements, the vast majority of which you can find listed in our [v1.5 changelog](https://meta.discourse.org/t/discourse-version-1-5/30609/3?u=erlend_sh). - Attachments support - Email notifications in user's language. [gh#4004](https://github.com/discourse/discourse/pull/4004) - Layout improvements [gh#3969](https://github.com/discourse/discourse/pull/3969), [gh#4008](https://github.com/discourse/discourse/pull/4008) - Unsubscribe by email [gh#3952](https://github.com/discourse/discourse/pull/3952) - [Better email context](https://meta.discourse.org/t/forcing-email-context-input-requested/25577/67?u=erlend_sh). Major shoutout to @simon, @gdpelican and @joebuhlig for stepping up to the email plate and taking on a portion. @zogstrip please let me know if I missed anything major. Will post another update in a couple of months! ------------------------- tobiaseigen | 2016-04-06 13:55:59 UTC | #25 amazing. congrats :tada: and many thanks! :heart_eyes_cat: ------------------------- zogstrip | 2016-04-06 15:21:45 UTC | #26 [quote="erlend_sh, post:1, topic:36432"] :thought_balloon: Threaded replies by e-mailhttps://discourse.chef.io/t/thread-detection-when-responding-via-email/7329 [/quote] I _think_ I fixed that one. Not sure though, will have to confirm this. ------------------------- tarek | 2016-05-31 11:06:54 UTC | #27 Hello @erlend_sh. I wonder if you would consider adding the feature to allow replying only to sender to within this work? Before I found this thread, I described the problem [in another topic](https://meta.discourse.org/t/allow-reply-to-individual-instead-of-topic-forum-mailing-list-feature/44905) that you commented in. Thank you! ------------------------- erlend_sh | 2016-05-31 11:14:26 UTC | #28 If that topic culminates in (1) a clear specification that (2) multiple users clearly want, then it's a great candidate for MOSS work, yes. ------------------------- tarek | 2016-05-31 11:15:52 UTC | #29 Could you point to an example of a clear specification so that I could generate one? ------------------------- erlend_sh | 2016-05-31 11:23:48 UTC | #30 Sure, you can peruse our many #feature:spec topics to get an idea of what we're looking for in a spec. But there's no point spending too much time putting together a spec until you've reached a semblance of a consensus in the topic where this feature request is currently being discussed. ------------------------- tarek | 2016-05-31 11:39:27 UTC | #31 Understood. Because of the utility of the feature for me (essentially, it's a must-have for our group), it seems prudent to develop a spec for me to work from, no? That way, people with strong programming skills / experience might be able to comment / stop me from making errors before I make them / contribute code? ------------------------- scombs | 2016-05-31 17:24:52 UTC | #32 I agree let's get [quote="erlend_sh, post:30, topic:36432"] semblance of a consensus in the topic where this feature request is currently being discussed. [/quote] I have some input on the reply-to-sender feature and a request from my customer. I will post back on the [other topic](https://meta.discourse.org/t/allow-reply-to-individual-instead-of-topic-forum-mailing-list-feature/44905) shortly. ------------------------- peircej | 2016-07-31 14:17:58 UTC | #33 As well as migrating existing posts I'm keen to forward posts (for a period) that will continue to arrive at our old mailing list (a googlegroup). @erlend_sh suggested [back in 2013](https://meta.discourse.org/t/import-from-google-groups-to-discourse/7307/4) that this could be achieved by simply subscribing a Discourse email recipient to the mailing list. The problem is that the mail gets rejected by discourse on the basis that it's from a list :-/ Is there a way to whitelist particular mailing lists so we can make this work? ------------------------- modius | 2016-09-22 07:46:11 UTC | #34 [quote="erlend_sh, post:1, topic:36432"] :hammer: Read-only web archive of active mailing list. https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/9 [/quote] Been holding out for Web Archive for a long time ;) Is there any update? Has the MOSS budget run out? ------------------------- gerhard | 2016-09-22 08:35:51 UTC | #35 I'm working on a proof of concept for this... might take some time though... ------------------------- erlend_sh | 2016-09-22 09:40:30 UTC | #36 [quote="modius, post:34, topic:36432"] Has the MOSS budget run out? [/quote] It has, but of course we still care about email :grin: Post-MOSS we've continued to approach developers from our community with bite-sized paid projects. The web archive is one such project, which we've enlisted @gerhard to work on. But like he said, it'll certainly take some time as we've definitely pushed the limits of our usual "bite-sized" requirement here. ------------------------- pfaffman | 2016-09-22 14:51:24 UTC | #37 I've made some improvements to the mbox importer. I could imagine some cron job solution that used that importer as a stop gap. ------------------------- hellekin | 2016-09-30 09:24:31 UTC | #38 [quote="erlend_sh, post:36, topic:36432"] Post-MOSS [/quote] Is there some kind of development report? I remember reading a plan when it was announced. Any debrief? Added: [quote="erlend_sh, post:1, topic:36432"] A user should be able to join, participate and leave group discussions run through Discourse without ever having to log in to the Discourse web interface. [/quote] How far are you from this? I have Web-angry users that complain the mailing-list mode sends HTML email (and I didn't try subscription by email). That suggests me we're not there yet, but I'd be very happy if we were. ------------------------- codinghorror | 2016-09-30 10:40:41 UTC | #39 Not true; it is always multi part email where the text part is raw Markdown. If you don't want the HTML bit then don't use that and look at the plain text payload. ------------------------- hellekin | 2016-09-30 11:07:12 UTC | #40 Maybe that's an issue with their MUA. I don't have this problem. I will ask for more precision. ------------------------- coderanger | 2016-09-30 11:25:03 UTC | #41 Most mail clients will default to showing HTML content if present. I'm not sure Mail.app actually has a way to force it to show the text content by default. That said most of those clients also stopped loading remote content by default and it would be hard to imagine a case where a security issue would be a real concern. But as Discourse rolls into more "traditional" (read: with expectations of traditional mailing list features) environments, you're going to get more and more pushback on not having this as a user preference. I've certainly had a fair bit of flak from Chef folks about it. ------------------------- hellekin | 2016-09-30 11:43:58 UTC | #42 Here's what [RFC 2046](https://tools.ietf.org/html/rfc2046#section-5.1.4) has to say (emphasis mine): > Systems should recognize that the content of the various parts are interchangeable. **Systems should choose the "best" type based on the local environment and references**, in some cases even through user interaction. As with "multipart/mixed", the order of body parts is significant. In this case, **the alternatives appear in an order of increasing faithfulness to the original content**. In general, **the best choice is the LAST part** of a type supported by the recipient system's local environment. From that reading, the Discourse emails are properly formatted, and the problem comes with mis-configuration on the user's side. **BUT** according to mailing list _tradition_, HTML and email do not mix well, and **plain text is always preferred**. Maybe there could be a switch in the admin section for the order of parts? ------------------------- coderanger | 2016-09-30 11:46:45 UTC | #43 I don't think there is a technical reason to change things, it's a question of user expectations. Adding a user preference to disable the HTML part seems doable if somewhat annoying given how many bits of code it would touch (as with all new user prefs), but I'm not lining up to contribute it so it's not the hill I'll pick to die on :) ------------------------- pfaffman | 2016-09-30 16:18:32 UTC | #44 [quote="hellekin, post:42, topic:36432"] BUT according to mailing list tradition, HTML and email do not mix well, and plain text is always preferred. [/quote] Yeah. If only. I am pretty curmudgeonly on such issues, and I gave up on receiving plain text email at least a decade ago. And RFC 2046? I'm an RFC 822 guy myself. :smiling_imp: If you're going to go citing chapter and verse you should probably check out [RFC4288](https://tools.ietf.org/html/rfc4288) which is only a decade old instead of three decades old. All that to say that there's probably no good solution, and people who expect text-only email live in a world of hurt. ------------------------- mpalmer | 2016-09-30 16:27:32 UTC | #45 I'm Maximum Curmudgeon (and I normally use mutt as my mail client), and as long as there's a `text/plain` variant available, I care not what else is floating around in the pot of crud that is a modern e-mail. I've got to agree that if we're sending a `text/plain` variant and your MUA isn't showing it, that's something for you to discuss with your MUA of choice. Even I'm willing to concede that HTML would be the, in general, "preferred" format, so if you want plain text, talk to your MUA. I wouldn't even recommend a user pref to say "send plain-text e-mail by default", and my beard is as grey as they come. ------------------------- elijah | 2016-09-30 21:01:41 UTC | #46 [quote="mpalmer, post:45, topic:36432"] I wouldn't even recommend a user pref to say "send plain-text e-mail by default", and my beard is as grey as they come. [/quote] My beard, in real life, is not grey. That said.... My email tool chain involves a personally modified `mailx`, though, and HTML is viewed in source form until hand-modified. But sending `text/markdown` with headers declaring it as `text/plain` could be annoying to someone who is particularly pedantic. (I am not very concerned myself.) And I can confirm Discourse does do that. ------------------------- hellekin | 2016-09-30 21:00:25 UTC | #47 Dear @pfaffman, RFC 4288 says: > All subtypes of multipart and message MUST conform to the syntax rules and other requirements specified in [RFC2046]. ------------------------- pfaffman | 2016-09-30 21:06:35 UTC | #48 Sorry. I was mostly being silly. My point was that in my view including anything other than 7-bit ASCII in email is an abomination and should be ignored. But, really, you should mostly ignore me. :slight_smile: ------------------------- elijah | 2016-09-30 21:12:11 UTC | #49 ```text ----==_mimepart_57eec1754fb1b_613fb08d373ca061471a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ``` Actual headers for the text part of a multipart/alternative message. I've not seen (closely looked at) enough of Discourse's email to know how it deals with non-ASCII in messages or SMTP line length considerations. ------------------------- hellekin | 2016-09-30 21:20:11 UTC | #50 [quote="elijah, post:46, topic:36432"] But sending text/markdown with headers declaring it as text/plain could be annoying to someone who is particularly pedantic. (I am not very concerned myself.) And I can confirm Discourse does do that. [/quote] That's an interesting thought to have Markdown supported in email. I tried Markdown-here addon for Thunderbird, but it requires "a rich text editor" (AKA HTML email, which is yuck.) Then I found these [thoughts on writing emails using Markdown](https://blog.freron.com/2011/thoughts-on-writing-emails-using-markdown/) that proposes to add a markup option to the Content-Type: `Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown` It sounds better, as the MUA can then format the markdown properly (although not many MUAs support Markdown at all, and other inconvenients mentioned in the article.) Best of both worlds would be to keep using text/plain, and automatically convert Markdown when **reading**, and not convert to text/html when **sending** as Markdown-here seems to be doing. ------------------------- hellekin | 2016-09-30 21:47:59 UTC | #51 ## Issues with email-in (Feel free to split topic or move where appropriate) I've been trying to reply by email whenever possible. Here's an example of what I sent, and what the final HTML post looks like. I guess there's room for improvement. First point would be to automatically remove the email signature (using `.gsub('/^--\n(.*)\A/m', '')`?) (also note that GPG-signatures seem to stick around) and fixing the line-breaks. I remember that Mutt has a very nice TOFU plugin to take care of cruft pretty effectively. Another issue is that normally, with email you always quote a bit of the message (when you're well-behaved) which works like quoting here. But more often than not people are not well-behaved with email and end up quoting the whole thing. I guess top-posting is handled nicely, but I didn't check. Original: [details=click to view markdown source of the resulting HTML shown in screenshot below] ``` We don't have a clear process yet. But it would go something along these lines: 1. You upload your package to your personal account on [git.do](https://git.devuan.org/) 2. You contact the [devuan-for-review group](https://git.devuan.org/groups/devuan-for-review) so that they fork it into the group for review and testing. You can contact them using the #devuan-dev channel on Freenode IRC, or the DNG mailing list, or by opening an issue in your package's page mentioning `@devuan-for-review` (I guess this would work) 3. Once your package has been reviewed, corrected, etc., it will enter the [devuan-packages group](https://git.devuan.org/groups/devuan-packages) and `experimental`. From there, if nothing special happens it should be entering `unstable` after a couple of weeks, like Debian does. Usually you would then become the maintainer. Does that make sense? I guess we should submit a proposal for this process, refine it, etc. I know @Centurion_dan was perplex about using the `devuan-for-review` group, but I think it's worth a try. -- _ _ We are free to share code and we code to share freedom (_X_)yne Foundation, Free Culture Foundry * https://www.dyne.org/donate/ ``` [/details] Result: ------------------------- pfaffman | 2016-09-30 21:43:16 UTC | #52 [quote="hellekin, post:51, topic:36432"] Original: (how can I limit the number of lines to say, 5, to be expanded on click?) [/quote] Is this what you mean? [details=click here to expand]lkj sdlkj sdlkfj sdlkf jsdlkf sdlkf [/details] [details=click here to expand]lkj sdlkj sdlkfj sdlkf jsdlkf sdlkf [/details] [quote="hellekin, post:51, topic:36432"] First point would be to automatically remove the email signature (using .gsub('/^--\n(.*)\A/m', '')?) [/quote] https://meta.discourse.org/t/email-reply-parsing/41597/8 ------------------------- hellekin | 2016-09-30 21:52:16 UTC | #53 Right, thank you @pfaffman. Well I get the "we do not remove signatures", but that means informing the users they need to skip their signature for replying by email unless you want to end up with ugly signatures across the board. :grimacing: ------------------------- pfaffman | 2016-09-30 22:05:39 UTC | #54 [quote="hellekin, post:53, topic:36432"] that means informing the users they need to skip their signature for replying by email unless you want to end up with ugly signatures across the board. :grimacing: [/quote] It's horrible. And the last place I worked required people to include postal address, fax address, office number, official title (or several), university icon, and I don't know what all. A client who just switched to Discourse from a mailing list is already talking about disabling incoming email. His other solution is to hire people where labor is cheap to fix the stuff by hand. ------------------------- sam | 2017-12-28 01:21:25 UTC | #55 Closing this as it is mostly implemented, no need to carry it open forever. ------------------------- sam | 2017-12-28 01:21:27 UTC | #56 -------------------------