<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Cameron, <br>
</p>
<p>thanks for the pointer to the new / old/ checklist link. <br>
</p>
<p><br>
</p>
<p>All, <br>
</p>
<p>the Incubation process and Checklists are not in a good state
right now. There also have been changes during the migration from
the old web site to the new website. For example the topic of
requiring Open Source / Free Software licenses is much less
prominent than on the old linked version Cameron provided and the
even older Incubation Status pages Oskari had started on. I am
pretty sure that these changes have not been discussed on the
Incubation lists?! The official document on the web (<a
moz-do-not-send="true"
href="https://www.osgeo.org/resources/project-graduation-checklist/">https://www.osgeo.org/resources/project-graduation-checklist/</a>)
points to a PDF file. Why on earth would we want this to be a file
and not plain HTML?! Incubation is core and heart to OSGeo and the
content is not readily available on the web? <br>
</p>
<p>No dramatic thing but we may want to go through the whole process
on this list again, flesh out old docs and so on. Happy to help
out on this around October / November when my schedule relaxes a
bit. If anybody is eager to push this forward before then please
go ahead. <br>
</p>
<p>Over the coming days we will move the Oskari Incubation status
page content to the version provided by Cameron and then ask the
Incubation committee to comment and eventually come to a decision
whether we can recommend Oskari for graduation.<br>
</p>
<p><br>
</p>
<p>It is somewhat hard to find things on the OSGeo Web in general
because many links from the Wiki to the new website are broken.
This causes quite a disconnect. When trying to fix some of the
links I also noticed difference in content and language which we
may have to fix with a lot of manual editing so that Wiki and
website are in sync again. Would be great to see this coordinated
by the web site committee - but that channel is dead since
December 2017 which is unfortunate because we now have a nice web
site but little editing going on - but this is a another topic. <br>
</p>
<p><br>
</p>
Have fun,<br>
Arnulf<br>
<br>
<br>
<div class="moz-cite-prefix">Am 2018-07-08 um 10:01 schrieb Cameron
Shorter:<br>
</div>
<blockquote type="cite"
cite="mid:10d1e580-2d0a-5726-3328-82531f238c00@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>Aarnio, Arnulf,</p>
<p>I just checked up on the link Arnulf pointed us to, <a
href="https://wiki.osgeo.org/wiki/Oskari_Incubation_Status"
moz-do-not-send="true">https://wiki.osgeo.org/wiki/Oskari_Incubation_Status</a>,
and it appears you are using an old version of the OSGeo
Incubation Checklist. This is understandable, as our incubation
docs have not been copied across into our new website. (Mumble,
mumble, grrr, grr.)</p>
<p>This is the checklist we should be using:<br>
<a class="moz-txt-link-freetext"
href="http://old.www.osgeo.org/incubator/process/project_graduation_checklist.html"
moz-do-not-send="true">http://old.www.osgeo.org/incubator/process/project_graduation_checklist.html</a><br>
</p>
<br>
<div class="moz-cite-prefix">On 6/7/18 10:10 pm, Aarnio Timo (MML)
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:6598f6446b1f478cabe7c93ed46af476@C119S212VM036.msvyvi.vaha.local">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;
font-weight:bold;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:13.5pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
mso-fareast-language:FI;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Cambria",serif;
color:#365F91;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Cambria",serif;
color:#243F60;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
mso-fareast-language:EN-US;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 2.0cm 70.85pt 2.0cm;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1463310450;
mso-list-template-ids:-898194814;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:2034571554;
mso-list-template-ids:-1397866638;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Dear
list members!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Thank
you so much for you assesment Arnulf and thank you for
your valuable comments Cameron and Bruce!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">I’ll
try to answer some of the questions and concerns raised
here.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">The
mailing list has been so far more as Arnulf described, an
announcement channel. However there have been multiple
questions and answers regarding the software as well.
You’ve gotta start somewhere right? Also some people seem
to dislike email lists and say that they are old
fashioned. Personally I don’t completely agree but I see
where these comments are coming from.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">In
our day to day work we use Slack (and nowadays also
Rocket.Chat) for communication. I agree that having logs
from our chats might be beneficial for others, but there
are at least two things to note here:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">-
We use the free version of Slack which supports only 10k
messages of history, so we’d have to develop some method
of fetching the chat archive (+attached media) and then
store&publish it somewhere. Not sure what the terms of
use for Slack say about this - we could check.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">-
A lot of the discussion (chat) is in Finnish. Also a lot
of it happens via private messages between two developers
and even though we’ve tried to encourage people to chat on
the public channels sometimes it just does not happen.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Anyone
that has questions and/or is developing something to
Oskari is welcomed to our Slack. We even planned to
automate the invitations, so that one wouldn’t have to ask
one from us.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">For
now I guess the best source for discussions and decisions
is GitHub and the PSC meeting notes. We also planned to
make the PSC meetings happen regularly (e.g. once a month)
in the sake of sharing information & knowledge
exchange.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">We’ve
discussed the OSGeo Live issue early last year and decided
that at this point it’s not something we will focus on.
Like Arnulf noted Oskari is a “platform” product and
relies heavily on external data sets so it’s not that well
suited for OSGeo Live.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">About
the question about Roadmap items and external
contributors: Oskari has had external contributors for
quite some time, but obviously here more is better. The
most recent “external” contribution is this <a
href="https://github.com/oskariorg/oskari-docs/issues/61"
moz-do-not-send="true">https://github.com/oskariorg/oskari-docs/issues/61</a>
- as an example of something that “went through the
process”. I put the word external in quotes because I
don’t know what qualifies as being external? The
free-to-join Oskari Community has now more than 30
organizations and many of them are using or developing
Oskari actively. Last year the first company (then
Dimenteq Ltd now Sitowise Ltd) started selling Oskari as a
service and also Oskari development and maintenance. This
year another company (Gispo Ltd) started offering
crowd-funding facilitating services for developing Oskari
collaboratively - tbh they are piloting it for now. I
really see both of these examples as very positive
development and I think they also secure the future of
Oskari to some extent.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Obviously
a more broader adoption is something we still strive for.
For a software like Oskari it’s challenging but little by
little we’ve already managed to do it so it’s possible :)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">I
don’t think we’re in any rush for the graduation and this
discussion will be very helpful for us to develop our
process even further. So please do comment back so we know
what kind of steps to take next and how to proceed. My
holidays start today so don’t wonder if I’m not replying
for a while, I’ll get back to work in August.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Thanks
again for your support!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">BR,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Timo<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="mso-fareast-language:FI" lang="EN-US">From:</span></b><span
style="mso-fareast-language:FI" lang="EN-US">
Incubator [<a class="moz-txt-link-freetext"
href="mailto:incubator-bounces@lists.osgeo.org"
moz-do-not-send="true">mailto:incubator-bounces@lists.osgeo.org</a>]
<b>On Behalf Of </b>Bruce Bannerman<br>
<b>Sent:</b> 6. heinäkuuta 2018 0:17<br>
<b>To:</b> Cameron Shorter <a
class="moz-txt-link-rfc2396E"
href="mailto:cameron.shorter@gmail.com"
moz-do-not-send="true"><cameron.shorter@gmail.com></a><br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated"
href="mailto:Oskari-user@lists.osgeo.org"
moz-do-not-send="true">Oskari-user@lists.osgeo.org</a>;
Sanna Jokela (Gispo) <a class="moz-txt-link-rfc2396E"
href="mailto:sanna@gispo.fi" moz-do-not-send="true"><sanna@gispo.fi></a>;
<a class="moz-txt-link-abbreviated"
href="mailto:incubator@lists.osgeo.org"
moz-do-not-send="true">incubator@lists.osgeo.org</a><br>
<b>Subject:</b> Re: [Incubator] Oskari Incubation
status<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi Arnulf,<span
style="font-size:12.0pt;mso-fareast-language:FI"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks for your detailed assessment.
...and yes, I did read to the bottom ;-)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I would like to see a response to your
questions from Timo, or another representative of the
Oskari community. In particular a response to the issues
of open communities and decision making.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">From what I’ve viewed on the project
website, Oskari has considerable potential. However, good
software is only part of the picture.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Having a good, strong, healthy and
active community that is diverse and uses open processes
will help the project to survive when funding from the
major sponsor ceases.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Kind regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Bruce<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On 6 Jul 2018, at 03:02, Cameron Shorter <<a
href="mailto:cameron.shorter@gmail.com"
moz-do-not-send="true">cameron.shorter@gmail.com</a>>
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p>Arnulf, to answer your question at the bottom, yes I
read to the bottom, and really appreciate your detailed
assessment.<o:p></o:p></p>
<p>Based on Arnulf's assessment, it sounds like Sskari
probably has a good codebase, with good work from within
one organisation, but is yet to attract engaged external
developers. This is a great milestone, and worth
acknowledging. But the "unicorn" projects that we look
for in OSGeo incubation are those with a healthy
community from multiple organisations.<o:p></o:p></p>
<p>The "extent of collaboration" criteria provides
validation of the quality of the project, and is a very
good indicator of long term sustainability. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">To the
Oskari folks, you might want to read this presentation I
gave a while back on business justifications for backing
collaboration: <br>
<a
href="http://cameronshorter.blogspot.com/2017/11/open-source-pitch-for-your-boss.html"
moz-do-not-send="true">http://cameronshorter.blogspot.com/2017/11/open-source-pitch-for-your-boss.html</a><br>
<br>
Without digging into the details any further, I suspect
Oskari would need to work on attracting co-contributors,
from multiple organisations, and we would likely see
evidence of this happening by seeing archive logs of
collaborative email lists, or slack or IRC or similar.<br>
<br>
Warm regards, Cameron<o:p></o:p></p>
<div>
<p class="MsoNormal">On 6/7/18 2:11 am, Arnulf Christl
(Metaspatial) wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p>Hi Folks, <o:p></o:p></p>
<p>this is an update on the Incubation process of
Oskari. <o:p></o:p></p>
<p><a
href="https://wiki.osgeo.org/wiki/Oskari_Incubation_Status"
moz-do-not-send="true">https://wiki.osgeo.org/wiki/Oskari_Incubation_Status</a><o:p></o:p></p>
<p>As mentor I am still somewhat hesitant to recommend
Oskari for OSGeo Incubation because I cannot find a
good indicator supporting that there is an open
community and communication. Personally I know some of
the current core team and totally trust them to work
in the Open Source way of doing things. But this may
not be quite apparent to anybody not into the project.
<o:p></o:p></p>
<p>Oskari is doing a good job posting news and updates
to the OSGeo user list (<a
href="https://lists.osgeo.org/pipermail/oskari-user/"
moz-do-not-send="true">https://lists.osgeo.org/pipermail/oskari-user/</a>)
but the list is not really used by users for any kind
of discussion, help or future development. It feels
more like a low volume announce list (which is totally
OK, so please keep it up). <o:p></o:p></p>
<p>How and where is the development being discussed? Who
can join the Oskari Slack channel - or whatever else
is used to have technical and strategic discussions?
Are there archives of discussions and decisions? Do
you manage to do this in English or is it still
everything communicated in Finnish? <o:p></o:p></p>
<p>In a PSC presentation from December 2016 one
bullet-point says that Oskari may become a project on
OSGeo live: <a
href="https://oskariorg.github.io/files/20161220-Oskari_OSGEO_PSC.pdf"
moz-do-not-send="true">https://oskariorg.github.io/files/20161220-Oskari_OSGEO_PSC.pdf.
<br>
</a><o:p></o:p></p>
<p>Actually, Incubation is not a requirement, so please
feel free to approach the OSGeo Live team to find out
more.<o:p></o:p></p>
<p>In the Roadmap document (which in my opinion is
actually ery good) at: <a
href="https://github.com/oskariorg/oskari-docs/wiki/Roadmap-process"
moz-do-not-send="true">
https://github.com/oskariorg/oskari-docs/wiki/Roadmap-process</a> you
say that: <o:p> </o:p></p>
<p><i>"After communicating with Oskari community the
roadmap items enter Active stage [...]". </i><o:p></o:p></p>
<p>Can you give us an example of where and how this has
happened? <o:p></o:p></p>
<p>There are some updates on GitHub issues but it
appears to be mostly internal team members (which is
totally OK, is this where the collaborative aspect of
the future development takes place? <o:p></o:p></p>
<p><a
href="https://github.com/oskariorg/oskari-docs/labels/roadmap"
moz-do-not-send="true">https://github.com/oskariorg/oskari-docs/labels/roadmap</a><o:p></o:p></p>
<p>Regarding Code Copyright Review you state that: <o:p></o:p></p>
<p><i>All code has been developed by the registered
developers listed on github who have signed the CLA.
All external libraries have project compatible
licenses. The project has been started as a regular
Open Source project following the guidelines as set
out by OSGeo. A file-per-file code review was
therefore deemed superfluous. </i><o:p></o:p></p>
<p>As mentor I can confirm that this is correct and
satisfies OSGeo's requirements (and yes, I did some
quick checks on random code files but due to the well
organized origin of the project did not go through all
code like we had to in the GRASS project... :-).<o:p></o:p></p>
<p>In the last PSC meeting in December 2017 a decision
was taken to schedule the next meeting "as needed". <o:p></o:p></p>
<h2 id="meetingsactivity"><i>Meetings/activity</i><o:p></o:p></h2>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1"> <i>[...]</i><o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1"> <i>future meetings schedule: continue
with “as needed” (no need for a fixed schedule)</i><o:p></o:p></li>
</ul>
<p>Summarizing the current status: We discussed some of
the above topics before and it is not a requirement
for OSGeo Incubation to have active mailing lists and
so on. But it is a requirement to have an open process
and ideally also a somewhat growing user community.
Obviously due its character as a complex portal
platform Oskari is not a software that will have
millions of downloads but a little broader adoption
would be nice to see. <o:p></o:p></p>
<p>You also say: <o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo2"> <i>Slack/Mailinglist can be used more
actively to discuss any issues/voting</i><o:p></o:p></li>
</ul>
<p>If you are not using the Slack channel (which
unfortunately is not open), where is the communication
taking place? <o:p></o:p></p>
<p>The PSC meeting notes from December 2017 has a list
of current installations / users / contributions. This
is good to see. Has there been any additions, changes
over the past half year? <o:p></o:p></p>
<p class="MsoNormal"><br>
Even if you can not produce evidence for any or all of
the above issues I will be happy to recommend Oskari
for Incubation if you believe that this will help the
project. Then it will be up to the Incubation
committee to decide whether we can recommend
graduation to the OSGeo Board of Directors. <o:p></o:p></p>
<p>We will have to expect some discussion on the
Incubation list on the above topics and this is not
bad but a sign of a healthy process. <o:p></o:p></p>
<p><o:p> </o:p></p>
<h3>Internal note to the Incubation committee <o:p></o:p></h3>
<p>IF you ever made it down to this line and maybe even
checked some of the referenced documents, please be so
kind as to acknowledge this on the mailing list so
that we can help Oskari move on. <o:p></o:p></p>
<p>It may also be a good idea to go back to the
Incubation process and check whether it should be
revised for certain aspects (especially requirement on
mailing lists / alternatives like Slack). <o:p></o:p></p>
<p><o:p> </o:p></p>
<p>Anything else you need, let me know. <o:p></o:p></p>
<p><o:p> </o:p></p>
<p>Thank you, <o:p></o:p></p>
<p>Arnulf<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Am 2018-06-25 um 17:05 schrieb
Aarnio Timo (MML):<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi Incubator-list!<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">We’d like to
inquire about the incubation status of Oskari.
What are the next steps should be in the
incubation process? In our end we’ve done
everything we’ve realized that we have to do. But
is there something still wanted from us? Or is the
process in the OSGeo end now? If so, what are the
steps there and is there possibly any estimate
when we can think about graduating?</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Kind regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="mso-fareast-language:FI" lang="EN-US">Timo
Aarnio</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times
New Roman",serif;mso-fareast-language:FI"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Incubator mailing list<o:p></o:p></pre>
<pre><a href="mailto:Incubator@lists.osgeo.org" moz-do-not-send="true">Incubator@lists.osgeo.org</a><o:p></o:p></pre>
<pre><a href="https://lists.osgeo.org/mailman/listinfo/incubator" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/incubator</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman",serif;mso-fareast-language:FI"><br>
<br>
<o:p></o:p></span></p>
<pre>-- <o:p></o:p></pre>
<pre>Spatially enabling your business<o:p></o:p></pre>
<pre><a href="http://metaspatial.net" moz-do-not-send="true">http://metaspatial.net</a><o:p></o:p></pre>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman",serif;mso-fareast-language:FI"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Incubator mailing list<o:p></o:p></pre>
<pre><a href="mailto:Incubator@lists.osgeo.org" moz-do-not-send="true">Incubator@lists.osgeo.org</a><o:p></o:p></pre>
<pre><a href="https://lists.osgeo.org/mailman/listinfo/incubator" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/incubator</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman",serif;mso-fareast-language:FI"><br>
<br>
<o:p></o:p></span></p>
<pre>-- <o:p></o:p></pre>
<pre>Cameron Shorter<o:p></o:p></pre>
<pre>Technology Demystifier<o:p></o:p></pre>
<pre>Open Technologies and Geospatial Consultant<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>M +61 (0) 419 142 254<o:p></o:p></pre>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman",serif;mso-fareast-language:FI">_______________________________________________<br>
Incubator mailing list<br>
<a href="mailto:Incubator@lists.osgeo.org"
moz-do-not-send="true">Incubator@lists.osgeo.org</a><br>
<a
href="https://lists.osgeo.org/mailman/listinfo/incubator"
moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/incubator</a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Incubator mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Incubator@lists.osgeo.org">Incubator@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/incubator">https://lists.osgeo.org/mailman/listinfo/incubator</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Spatially enabling your business
<a class="moz-txt-link-freetext" href="http://metaspatial.net">http://metaspatial.net</a>
</pre>
</body>
</html>