<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div><font face="monospace" size="3">Hi <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Trevor Vaughan,</span></font></div><div><font face="monospace" size="3"><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><b><br></b></span></font></div><div>Github is probably one of the most commonly used SCM for open-source projects. Though Github itself isn't opensource, it doesn't affect PKI as opensource project. We are not tied to github in anyway and it's just a platform that we decided to be the best to use at the current moment. </div><div><br></div><div>However, we do have gitlab repo (mirrored) already: <a href="https://gitlab.com/dogtagpki/pki/">https://gitlab.com/dogtagpki/pki/</a> . This repo is setup as pull mirroring.</div><div><br></div><div>Regards,</div><div>Dinesh</div><div><font face="monospace" size="3"></font><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br></span></div><div>On Fri, 2018-09-07 at 12:13 -0400, Trevor Vaughan wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="ltr"><div>Interesting, is there any insight on why you decided to go with a closed source platform instead of a FOSS one, like GitLab?</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Sep 7, 2018 at 12:09 PM Dinesh Prasanth Moluguwan Krishnamoorthy <<a href="mailto:dmoluguw@redhat.com">dmoluguw@redhat.com</a>> wrote:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div style="text-align:left;direction:ltr"><div>Hello PKI developers,</div><div><br></div><div>First, I would like to thank everyone for your contributions to the PKI project. As a PKI team, we strive our best to keep the project clean, tidy and functional. Implementing CI and gerrithub (for code review) were some of the steps taken to keep the patch submission easy & clean. A bot (hosted on jenkins) was created to post comments to the patch you submitted on Gerrithub.</div><div><br></div><div>However, we <b>decided to decommision <u>Gerrithub and Jenkins</u> as of 09/21/2018 (Friday) </b>and move to <b>Github Pull Requests. </b> Jenkins will be shutdown on 09/21/2018 and you'll not be receiving comments (or required acks) to your submitted patches.</div><div><br></div><div>The primary reasons for the decommission are:</div><div>* Easier to track issues and commits since our upstream project is hosted on Github</div><div>* Easier to review changes </div><div>* Reliable CI results on single patch with multiple commits</div><div>* The extra effort to maintain these infrastructures</div><div><br></div><div>You can read more about gerrit vs github PR here: <a href="http://www.dogtagpki.org/wiki/Gerrit_vs_GitHub_Pull_Request" target="_blank">http://www.dogtagpki.org/wiki/Gerrit_vs_GitHub_Pull_Request</a></div><div><br></div><div>It takes a few steps to submit your patch as a PR. The step-by-step instructions to submit patches via Github Pull Request is available here: <a href="http://www.dogtagpki.org/wiki/GitHub_Pull_Request" target="_blank">http://www.dogtagpki.org/wiki/GitHub_Pull_Request</a></div><div><br></div><div>If you have any concerns with this decommission, please feel free to reach out.</div><div><br></div><div>Regards,</div><div>Dinesh</div><div><br></div><div><br></div> </div> _______________________________________________<br> Pki-devel mailing list<br> <a href="mailto:Pki-devel@redhat.com" target="_blank">Pki-devel@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/pki-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pki-devel</a></blockquote></div><br clear="all"><br></blockquote></body></html>