[Incubator] MDAL OSGeo Community Project Application Request

Fri Dec 18 01:40:33 PST 2020

Hi, thanks for review and starting the voting process.

- for contributing, there is section both in main README and mdal.xyz
- i have checked headers, they should be fine
- i have created ticket for quickstart
https://github.com/lutraconsulting/MDAL/issues/330

Have a relaxing holiday and new year 2021.

Peter

On Tue, Dec 8, 2020 at 2:32 AM Jody Garnett <jody.garnett at gmail.com> wrote:

> Oh great, thanks for pointing that out! I did not see that when I
> scanned the README.md. I did find something similar in the user manual.
>
> We can keep the vote open for a bit longer, note my vote was a +1 - I just
> had some questions I should of asked earlier.
> --
> Jody Garnett
>
>
> On Mon, 7 Dec 2020 at 03:12, Jo Cook <jocook at astuntechnology.com> wrote:
>
>> Hi Jody,
>>
>> There's a statement on contributing in the readme at
>> https://github.com/lutraconsulting/MDAL/blob/master/README.md- I felt
>> it was clear enough?
>>
>> Ideally my vote should close today, but we don't have a quorum so
>> shall we just keep it open for another fortnight or do you want to
>> make a separate CONTRIBUTING.md file a condition of acceptance?
>>
>> Jo
>>
>> On Fri, Dec 4, 2020 at 6:51 PM Jody Garnett <jody.garnett at gmail.com>
>> wrote:
>> >
>> > I see that Jo made a motion, but I did find a review handy ...
>> >
>> > Grabbing the checklist from here, and checking project repository:
>> >
>> > 1. Be geospatial
>> >
>> > Confirm by checking README or project description
>> > project page on the osgeo website
>> > We ask projects have some user documentation, for example an OSGeo Live
>> quickstart
>> >
>> > README (https://github.com/lutraconsulting/MDAL/blob/master/README.md)
>> looks good.
>> >
>> > Website page (https://www.osgeo.org/projects/mdal/) looks good,
>> ideally the logo is on a white background so it shows up like on other
>> pages.  If there is a screen snap or something (you mentioned use in QGIS)
>> it really helps the page communicate the project working with meteorology
>> and hydrology data.
>> >
>> > The page links to documentation (https://www.mdal.xyz) but I do not
>> see a quickstart on using the library. I was looking forward to seeing some
>> C++ code, I even hunted around in the tutorials (
>> https://www.mdal.xyz/tutorials/index.html). The README had some tips on
>> building but not using the library.
>> >
>> > 2. Have a free license or an open source license.
>> >
>> > The license must be OSI approved
>> > We ask that the project team check the file headers and double check
>> the license has been appropriately applied
>> >
>> >
>> > Nice clear MIT LICENSE (
>> https://github.com/lutraconsulting/MDAL/blob/master/LICENSE).
>> >
>> > Do you have a record of checking the headers somewhere? Looking at the
>> codebase myself everything seemed good. But the idea is the project team
>> checks ...
>> >
>> > 3. Welcome participation and new contributors.
>> >
>> > We look for a clear contribution policy
>> > We ask that the project demonstrate collaboration, perhaps with a
>> history of bug report or pull requests
>> > Projects are required to have a code of conduct
>> >
>> >
>> > I do not see a CONTRIBUTING.md file.
>> > Digging deeper the manual has something on community (
>> https://www.mdal.xyz/community.html) with a section covering development
>> and welcoming pull requests. A CONTRIBUTING.md file is still recommended as
>> the project is hosted on GitHub.
>> > - As an example the project contains a list of AUTHORS (
>> https://github.com/lutraconsulting/MDAL/blob/master/AUTHORS)  is this
>> file updated when accepting a PR from a new contributor?
>> > - Does they new contributor add their copyright to the header when
>> updating a file?
>> > - How about when a contributor is adding a new file ...
>> >
>> > Nice clear pull request history. are they all from Vincent Cloarec? Who
>> may be from an external organization? Checking commit history to try and
>> answer this question, other authors are committing directly on a very
>> active codebase.
>> >
>> > Nice clear code of conduct.
>> >
>> > So I am soft +1 on this one:
>> > - I see nothing missing - it looks to be an interesting active project
>> :)
>> > - would like to double check that the team checked headers
>> > - ask that the team pick up their section from the user manual into a
>> CONTIRBUTING.md, and perhaps add to it over time
>> > --
>> > Jody Garnett
>> >
>> >
>> > On Mon, 23 Nov 2020 at 23:24, Peter Petrik <
>> peter.petrik at lutraconsulting.co.uk> wrote:
>> >>
>> >> Hi,
>> >>
>> >> We would like to proceed with the application process for MDAL but
>> haven't received any updates for a few months. Is there anything we can do
>> to continue with the process?
>> >>
>> >> Kind regards,
>> >> Peter
>> >>
>> >> On Thu, Oct 29, 2020 at 8:46 AM Peter Petrik <
>> peter.petrik at lutraconsulting.co.uk> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> any update on the reviewing the application? Are any steps needed
>> from our side?
>> >>>
>> >>> Thanks,
>> >>> Peter
>> >>>
>> >>> On Wed, Sep 30, 2020 at 12:56 PM Peter Petrik <
>> peter.petrik at lutraconsulting.co.uk> wrote:
>> >>>>
>> >>>> Hi,
>> >>>>
>> >>>> the mdal-developer mailing list is completed, thank you for
>> assistance.
>> >>>> Are there some regular incubator committee meetings where you
>> discuss applications?
>> >>>>
>> >>>> Peter
>> >>>>
>> >>>> On Tue, Sep 22, 2020 at 8:40 AM Peter Petrik <
>> peter.petrik at lutraconsulting.co.uk> wrote:
>> >>>>>
>> >>>>> Hi OSGeo!,
>> >>>>>
>> >>>>> We have been working with Jody (thanks!) on preparing the
>> application of MDAL for OSGeo Community Project, see
>> https://lists.osgeo.org/pipermail/discuss/2020-September/039048.html
>> >>>>>
>> >>>>> I believe the page https://www.osgeo.org/projects/mdal/ is
>> finished, and I also submitted request for a MDAL-Development mail list
>> (ongoing https://trac.osgeo.org/osgeo/ticket/2509#ticket)
>> >>>>>
>> >>>>> We would like to kindly ask the committee to review our application
>> and let us know the next steps.
>> >>>>>
>> >>>>> Kind regards,
>> >>>>> Peter for MDAL team
>> >>>>> https://www.mdal.xyz
>> >>>>>
>> > _______________________________________________
>> > Incubator mailing list
>> > Incubator at lists.osgeo.org
>> > https://lists.osgeo.org/mailman/listinfo/incubator
>>
>>
>>
>> --
>> Jo Cook
>> t:+44 7930 524 155/twitter:@archaeogeek
>> Please note that currently I do not work on Friday afternoons. For
>> urgent responses at that time, please visit
>> support.astuntechnology.com or phone our office on 01372 744009
>>
>> --
>> --
>> *Sign up to our mailing list
>> <https://astuntechnology.com/company/#email-updates> for updates on
>> news,
>> products, conferences, events and training*
>> *
>> *
>>
>> Astun Technology Ltd, 120
>> Manor Green Road, Epsom, Surrey, KT19 8LN, UK
>> t:+44 1372 744 009 w:
>> astuntechnology.com <http://astuntechnology.com/> twitter:@astuntech
>> <https://twitter.com/astuntech>
>>
>>
>>
>> iShare - enterprise geographic
>> intelligence platform <https://astuntechnology.com/ishare/>
>> GeoServer,
>> PostGIS and QGIS training <https://astuntechnology.com/training-courses/>
>> Helpdesk and customer portal
>> <
>> https://astuntech.atlassian.net/wiki/spaces/ISHAREHELP/pages/364970043/Astun+Technology+Support+Portal
>> >
>>
>>
>>
>>
>> Company registration no. 5410695. Registered in England and Wales.
>> Registered office: 120 Manor Green Road, Epsom, Surrey, KT19 8LN VAT no.
>> 864201149.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20201218/6b83a442/attachment.html>