Re: New egg: SRFI-143: Fixnums
On Tue, 17 Nov 2020 17:56:33 -0800 noosph...@mailc.net wrote: > I would like to submit for publication: > > SRFI-143: Fixnums > > Its documentation is here: [1] > > Its release-info is here: [2] > > test-new-egg gives the egg a clean bill of health. > > --Sergey > > [1] - https://wiki.call-cc.org/eggref/5/srfi-143 > > [2] - https://github.com/diamond-lizard/srfi-143/raw/main/release-info Thanks! Your egg has been added to the coop. All the best. Mario -- http://parenteses.org/mario
Re: New egg: SRFI-47: Array
On Tue, 17 Nov 2020 14:52:31 -0800 noosph...@mailc.net wrote: > I would like to submit a new egg for publication: > > SRFI-47: Array > > This is a Chicken 5 port, with permission, of Felix Winkelmann's Chicken > 3 egg[1]. > > The documentation for it can be found here: [2] > > The release-info is here: [3] > > test-new-egg gives it a clean bill of health. > > --Sergey > > [1] - https://wiki.call-cc.org/eggref/3/srfi-47 > > [2] - https://wiki.call-cc.org/eggref/5/srfi-47 > > [3] - https://github.com/diamond-lizard/srfi-47/raw/main/release-info Thanks! Your egg has been added to the coop! All the best. Mario -- http://parenteses.org/mario
New egg: SRFI-143: Fixnums
I would like to submit for publication: SRFI-143: Fixnums Its documentation is here: [1] Its release-info is here: [2] test-new-egg gives the egg a clean bill of health. --Sergey [1] - https://wiki.call-cc.org/eggref/5/srfi-143 [2] - https://github.com/diamond-lizard/srfi-143/raw/main/release-info
New egg: SRFI-47: Array
I would like to submit a new egg for publication: SRFI-47: Array This is a Chicken 5 port, with permission, of Felix Winkelmann's Chicken 3 egg[1]. The documentation for it can be found here: [2] The release-info is here: [3] test-new-egg gives it a clean bill of health. --Sergey [1] - https://wiki.call-cc.org/eggref/3/srfi-47 [2] - https://wiki.call-cc.org/eggref/5/srfi-47 [3] - https://github.com/diamond-lizard/srfi-47/raw/main/release-info
Re: New egg: SRFI-137: Minimal Unique Types
On Tue, 17 Nov 2020 11:15:32 -0800 noosph...@mailc.net wrote: > I would like to submit a new egg for publication: > > SRFI-137: Minimal Unique Types > > The documentation for it is here: [1] > > Its release-info is here: [2] > > test-new-egg gives it a clean bill of health. > > --Sergey > > [1] - https://wiki.call-cc.org/eggref/5/srfi-137 > > [2] - https://github.com/diamond-lizard/srfi-137/raw/main/release-info Thanks! Your egg has been added to the coop. All the best. Mario -- http://parenteses.org/mario
New egg: SRFI-137: Minimal Unique Types
I would like to submit a new egg for publication: SRFI-137: Minimal Unique Types The documentation for it is here: [1] Its release-info is here: [2] test-new-egg gives it a clean bill of health. --Sergey [1] - https://wiki.call-cc.org/eggref/5/srfi-137 [2] - https://github.com/diamond-lizard/srfi-137/raw/main/release-info
Re: Establishing Git repos for miscellaneous Chicken tools
Sure. What should it be called? Is "chicken-tools" ok? Or "chicken-integrations" or "chicken-contrib"? Or even more generically, "chicken-scheme" which doesn't exist yet. It could be "chicken-emacs" but Dan suggested: an organization that focuses on Chicken tool integration would be good; not just for Emacs. I'd love to see LSP support, for instance
Re: Establishing Git repos for miscellaneous Chicken tools
On Tue, 17 Nov 2020 20:59:01 +0200 Lassi Kortela wrote: >> Sounds good to me. Thanks for organizing this. > > Great. Mario, can you create the org since from our initial group of > contributors you are the one most closely associated with Chicken? Sure. What should it be called? All the best. Mario -- http://parenteses.org/mario
Re: Establishing Git repos for miscellaneous Chicken tools
Sounds good to me. Thanks for organizing this. Great. Mario, can you create the org since from our initial group of contributors you are the one most closely associated with Chicken?
Re: Establishing Git repos for miscellaneous Chicken tools
On Tue, 17 Nov 2020 20:41:31 +0200 Lassi Kortela wrote: >> Please note that what I wrote was just a suggestion to prevent future >> problems. I don't mean to impose anything. If you think using GitHub, >> GitLab or whatever git host available would be a good solution, that's >> absolutely fine by me. I use GitHub myself. It was just a small remark >> to avoid falling in the trap of having a lot of dependencies on >> vendor-specific features that might just vanish (like what happened with >> Sourceforge, Google Code etc.). > > No problem, I agree that it's important to avoid vendor lock-in. > >> And, sure, the CHICKEN bug tracker, mailing lists, wiki and IRC channel >> can be used for CHICKEN-related stuff. > > +1 > >> Currently we don't have e-mail notifications. Our use-case is very >> modest for today's standards of fanciness. Our git traffic is very low. >> We basically use the mailing lists to communicate. It's a very simple >> setup -- as it must be, otherwise we wouldn't be able to maintain it. > > Given: > > - a GitHub organization would be preferred for ease of maintenance by > Dan and Vasilij who have written some of the Chicken Emacs support so > far > > - you and I don't object to GH > > - nobody else has said anything > > - a decision seems hard to make > > should we just make a `chicken-tools` org on GitHub? That would let us > resolve the current stagnation in maintaining these packages, and if > we disable the wikis and issue trackers we can move the repos to > another host later on. Sounds good to me. Thanks for organizing this. All the best. Mario -- http://parenteses.org/mario
Re: Establishing Git repos for miscellaneous Chicken tools
On 17/11/2020 18:41, Lassi Kortela wrote: > Given: > > - a GitHub organization would be preferred for ease of maintenance by > Dan and Vasilij who have written some of the Chicken Emacs support so far > > - you and I don't object to GH > > - nobody else has said anything > > - a decision seems hard to make > > should we just make a `chicken-tools` org on GitHub? That would let us > resolve the current stagnation in maintaining these packages, and if we > disable the wikis and issue trackers we can move the repos to another > host later on. Sounds good to me. I'm a staunch opponent of the centralisation of the Internet by monopolies, but using free github stuff in ways that just treat it as a node in a decentralised web of git repos bleeds them of money without letting them use that to get their greedy hooks into you, so DO IT DO IT DO IT AND THEN BRING THEM CRASHING DOWN FROM WITHIN MUHAHAHAH, I reckon :-) -- Alaric Snell-Pym (2E0LOJ neé M7KIT) http://www.snell-pym.org.uk/alaric/ signature.asc Description: OpenPGP digital signature
Re: Establishing Git repos for miscellaneous Chicken tools
Please note that what I wrote was just a suggestion to prevent future problems. I don't mean to impose anything. If you think using GitHub, GitLab or whatever git host available would be a good solution, that's absolutely fine by me. I use GitHub myself. It was just a small remark to avoid falling in the trap of having a lot of dependencies on vendor-specific features that might just vanish (like what happened with Sourceforge, Google Code etc.). No problem, I agree that it's important to avoid vendor lock-in. And, sure, the CHICKEN bug tracker, mailing lists, wiki and IRC channel can be used for CHICKEN-related stuff. +1 Currently we don't have e-mail notifications. Our use-case is very modest for today's standards of fanciness. Our git traffic is very low. We basically use the mailing lists to communicate. It's a very simple setup -- as it must be, otherwise we wouldn't be able to maintain it. Given: - a GitHub organization would be preferred for ease of maintenance by Dan and Vasilij who have written some of the Chicken Emacs support so far - you and I don't object to GH - nobody else has said anything - a decision seems hard to make should we just make a `chicken-tools` org on GitHub? That would let us resolve the current stagnation in maintaining these packages, and if we disable the wikis and issue trackers we can move the repos to another host later on.
Re: New egg: SRFI-78: Lightweight testing
On Tue, 17 Nov 2020 10:04:36 -0800 noosph...@mailc.net wrote: > I would like to submit a new egg for publication: > > SRFI-78: Lightweight testing > > The documentation is here: [1] > > The release-info is here: [2] > > test-new-egg gives the egg a clean bill of health. > > --Sergey > > [1] - https://wiki.call-cc.org/eggref/5/srfi-78 > > [2] - https://github.com/diamond-lizard/srfi-78/raw/main/release-info Thanks! Your egg has been added to the coop. All the best. Mario -- http://parenteses.org/mario
New egg: SRFI-78: Lightweight testing
I would like to submit a new egg for publication: SRFI-78: Lightweight testing The documentation is here: [1] The release-info is here: [2] test-new-egg gives the egg a clean bill of health. --Sergey [1] - https://wiki.call-cc.org/eggref/5/srfi-78 [2] - https://github.com/diamond-lizard/srfi-78/raw/main/release-info
Re: Establishing Git repos for miscellaneous Chicken tools
On Tue, 17 Nov 2020 18:36:24 +0200 Lassi Kortela wrote: >> Switching git hosting solutions should be just a matter of changing the git >> URL. > > AFAICT this can be achieved by turning off the issue tracker and wiki > on GitHub repos. This would mean we use the mailing list, Chicken's > issue tracker, or email/irc for coordination. Since it's just a few > tools, maybe not worth overthinking this? Please note that what I wrote was just a suggestion to prevent future problems. I don't mean to impose anything. If you think using GitHub, GitLab or whatever git host available would be a good solution, that's absolutely fine by me. I use GitHub myself. It was just a small remark to avoid falling in the trap of having a lot of dependencies on vendor-specific features that might just vanish (like what happened with Sourceforge, Google Code etc.). And, sure, the CHICKEN bug tracker, mailing lists, wiki and IRC channel can be used for CHICKEN-related stuff. > Another option would be to put all the tools in one git repo on > code.call-cc.org, and give write access to that repo to the few people > who need it. Is there some way to have it send email notifications, > similar to the GitHub "watch this repo" feature? Currently we don't have e-mail notifications. Our use-case is very modest for today's standards of fanciness. Our git traffic is very low. We basically use the mailing lists to communicate. It's a very simple setup -- as it must be, otherwise we wouldn't be able to maintain it. All the best. Mario -- http://parenteses.org/mario
Re: Establishing Git repos for miscellaneous Chicken tools
Switching git hosting solutions should be just a matter of changing the git URL. AFAICT this can be achieved by turning off the issue tracker and wiki on GitHub repos. This would mean we use the mailing list, Chicken's issue tracker, or email/irc for coordination. Since it's just a few tools, maybe not worth overthinking this? Another option would be to put all the tools in one git repo on code.call-cc.org, and give write access to that repo to the few people who need it. Is there some way to have it send email notifications, similar to the GitHub "watch this repo" feature?
Re: Establishing Git repos for miscellaneous Chicken tools
On Mon, 16 Nov 2020 23:14:03 +0200 Lassi Kortela wrote: > We spoke with Mario and Dan about gathering Git repos for all the > Chicken Emacs packages under one roof, and Dan suggested adding other > tools such as an LSP server into the mix. > > We thought it'd be convenient to start an organization on GitHub or > GitLab to do this, but are not sure whether the community accepts > this. Any suggestions to the contrary? We could use code.call-cc.org, > but is it simple to create organizations and teams there and receive > notifications about commits? call-cc.org doesn't provide fancy collaborative tools on top of git. The workflow for merging changes in the repositories hosted there is based on sending patches to people who have write access to the repositories. As far as I can tell, we have no plan to change that in the foreseeable future. I have no objections against using other git hosting solutions. I'd suggest, though, that we strive to keep things as simple as possible and don't get locked in by using features that might screw us in the future if (actually more like a matter of "when") the host goes out of business, becomes too unstable, changes its services in ways that we don't like, changes its terms of use to something that would be unacceptable for such a project or any other reason. Switching git hosting solutions should be just a matter of changing the git URL. All the best. Mario -- http://parenteses.org/mario
Re: New egg: SRFI-67: Compare Procedures
On Mon, 16 Nov 2020 21:42:00 -0800 noosph...@mailc.net wrote: > I'd like to submit a new egg for publication: > > SRFI-67: Compare Procedures > > This was packed from the reference implementation with permission from > Kon Lovett, the author of the Chicken 3 SRFI-67 egg. > > Unfortunately, that egg could not itself be ported because it relied on > syntax-case, which was available for Chicken 3, but is not for > Chicken 5. So this Chicken 5 implementation is done from scratch from > the reference implementation. > > Its documentation is here: [1] > > Its release-info is here: [2] > > test-new-egg gives the egg a clean bill of health. > > --Sergey > > [1] - https://wiki.call-cc.org/eggref/5/srfi-67 > > [2] - https://github.com/diamond-lizard/srfi-67/raw/main/release-info Thanks! Your egg has been added to the coop. All the best. Mario -- http://parenteses.org/mario
Re: New egg: SRFI-74: Octet-Addressed Binary Blocks
On Mon, 16 Nov 2020 23:14:16 -0800 noosph...@mailc.net wrote: > I would like to submit a new egg for publication: > > SRFI-74: Octet-Addressed Binary Blocks > > Its documentation is here: [1] > > Its release-info is here: [2] > > test-new-egg gives it a clean bill of health. > > --Sergey > > [1] - https://wiki.call-cc.org/eggref/5/srfi-74 > > [2] - https://github.com/diamond-lizard/srfi-74/raw/main/release-info Thanks! Your egg has been added to the coop. All the best. Mario -- http://parenteses.org/mario
Re: New egg: SRFI-51: Handling rest list
On Mon, 16 Nov 2020 16:31:39 -0800 noosph...@mailc.net wrote: > I'd like to submit a new egg for publication: > > SRFI-51: Handling rest list > > Its documenation is here: [1] > > Its release-info is here: [2] > > test-new-egg gave it a clean bill of health. > > --Sergey > > [1] - https://wiki.call-cc.org/eggref/5/srfi-51 > > [2] - https://github.com/diamond-lizard/srfi-51/raw/main/release-info Thanks! Your egg has been added to the coop. All the best. Mario -- http://parenteses.org/mario
