V1.1

.github/workflows/ci_check.yml

@@ -2,10 +2,14 @@ name: ci_check
 
 on:
   push:
-    branches: "main"
+    branches:
+      - latest
+      - stable
 
   pull_request:
-    branches: "main"
+    branches:
+      - latest
+      - stable
 
 jobs:
   build:
@@ -15,7 +19,7 @@ jobs:
       fail-fast: false
 
       matrix:
-        os: [ubuntu-latest, windows-latest]
+        os: [ubuntu-latest, windows-latest, macos-latest]
         build_type: [Release]
         c_compiler: [gcc, clang, cl]
         include:
@@ -28,6 +32,9 @@ jobs:
           - os: ubuntu-latest
             c_compiler: clang
             cpp_compiler: clang++
+          - os: macos-latest
+            c_compiler: clang
+            cpp_compiler: clang++
         exclude:
           - os: windows-latest
             c_compiler: gcc
@@ -42,7 +49,7 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v4
         with:
-          go-version: '1.21'
+          go-version: '1.22'
 
       - name: Update Packages (Linux)
         if: startsWith(matrix.os, 'ubuntu')
@@ -57,3 +64,4 @@ jobs:
 
       - name: Make Ci_Check
         run: make ci_check
+

.github/workflows/format.yml

@@ -0,0 +1,36 @@
+name: Go Format Check
+
+on:
+  push:
+    branches:
+      - latest
+      - stable
+
+  pull_request:
+    branches:
+      - latest
+      - stable
+jobs:
+  go-fmt-check:
+    runs-on: ubuntu-latest
+
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v2
+
+    - name: Set up Go
+      uses: actions/setup-go@v3
+      with:
+        go-version: '1.22'
+
+    - name: Check Go format
+      run: |
+        files=$(gofmt -l .)
+        if [ -n "$files" ]; then
+        echo "Following files arent formatted:"
+          echo "$files"
+          exit 1
+        else
+          echo "Everything is formatted."
+        fi
+

.github/workflows/mkdocs.yml

@@ -2,10 +2,12 @@ name: MkDocs Deploy
 on:
   push:
     branches:
-      - master 
-      - main
+      - latest 
+      - stable
+
 permissions:
   contents: write
+
 jobs:
   deploy:
     runs-on: ubuntu-latest

.gitignore

@@ -13,3 +13,5 @@ CMakeFiles/
 .cmake
 Testing
 site
+
+internal/gl/opengl/old

CODE_OF_CONDUCT.md

@@ -0,0 +1,19 @@
+# Vuelto Code of Conduct
+
+Vuelto is built by developers, for developers. We are committed to fostering a welcoming and inclusive community. By participating in this project, you agree to the following principles:  
+
+1. **Respect Everyone**    
+Treat all contributors with kindness and respect. Discrimination, harassment, or offensive language is not tolerated.  
+
+2. **Collaborate Openly**    
+ Share ideas, feedback, and code in a constructive and respectful manner. Assume good intentions and work to resolve disagreements with empathy.  
+
+3. **Stay Professional**    
+ Keep discussions focused on the project. Avoid disruptive behavior, spamming, or derailing conversations.  
+
+4. **Be Inclusive**    
+ Make the community accessible to everyone, regardless of experience level, background, or identity.  
+
+Violations of this Code of Conduct may result in warnings, bans, or other actions as necessary. If you experience or witness any unacceptable behavior, please report it to the maintainers.  
+
+Together, let's build a community where creativity and collaboration thrive!

CONTRIBUTING.md

@@ -0,0 +1,58 @@
+# Contributing rules  
+We are happy and welcome if you want to contribute to Vuelto. But please consider a few details before continuing:
+
+1. Branch: Please when working on your fork, work in the dev branch, because we only will accept commits to the dev branch. It will later be released with the next version of Vuelto.  
+2. Explain: Please explain why this should be considered and merged. That will make our life easier.  
+3. Test: Please test your code before even opening a new pull request.  
+4. Documentation: Please, if you’re adding something new, like a feature, please document everything.  
+5. Format: Please, run `make format` for formatting of the code.
+
+Not following these rules  
+If we see a pull request that doesn't follow these rules, we will tell you that, and close the pull request.  
+We allow you to re-open a new pull request, but we expect you to have your code fixed.  
+So make sure that you followed [the rules](#contributing-rules)
+
+Some technologies we are using  
+- GLFW: We use this for the desktop windowing  
+- “syscall/js”: We use this to interact with the JS runtime  
+- glow: Generate OpenGL Go bindings  
+- CGo: Interface to use C with Go
+
+## How to setup the work environment
+
+If you want to contribute, you have to set up the work environment, so you can develop vuelto the right way.
+
+1. Install  the packages
+
+```bash
+go mod tidy  
+```
+
+2. Fork [the repository](https://github.com/vuelto-org/vuelto).
+
+3. Clone your forked github repository:
+
+```bash
+git clone https://github.com/your_username_/vuelto.git
+cd vuelto  
+```
+
+4. Change the branch to the dev branch to follow rule \#1:
+
+```bash
+git checkout dev  
+```
+
+## Pull Request
+
+If you're ready with your changes, then you must follow a few steps before pull requesting.
+
+1. Run `make` to format your code:
+
+```bash
+Make format  
+```
+
+Then make sure your pull request code works without erroring and you followed the [contribution rules](#contributing-rules)
+
+After all of this, you can create a pull request and one of our main organization members will look at it.