Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Luís de Sousa
    @ldesousa
    @jorgejesus @jachym @jonas-eberle PyWPS 4.2 is being ultimated, please the maillist and stand by for a vote.
    Tom Kralidis
    @tomkralidis
    I can look at this tomorrow.
    Jachym Cepicky
    @jachym
    +1
    sorry, i was off, overloaded by work (of course) and than I was mowed-down sick
    is there anyting I can do?
    Tom Kralidis
    @tomkralidis
    Should we do a round of fixing #427 or too risky and release 4.2?
    MacPingu
    @cehbrecht

    I would prefere to postpone #427 to the next patch release. It is nothing critical.

    The PRs we want to have in the 4.2 release are merged now … and pywps is still working;) So, I could say we are “good to go” and follow the release procedure (vote, tom or jachym doing the release?, moving open issue to next milestone, …). After the release I can take care about the conda package #234.

    Jachym Cepicky
    @jachym
    427 is IMHO just cosmetics, if we want to release any time soon, I would skip this for now, its nice to have. I have, ther is no security reason
    I can do the release (it's described in RELEASE.howto I hope). are we as psc /all satisfied ?
    MacPingu
    @cehbrecht
    +1
    Tom Kralidis
    @tomkralidis
    fwiw #427 fixed by #433 (we can either merge now or post 4.2).
    Tom Kralidis
    @tomkralidis
    I think we should have a vote on the release, draft a release announcement, then cut 4.2.0 and announce. Thoughts?
    Tom Kralidis
    @tomkralidis
    see email, moving there
    Tom Kralidis
    @tomkralidis
    thanks for the approval @cehbrecht. Merged. What are you thoughts on backporting to 4.2 branch ?
    MacPingu
    @cehbrecht
    We were not so well in maintaing the official release and need to get into a better release flow. In our case we always want the latest :) So, maintaing a bugfix release might not be necessary at the moment.
    Tom Kralidis
    @tomkralidis
    fair enough. I'll keep to master.
    RE: #435 where is the dev guide?
    Jorge Samuel Mendes de Jesus
    @jorgejesus
    Hi to all I have noticed that pywps-flask (dockers) use gdal 1.1.0, could we upgrade this sooner or later to gdal 2 ?
    Luís de Sousa
    @ldesousa
    Tom Kralidis
    @tomkralidis
    +1 (see email)
    MacPingu
    @cehbrecht
    +1 (answered via email as well)
    Jorge Samuel Mendes de Jesus
    @jorgejesus
    pywps-flask is working properly with pywps 4.2.1, also fixed travis
    After will look at Dockerhub to automatically build the new images
    Jorge Samuel Mendes de Jesus
    @jorgejesus
    Here is another pull request
    Totally forgot about issue geopython/pywps-flask#16
    Tom Kralidis
    @tomkralidis
    Hi PSC: FYI we are walking through OSGeo budget. As an OSGeo project we can ask for funds to support PyWPS activities. The baseline for OSGeo projects is 2K USD. More info at https://wiki.osgeo.org/wiki/OSGeo_Budget_2019
    Tom Kralidis
    @tomkralidis
    @/all PSA HTTPS is now enabled for pywps.org website.
    Tom Kralidis
    @tomkralidis
    @cehbrecht geopython/pywps#449 is some cosmetic changes
    Jachym Cepicky
    @jachym
    I do wonder, that it works, thanks @tomkralidis
    Tom Kralidis
    @tomkralidis
    thank you @jachym !
    @jachym et. al. any thoughts on OSGeo funding?
    Tom Kralidis
    @tomkralidis
    hey all: On request, I've created a public geopython room in https://geopython.github.io. Please spread the word! https://twitter.com/tomkralidis/status/1088594540225654784
    Jachym Cepicky
    @jachym
    I've added WPS 2.0 "worskohp" to the budget proposal
    Tom Kralidis
    @tomkralidis
    all: is anyone able to attend the OSGeo Code Sprint in May?
    Jorge Samuel Mendes de Jesus
    @jorgejesus
    nop
    Tom Kralidis
    @tomkralidis
    I think there are funds in the project budget for folks to attend?
    (I am already attending via pycsw)
    Jorge Samuel Mendes de Jesus
    @jorgejesus
    maybe @ldesousa or @jachym know it beter
    Luís de Sousa
    @ldesousa
    Sorry, I can not attend the code sprint in May.
    Tom Kralidis
    @tomkralidis
    @ldesousa where is the PyWPS paper again? See email, I would like to review attribution for myself
    Jachym Cepicky
    @jachym
    -1 :-(
    MacPingu
    @cehbrecht

    @tomkralidis Could you add me as maintainer on RTD for pywps?
    https://readthedocs.org/projects/pywps/

    Probably the GitHub webhook is broken, so the RTD update of pywps from master does not work.

    Tom Kralidis
    @tomkralidis
    @cehbrecht what's your rtd username?
    MacPingu
    @cehbrecht
    I’m PinguCarsti
    Tom Kralidis
    @tomkralidis
    @cehbrecht thanks, done
    Tom Kralidis
    @tomkralidis
    hi @/all for the OSGeo Code Sprint in a couple of weeks I put up some items for various geopython projects: https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2019#Project_Plans . Please feel free to add/update. I didn't put anything for PyWPS per se, but will anyone be there with interest in PyWPS?
    Tom Kralidis
    @tomkralidis
    @jachym can you update demo.pywps.org DNS to point to 140.211.15.30 ? Thanks
    Tom Kralidis
    @tomkralidis
    @jachym et. al.: for the FOSS4G AGM are we able to provide some 2019 updates for PyWPS? https://docs.google.com/presentation/d/1imiG7x09ry7lGvmS15FCVq2Z7yaICY00fcpXBK27TXY/edit#slide=id.g24e11ca246_1_0 (slide 44)