<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">Hi,</div><div dir="ltr">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.</div><div dir="ltr"><br></div><div dir="ltr">But most commonly it works this way:</div><div dir="ltr">- you clone the repo at github (so its public)</div><div dir="ltr">- you make a new branch and do your stuff</div><div dir="ltr">- you then open a pull request against the upstream repo</div><div dir="ltr">- someone there inspects it and if it is accepted, will merge</div><div dir="ltr">- done</div><div dir="ltr"><br><blockquote type="cite">Am 19.12.2021 um 00:43 schrieb Bruce Mutton <bruce@tomo.co.nz>:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--><div class="WordSection1"><p class="MsoNormal">Not directly a Therion question.<o:p></o:p></p><p class="MsoNormal">I’ve been loosely following the progress of <a href="https://github.com/iccaving/migovec-survey-data">https://github.com/iccaving/migovec-survey-data</a> a couple of years, but only recently started migrating some projects of my own to git.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">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…<o:p></o:p></p><p class="MsoNormal">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.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">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.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Anyone here know how the iccaving migovec Therion team communicates or would one of them on this list be able to PM me?<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Bruce<o:p></o:p></p></div><span>_______________________________________________</span><br><span>Therion mailing list</span><br><span>Therion@speleo.sk</span><br><span>https://mailman.speleo.sk/listinfo/therion</span><br></div></blockquote></body></html>