Non-Forum Problems: Why not use a code repository

[bluedevil]

Hello friends.

I know we still cannot solve the administrative and financial problems of our beloved forum. But I want to suggest an important thing.

Dear friends in my opinion we should "also" open a MASM-SDK organization on github(or gitlab). Then we should put MASM32 SDK and MASM64 SDK to there. We should license them if they do not have licensed by hutch--. So that we can easily improve, bug fix, typo fix and release new versions of SDK's. People can easily contribute and issue problems. We can hold our sdk's more updated. And we don't have to be afraid that they will disappear suddenly.

Until now, hutch-- himself tracked issues, fixed typos/bugs and released new versions. From now on we should do this on Github(or gitlab)

After SDK's, we should put important or community driven projects and code sniplets(maybe?) to our our code repositories. We can put member projects(You know; some member projects are full-fledged projects).

P.S. I am very aware that most (total?) of the macros for masm64-sdk has written by vasily. We have to ask him first. But I do not have direct communication with him.

BTW folks, those are just thought. I love assembly programming. And I really do not want to lost anything on this forum. I saw many forums and portals has gone in one night! Using a code repository solves many problems.

What do you think? I can't wait to hear your thoughts too.
Cya

[Greenhorn]

Good idea ! 

[HSE]

P.S. I am very aware that most (total?) of the macros for masm64-sdk has written by vasily. We have to ask him first. But I do not have direct communication with him.

Just part of macros were writed by Vasily. Curiously... those macros are in file Vasily.inc 

[bluedevil]

P.S. I am very aware that most (total?) of the macros for masm64-sdk has written by vasily. We have to ask him first. But I do not have direct communication with him.

Just part of macros were writed by Vasily. Curiously... those macros are in file Vasily.inc 

How can I reach Vasily? Or do I need to reach him If we agreed on publishing MASM SDK's on Github(lab)

[HSE]

What you CANNOT do with the MASM32 SDK.

1. The MASM32 SDK is not an item of trade or commerce. It cannot be either purchased or sold.
2. The MASM32 SDK cannot be re-licenced or made subordinate to any other form of licence.
3. None of its components or source code are redistributable.
4. You cannot use the MASM32 SDK to write software for Non-Microsoft Operating Systems.
5. You cannot use the MASM32 SDK to write any form of illegal software.
6. The SDK does not authorise the use of the Microsoft Trademark in your software or claims that your software is certified by Microsoft.

That means no GitHub for MASM32 SDK

[bluedevil]

3. None of its components or source code are redistributable.

So we cannot improve, develop, bugfix or typofix MASM64 SDK through a code repository right? Sooo, what can we do?

[HSE]

Sooo, what can we do?

So far, you can improve, develop, bugfix or typofix MASM64 SDK here.

[jj2007]

Sooo, what can we do?

So far, you can improve, develop, bugfix or typofix MASM64 SDK here.

Right. A code repository is an absolute overkill imho.

[bluedevil]

Sooo, what can we do?

So far, you can improve, develop, bugfix or typofix MASM64 SDK here.

I got it, thank you =)

[Mikl__]

bluedevil,
did you receive my e-letter?

[daydreamer]

Masm64 sdk,who should be in charge of continue develop it ?
Masm32 sdk has different coders contributed to examples
If anyone want to contribute with masm64 examples,who will decide if they get included in masm64 sdk ?
Group effort easier can produce more than a single coder
I hope for keep on develop it

[bluedevil]

bluedevil,
did you receive my e-letter?

Thank you @Mikl__ I've got it.

[jj2007]

Masm64 sdk,who should be in charge of continue develop it ?
Masm32 sdk has different coders contributed to examples
If anyone want to contribute with masm64 examples,who will decide if they get included in masm64 sdk ?
Group effort easier can produce more than a single coder
I hope for keep on develop it

The Masm32 SDK was indeed a joint effort, although Hutch contributed most of it, if I remember correctly.
Same applies to MasmBasic: many of its routines have been thoroughly tested in The Laboratory.
(There are other packages like GoAsm, ObjAsm that I don't know well - I hope their authors see this and comment.)

So in these two cases there was one maintainer and several contributors, loosely organised. That worked fine, and there was never a need for a GitHub-style repository.

Now the Masm64 SDK was exclusively Hutch' work (building on some macros by Vasily - but that was a minor part).
The situation is a lot different, also because there were three different approaches to Masm64: Hutch, UAsm and my dual assembly.

Masm 64-bit coding was, and is, a bit messy. Personally, I don't have stakes in 64-bit Assembly, as I am so old that I will not see the end of 32-bit coding. Who wants to take the lead? Mikl, what about you?

As to "Group effort easier", dear daydreamer, I would be happy to see any new code in this forum...

[Caché GB]

I don't have stakes in 64-bit Assembly, as I am so old that I will not see the end of 32-bit coding.

Are you sure about that JJ.

Intel Wants to KILL 32-bit Mode in its CPUs - X86-S Explained
https://www.youtube.com/watch?v=KSagW5gmPo4

https://www.intel.com/content/www/us/en/developer/articles/technical/envisioning-future-simplified-architecture.html

[Mikl__]

Ciao, Jochen!
Of course, I would like to make every effort to create a masm64 package, but the project leader from me is so-so, I'm not even a professional programmer, I'm just an engineer, assembler is just my hobby. I'm happy to join the group work on the project, whatever that means...