<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 15, 2019 at 9:14 AM Martin Landa <<a href="mailto:landa.martin@gmail.com">landa.martin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
st 15. 5. 2019 v 9:51 odesílatel Martin Landa <<a href="mailto:landa.martin@gmail.com" target="_blank">landa.martin@gmail.com</a>> napsal:<br>
> Something strange happen with svn repo after r74441. I will publish<br>
> testing repo for public review hopefully today.<br>
<br>
OK, finally a new fresh grass repo preview available for review (last<br>
processed commit 74475).<br>
<br>
Please compare git content [1], branches [2] and tags [3] with svn.<br>
Please review logs reporting changed message [4] and unchanged<br>
messages [5]. </blockquote><div><br></div><div>I was also looking at the list of contributors [6]. I know this was discussed, but now I'm not really sure what to expect there.<br></div><div><br></div><div>[6] <a href="https://github.com/grass-svn2git/grass/graphs/contributors">https://github.com/grass-svn2git/grass/graphs/contributors</a><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">If no problems appears this will be the last<br>
preview before REAL migration.<br></blockquote><div><br></div><div>When comparing the content of the repositories, I see the difference in $Date$ which of course has the whole system related to it. What we are doing with that?</div><div><br></div><div>Another thing is the need for new contributing guidelines. Git is not Subversion and committing to master won't work (please, let me know if you want me to show some examples). What other OSGeo projects are doing is that contributing guidelines say that you should do pull request. It seems that this is often preferred way even for core developers. From what I gathered from a small sample of people at OSGeo sprint, the core devs don't go though fork, but they do go through a branch. In GitHub, we can set "Require pull request reviews before merging" and "Include administrators" for the master branch to enforce that. I think we should do it at least at the beginning.</div><div><br></div><div>Vaclav<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
[1] <a href="https://github.com/grass-svn2git/grass" rel="noreferrer" target="_blank">https://github.com/grass-svn2git/grass</a><br>
[2] <a href="https://github.com/grass-svn2git/grass" rel="noreferrer" target="_blank">https://github.com/grass-svn2git/grass</a><br>
[3] <a href="https://github.com/grass-svn2git/grass/releases" rel="noreferrer" target="_blank">https://github.com/grass-svn2git/grass/releases</a><br>
[4] <a href="http://geo102.fsv.cvut.cz/~landa/tmp/log_grass_touched.txt" rel="noreferrer" target="_blank">http://geo102.fsv.cvut.cz/~landa/tmp/log_grass_touched.txt</a><br>
[5] <a href="http://geo102.fsv.cvut.cz/~landa/tmp/log_grass_untouched.txt" rel="noreferrer" target="_blank">http://geo102.fsv.cvut.cz/~landa/tmp/log_grass_untouched.txt</a><br>
<br>
-- <br>
Martin Landa<br>
<a href="http://geo.fsv.cvut.cz/gwiki/Landa" rel="noreferrer" target="_blank">http://geo.fsv.cvut.cz/gwiki/Landa</a><br>
<a href="http://gismentors.cz/mentors/landa" rel="noreferrer" target="_blank">http://gismentors.cz/mentors/landa</a><br>
_______________________________________________<br>
grass-dev mailing list<br>
<a href="mailto:grass-dev@lists.osgeo.org" target="_blank">grass-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/grass-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/grass-dev</a></blockquote></div></div></div></div></div></div>