<html><body><div><p style="line-height:normal;margin-bottom:0pt">
Hello Community,</p><p style="line-height:normal;margin-bottom:0pt"><br></p><div>
I am sending my report for Week 10 (August 3-August 9). The report can also be found in the project wiki: <a href="https://trac.osgeo.org/grass/wiki/GSoC/2020/StartupWindow" title="https://trac.osgeo.org/grass/wiki/GSoC/2020/StartupWindow" rel="noopener">https://trac.osgeo.org/…dow</a>.</div></div><div><br></div>
<p>
<strong>1) What did I complete this week?</strong><br>
First of all, I finished two PRs related to two modes "Allow edits
outside of the current mapset" and "Restrict edits to the current
mapset". The first PR deals with the implementation of these
restrictions (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/843"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/843</a>, <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/848"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/pull/848</a>).
The motion is that when Allow editing mode is ON we are allowed to
rename and delete outside of the current mapset, if OFF no edits are
restricted to the current mapset. The second PR suggested the new symbol
since previous one was very misleading (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/844"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/844</a>, <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/870"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/pull/870</a>).
Secondly, I implemented storing list of databases in settings (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/842"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/842</a>, <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/858"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/pull/858</a>).
Thirdly, I enabled the option of deleting multiple locations (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/874"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/874</a>, <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/875"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/pull/875</a>). <br></p><p><br></p>
<p>
Currently, there are 3 other PRs that are in the process:
</p>
<ul><li>Start in a demo/startup location (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/862"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/862</a>, <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/868"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/pull/868</a>)
</li></ul><p>
This is almost done. However, there will be another PR opened that is
gonna treat the initial state of GRASS more systematically.
</p>
<ul><li>Distinguish mapsets by ownership and lock in Data tab (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/714"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/714</a>, <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/849"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/pull/849</a>)
</li></ul><p>
Almost done, just some smaller cosmetic changes. In this PR I also
established the mapset key "current". Therefore, not only the locked
mapset and the mapset owned by the different owner than the current
user, but also the current mapset is distinguished by label.
</p>
<ul><li>Data Catalog: Double click on map from different locations fails - BUG (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/884"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/884</a>, <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/886"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/pull/886</a>)
</li></ul><p>
The initial suggestion was to inform the user that the map is in a
different location and ask if they want to switch to this mapset.
However, there are probably more ways in the game how to solve this
issue (e.g. not allowing to display those maps at all?...) Should be
discussed. <br></p><p><br></p>
<p>
<strong>2) What am I going to achieve for next week?</strong><br>
</p>
<p>
I am gonna end up those above-mentioned PRs.
Then I will continue with checking for gislock and ownership when
performing operations with mapsets and locations. Furthermore, I am
gonna reflect changes, I made in Data Catalog, in GUI.
</p>
<ul><li>Check for gislock and other issues when deleting/renaming/editing mapset and location in catalog (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/801"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/801</a>)
</li><li>Reflect changes done from Data Catalog in GUI and vice versa (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/885"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/885</a>)
<ul><li>when map is renamed in data catalog while it is displayed, the layer needs to be changed otherwise rendering fails
</li><li>when map is moved elsewhere in data catalog while it is displayed
</li><li>new map is created (this item needs to be expanded, there are multiple ways a new map is created)
</li><li>current mapset/location is changed from menu
</li><li>etc.
</li></ul></li></ul><p>
<strong>3) Is there any blocking issue?</strong><br>
No, it is not. <br></p><p><br></p><p>Any suggestions are welcome.</p><p>Regards,</p>Linda Kladivova</body></html>