<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">hello</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">i made a couple of pull requests to fix a typo - will focus on the
<a href="https://geonetwork-opensource.org/manuals/3.6.x/en/user-guide/harvesting/harvesting-geoportal.html?highlight=esri" class="OWAAutoLink" id="LPlnk111664" defang_previewremoved="true">
harvesting geoportal</a> page first (starting this thursday)</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">joe</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Jo Cook <jocook@astuntechnology.com><br>
<b>Sent:</b> 11 June 2019 09:19:46<br>
<b>To:</b> jonathan-lists@lightpear.com; Joseph Leach<br>
<b>Cc:</b> uk@lists.osgeo.org<br>
<b>Subject:</b> Re: [OSGeo-UK] Geonetwork users?</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi Jonathan and Joseph,<br>
<br>
Many thanks for your responses!<br>
<br>
It sounds as if an important first step would be to highlight the fact<br>
that you can bypass the whole "install git locally just to fix a typo"<br>
merry-go-round in a lot of cases because github allows you to do and<br>
edit and pull request within the browser. For information, if you do<br>
that in the geonetwork docs, I can approve the change :-)<br>
<br>
Joseph, would you be prepared to submit some issues at<br>
<a href="https://github.com/geonetwork/doc/issues">https://github.com/geonetwork/doc/issues</a> for larger changes?<br>
<br>
Jonathan- your point about licenses is interesting and it's not one<br>
I'd thought of with regards to documentation contributions. Is this<br>
something that you've come across, as opposed to code contributions? I<br>
can see some licensing "delicacies" in the case of training materials<br>
or similar, but if there are cases of licensing problems for<br>
straightforward documentation then that's something that should be<br>
explored in more detail.<br>
<br>
Thanks again!<br>
<br>
Jo<br>
<br>
On Fri, Jun 7, 2019 at 1:15 PM Jonathan Moules<br>
<jonathan-lists@lightpear.com> wrote:<br>
><br>
> Hi Jo,<br>
><br>
> Good stuff!<br>
><br>
> Personally I've always thought the need to do GIT pull-requests to<br>
> update documents was onerous.<br>
><br>
> Documenters are less likely to be familiar with git and version control,<br>
> and of course git is nothing if not unintuitive (there's a reason many<br>
> of the highest scored and most viewed stackoverflow questions are git<br>
> related). If someone's a serious documenter then the considerable time<br>
> required to get familiar with and install all of the tooling is<br>
> burdensome but do-able. However if someone just spots a few minor<br>
> things, they're unlikely to make the effort.<br>
><br>
> For my part this certainly applies to me - my version control system of<br>
> choice isn't git so I don't have it installed and I'm not interested in<br>
> getting it, going through the checkout dance, etc, just to correct a few<br>
> typos.<br>
><br>
> Fortunately this is already a solved problem with wikis, ideally of the<br>
> sort that don't require accounts, although I appreciate that presents<br>
> its own problems.<br>
><br>
> There's also implications regarding licensing and contributor agreements<br>
> which projects may require. Reading and signing 1000 words of legalese<br>
> is rarely fun even if unfortunately necessary -<br>
> <a href="https://www.osgeo.org/resources/individual-contributor-license/">https://www.osgeo.org/resources/individual-contributor-license/</a><br>
><br>
> Just my 2p,<br>
><br>
> Cheers,<br>
><br>
> Jonathan<br>
><br>
><br>
> On 2019-06-07 12:46, Jo Cook wrote:<br>
> > Hi All,<br>
> ><br>
> > I'm involved with Google Season of Docs this year<br>
> > (<a href="https://wiki.osgeo.org/wiki/Season_of_Docs_2019">https://wiki.osgeo.org/wiki/Season_of_Docs_2019</a>). The main focuses<br>
> > for us are QGIS, OSGeoLIVE and Geonetwork. We will be getting a paid<br>
> > technical writer for a few months to work on the OSGeo projects<br>
> > collectively, but the main aim is to get more community engagement in<br>
> > contributing to documentation.<br>
> ><br>
> > I'm heading up the Geonetwork team, and part of what I'm trying to do<br>
> > is lower the barriers for users to contribute to documentation, and<br>
> > figure out where information is missing, or how the documentation can<br>
> > be improved in other ways.<br>
> ><br>
> > So this is really a call out to fellow UK Geonetwork users- let me<br>
> > know what you think could do with improving in the documentation, and<br>
> > also if you're interested in getting further involved with the<br>
> > project. Any level of experience in contributing to documentation is<br>
> > fine- if you're a beginner and have previously been put off<br>
> > contributing or correcting a typo or something, then let me know what<br>
> > it is that put you off and we'll see what we can do to help. Contact<br>
> > me on or off list!<br>
> ><br>
> > If QGIS and/or OSGeoLive are more your thing, then head over to the<br>
> > Season of Docs mailing list at<br>
> > <a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a> as there are<br>
> > some active discussions going on about training materials and such<br>
> > like.<br>
> ><br>
> > All the best<br>
> ><br>
> > Jo<br>
> ><br>
> > --<br>
> > Jo Cook<br>
> > t:+44 7930 524 155/twitter:@archaeogeek<br>
> > Please note that currently I do not work on Friday afternoons. For<br>
> > urgent responses at that time, please visit<br>
> > support.astuntechnology.com or phone our office on 01372 744009<br>
> ><br>
><br>
> _______________________________________________<br>
> UK mailing list<br>
> UK@lists.osgeo.org<br>
> <a href="https://lists.osgeo.org/mailman/listinfo/uk">https://lists.osgeo.org/mailman/listinfo/uk</a><br>
<br>
<br>
<br>
-- <br>
Jo Cook<br>
t:+44 7930 524 155/twitter:@archaeogeek<br>
Please note that currently I do not work on Friday afternoons. For<br>
urgent responses at that time, please visit<br>
support.astuntechnology.com or phone our office on 01372 744009<br>
<br>
-- <br>
-- <br>
*Sign up to our mailing list <br>
<<a href="https://astuntechnology.com/company/#email-updates">https://astuntechnology.com/company/#email-updates</a>> for updates on news,
<br>
products, conferences, events and training*<br>
*<br>
*<br>
<br>
Astun Technology Ltd, The <br>
Coach House, 17 West Street, Epsom, Surrey, KT18 7RL, UK <br>
t:+44 1372 744 <br>
009 w: astuntechnology.com <<a href="http://astuntechnology.com/">http://astuntechnology.com/</a>> twitter:@astuntech
<br>
<<a href="https://twitter.com/astuntech">https://twitter.com/astuntech</a>><br>
<br>
<br>
<br>
iShare - enterprise geographic <br>
intelligence platform <<a href="https://astuntechnology.com/ishare/">https://astuntechnology.com/ishare/</a>><br>
GeoServer, <br>
PostGIS and QGIS training <<a href="https://astuntechnology.com/services/#training">https://astuntechnology.com/services/#training</a>><br>
<br>
Helpdesk and customer portal <br>
<<a href="http://support.astuntechnology.com/support/login">http://support.astuntechnology.com/support/login</a>><br>
<br>
<br>
<br>
<br>
Company registration <br>
no. 5410695. Registered in England and Wales. Registered office: 120 Manor <br>
Green Road, Epsom, Surrey, KT19 8LN VAT no. 864201149.<br>
<br>
<br>
------------------------------------------------------------------------------<br>
<br>
This message has been scanned for viruses by the Greater London Authority.<br>
<br>
Click <a href="https://www.mailcontrol.com/sr/wjUJelAtAVDGX2PQPOmvUg0Q1FXI7AabXbPzx9Q-uG8ehJb5DGDf9-bJ-wDGl1m4VX4zexuKDmaK0Rphlb7DTA==">
https://www.mailcontrol.com/sr/wjUJelAtAVDGX2PQPOmvUg0Q1FXI7AabXbPzx9Q-uG8ehJb5DGDf9-bJ-wDGl1m4VX4zexuKDmaK0Rphlb7DTA==</a> to report this email as spam.<br>
<br>
------------------------------------------------------------------------------<br>
</div>
</span></font></div>
<!--/*SC*/DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"/*EC*/-->
<HTML><HEAD><TITLE>GLA approved disclaimer</TITLE>
<META content="text/html; charset=windows-1252" http-equiv=Content-Type>
<STYLE><!--
a.noTextDecoration {color: #6495ed; text-decoration: none;}
div.glaLegalDisclaimer {border: thin solid silver; color: black; font-family: Verdana, Geneva, Arial, Helvetica, sans-serif; font-size: 8pt; padding: 5px;}
div.glaLegalDisclaimer:hover {border: thin solid #4a4a4a; color: gray;}
div.glaLegalDisclaimer:hover a.noTextDecoration {color: #4169e1; text-decoration: underline;}
div.glaLegalDisclaimer:hover span.glaLegalDisclaimerHeader {color: #4a4a4a;}
p.glaSignature {font-family: Arial, Helvetica, sans-serif; font-size: 12pt; margin: 0cm 0cm 3pt;}
span.glaLegalDisclaimerHeader {font-size: 10pt; font-variant: small-caps; font-weight: bold; line-height: 20px;}
span.glaLegalDisclaimerText {font-size: 8pt;}
--></STYLE>
<META name=GENERATOR content="MSHTML 11.00.10570.1001"></HEAD>
<BODY lang=EN-GB style="tab-interval: 36.0pt">
<DIV class=glaLegalDisclaimer><SPAN class=glaLegalDisclaimerHeader>GREATER
LONDON AUTHORITY NOTICE:</SPAN> <BR><SPAN class=glaLegalDisclaimerText>The
information in this email may contain confidential or privileged
materials. For more information see <A class=noTextDecoration
href="https://www.london.gov.uk/about-us/email-notice">https://www.london.gov.uk/about-us/email-notice</A>/</SPAN></DIV></BODY></HTML>
</body>
</html>