Now that the dates for the OSGeo virtual code sprint are set, is anyone planning to participate? The table here [0] looks pretty empty so far… I’m not sure I’ll be able to commit full time, but we could arrange a meeting one of those days to discuss our own agenda. What do you think?
On Fri, 6 Nov 2020 at 12:42, Veronica Andreo <veroandreo@gmail.com> wrote:
Hi devs,
Hi
Now that the dates for the OSGeo virtual code sprint are set, is anyone planning to participate? The table here [0] looks pretty empty so far... I'm not sure I'll be able to commit full time, but we could arrange a meeting one of those days to discuss our own agenda. What do you think?
I will participate, for the meeting depends on scheduled time
I've been working on a geomorphon data processing project for a while
and would like to have the code completed and published soon, would it
make sense to do that as a part of the sprint?
The work that still needs to be done is as follows:
1. Merge https://github.com/OSGeo/grass/pull/1052
2. Open and merge another GRASS pull request with a few more cleanups
(ready as soon as you are).
3. Open and merge another GRASS pull request with a new feature for
r.geomorphon (will be ready after a bugfix).
4. Finalize and publish a small stand-alone data processing tool based
on the new r.geomorphon feature. It is a niche solution that I have
developed as an independent contribution to a research project. I am
not sure if it is useful enough to live under GRASS or OSGeo hood,
but hopefully it is useful enough in similar research elsewhere.
Let me know what you think and if you need additional information.
On Sat, Nov 7, 2020 at 7:38 PM Denis Ovsienko <denis@ovsienko.info> wrote:
Hello all.
I've been working on a geomorphon data processing project for a while
and would like to have the code completed and published soon, would it
make sense to do that as a part of the sprint?
Sure, any contribution is welcome!
The work that still needs to be done is as follows:
1. Merge https://github.com/OSGeo/grass/pull/1052
2. Open and merge another GRASS pull request with a few more cleanups
(ready as soon as you are).
3. Open and merge another GRASS pull request with a new feature for
r.geomorphon (will be ready after a bugfix).
4. Finalize and publish a small stand-alone data processing tool based
on the new r.geomorphon feature. It is a niche solution that I have
developed as an independent contribution to a research project. I am
not sure if it is useful enough to live under GRASS or OSGeo hood,
but hopefully it is useful enough in similar research elsewhere.
Let me know what you think and if you need additional information.