<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 11, 2014 at 10:53 PM, Vaclav Petras <span dir="ltr"><<a href="mailto:wenzeslaus@gmail.com" target="_blank">wenzeslaus@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Wed, Jun 11, 2014 at 1:41 PM, Martin Landa <span dir="ltr"><<a href="mailto:landa.martin@gmail.com" target="_blank">landa.martin@gmail.com</a>></span> wrote:<br>
<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>
2014-06-10 15:26 GMT+02:00 Vaclav Petras <<a href="mailto:wenzeslaus@gmail.com" target="_blank">wenzeslaus@gmail.com</a>>:<br>
<div>>>> when updating SUBMITTING files we need to touch all the files in all<br>
>>> the branches. I would suggest to move this files to Trac wiki. What do<br>
>>> you think?<br>
>><br>
>><br>
> Yes, see<br>
><br>
> <a href="http://trac.osgeo.org/grass/ticket/2103" target="_blank">http://trac.osgeo.org/grass/ticket/2103</a> Make SUBMITTING files more<br>
> accessible<br>
><br>
> Putting them to Trac seems the most easy think (comparing to creating HTML,<br>
> putting them to Doxygen, etc.).<br>
<br>
</div>I started with SUBMITTING file [1]. Any review is welcome. The process<br>
of transferring plain files to Trac wiki is quite time consuming, so I<br>
will appreciate if anyone helps with other submitting files (just let<br>
us know about that).<br>
<br></blockquote></div></div><div>I'll now work on:<br><a href="http://trac.osgeo.org/grass/wiki/Submitting/Python" target="_blank">http://trac.osgeo.org/grass/wiki/Submitting/Python</a><br><a href="http://trac.osgeo.org/grass/wiki/Submitting/wxGUI" target="_blank">http://trac.osgeo.org/grass/wiki/Submitting/wxGUI</a><br>
<br></div><div>I think that we should avoid duplication between C, Python and wxGUI. There is a lot of general notes about SVN etc. One thing is maintenance but in this case what more important is a developer reading through these files and reading something about svn properties over and over again. So I would vote for creation of<br>
<br><a href="http://trac.osgeo.org/grass/wiki/Submitting/General" target="_blank">http://trac.osgeo.org/grass/wiki/Submitting/General</a><br><br></div><div>It can be also just in <a href="http://trac.osgeo.org/grass/wiki/Submitting/" target="_blank">http://trac.osgeo.org/grass/wiki/Submitting/</a> but .../General seems a little bit better for me.<br>
</div><div><br></div></div></div></div></blockquote><div><br>I have few notes:<br><br></div><div>svn properties should be solved by svn propset script [1]. The submitting files can then just contain instructions how to run it.<br>
<br></div><div>I think that the formatting should be more in the way of a standard page with sections and subsections rather than the list. I did this for the Python and wxGUI pages. It is of course harder to write because you have to think what should be where and which sections to have but it is more readable and we don't need the numbered paragraphs/rules.<br>
</div><div><br>[1] <a href="http://trac.osgeo.org/grass/browser/grass-addons/tools/module_svn_propset.sh">http://trac.osgeo.org/grass/browser/grass-addons/tools/module_svn_propset.sh</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">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div>Thanks Martin for starting this,<br></div><div>Vaclav<br></div><div class=""><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Thanks, Martin<br>
<br>
[1] <a href="http://trac.osgeo.org/grass/wiki/Submitting/C" target="_blank">http://trac.osgeo.org/grass/wiki/Submitting/C</a><br>
</blockquote></div></div><br></div></div>
</blockquote></div><br></div></div>