Github start

[d.healey]

@Robert-Puza For musicians you need to provide a VST3 plugin for each operating system (and an AU on MacOS).

MacOS is a bit tricky because you'll also need to codesign and notarize the plugin and this requires an Apple developer account which you need to pay for.

@Robert-Puza said in Github start:

but theoretically now anyone can make a tagged release? please someone do it if it's not a big job

Only people with permission on your repo can do it - but you should do it because it's your project and you'll need to do it every time you make a new version.

Here's how mine look for Rhapsody - https://codeberg.org/LibreWave/Rhapsody/releases

[Robert Puza]

@d-healey Ok. Thank you

[Robert Puza]

@d-healey and here is the limit i have to create a GPL3 business model to be able to pay the git manager ..hub etc.

[d.healey]

@Robert-Puza said in Github start:

i have to create a GPL3 business model to be able to pay the git manager ..hub etc.

What are you talking about?

[Robert Puza]

@d-healey that it's not me who should manage the git and hub theme in my creation, but a person for whom it's a normal routine.

[d.healey]

@Robert-Puza Definitely your job, if you want to be a developer you have to learn to do the things developers do. It's part of the adventure. Of course if you don't want to be a developer then you need to find a collaborator.

[Robert Puza]

@d-healey ok. Thank you

[Robert Puza]

@d-healey is there a problem that everything is in master and not in mein Branch? I work with Sourcetree

[d.healey]

@Robert-Puza No there's no problem. The branch feature is used to help you work on multiple versions of your code at once without them interfering with each other, and then you can merge them all back into the master branch. But for a smaller project with a single developer you can just work on the master all the time and don't worry about branches.

[Robert Puza]

@d-healey ok