Some insights from another place..... I use JAL to validate another another 8bit PIC/AVR compiler. Great Cow BASIC.
I am sharing my insights from taking on the development and release management leadership for Great Cow BASIC.
Why? Because Open Source tools need to be available to engineers across the world that work and offer a different experience and price point to commercial software.
I am not pushing another compiler. So, please DO NOT have a go at me for sharing, or, the fact that this is BASIC.
I am very, very willing to provide tooling we use to use to make life easy.
------
The GCB community is key to what we do today and how we do it. The outcomes produced enable people/engineers to discover, use and maintain projects using the compiler and the tool chain.
The journey to create the outcomes we have today is totally based on the community.
I collate these efforts (including my own efforts) into the releases. The outcomes today are - in no specific order:
1. High quality compiler and supporting tool chain. The IDE, PPSTOOL, etc etc.
3. Website - with interesting material that is maintained by a webmaster.
4. Forum - a friendly forum.
5. Help - in many formats CHM, PDF, HTML, XML, Git WIKI etc for many different OSs and working practices by users.
6. Demonstrations (1000s of them... and these same demonstrations can be used to the test the compiler, libraries etc.
7. YouTube - tutorials, projects and show & tells
8. Source code - published and controlled
9. Installer - Windows, MacOS, Linux etc.
10. Push messages via Twitter and Social Media.
-----
The journey from a ZIP file for a command line Windows compiler that controlled LEDs and an LCD to the project today was as follows:
I am assuming the source code repository and forum are ok.
1. Creation of OS specific installers using a continuous build process to enable a consistent user development environment. Assign OS masters [aka lead engineer] (windows, MacOs, LInux etc).
2. Website update using TypeSetter (very easy!) - assign a webmaster. Ensure highest quality. Learn how Google etc assess a website for quality.
3. Establish automated testing using the demonstrations to perform compiler, library and functional testing - you will need a project team to create this capability - we use software R2BUILD to support this activity.
4. Establish automated creation of Help. (I can give you these tools to create the Help outputs) GCB is 438 pages of Help. Assign Editor master.
5. Start YouTube publication of tutorials based on a) chip architecture [we have standard approach for this], b) Libraries show casing and/or c) Major updates. Need to get lots of folks to do this. Start publication of shorts on TikTok.
6. Start Social media comms plan - need to get JAL to top search in major search engines.
This has taken 4 years and there is steady community of users.
----
I really hope this posts help the discussion.
Evan