Re: [Amforth] draft: roadmap for AmForth
Hi Erich, I’m probably another year out to offer any help if I’m even still capable… although I think I could muddle through and contribute some system admin type help with the irksome repositories. It seems to me that embedded hardware is vibrantly healthy and with the pressures IoT and of energy management low power etc. may stay that way. I’m curious therefore about the future of the current Atmel platform vs some of the other chips out there. Should amforth keep its name or has it evolved to something else than Atmel Forth? As for the plan it sounds great to me. I am especially the part about realizing that having a plan makes us better prepared for change not resistant to it. “it might change anytime without prior notice” . Thank you again for stepping in on this project. I hope to return to forth when I unpack my Oscilloscope and bench power supply wherever they went. May the forth be with all the AMForthers - or any other corny positive greeting I can offer in this very strange and ugly year. Ian > On Nov 2, 2020, at 2:36 PM, Erich Wälde wrote: > > > Dear AmForthers, > > some time ago (2020-08-02), Mark Roth suggested to come up with a > "road map". Now while mapping unknown territory is a challenge of > sorts, it might be not that difficult in this case. > > This my personal point of view, it might change anytime without prior > notice. > > 1. Accumulate all commits since Jan 2019 and call it *release 6.9* > That I have done. :) > > 2. Document the exact steps that were needed to create "a release". > Well yes, I have these lines, but not in shape and maybe not > complete. It should be added to the repository nonetheless. > > 3. Add testing scripts --- I have a set of scripts for that, but I > have not run this stuff yet. However, in my opinion adding a > working test suite is far more important at the moment, than > anything else. > > This includes preparing some hardware with 4 relevant target boards > in order to simplify the process. > > 4. Call this *release 7.0* > > 5. Convert and Move Repository > > Currently it looks like I would have to convert the svn repository > to a git repository with a tool like svn2git. This is a process I > would like to avoid, so if someone knows how to convert the > repository "server side", or even how to export the complete svn > repository on sourceforge into a big file ... all hints are kindly > appreciated. > > I would then move to sourcehut.org. Why? > > - I do have an account there already > - sourcehut offers accounts for a very reasonable amount of money. > - sourchut works without javascript! Can you believe this? No? Try it. > For me this is a major step in the correct direction. [1] > - I would order and pay for a new project account > - I would like to add at least two collaborators with full access > from day one. Volunteers? > > This is going to include more things than just converting the > repository: > > - possibly convert the releases/N.M directories into branches > - create a new space for the webpage > - automate generation of the webpage, serverside if possible > - document how to locally generate the documentation --- well, the > stuff you have to install before "cd doc; make all". > - look into the use of javascript and possible ways to reduce that, > should it be desirable > - create an archive for (some of) the old tarballs > - archive and transfer the mailing list content > - create a new mailing list > - automate the generation of a release > - document the release process > - start using the bugtracker (preferably with connection to the > mailing list) > - test the branch-edit-pull.request-merge workflow > - possibly convert "Opinion" into a prober blog? > - setup a redirection notice on sourceforge, close everything else > down. > - possibly dissolve amforth/community into a ./contrib/ > subdirectory, test the stuff again and document it better > https://sourceforge.net/p/amforth/community/HEAD/tree/ > > And this list is not complete. > > 6. Call this *release 8.0* > > 7. Remove arm msp430 riscv for the sake of simplicity -- unless > someone speaks up to offer help. > > Carsten has offered support for arm and riscv --- Thank you! > > msp430 anyone? > > 8. Fix and automate the creation of the reference cards > > - include ALL available WORDs (not only the ones in a particular > build) > - include the exact file path(s), where WORD is defined > - possibly add a Forth equivalent (.asm WORDS) > - possibly a pointer to a worked example > > In order to achieve that I would rework the existing perl script > AND add any missing file headers, possibly in a new/enhanced > format. > > > If we get this far, then imho we have /advanced considerably/. > > > > > Does this sound like a worthwile plan? > > I'm sure there are other ideas and suggestions. > >
Re: [Amforth] draft: roadmap for AmForth
I would love to see native Forth on the ESP8266 boards. With 4mb of storage that my boards have, it would be really handy. -- Matt On 11/2/20 3:36 PM, Tristan Williams wrote: Hello Erich, AmForthers, Does this sound like a worthwile plan? Yes, very much so. I would be interested in progressing further with AmForth for RISC-V. The existing AmForth target board HiFive1 has been discontinued [1] - though there is the upgraded HiFive1 Rev B [2]. Are there any views on which RISC-V board(s) should be considered for AmForth? I like the idea of converting "opinion" into a proper blog, perhaps extending it to some more general Forth ideas/resources. Best wishes, Tristan [1] https://www.sifive.com/boards/hifive1 [2] https://www.sifive.com/boards/hifive1-rev-b On 02Nov20 20:36, Erich Wälde wrote: Dear AmForthers, some time ago (2020-08-02), Mark Roth suggested to come up with a "road map". Now while mapping unknown territory is a challenge of sorts, it might be not that difficult in this case. This my personal point of view, it might change anytime without prior notice. 1. Accumulate all commits since Jan 2019 and call it *release 6.9* That I have done. :) 2. Document the exact steps that were needed to create "a release". Well yes, I have these lines, but not in shape and maybe not complete. It should be added to the repository nonetheless. 3. Add testing scripts --- I have a set of scripts for that, but I have not run this stuff yet. However, in my opinion adding a working test suite is far more important at the moment, than anything else. This includes preparing some hardware with 4 relevant target boards in order to simplify the process. 4. Call this *release 7.0* 5. Convert and Move Repository Currently it looks like I would have to convert the svn repository to a git repository with a tool like svn2git. This is a process I would like to avoid, so if someone knows how to convert the repository "server side", or even how to export the complete svn repository on sourceforge into a big file ... all hints are kindly appreciated. I would then move to sourcehut.org. Why? - I do have an account there already - sourcehut offers accounts for a very reasonable amount of money. - sourchut works without javascript! Can you believe this? No? Try it. For me this is a major step in the correct direction. [1] - I would order and pay for a new project account - I would like to add at least two collaborators with full access from day one. Volunteers? This is going to include more things than just converting the repository: - possibly convert the releases/N.M directories into branches - create a new space for the webpage - automate generation of the webpage, serverside if possible - document how to locally generate the documentation --- well, the stuff you have to install before "cd doc; make all". - look into the use of javascript and possible ways to reduce that, should it be desirable - create an archive for (some of) the old tarballs - archive and transfer the mailing list content - create a new mailing list - automate the generation of a release - document the release process - start using the bugtracker (preferably with connection to the mailing list) - test the branch-edit-pull.request-merge workflow - possibly convert "Opinion" into a prober blog? - setup a redirection notice on sourceforge, close everything else down. - possibly dissolve amforth/community into a ./contrib/ subdirectory, test the stuff again and document it better https://sourceforge.net/p/amforth/community/HEAD/tree/ And this list is not complete. 6. Call this *release 8.0* 7. Remove arm msp430 riscv for the sake of simplicity -- unless someone speaks up to offer help. Carsten has offered support for arm and riscv --- Thank you! msp430 anyone? 8. Fix and automate the creation of the reference cards - include ALL available WORDs (not only the ones in a particular build) - include the exact file path(s), where WORD is defined - possibly add a Forth equivalent (.asm WORDS) - possibly a pointer to a worked example In order to achieve that I would rework the existing perl script AND add any missing file headers, possibly in a new/enhanced format. If we get this far, then imho we have /advanced considerably/. Does this sound like a worthwile plan? I'm sure there are other ideas and suggestions. Point 5 is huge and needs to be broken into smaller steps. I would appreciate any response, and if you could include, which target you are using, all the better. Still reading? Thank you for your precious time. Happy forthing, Erich [1] I'm using torbrowser most of the time. I'm using firefox to work at amforth.sourceforge.net. However, NoScript or uMatrix do an excellent
Re: [Amforth] draft: roadmap for AmForth
Hello Erich, AmForthers, > Does this sound like a worthwile plan? Yes, very much so. I would be interested in progressing further with AmForth for RISC-V. The existing AmForth target board HiFive1 has been discontinued [1] - though there is the upgraded HiFive1 Rev B [2]. Are there any views on which RISC-V board(s) should be considered for AmForth? I like the idea of converting "opinion" into a proper blog, perhaps extending it to some more general Forth ideas/resources. Best wishes, Tristan [1] https://www.sifive.com/boards/hifive1 [2] https://www.sifive.com/boards/hifive1-rev-b On 02Nov20 20:36, Erich Wälde wrote: > > Dear AmForthers, > > some time ago (2020-08-02), Mark Roth suggested to come up with a > "road map". Now while mapping unknown territory is a challenge of > sorts, it might be not that difficult in this case. > > This my personal point of view, it might change anytime without prior > notice. > > 1. Accumulate all commits since Jan 2019 and call it *release 6.9* >That I have done. :) > > 2. Document the exact steps that were needed to create "a release". >Well yes, I have these lines, but not in shape and maybe not >complete. It should be added to the repository nonetheless. > > 3. Add testing scripts --- I have a set of scripts for that, but I >have not run this stuff yet. However, in my opinion adding a >working test suite is far more important at the moment, than >anything else. > >This includes preparing some hardware with 4 relevant target boards >in order to simplify the process. > > 4. Call this *release 7.0* > > 5. Convert and Move Repository > >Currently it looks like I would have to convert the svn repository >to a git repository with a tool like svn2git. This is a process I >would like to avoid, so if someone knows how to convert the >repository "server side", or even how to export the complete svn >repository on sourceforge into a big file ... all hints are kindly >appreciated. > >I would then move to sourcehut.org. Why? > >- I do have an account there already >- sourcehut offers accounts for a very reasonable amount of money. >- sourchut works without javascript! Can you believe this? No? Try it. > For me this is a major step in the correct direction. [1] >- I would order and pay for a new project account >- I would like to add at least two collaborators with full access > from day one. Volunteers? > >This is going to include more things than just converting the >repository: > >- possibly convert the releases/N.M directories into branches >- create a new space for the webpage >- automate generation of the webpage, serverside if possible >- document how to locally generate the documentation --- well, the > stuff you have to install before "cd doc; make all". >- look into the use of javascript and possible ways to reduce that, > should it be desirable >- create an archive for (some of) the old tarballs >- archive and transfer the mailing list content >- create a new mailing list >- automate the generation of a release >- document the release process >- start using the bugtracker (preferably with connection to the > mailing list) >- test the branch-edit-pull.request-merge workflow >- possibly convert "Opinion" into a prober blog? >- setup a redirection notice on sourceforge, close everything else > down. >- possibly dissolve amforth/community into a ./contrib/ > subdirectory, test the stuff again and document it better > https://sourceforge.net/p/amforth/community/HEAD/tree/ > >And this list is not complete. > > 6. Call this *release 8.0* > > 7. Remove arm msp430 riscv for the sake of simplicity -- unless >someone speaks up to offer help. > >Carsten has offered support for arm and riscv --- Thank you! > >msp430 anyone? > > 8. Fix and automate the creation of the reference cards > >- include ALL available WORDs (not only the ones in a particular > build) >- include the exact file path(s), where WORD is defined >- possibly add a Forth equivalent (.asm WORDS) >- possibly a pointer to a worked example > >In order to achieve that I would rework the existing perl script >AND add any missing file headers, possibly in a new/enhanced >format. > > > If we get this far, then imho we have /advanced considerably/. > > > > > Does this sound like a worthwile plan? > > I'm sure there are other ideas and suggestions. > > Point 5 is huge and needs to be broken into smaller steps. > > > I would appreciate any response, and if you could > include, which target you are using, all the better. > > > Still reading? > Thank you for your precious time. > > Happy forthing, > Erich > > > > [1] I'm using torbrowser most of the time. I'm using firefox to > work at amforth.sourceforge.net. However, NoScript or uMatrix do > an
[Amforth] draft: roadmap for AmForth
Dear AmForthers, some time ago (2020-08-02), Mark Roth suggested to come up with a "road map". Now while mapping unknown territory is a challenge of sorts, it might be not that difficult in this case. This my personal point of view, it might change anytime without prior notice. 1. Accumulate all commits since Jan 2019 and call it *release 6.9* That I have done. :) 2. Document the exact steps that were needed to create "a release". Well yes, I have these lines, but not in shape and maybe not complete. It should be added to the repository nonetheless. 3. Add testing scripts --- I have a set of scripts for that, but I have not run this stuff yet. However, in my opinion adding a working test suite is far more important at the moment, than anything else. This includes preparing some hardware with 4 relevant target boards in order to simplify the process. 4. Call this *release 7.0* 5. Convert and Move Repository Currently it looks like I would have to convert the svn repository to a git repository with a tool like svn2git. This is a process I would like to avoid, so if someone knows how to convert the repository "server side", or even how to export the complete svn repository on sourceforge into a big file ... all hints are kindly appreciated. I would then move to sourcehut.org. Why? - I do have an account there already - sourcehut offers accounts for a very reasonable amount of money. - sourchut works without javascript! Can you believe this? No? Try it. For me this is a major step in the correct direction. [1] - I would order and pay for a new project account - I would like to add at least two collaborators with full access from day one. Volunteers? This is going to include more things than just converting the repository: - possibly convert the releases/N.M directories into branches - create a new space for the webpage - automate generation of the webpage, serverside if possible - document how to locally generate the documentation --- well, the stuff you have to install before "cd doc; make all". - look into the use of javascript and possible ways to reduce that, should it be desirable - create an archive for (some of) the old tarballs - archive and transfer the mailing list content - create a new mailing list - automate the generation of a release - document the release process - start using the bugtracker (preferably with connection to the mailing list) - test the branch-edit-pull.request-merge workflow - possibly convert "Opinion" into a prober blog? - setup a redirection notice on sourceforge, close everything else down. - possibly dissolve amforth/community into a ./contrib/ subdirectory, test the stuff again and document it better https://sourceforge.net/p/amforth/community/HEAD/tree/ And this list is not complete. 6. Call this *release 8.0* 7. Remove arm msp430 riscv for the sake of simplicity -- unless someone speaks up to offer help. Carsten has offered support for arm and riscv --- Thank you! msp430 anyone? 8. Fix and automate the creation of the reference cards - include ALL available WORDs (not only the ones in a particular build) - include the exact file path(s), where WORD is defined - possibly add a Forth equivalent (.asm WORDS) - possibly a pointer to a worked example In order to achieve that I would rework the existing perl script AND add any missing file headers, possibly in a new/enhanced format. If we get this far, then imho we have /advanced considerably/. Does this sound like a worthwile plan? I'm sure there are other ideas and suggestions. Point 5 is huge and needs to be broken into smaller steps. I would appreciate any response, and if you could include, which target you are using, all the better. Still reading? Thank you for your precious time. Happy forthing, Erich [1] I'm using torbrowser most of the time. I'm using firefox to work at amforth.sourceforge.net. However, NoScript or uMatrix do an excellent job, but break the sf.net webpage routinely. I do not see all the buttons and what not unless I really switch off NoScript. This is not, what I prefer. -- May the Forth be with you ... ___ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
