From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, RCVD_IN_DNSWL_MED autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 16171 invoked from network); 15 Jun 2020 16:20:00 -0000 Received: from lists1.math.uh.edu (129.7.128.208) by inbox.vuxu.org with ESMTPUTF8; 15 Jun 2020 16:20:00 -0000 Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.92.3) (envelope-from ) id 1jkrpV-0005WY-Kd; Mon, 15 Jun 2020 11:19:25 -0500 Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from ) id 1jkrpR-0005Tk-8X for ding@lists.math.uh.edu; Mon, 15 Jun 2020 11:19:21 -0500 Received: from quimby.gnus.org ([95.216.78.240]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1jkrpA-00DG1E-P9 for ding@lists.math.uh.edu; Mon, 15 Jun 2020 11:19:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:Mime-Version:References:Message-ID:Date:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=DhW0ZcI41+oUSg0KbSg5Mp6EkMbcajKf4XQXV4edhGs=; b=LrEsdttI63KhfCNcTipZXI0/wU G3E/qAT2QfUCAT6dedOwHKBWhRnksMRXf+OG+9jwUqRKQCCc08poT0QX/4xb3/Y1l5CgaRJtMmonk ei7hbEU8l9v8EHWyuOJ92x4GJ1aB31SAEqTTXEMbWGXFV0ZuPbDCakFJEWXobzyqqCIA=; Received: from ciao.gmane.io ([159.69.161.202]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jkrp1-000154-6u for ding@gnus.org; Mon, 15 Jun 2020 18:18:59 +0200 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1jkroy-000InR-LT for ding@gnus.org; Mon, 15 Jun 2020 18:18:52 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: [RFC] [WIP] Creating icalendar event invitations Date: Mon, 15 Jun 2020 09:18:38 -0700 Message-ID: <87y2oob8v5.fsf@ericabrahamsen.net> References: <87k10bp71u.fsf@ims.uni-hannover.de> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cancel-Lock: sha1:Qkf8ZuiK/rDILp0+cQZ+f5uaHjY= List-ID: Precedence: bulk Ferdinand Pieper writes: > Hi all, > > gnus has good support to accept/decline icalendar invitations with > gnus-icalendar.el. I'm looking to extend this to also allow the > creation of new invitations from within gnus. > Below is a first rough implementation which I for now kept in a > separate file from gnus-icalendar.el, but the goal would be for > the code to also live in gnus-icalendar.el. > > Most of the code is still very rough and the implementation is not > handling all cases correctly. I'm mainly sharing it now to ask you > whether this is a welcome addition to gnus-icalendar and to ask for > thoughts on the general implementation, before I spend more time to > polish the code. I'll echo the others and say this looks great! I assume you've done your FSF copyright paperwork? > How it works: The code adds functions to create RFC5545 compliant > VCALENDAR and VEVENT parts from gnus-icalendar-event objects and > also a function to create a event invitation based on the current > message buffer. > To create the gnus-icalendar-event the mail addresses in the To header > are converted to required participants, addresses in Cc are > interpreted as optional participants and the subject and message > body are added as summary and description of the event. The date range > and location have to be entered interactively for now. > Please let me know if you have any other ideas on how users could > create new events. I think it would be great to be able to create events starting from an Org heading. Perhaps I've already got an event set up inside Org, and I'd like to use it to compose an invitation. The various values could be taken from heading properties, and the timestamp. > Next step will be to polish the code so that the basic functionality > of creating simple one-shot event invitations works reliably. > Long term goals include handling request responses and supporting a > wider range of the RFC5545 spec. Looking forward to more!