Re: Eu 4.2 Help
- Posted by ghaberek (admin) Nov 11, 2022
- 940 views
As Greg stated in a previous thread, help is needed to get Euphoria 4.2 out the door. I'd like to make this thread as a TO-DO list if you will. Things that we can do to help speed up the process of getting Eu 4.2 out the door. I'll try to help any way I can. I know Euphoria pretty well. I have decent knowledge of C, so hopefully there are parts or libraries that I can work on.
As per my previous post, I am happy to help, just need to know where to be pointed. If there was a project structure, with reviewers and appointers, that would be immensely helpful to me.
I have a running list on the Roadmap42 page but I'll it summarize here. This list is mostly in order of priority, which happens to correlate well with the "approachability" of each task. The further down the list you go, the more you'll need to have a good understanding of how Euphoria is put together and how to make changes to the backend, which has taken me a few years of sporadic testing and tinkering to understand. I know a lot of the documentation needs correcting less for spelling/grammar and more for verbiage, like statements that still imply we're strictly 32-bit. There are a lot of open tickets that are ten years old and assigned to folks who haven't been around in years, most of which can probably be closed. Remaining tickets should be reassigned and addressed if possible before we do a release.
- Audit documentation without bike-shedding about how we build docs
- Audit tickets and close or reassign to active users where required
- Provide feedback/discussion on new feature decisions and design
- Extending the standard library with new features
- Migrating and updating libraries from Euphoria MVC
- Build and test latest code from master branch
- Implementing additional backend features like FFI
- Wrap third-party libraries to bundle with Euphoria
- Update installers and distribution packaging
- Update Makefile to improve build system
- Revisit documentation build/hosting strategy
- Migrate website tickets (after cleanup) to GitHub issues
- Rebuild the website using more modern web development tools
-Greg
