AutoIt Community (GitHub Organization)

[SOLVE-SMART]

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:

Spoiler

Like @genius257 suggested:

• Create a new GitHub organization or use an existing if applicable. ✅
• Setup global repository ruleset(s). At least one ruleset should require pull requests to merge to - master/main, and at least one pull request review, to merge. ✅
• Invite relevant users and setup permissions. ✅
  • For now, I invited @genius257 and @WildByDesign because I know their GitHub accounts.
  • Additional member or non-members but "Outside collaborators" can be added easyly later.
  • The "Members" of the organization are also restricted quite a lot for now, because I would add more permission from time to time.
  • The "Outside collaborators" would have only access to specific repositories, not the whole organization.
• Create a new repository for the organization, as a proof of concept. ✅
  • https://github.com/AutoIt-Community/playground
• Create the license file. ✅
  • I started with the playground repo with the default and very open source like MIT license.
• Decide on a versioning standard. I would suggest semver, but that is just my preference. ✅
  • I started with SemVer, yes.
• Decide on how to document dependency version requirements, preferable in a format for a script to use. 💡 (not done yet)
• Optionally have a maintained changelog file. my personal prefence is the Keep a Changelog standard. ✅
  • I started with the Keep a Changelog standard, yes
• Create a code of conduct. More information here, if needed. 💡 (not done yet)
• Create guidelines for contributors. 💡 (not done yet)
• Optionally there are issue and pr templates in GitHub, if relevant. 💡 (not done yet)
  • I added two example GitHub issues to demonstrate the handling.
• I would also suggest setting up GitHub workflows for automated tests, like linting, maybe testing functionality. This will also help in pull requests, before any reviewer needs to be involved. 💡 (not done yet)

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

Edited 21 hours ago by SOLVE-SMART

[TheDcoder]

Hey @SOLVE-SMART, I recieved your invite to the org, and it is an interesting idea, however one of the "concerns" with joining the org is that our IP address is shared with the admins of the org, and I personally am not comfortable with providing that kind of access to my data, and some others might have the same opinion as well. Perhaps it's better to host it on some other place with better privacy, maybe Codeberg? I recently started using it with my latest project and it looks like a good enough place to build software.

Aside from that, I don't think I can really contribute at this time since I don't use AutoIt these days, it being not available in Linux and all

3 hours ago, SOLVE-SMART said:

But scripts that are shipped with the AutoIt product like the default "include" folder (official UDFs) or the example scripts, are product related code.

I don't think that's going to be an issue due to this clause:

Quote

Reproduction and Distribution. You may reproduce and distribute an unlimited number of copies of the SOFTWARE PRODUCT either in whole or in part; each copy should include all copyright and trademark notices, and shall be accompanied by a copy of this EULA. Copies of the SOFTWARE PRODUCT may be distributed as a standalone product or included with your own product.

Obligatory IANAL

[SOLVE-SMART]

Hi @TheDcoder 👋 ,

thank you for the response. I respect your concerns, it's your choise what you want to share and what not, of course. I personally wasn't aware about the fact that I as "Owner" (admin) of the GitHub Org. can see your IP address and to be honest it doesn't matter to me in any case 😅 . Are you sure the admins/owner can see such information?

What you describe is basically all around the web, am I right? I mean the server admins of this forum do also know your IP address, your email provider and so forth. But still, it's your choise, I am fine with it.

1 hour ago, TheDcoder said:

[...] maybe Codeberg [...]

I know Codeberg, but I am not familiar with it and don't think that the few AutoIt folks here, do join Codeberg while they already have a GitHub presents.

1 hour ago, TheDcoder said:

Aside from that, I don't think I can really contribute at this time since I don't use AutoIt these days, it being not available in Linux and all

That's a deal-breaker for you anyway, so I'd prefer to leave it at GitHub and let everyone decide for themselves what they want to do - sure.
The situation makes me a little sad, as you are a very experienced developer and know your way around Git and GitHub well. However, I also understand that you don't use AutoIt as much anymore since you're on Linux.

1 hour ago, TheDcoder said:

[...] due to this clause: [...]

Thank you for that remark 👌 . Seems to be clear and okay then for me. But I double check, maybe directly with Jon, Jpm and/or Jos.

-------------------------

🖼️ Invited members so far:

Spoiler

💡 Disclaimer: This is not privacy relevant, because these are public account on GitHub.

Should I cancel the invitation for your account @TheDcoder or what do you prefer? Maybe you decide to join later (in months), then simple get in touch with me and you are in 😁 .

 

🖼️ Already joined members:

Spoiler

💡 Disclaimer: This is not privacy relevant, because these are public account on GitHub.

Best regards
Sven

Edited 22 hours ago by SOLVE-SMART

[TheDcoder]

1 hour ago, SOLVE-SMART said:

Are you sure the admins/owner can see such information?

Yes, I am sure because GitHub itself mentions it when you are about to accept the invite

1 hour ago, SOLVE-SMART said:

What you describe is basically all around the web, am I right?

That's true, but on GitHub it's the private users who are able to see the IP address, not the actual admins running the website

I know that it's not a big deal but I'm privacy conscious.

1 hour ago, SOLVE-SMART said:

I know Codeberg, but I am not familiar with it and don't think that the few AutoIt folks here, do join Codeberg while they already have a GitHub presents.

It's great, it's based on an self-hosted version of a Git "forge" called Forgejo, and since they're a registered non-profit in Germany/Europe I trust them as well. If it wasn't for the community on GitHub I would've moved away a long time ago.

1 hour ago, SOLVE-SMART said:

But I double check, maybe directly with Jon, Jpm and/or Jos.

That's a good idea too, I'd be surprised if have any objections.

1 hour ago, SOLVE-SMART said:

Should I cancel the invitation for your account @TheDcoder

Yeah I think that'll be the best for now.

1 hour ago, SOLVE-SMART said:

Maybe you decide to join later (in months), then simple get in touch with me and you are in 😁 .

Great, I'll reconsider joining whenever I resume working on EasyCodeIt

1 hour ago, SOLVE-SMART said:

💡 Disclaimer: This is not privacy relevant, because these are public account on GitHub.

By the way, you say that but you blur the names of some members... but not their usernames, which you probably should blur too if you don't want to reveal their names.

[SOLVE-SMART]

2 minutes ago, TheDcoder said:

Yes, I am sure because GitHub itself mentions it when you are about to accept the invite

Okay, understood 😅 .

2 minutes ago, TheDcoder said:

1 hour ago, SOLVE-SMART said:

Should I cancel the invitation for your account @TheDcoder

Yeah I think that'll be the best for now.

Done, invitation is canceled.

3 minutes ago, TheDcoder said:

Great, I'll reconsider joining whenever I resume working on EasyCodeIt

Would be great to see that you work on it again 💪 .

3 minutes ago, TheDcoder said:

you blur the names of some members...

This is a mistake. I blurry all before and remove the blurring again. So I missed two places.

---------------------

I will have a deeper look at Codeberg 👌 .

Best regards
Sven

[argumentum]

9 hours ago, SOLVE-SMART said:

I know Codeberg, but I am not familiar with it and don't think that the few AutoIt folks here, do join Codeberg while they already have a GitHub presents.

GitHub is trying to come up with new ways to monetize. Codeberg has "members" ( if you wanna cast a vote ). All git commands are the same.
Going one way or the other is all the same to me.

Edit: Can't find a way to recover my argumentum GitHub account ( that should be mine but, can't remember a thing ) so am going with another one 🤷‍♂️

Edited 13 hours ago by argumentum

[SOLVE-SMART]

Thanks @argumentum. I also saw the video from theprimeagen, but as we are not a commercial community and we probably would not use extended features like enterprise GitHub features, we wouldn't be charged anyway.

10 hours ago, argumentum said:

Edit: Can't find a way to recover my argumentum GitHub account ( that should be mine but, can't remember a thing ) so am going with another one 🤷‍♂️

I sent you, your "new" account, a GitHub invitation 🤝 .

Best regards
Sven

[SOLVE-SMART]

FYI folks 😁 : 

I will definitely start with GitHub.

Compared to other languages, only a few AutoIt developers are active outside the AutoIt forums. As far as I know, most of them have profiles on GitHub. Even if I were to switch to Codeberg, I would still be asking the few people to migrate with me or use a second Git repository hosting platform, which I don't consider practical. Therefore, thank you for the ideas and suggestions regarding alternatives to GitHub, but for now, I'll stick with it.

Additionally, if we decide to switch to Jon's GitHub Organization (which would be more official), we would still use GitHub because I don't think he would move his organization.

Whether we migrate together later remains to be seen. I'm open to changes, but I want to make it as convenient as possible for most people so that something actually happens within the community.

Best regards
Sven