From: <ho...@tj...> - 2025-08-31 13:51:19
|
Fellow AmForthers, Nice to see some activity on the mailing list, which highlights (a) There is still some interest in AmForth from people new to the list. (b) There are still some existing AmForth list members who read the list. (c) AmForth still does not have a maintainer. Regarding (c) I'm putting myself forward as a "maintainer-lite" for AmForth. For those not on the list at the time, the links [0..2] below give some history. Without somebody performing the maintenance role, even in a limited way, it is hard to address some of the issues raised on the mailing list. In short, I think a maintainer-lite would (hopefully!) be better than no maintainer at all, and I have the time now to do that. I would, however, be delighted if anyone wanted to join me. Let me know what you think. Kind regards, Tristan [0] https://sourceforge.net/p/amforth/mailman/message/36959799/ [1] https://sourceforge.net/p/amforth/mailman/message/37649964/ [2] https://sourceforge.net/p/amforth/mailman/message/37894180/ |
From: Mark R. <cab...@gm...> - 2025-09-06 03:09:21
|
It's nice to hear from you Tristan and I will also mirror the good sentiment that there are still people out there interested in AmForth. Granted, there have been less than a dozen messages over the last year but for every message there must be what, 10 or 20 thousand that don't respond? ;) In all seriousness though I thought perhaps Erich would have chimed in. I saw this mail show up at the tail end of my summer vacation after, oddly enough, thinking of your Risc-V project when playing around with the newer esp32-c6s. That day this mail popped in. I should also add that with my eyes getting older I thought it said, "maintainer LIFE" not "lite". One of the reasons, apart from the fact that I still use my local instance of AmForth on my atmel random bitstream thing, that the project was in mind is that someone has been trying to catch up the avra project to the point where the person (Rob3rt iirc) that had the repo allowed in a collaborator that was interested in bringing things up to date. In fact they originally offered to give them the repo. When the conversation turned to forks etc I chimed in with what I'd done last year (or whenever that was) to get avra working for us here. Sadly though, it has only been fits and starts with that although it seems maybe something will come of it. Possibly. So (get to it old man) in any case I'm glad to hear you are putting your hand up to maintain things. I would reiterate though that it should be on some flavor of git as opposed to here on sourceforge. I think Erich did that part some time ago. I know I have a bunch of git repos locally that I think I got from that time that managed to keep the history intact for the most part. Mine is a bit butchered up I think from when I more or less just wanted to make sure I had access to the codebase non-locally. (oof, i'm long winded these days) In any case Tristan, I would be happy to offer whatever assistance I could if you move forward with any of this. Now that the good weather will start winding down I should have a bit more time to offer in that respect. All the best, Mark On Sun, Aug 31, 2025 at 4:51 PM <ho...@tj...> wrote: > Fellow AmForthers, > > Nice to see some activity on the mailing list, which highlights > > (a) There is still some interest in AmForth from people new to the list. > (b) There are still some existing AmForth list members who read the > list. > (c) AmForth still does not have a maintainer. > > Regarding (c) I'm putting myself forward as a "maintainer-lite" for > AmForth. For those not on the list at the time, the links [0..2] below > give some history. Without somebody performing the maintenance role, > even in a limited way, it is hard to address some of the issues raised > on the mailing list. In short, I think a maintainer-lite would > (hopefully!) be better than no maintainer at all, and I have the time > now to do that. I would, however, be delighted if anyone wanted to join > me. > > Let me know what you think. > > Kind regards, > Tristan > > [0] https://sourceforge.net/p/amforth/mailman/message/36959799/ > [1] https://sourceforge.net/p/amforth/mailman/message/37649964/ > [2] https://sourceforge.net/p/amforth/mailman/message/37894180/ > > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
From: Martin N. <amf...@mg...> - 2025-09-12 13:41:20
|
On Sun, 31 Aug 2025 14:45:52 +0100 Tristan wrote: > Fellow AmForthers, > > Nice to see some activity on the mailing list, which highlights > > (a) There is still some interest in AmForth from people new to the > list. (b) There are still some existing AmForth list members who read > the list. > (c) AmForth still does not have a maintainer. > > Regarding (c) I'm putting myself forward as a "maintainer-lite" for > AmForth. For those not on the list at the time, the links [0..2] > below give some history. Without somebody performing the maintenance > role, even in a limited way, it is hard to address some of the issues > raised on the mailing list. In short, I think a maintainer-lite would > (hopefully!) be better than no maintainer at all, and I have the time > now to do that. I would, however, be delighted if anyone wanted to > join me. > > Let me know what you think. > > Kind regards, > Tristan > > All in favour. I am still working with AmForth and have some bugs/patches/improvements waiting for a maintainer. BTW, I found a fork of AmForth on GitHub whilst looking for a Python3 version of amforth-shell.py: https://github.com/CableGuy67/AmForth Probably there is more good stuff there. -- Regards, Martin Nicholas. E-mail: rep...@mg... (Address will be valid throughout 2025). |
From: Mark R. <cab...@gm...> - 2025-09-12 14:56:43
|
lol, that's mine. It's where I parked stuff when I was trying to get the avra stuff working. I bashed the avra (enough of) into it last year or whenever that was. :) On Fri, Sep 12, 2025 at 4:41 PM Martin Nicholas via Amforth-devel < amf...@li...> wrote: > On Sun, 31 Aug 2025 14:45:52 +0100 > Tristan wrote: > > > Fellow AmForthers, > > > > Nice to see some activity on the mailing list, which highlights > > > > (a) There is still some interest in AmForth from people new to the > > list. (b) There are still some existing AmForth list members who read > > the list. > > (c) AmForth still does not have a maintainer. > > > > Regarding (c) I'm putting myself forward as a "maintainer-lite" for > > AmForth. For those not on the list at the time, the links [0..2] > > below give some history. Without somebody performing the maintenance > > role, even in a limited way, it is hard to address some of the issues > > raised on the mailing list. In short, I think a maintainer-lite would > > (hopefully!) be better than no maintainer at all, and I have the time > > now to do that. I would, however, be delighted if anyone wanted to > > join me. > > > > Let me know what you think. > > > > Kind regards, > > Tristan > > > > > > All in favour. I am still working with AmForth and have some > bugs/patches/improvements waiting for a maintainer. > > BTW, I found a fork of AmForth on GitHub whilst looking for a Python3 > version of amforth-shell.py: > https://github.com/CableGuy67/AmForth > Probably there is more good stuff there. > > -- > Regards, > > Martin Nicholas. > > E-mail: rep...@mg... (Address will be valid throughout 2025). > > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
From: Erich W. <ew....@na...> - 2025-09-13 15:00:24
|
Mark Roth <cab...@gm...> writes: > lol, that's mine. > > It's where I parked stuff when I was trying to get the avra > stuff working. I bashed the avra (enough of) into it last year > or whenever that was. :) I'm using that version of avra! :) With versions 5.0 .. 5.5 of avra. Thanks, Mark! Erich > > On Fri, Sep 12, 2025 at 4:41 PM Martin Nicholas via Amforth-devel < > amf...@li...> wrote: > >> On Sun, 31 Aug 2025 14:45:52 +0100 >> Tristan wrote: >> >> > Fellow AmForthers, >> > >> > Nice to see some activity on the mailing list, which highlights >> > >> > (a) There is still some interest in AmForth from people new to the >> > list. (b) There are still some existing AmForth list members who read >> > the list. >> > (c) AmForth still does not have a maintainer. >> > >> > Regarding (c) I'm putting myself forward as a "maintainer-lite" for >> > AmForth. For those not on the list at the time, the links [0..2] >> > below give some history. Without somebody performing the maintenance >> > role, even in a limited way, it is hard to address some of the issues >> > raised on the mailing list. In short, I think a maintainer-lite would >> > (hopefully!) be better than no maintainer at all, and I have the time >> > now to do that. I would, however, be delighted if anyone wanted to >> > join me. >> > >> > Let me know what you think. >> > >> > Kind regards, >> > Tristan >> > >> > >> >> All in favour. I am still working with AmForth and have some >> bugs/patches/improvements waiting for a maintainer. >> >> BTW, I found a fork of AmForth on GitHub whilst looking for a Python3 >> version of amforth-shell.py: >> https://github.com/CableGuy67/AmForth >> Probably there is more good stuff there. >> >> -- >> Regards, >> >> Martin Nicholas. >> >> E-mail: rep...@mg... (Address will be valid throughout 2025). >> >> >> _______________________________________________ >> Amforth-devel mailing list for http://amforth.sf.net/ >> Amf...@li... >> https://lists.sourceforge.net/lists/listinfo/amforth-devel >> > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel -- May the Forth be with you ... |
From: Brian K N. <bkn...@gm...> - 2025-09-15 14:01:43
|
Thanks for the work. Love amforth and especially when I don't have to use wine under linux brian-in-ohio On Sat, Sep 13, 2025 at 11:01 AM Erich Wälde <ew....@na...> wrote: > Mark Roth <cab...@gm...> writes: > > > lol, that's mine. > > > > It's where I parked stuff when I was trying to get the avra > > stuff working. I bashed the avra (enough of) into it last year > > or whenever that was. :) > > I'm using that version of avra! :) > With versions 5.0 .. 5.5 of avra. > > Thanks, Mark! > Erich > > > > > On Fri, Sep 12, 2025 at 4:41 PM Martin Nicholas via Amforth-devel < > > amf...@li...> wrote: > > > >> On Sun, 31 Aug 2025 14:45:52 +0100 > >> Tristan wrote: > >> > >> > Fellow AmForthers, > >> > > >> > Nice to see some activity on the mailing list, which highlights > >> > > >> > (a) There is still some interest in AmForth from people new to the > >> > list. (b) There are still some existing AmForth list members who read > >> > the list. > >> > (c) AmForth still does not have a maintainer. > >> > > >> > Regarding (c) I'm putting myself forward as a "maintainer-lite" for > >> > AmForth. For those not on the list at the time, the links [0..2] > >> > below give some history. Without somebody performing the maintenance > >> > role, even in a limited way, it is hard to address some of the issues > >> > raised on the mailing list. In short, I think a maintainer-lite would > >> > (hopefully!) be better than no maintainer at all, and I have the time > >> > now to do that. I would, however, be delighted if anyone wanted to > >> > join me. > >> > > >> > Let me know what you think. > >> > > >> > Kind regards, > >> > Tristan > >> > > >> > > >> > >> All in favour. I am still working with AmForth and have some > >> bugs/patches/improvements waiting for a maintainer. > >> > >> BTW, I found a fork of AmForth on GitHub whilst looking for a Python3 > >> version of amforth-shell.py: > >> https://github.com/CableGuy67/AmForth > >> Probably there is more good stuff there. > >> > >> -- > >> Regards, > >> > >> Martin Nicholas. > >> > >> E-mail: rep...@mg... (Address will be valid throughout 2025). > >> > >> > >> _______________________________________________ > >> Amforth-devel mailing list for http://amforth.sf.net/ > >> Amf...@li... > >> https://lists.sourceforge.net/lists/listinfo/amforth-devel > >> > > > > _______________________________________________ > > Amforth-devel mailing list for http://amforth.sf.net/ > > Amf...@li... > > https://lists.sourceforge.net/lists/listinfo/amforth-devel > > -- > May the Forth be with you ... > > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |
From: <ho...@tj...> - 2025-09-18 09:22:22
|
Fellow AmForthers, Erich has very kindly given me admin access to the sourceforge repo, so I have the tools to be a maintainer-lite for the AmForth project. What I need to do now is to (a) practise some svn in a safe place (b) compile a TODO list for the next release. Currently on the TODO list are - a build process that makes use of an amended avra (from Mark ) - inclusion of prebuilt hex files in releases to be the norm - bugs/patches/improvements (from Nicholas) - AmForth RISC-V developments (from me) I would be very happy to receive suggestions, opinions, patches from list members to add to the above. The more the merrier. Best wishes, Tristan |