<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">From the discussion we had so far on this thread and on IRC <div class="">Is clear to me we need a *official revision procedure* to have the work done for the GSoC integrated into the live.</div><div class=""><br class=""></div><div class="">I agreed in “hiding” the jupyter notebook, and so the GSoC work, from this release of the Live,</div><div class="">in favor of a transparent public commitment to review the efforts done.<div class=""><div class=""><br class=""></div><div class="">IMHO the spreadsheet approach we use for project review doesn’t apply very well in this context.</div><div class="">To facilitate keeping track of the review and facilitate potential new contributors, </div><div class="">I propose to open a motion in accepting the use of github checklist+issue tracker to keep track of the review process.</div><div class=""><br class=""></div><div class="">I started this page, which should help in making this possible:</div><div class=""><br class=""></div><div class=""><a href="https://github.com/epifanio/OSGeoLive-Notebooks/wiki/Notebook-review" class="">https://github.com/epifanio/OSGeoLive-Notebooks/wiki/Notebook-review</a> </div><div class=""><br class=""></div><div class="">We can improve it making it more clear, but should give you the idea.</div><div class=""><br class=""></div><div class="">This motion is to validate the work done during GSoC, which is:</div><div class=""><br class=""></div><div class="">“Development of educational material in the form of interactive notebooks”</div><div class=""><br class=""></div><div class="">and to help the coordination between potential contributors for this specific topic.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Here it is my +1</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Massimo.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 10, 2016, at 4:09 AM, Angelos Tzotsos <<a href="mailto:gcpp.kalxas@gmail.com" class="">gcpp.kalxas@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<div class="moz-cite-prefix">Hi Cameron,<br class="">
<br class="">
In order to check the latest status of the notebooks try this from
a terminal within the running iso:<br class="">
<br class="">
$ cd /home/user/jupyter/notebooks<br class="">
$ git pull origin<br class="">
<br class="">
Then start the notebooks and check again.<br class="">
There have been many changes from Massimo which should be taken
into account.<br class="">
<br class="">
Best,<br class="">
Angelos<br class="">
<br class="">
<br class="">
On 03/10/2016 12:59 AM, Cameron Shorter wrote:<br class="">
</div>
<blockquote cite="mid:56E0AABB.3050506@gmail.com" type="cite" class="">-1
from me for including all python notebooks on the upcoming
OSGeo-Live 9.5 release in a few days. I don't think we can make it
ready in time.
<br class="">
<br class="">
This is based on my preliminary review of the gsoc iso:
<br class="">
<a class="moz-txt-link-freetext" href="http://osprey.ucdavis.edu/downloads/osgeo/gisvm/gisvm/9.5nightly/osgeo-live-nightly-gsoc-amd64-c83a060.iso">http://osprey.ucdavis.edu/downloads/osgeo/gisvm/gisvm/9.5nightly/osgeo-live-nightly-gsoc-amd64-c83a060.iso</a>
<br class="">
<br class="">
I haven't done a comprehensive review, but have reviewed enough to
feel the initial user experience when looking at notebooks is
close, but is yet to meet our OSGeo-Live presentation standards.
<br class="">
<br class="">
My comments so far:
<br class="">
<br class="">
1. Quickstart review comments haven't been addressed yet, although
hopefully Massimo should have that complete soon.
<br class="">
<br class="">
2. Structure of notebook docs directory should be by project,
rather than singled out as a GSoC directory, then by project. Long
term we want GSoC content to be part of the core OSGeo-Live
offering.
<br class="">
<br class="">
3. We are missing an obvious Table of Contents.
<br class="">
<br class="">
4. I've randomly picked iris_basics.ipynb, running step 2, I get a
warning about a library being deprecated. (It still works, but
this is the sort of thing that should be cleaned up before
presenting to a new user).
<br class="">
<br class="">
5. There should be an introductory notebook which starts with
"Press the RUN CELL button to see the output of [In] cells".
<br class="">
<br class="">
6.1 I've found a number of spelling and grammar errors in the
first GSoC notebook I reviewed. Nothing major, but they should be
identified and cleaned up all the same.
<br class="">
For example, this is the first paragraph of the GDAL/OGR
Quickstart (which is the first Docbook I looked at):
<br class="">
<br class="">
/"The first Notebook is dedicared [SPELLING] to the use of the
Geospatial Data Abstraction Library GDAL [USE BRACES AROUND FIRST
USE OF CAPITALS] from the bash command line. GDAL is a powerful
translator library for raster and vector geospatial data formats
[INSERT FULL STOP] it presents a single raster abstract data model
and vector abstract data model to the calling application for all
supported formats."/
<br class="">
<br class="">
6.2 In the same notebook, I found:
<br class="">
/"#unfinished - need to add ogr2ogr features yet, I'm considering
to split this notebook in 2 parts (one for gdal and one for
ogr2ogr) i'll study the gdal tutorial released recently"/
<br class="">
<br class="">
Massimo notes that he is fixing this, but my point is that I'm
assuming that if reviewed, similar issues would be found in other
notebooks.
<br class="">
<br class="">
7. The term "IPython" and "Jupyter" is used interchangeably, which
would be confusing for a new user, and I'd be interested to
understand if is technically incorrect?
<br class="">
<br class="">
8. Quantity of material to review and short time period. We have
days left before the our final release candidate is due, and
multiple notebooks (say 20+ ?) which I suggest need review to get
to same level of review as Project Overviews and Quickstarts.
<br class="">
<br class="">
9. Also on quantity of material, we are introducing a maintenance
load for future OSGeo-Live releases, and we are as yet to build up
a community of volunteers willing to maintain these notebooks.
Massimo and Brian have been doing a great job creating these
notebooks, but are already under time pressure to update for this
release, let alone future releases. I think we need to reach out
to all projects with the offer of:
<br class="">
"A notebook has been created for your project. If you are prepared
to review it now, and commit to verifying it is still valid before
each OSGeo-Live release, then we will include the notebook on
OSGeo-Live."
<br class="">
<br class="">
--
<br class="">
So my recommendation is to either:
<br class="">
A. Include Notebooks on next OSGeo-Live 9.5, but remove reference
to it from main docs. (My preference at this point)
<br class="">
<br class="">
B. Include ONE Jupyter notebook example which can be found from
main docs, which we make sure is well reviewed. All the remainder
of Notebooks to be hidden. (This will likely be a messy solution,
as we'd probably need to move directories around so they are hard
to find for a new user).
<br class="">
<br class="">
On 9/03/2016 11:44 pm, massimo di stefano wrote:
<br class="">
<blockquote type="cite" class="">To All,
<br class="">
<br class="">
during the last 2 years I worked in having the python software
ecosystem included in the OSGeo-Live.
<br class="">
The PR proposed below [1] is a first step towards the official
inclusion of this work into the project.
<br class="">
<br class="">
As you may have noticed from previous e-email [2] there isn’t a
clear agreement on the decision to take.
<br class="">
We had an IRC discussion (logs [3]) with an initial motion to
merge the notebook PR.
<br class="">
<br class="">
I would like to have a voting started here on the mailing.
<br class="">
this is mine:
<br class="">
<br class="">
+1
<br class="">
<br class="">
<br class="">
Thanks,
<br class="">
Massimo.
<br class="">
<br class="">
<br class="">
===
<br class="">
<br class="">
[1] <a class="moz-txt-link-freetext" href="https://github.com/OSGeo/OSGeoLive-Notebooks/pull/5">https://github.com/OSGeo/OSGeoLive-Notebooks/pull/5</a>
<br class="">
[2]
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/pipermail/live-demo/2016-March/011010.html">http://lists.osgeo.org/pipermail/live-demo/2016-March/011010.html</a>
<br class="">
[3]
<a class="moz-txt-link-freetext" href="http://irclogs.geoapt.com/osgeolive/%23osgeolive.2016-03-07.log">http://irclogs.geoapt.com/osgeolive/%23osgeolive.2016-03-07.log</a>
<a class="moz-txt-link-rfc2396E" href="http://irclogs.geoapt.com/osgeolive/#osgeolive.2016-03-07.log"><http://irclogs.geoapt.com/osgeolive/#osgeolive.2016-03-07.log></a>
<br class="">
<br class="">
<br class="">
_______________________________________________
<br class="">
Live-demo mailing list
<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Live-demo@lists.osgeo.org">Live-demo@lists.osgeo.org</a>
<br class="">
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/live-demo">http://lists.osgeo.org/mailman/listinfo/live-demo</a>
<br class="">
<a class="moz-txt-link-freetext" href="http://live.osgeo.org/">http://live.osgeo.org</a>
<br class="">
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/Live_GIS_Disc">http://wiki.osgeo.org/wiki/Live_GIS_Disc</a>
<br class="">
</blockquote>
<br class="">
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre wrap="" class="">_______________________________________________
Live-demo mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Live-demo@lists.osgeo.org">Live-demo@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/live-demo">http://lists.osgeo.org/mailman/listinfo/live-demo</a>
<a class="moz-txt-link-freetext" href="http://live.osgeo.org/">http://live.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/Live_GIS_Disc">http://wiki.osgeo.org/wiki/Live_GIS_Disc</a></pre>
</blockquote>
<br class="">
<br class="">
<pre class="moz-signature" cols="72">--
Angelos Tzotsos, PhD
OSGeo Charter Member
<a class="moz-txt-link-freetext" href="http://users.ntua.gr/tzotsos">http://users.ntua.gr/tzotsos</a></pre>
</div>
_______________________________________________<br class="">Live-demo mailing list<br class=""><a href="mailto:Live-demo@lists.osgeo.org" class="">Live-demo@lists.osgeo.org</a><br class="">http://lists.osgeo.org/mailman/listinfo/live-demo<br class="">http://live.osgeo.org<br class="">http://wiki.osgeo.org/wiki/Live_GIS_Disc</div></blockquote></div><br class=""></div></div></div></body></html>