From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) by sourceware.org (Postfix) with ESMTPS id 5F3ED3857804 for ; Mon, 9 Nov 2020 17:06:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 5F3ED3857804 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=bothner.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=per@bothner.com Received: from [10.9.9.74] (helo=submission03.runbox) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1kcAcg-0006dk-L2 for kawa@sourceware.org; Mon, 09 Nov 2020 18:06:31 +0100 Received: by submission03.runbox with esmtpsa [Authenticated alias (524175)] (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) id 1kcAcV-0007W9-K4 for kawa@sourceware.org; Mon, 09 Nov 2020 18:06:19 +0100 From: Per Bothner Subject: Kawa future and governance To: Kawa mailing list Message-ID: Date: Mon, 9 Nov 2020 09:06:16 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=5.0 tests=BAYES_50, KAM_DMARC_STATUS, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: kawa@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Kawa mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2020 17:06:35 -0000 As you have probably noticed, there has been less Kawa development the last few years, and I have been less active. I make sure it will work with newer Java release, fix occasional bugs, and make minor improvements, but it's been a while since I've added a new non-trivial feature or API. Most of my "hacking time" these days is spent on DomTerm (https://domterm.org). I'm also less involved with the Scheme community, and I've expressed dissatisfaction with how SRFI and R7RS-large is evolving, with too many large large APIs that I fear will see little use. I am happy to continue in this "maintenance mode" as long as needed, but fresh blood would be welcome. So far Kawa has is mostly the result of my vision, opinions, and prejudices, which I think has resulted in a coherent, efficient, and powerful language - but it is limited what I can understand and implement. It is great what others have contributed to Kawa, but we need to encourage and enable more contributions I have not been as open as I should have to other ideas and impulses, wanting to full understand and implement the "right" solution, even when I have lacked time, knowledge, and energy to do so. Not sure where to go next. It would be good to have a small group who can check in updates and make releases without me. Right now the Kawa "bus factor" is basically one, which is not a good situation. I can see my role becoming a Benevolent Dictator For Life (like van Rossum's role in Python), but ideally getting less dictatorial as others gain experience. One task that could help and that does not require comprehensive understanding of the code is Release Manager(s). Not that it takes a lot of time and effort to make a release (especially since I don't do it very often), but it is one of multiple tasks that should not depend on me being able to do it. Next year Kawa will be 25 years old. It is the oldest continuously-active compiler-based non-Java language on the JVM, which is quite an achievement. But I am not getting any younger, and it needs fresh blood and energy. Thoughts? Volunteers? -- --Per Bothner per@bothner.com http://per.bothner.com/