Re: [fossil-users] What should email notifications look like?
On 2018-06-22 20:40, Joerg Sonnenberger wrote: [---] > BTW, the main mercurial list uses the following mail format for "batch" > changes: > > https://www.mercurial-scm.org/pipermail/mercurial-devel/2018-June/117551.html This is highly machine parse-friendly. I like it a lot. -- Kind Regards, Jan ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] What should email notifications look like?
Attached a zip file containing a number of mails as generated and send
by `fx` (https://core.tcl.tk/akupries/fx/index) to the tcl-bugs mailing
list. Soory, it was easiest to pull existing mails.
The footer ("See Tcl/Tk ...") is configurable.
The general structure is currently fixed in fx code.
--
See you,
Andreas Kupries
Re: [fossil-users] What should email notifications look like?
On Fri, Jun 22, 2018 at 02:18:35PM -0400, Richard Hipp wrote: > Shown below is what I have at the moment. It is more succinct than > other examples I've seen, but you can easily follow the link for > details. BTW, the main mercurial list uses the following mail format for "batch" changes: https://www.mercurial-scm.org/pipermail/mercurial-devel/2018-June/117551.html Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] What should email notifications look like?
On Jun 22, 2018, at 12:18 PM, Richard Hipp wrote: > > == 2018-06-22 01:28:10 Check-In == > Fix harmless compiler warnings. (user: drh tags: email-alerts) > https://fossil-scm.org/fossil/info/5fde17bbbc2cba69d3f8 Some systems I’ve used in the past have an option to include a diff on checkins. This avoids the need to go back to the web site — Fossil UI in this case — in most cases. Coupled with this option is usually a max diff size limit, so that a massive checkin doesn’t create huge email notifications. That in turn encourages sensibly-sized checkins, which is a good thing. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] What should email notifications look like?
On 22 June 2018 at 11:18, Richard Hipp wrote: > Shown below is what I have at the moment. It is more succinct than > other examples I've seen, but you can easily follow the link for > details. Very nice! I think you're on the right track! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] What should email notifications look like?
Shown below is what I have at the moment. It is more succinct than other examples I've seen, but you can easily follow the link for details. The example below has more check-ins that one would normally find in a single alert (unless you sign up for the "daily digest") because my local repo is not actually sending emails and thus is not purging its "pending alert" queue. --- BEGIN --- This is an automated email reporting changes on Fossil repository [fossil-src] (https://fossil-scm.org/fossil/timeline) == 2018-06-22 01:18:59 Check-In == Rename the email_pending table to pending_alert. Add triggers to fill in the pending_alert table each time a row is added to the event table. (user: drh tags: email-alerts) https://fossil-scm.org/fossil/info/8c4b92ad3e27bb17bdde == 2018-06-22 01:28:10 Check-In == Fix harmless compiler warnings. (user: drh tags: email-alerts) https://fossil-scm.org/fossil/info/5fde17bbbc2cba69d3f8 == 2018-06-22 01:37:26 Check-In == Add the --nocompress option to the "fossil clone" command. (user: drh tags: trunk) https://fossil-scm.org/fossil/info/96d0a4becffa5e4150ab == 2018-06-22 03:17:00 Check-In == Add the /unsubscribe page. (user: drh tags: email-alerts) https://fossil-scm.org/fossil/info/f9116088243353b0f072 == 2018-06-22 12:25:41 Check-In == Make sure the content of outbound email messages always ends with a newline. (user: drh tags: email-alerts) https://fossil-scm.org/fossil/info/b70034837382b06e4b35 == 2018-06-22 13:50:00 Check-In == Add the --sql option to the timeline command. (user: drh tags: email-alerts) https://fossil-scm.org/fossil/info/d51ca5f567349b484540 == 2018-06-22 15:34:06 Check-In == Add logic to generate the text of email alert messages. (user: drh tags: email-alerts) https://fossil-scm.org/fossil/info/bb30d02efdb768b424b0 == 2018-06-22 15:57:46 Check-In == Generate event report in chronological order for an alert text. (user: drh tags: email-alerts) https://fossil-scm.org/fossil/info/e02892522ecf7f3e7956 == 2018-06-22 17:36:33 Check-In == A new way of computing alert text. (user: drh tags: email-alerts) https://fossil-scm.org/fossil/info/6c06b1c896e9c97f9e3b To unsubscribe: https://fossil-scm.org/fossil/unsubscribe -- END -- -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] What should email notifications look like?
On 22 June 2018 at 07:09, jungle Boogie wrote: > On 22 June 2018 at 06:09, Richard Hipp wrote: >> You may have noticed that I've been working on adding support for >> email notifications or alerts to events on a Fossil repository. But I >> need your help. >> >> When an event occurs (such as a check-in, or wiki-page edit) and a >> user wants a notification of that event, what should the email look >> like? >> >> Please send me examples. Pick a timeline event from the Fossil >> self-hosting repository and send me the actual text of an email that >> you think should be dispatched to announce that event. >> > > This is an example of what some git client is sending for the chrony project: > https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-dev/2018/06/msg0.html > > I don't mind that format. > For an additional example, here's what openBSD cvs posts look like: https://marc.info/?l=openbsd-cvs=152964678232394=2 That's very simple, but still informative to show what's changed. I think Philip's format is nice and simple, much of what's above. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] What should email notifications look like?
On Fri, Jun 22, 2018 at 09:09:11AM -0400, Richard Hipp wrote: > When an event occurs (such as a check-in, or wiki-page edit) and a > user wants a notification of that event, what should the email look > like? What I am using for the Mercurial tests is the following: https://mail-index.netbsd.org/source-changes-hg/2018/06/21/msg002146.html Subject contains the common directory prefix of all changed files and the start of the commit message, up to 80 characters in total. The user on the web page is anti-spam fudging. Patch itself is truncated after 300 lines. Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] What should email notifications look like?
Personally I would like something simple such as: Subject line: New check-in on fossil drh made a check-in on branch trunk. Comment: Add a new capability that allows signup for email notification. Change the name of the older "EMail" privilege to "View-PII" to avoid confusion. Date: 2018-06-20 19:56 Hash: 25eafed1 Details at: https://www.fossil-scm.org/fossil/info/25eafed11494e801 The wording could be tweaked, of course, but that's basically the information that I would want to see - so more or less what's displayed on the timeline. If this were rewritten with variable inserts, maybe something like this? Subject line: New check-in on %repo-name% %user% made a check-in on branch %branch%. Comment: %comment% Date: %date% %time% Hash: %hash% Details at: %url% I think it would make sense to have different basic templates (one for check-ins, one for new issues etc). Kind regards, Philip Bennefall On 6/22/2018 3:38 PM, Richard Hipp wrote: On 6/22/18, Philip Bennefall wrote: Would it make sense to have the possibility to supply various email templates in markdown on an admin page, and have insertable variables? Of course with a default text for each new repo. That sounds like good idea. Please send an example. Ideally, your example would show us both the original template, and the text that results from apply the template to a specific timeline event. Perhaps use the check-in at https://www.fossil-scm.org/fossil/timeline?n=3=fa83e4b3 to complete your template. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] What should email notifications look like?
On Fri, 22 Jun 2018 16:46:07 +0200, Marcelo wrote: El vie., 22 jun. 2018 a las 11:09, jungle Boogie () escribió: I'd rather have emails delivered in plain text, bypassing html/markdown but that's just my preference. +1 for plain text notifications. +1 -- Using Opera's revolutionary email client: http://www.opera.com/mail/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] What should email notifications look like?
Yes, plain text please since hyperlinks will point to richer content. On Fri, Jun 22, 2018 at 10:46 AM, Marcelo wrote: > El vie., 22 jun. 2018 a las 11:09, jungle Boogie () > escribió: > >> >> I'd rather have emails delivered in plain text, bypassing >> html/markdown but that's just my preference. >> > > +1 for plain text notifications. > > -- >o-=< Marcelo >=-o > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] What should email notifications look like?
El vie., 22 jun. 2018 a las 11:09, jungle Boogie () escribió: > > I'd rather have emails delivered in plain text, bypassing > html/markdown but that's just my preference. > +1 for plain text notifications. -- o-=< Marcelo >=-o ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] What should email notifications look like?
On 22 June 2018 at 06:09, Richard Hipp wrote: > You may have noticed that I've been working on adding support for > email notifications or alerts to events on a Fossil repository. But I > need your help. > > When an event occurs (such as a check-in, or wiki-page edit) and a > user wants a notification of that event, what should the email look > like? > > Please send me examples. Pick a timeline event from the Fossil > self-hosting repository and send me the actual text of an email that > you think should be dispatched to announce that event. > This is an example of what some git client is sending for the chrony project: https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-dev/2018/06/msg0.html I don't mind that format. I'd rather have emails delivered in plain text, bypassing html/markdown but that's just my preference. > You can reply to this mailing list, or send examples directly to me. > -- > D. Richard Hipp > d...@sqlite.org > ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] What should email notifications look like?
On 6/22/18, Philip Bennefall wrote: > Would it make sense to have the possibility to supply various email > templates in markdown on an admin page, and have insertable variables? > Of course with a default text for each new repo. That sounds like good idea. Please send an example. Ideally, your example would show us both the original template, and the text that results from apply the template to a specific timeline event. Perhaps use the check-in at https://www.fossil-scm.org/fossil/timeline?n=3=fa83e4b3 to complete your template. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] What should email notifications look like?
Would it make sense to have the possibility to supply various email templates in markdown on an admin page, and have insertable variables? Of course with a default text for each new repo. Kind regards, Philip Bennefall P.S. Email notifications are a very welcome addition for us. Thank you! On 6/22/2018 3:09 PM, Richard Hipp wrote: You may have noticed that I've been working on adding support for email notifications or alerts to events on a Fossil repository. But I need your help. When an event occurs (such as a check-in, or wiki-page edit) and a user wants a notification of that event, what should the email look like? Please send me examples. Pick a timeline event from the Fossil self-hosting repository and send me the actual text of an email that you think should be dispatched to announce that event. You can reply to this mailing list, or send examples directly to me. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
