Search the Community

Hi folks 👋 , I start this thread, because thread CONCEPT: UDF Updater allowing to update the UDFs between releases of the AutoIt3 installer where some content of this topic is discussed, set the scope to another main topic/content. I want to extend the discussion related to GitHub in this separate thread. Quick facts: I have now re-established and configured the following GitHub organization, which I have had for some time and used in the the german AutoIt community. These repositories (german related) are hidden (private) for now. So you will not be distracted by them 👌 . 🔗 GitHub Organization https://github.com/AutoIt-Community 🔗 first repository to play with playground 🔗 Discord Server to discuss things more in details https://discord.gg/5DWTpZK3QN What is done so far: Why: Originally, the reason was the topic (CONCEPT: UDF Updater... ) listed above, or rather its intention. But more generally: people with interest of do some sort of collaborative work, creating and sharing AutoIt-based software and libraries (UDFs) and/or enhancing the AutoIt ecosystem are welcome to join the GitHub Org. Other thoughts why this could be helpful and nice for us, see this comment. What's next: Do you want to try the collaboration within GitHub? Let me know and I can add you as "Member" or at least as an "Outside collaborators" (with rights/permission to a specific repository). Do you want to add your great repository which already serves as great examples for AutoIt usage, let me know and I can add the repo. to the Org. Brainstorming, suggestions, ideas ... everything is welcome 🤝 . Clarification needed: A few remaining obstacles or questions need to be clarified. First of all, how could we (in best case consistently) manage licenses regarding the User UDFs (libraries) in combination of the AutoIt software license? For own scripts, software that we would build with AutoIt, we could define which license is used very easy. But scripts that are shipped with the AutoIt product like the default "include" folder (official UDFs) or the example scripts, are product related code. In other words: These are subject to the AutoIt license. What I mean is that it needs to be clearly defined what we are allowed to do and what we are not, and that we would indicate a dual license when publishing. I will clarify how this is legally sound and acceptable. Anyhow, a starting point is given. Let's see what the time brings. ==> I appriciate any feedback. Let me know if you want to join that tryout (playground) GitHub Org. community 🤝. Best regards Sven