Hi,
no specific info on the exact project, but generally you could open a issue ticket there and ask your very question. Each project may have its own rules.

But most commonly it works this way:
- you clone the repo at github (so its public)
- you make a new branch and do your stuff
- you then open a pull request against the upstream repo
- someone there inspects it and if it is accepted, will merge
- done

Am 19.12.2021 um 00:43 schrieb Bruce Mutton <bruce@tomo.co.nz>:



Not directly a Therion question.

I’ve been loosely following the progress of https://github.com/iccaving/migovec-survey-data a couple of years, but only recently started migrating some projects of my own to git.

 

So thought I’d dispense with just admiring the outputs and fork the migovec repository to do a deep dive learn from the apparent masters…

The REDME.md is exemplary, but the section on ‘How to contribute’ seems to be missing a most important thing – how do contributors interact with other contributors and the repository?  The lack of issues and forks that similar sized GitHub projects have suggests I’m missing something obvious.  I know Therion pretty well, passible on version control but only just cutting my teeth on git and GitHub.

 

I found a simple problem in some thconfigs that causes Therion to crash and exit, and located the cause in the history.  I could potentially fix it, make a pull request, but as I have only studied the migovec structure for literally 10 minutes, any ‘fix’ I work on will take me a while and be bound to be error prone.  Better for me just to point out the problem.

 

Anyone here know how the iccaving migovec Therion team communicates or would one of them on this list be able to PM me?

 

Bruce

_______________________________________________
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion