Changes between Version 5 and Version 6 of GSoC/2018/FullSupportPython3

Timestamp:

05/15/18 07:50:53 (7 years ago)

Author:

sanjeet

Comment:

Community bonding period activity report

GSoC/2018/FullSupportPython3

@@ -203 +203 @@
 }}}
 
+== Community Bonding Period Report ==
+During the Community Bonding Period I performed the following activities:
+
+'''Introduction to Community'''\\
+I wrote an introductory email to the SoC mailing list and grass-dev mailing list and gave a description about my project and shared my wiki page, public repository, and project proposal links.
+
+'''Create Wiki page'''\\
+I requested the write access to setup a project wiki page. Then, I created my wiki page detailing the project description, containing link to my GSoC application, a detailed timeline, link to my public repository where all my commits and progress can be followed.
+
+'''Set up code repository'''\\
+I have setup my code repository on github for tracking the applied changesets.
+
+'''Set up development environment'''\\
+I setup my development environment (Ubuntu 18.04) for two Python versions (Python 2.7.x and Python 3.6.x) for which I am using virtual environments. This was done because I need to make sure that when I update any code it should be compatible with both the versions.
+
+'''Add links to community wiki pages'''\\
+I added my project links to the OSGeo's Google Summer of Code 2018 Accepted students wiki page and trac wiki page: https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2018_Accepted and https://trac.osgeo.org/grass/wiki/GSoC.
+
+'''Discussion with community members and mentors about the design of the project'''\\
+I got in touch with my mentors to discuss the right approach to test the code and submit files. 
+
+'''Get familiar with the testing framework'''\\
+I followed the wiki page to get familiar with the testing framework(https://grasswiki.osgeo.org/wiki/GRASS_and_Python). I also followed the grass Python Scripting tutorials from this link:
+https://github.com/wenzeslaus/python-grass-addon
+
+'''Update current tests of the python script library, adjust them to work with Python3'''\\
+I updated the code in the python script library to make it work on Python3 and submitted the patch files for those. I used the standard North Carolina dataset that uses the basic version of the dataset. 
+(https://grass.osgeo.org/download/sample-data/)
+I have looked through the summary reports for the current tests of GRASS which is going to be useful when I will update tests for the libraries in the system. (http://fatra.cnr.ncsu.edu/grassgistests/summary_report/)
+
+'''Get familiar with the overall working of GRASS GIS and understand Python dependencies in the system'''\\
+I went through the GRASS wiki pages to get familiar with the working of the system (https://grass.osgeo.org/grass75/manuals/libpython/) and looked through the source code. Also, I found the code dependencies that I will be working with throughout the coding period.
+
+'''Read documentation'''\\
+I read some documentation related to GSoC guidelines about working throughout the GSoC period.
+I also read GRASS GIS Python library documentation: (https://grass.osgeo.org/grass75/manuals/libpython/)
+
+'''Practice fixing bugs'''\\
+I wrote a bug fix related to wxPython(https://trac.osgeo.org/grass/ticket/3510) during Pre-bonding period and submitted the patch file.
+
 == Weekly reports ==