Jun 30, 17 / Leo 13, 01 07:57 UTC

Re: Open code on github or gitlab, and other steps toward transparency  

Hey, I think, it suits this topic:  "given enough eyeballs, all bugs are shallow" ))) Find more on wiki https://en.wikipedia.org/wiki/Linus%27s_Law. Folks, do you agree with this "law"?

Jul 2, 17 / Leo 15, 01 20:48 UTC

Quote: "Presenting the code to multiple developers with the purpose of reaching consensus about its acceptance is a simple form of software reviewing. Researchers and practitioners have repeatedly shown the effectiveness of various types of reviewing process in finding bugs and security issues,[3] and also that code reviews may be more efficient than testing"

Dec 20, 17 / Cap 18, 01 08:59 UTC

Also recommend you take a look at developers research "GitHub vs BitBucket vs GitLab" - https://www.cleveroad.com/blog/github-vs-bitbucket-vs-gitlab-developers-research I think you should read it to know more about these social repositories for open source code projects

Dec 29, 17 / Cap 27, 01 10:47 UTC

Thanks for sharing

I would like to add this article GitHub vs. Bitbucket vs. GitLab vs. Coding. Which to choose and why? https://artjoker.net/blog/github-vs-bitbucket-vs-gitlab-vs-coding/

Mar 23, 18 / Ari 26, 02 23:20 UTC

I think this article is much related to theme you are talking about: https://www.ukrsolution.com/PayPal-Invoice-Generator-Create-Invoices-From-Sales

Mar 25, 18 / Tau 00, 02 16:45 UTC

I know I'm coming late to the party here but I like the idea of using Github or other group coding site.  I believe that the more eyes we have on the code the better it will be.  After it is complete it can be checked by Asgardian coders then the site can be updated.  Think of the functions that could be coded in a short time, the bugs and normal options that could be fix.  It would be great for us all.