<html><body><p style="line-height:normal;margin-bottom:0pt">Hello Community,</p><p style="line-height:normal;margin-bottom:0pt"><br></p>
<p>I am sending my report for Week 7 (July 13-July 19). 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>.<br></p><p><br></p><p>
<strong>1) What did I complete this week?</strong><br>
</p>
<p>
I finalized the PR Add multiple GRASS databases (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/761"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/pull/761</a>, <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/741"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/741</a>).
I also made several smaller PRs related to several issues. As we would like distinguish different layers according to lock and ownership in
future, it was necessary to distinguish the label and name of nodes (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/783"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/pull/783</a>, <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/780"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/780</a>). I also changed the order of Layer Manager tabs and a label "Layers" to "Display" (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/802"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/pull/802</a>, <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/799"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/799</a>).
Simultaneously, I am working on bigger PRs related to new actions in
Data Catalog. The first one adds Create New Location and Download
Location actions to the database node in Data tab (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/790"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/pull/790</a>, <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/747"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/747</a>). The second one allows the Delete action on multiple selected mapsets (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/795"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/pull/795</a>, <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/791"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/791</a>). <br></p><p><br></p>
<p>
<strong>2) What am I going to achieve next week?</strong><br>
</p>
<p>
As the paradigm has quite changed after the community video call on July
15 (startup screen will be probably removed), I will go ahead and add
more functions and actions to Data Catalog which is now becoming the center point of the whole management in GRASS.
First I am gonna focus on Adding new icons to the data catalog for several actions whose list is still broadening. This is related to the
Issue <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/800"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/800</a>.
There are also other issues related to the Data Catalog I am gonna address:
</p>
<ul><li>Add functionality to load only data from the current mapset in the Data tree (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/issues/749"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/issues/749</a>)
</li><li>Startup screen: Distinguish mapsets by ownership and lock (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>)
</li><li>Check for gislock and other issues when deleting/renaming/editing mapset and location in catalog (<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></ul><p>
<strong>3) Is there any blocking issue?</strong><br>
No, it is not.
</p><p><br></p><p>Regards,</p>Linda Kladivova</body></html>