I guess the main reason I did the pull request was because I don't have commit access to the repository, and being a newbie to this project, didn't see any other way of doing what Matt had requested :-)
I'm by no means experienced with using Github. I just did what I thought is the right way to make a contribution to an open source software project like this. If I did this the wrong way, please let me know. And, while it does take a bit more work on my part to start making contributions (I had to fork the repository), I now have a way to make tracked revisions to my own version of the library that Matt might (or might not) choose to accept. Plus, another new fork of jallib makes jallib look more popular, which is always a good thing ;-). Given that using git and Github have become a defacto standard of collaboration in open source software, it seems reasonable that jallib should follow the same practices of most other software projects if it wants to stay relevant and encourage other experienced software developers to contribute. But I'm willing to defer to what everyone else thinks is best--especially Matt, since he's ultimately the one maintaining the project. -Jim On June 19, 2016 2:55:27 AM CDT, Rob Hamerling <[email protected]> wrote: > > >On 06/18/2016 10:59 PM, Jim Gregory wrote: >> I just created a pull request that includes the binary of the >compiler (v 2.4q5) for the Raspberry Pi and similar single board >computers, plus instructions on how to compile the compiler for it and >other ARM-based boards. >> >A pull request may be the formal way to contribute, but this seems to >me >much more complicated than necessary. And (as far as I understand the >process) it requires time and effort of someone else to merge the >additions into the repository. In Jallib all contributors were always >'peers', no hierarchy. Why not take the responsibility and simply add >the files to the repository like we have done for so many years? >Nothing >happens to the packaging as long as these files are not added to >TORELEASE, and since you have most likely tested your contributions you > >may as well add these to TORELEASE. > >Another disadvantage of this 'indirect' way of contributing is that the > >additions don't show up when browsing Github. At least I cannot find >'m, >but that may be caused by my short-sightedness ;-) > >Regards, Rob. > >-- >*Rob H*amerling - http://www.robh.nl > >-- >You received this message because you are subscribed to the Google >Groups "jallib" group. >To unsubscribe from this group and stop receiving emails from it, send >an email to [email protected]. >To post to this group, send email to [email protected]. >Visit this group at https://groups.google.com/group/jallib. >For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/jallib. For more options, visit https://groups.google.com/d/optout.
