[Incubator] eodash website listing

Jody Garnett jody.garnett at gmail.com
Wed Sep 18 21:55:52 PDT 2024


 Looks great folks!

Just providing small feedback and questions.

Q:  For the architecture diagrams perhaps use the "tablet" frame as
described in
https://www.osgeo.org/community/getting-started-osgeo/add-a-project/ ?

We just wrote these instructions so I am interested in how "easy" they are
to follow? Or if it is this activity is too difficult as described.

I think a couple sentences are still passive:

*This ecosystem is established by collaborating with and inviting the
different Earth Observation communities and understanding their
requirements, trying to set it up as a more open community project to
foster communication.*

*Core functionality defines a baseline intended for use by each of these
communities but still allowing to easily integrate their unique solutions.*


Without the "almost" disclaimers:

This ecosystem is established by collaborating with different Earth
Observation communities to understand our requirements. The eodash
ecosystem is set it up as an open community project to foster communication.

*Core functionality establishes a baseline for use by each of community,
allowing each to easily integrate their unique solutions.*


Okay I will stop now as this is not the marketing committee.
- -
Jody Garnett


On Sep 18, 2024 at 12:45:33 AM, "Santillan, Daniel" <daniel.santillan at eox.at>
wrote:

> Hello Jody, hello all,
>
> also from my side thank you for the feedback! I tried to incorporate your
> points also directly in the documentation
> <https://github.com/eodash/eodash-docs/pull/2/files>.
> Thank you Stephan for coordinating and updating the eodash entry in OSGeo
> accordingly, looking great.
> As to references, we are in discussion with ESA and in extension with
> other of the participating agencies (NASA, JAXA) to try and find a wording
> to reference them all, which they agree on.
> The eodash software in its form was made possible by a series of projects,
> also as Stephan mentioned in the issue, we will for sure extend this
> information.
> We have had a series of workshops where instances of eodash have been
> presented, which i imagine would be fitting for "show your people", but
> here also we will need to coordinate with ESA to make sure it is ok to use
> the content.
>
> Kind regards,
> Daniel
>
> On Mon, Sep 16, 2024 at 9:34 PM Meißl, Stephan <stephan.meissl at eox.at>
> wrote:
>
>> Hi Jody,
>>
>> I added a comment to issue #112 (although if you can just tell me that
>>> you have PRs from multiple organization that would be fine also).
>>>
>>
>> Thanks, I don't think we have them yet.
>>
>>
>>> Published: https://www.osgeo.org/projects/eodash/
>>>
>>
>> Awesome, thanks.
>>
>> Feedback on content (for discussion/consideration):
>>>
>>>    - Introduction: Only really the first sentence is shown in the list
>>>    of projects. You may wish to adjust.
>>>
>>>
>>>
>> Adjusted
>>
>>
>>>
>>>    - Photo: Do you have any image of your team? Your laptop? Your
>>>    coffee cup? Somehow we are seeking to communicate that software is made by
>>>    people ... It is like an academia where you "show your references", in open
>>>    source we wanted to "show your people" :)
>>>
>>>
>> Let me think, we have been using the hashtag #eodash a bit on twitter (
>> https://x.com/hashtag/eodash?f=live) and posted photos like in
>> https://x.com/EO_OPEN_SCIENCE/status/1721447493412454608. Would that
>> maybe be reasonable?
>>
>>
>>>
>>>    - Content:
>>>    - Recommendation: "Goal: With this ecosystem we want to provide an
>>>       easily usable...."
>>>          - It sounds a bit cautious/passive.
>>>       - Consider: "The eodash ecosystem provides ..."
>>>       - Easier to read, you can be confident and let people decide for
>>>          themselves!
>>>       - "Core functionality of the toolset should should cater to
>>>       provide a baseline that can be used by" ... that is a lot of indirection!
>>>          - Consider: "Core functionality defines a baseline intended
>>>          for use by each community"
>>>       - Similar feedback for "We want" for collaborating with different
>>>       EO communities. Instead clearly "Invite EO communities to collaborate"
>>>       - "The documentation tries to cater two user groups" --> This
>>>       documentation caters to:
>>>
>>>
>> Thanks, all suggestions integrated.
>>
>>
>>>
>>>    - Core features, take some of your topics out into bullet points, as
>>>    this is often all that people manage to read / retain..
>>>       - If I understand you could have one for "core functionality:
>>>       Baseline for all EO communities, Easy integration"
>>>
>>>
>> Added a first version for review.
>>
>>
>>>
>>>    - Image: Anything? Even a slide from a presentation? Or a screen
>>>    snap from this page https://eodash.org/data.html or
>>>    https://eodash.org/storytelling.html
>>>
>>>
>> Added the architecture or do you think a screenshot of a website using
>> eodash would be better?
>>
>>
>>>
>>>    - Communication? It looks like you have discussion -
>>>    https://github.com/eodash/eodash/discussions is that intended for
>>>    users?
>>>
>>>
>> Good point.
>>
>>
>>>
>>>    - End user resources - you do have nice manual to share?
>>>
>>>
>>>    - Developer resources - you can popular with some links to source
>>>    code, issue tracker, discussions, etc..
>>>
>>>
>> Added some links in both.
>>
>>
>>>
>>>    - Topic: I adjusted so it would show up under "Information
>>>    Technology > Client (primary)", but if appropriate you can list under
>>>    topics... " especially since you filled out lots for Level 1 and Level 2?
>>>
>>>
>> Thanks, sounds good.
>>
>>
>>>
>>>    - Standards: nice!
>>>
>>>
>>
>> Thanks for your thorough review!
>>
>> Best
>> Stephan
>>
>>
>>
>> - -
>>> Jody Garnett
>>>
>>>
>>> On Sep 16, 2024 at 2:21:24 AM, "Meißl, Stephan" <stephan.meissl at eox.at>
>>> wrote:
>>>
>>>> Hi Jody,
>>>>
>>>> Nice to meet you again and thanks for your review and granting author
>>>> permissions.
>>>>
>>>> I confirm that the project welcomes participation and contributors.
>>>> Thanks for the suggestion about adding a CONTRIBUTING.md (tracked in
>>>> https://github.com/eodash/eodash/issues/112).
>>>>
>>>> I edited the draft project page
>>>> https://www.osgeo.org/wp-admin/post.php?post=26369&action=edit and I'm
>>>> happy to hear your feedback.
>>>>
>>>> Best
>>>> Stephan
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, Sep 14, 2024 at 1:17 AM Jody Garnett <jody.garnett at gmail.com>
>>>> wrote:
>>>>
>>>>> Hello Stephan,
>>>>>
>>>>> Thanks for joining us and for sharing your work with the community.
>>>>>
>>>>> I chose one repo to check https://github.com/eodash/eodash
>>>>>
>>>>>
>>>>>    1. GeoSpatial: README.md
>>>>>    <https://github.com/eodash/eodash/blob/main/README.md>
>>>>>    Check - looks good!
>>>>>    2. License: LICENSE
>>>>>    <https://github.com/eodash/eodash/blob/main/LICENSE>
>>>>>    MIT check
>>>>>    3. Welcome participation and contributors: ... unclear?
>>>>>    I do not see a CONTRIBUTING.md file so I am not sure? I see an
>>>>>    interesting note on "The Conventional Commits" for developers. Checking
>>>>>    open and closed PRs see a very active project..
>>>>>
>>>>>    So I think you are open to new contributors but wish to confirm.
>>>>>    You may wish to add a CONTRIBUTING.md file to advise potential contributors
>>>>>    about your commit message policy (for example).
>>>>>
>>>>>
>>>>> I am giving you "project author" permission to create a page - we have
>>>>> new "Add a Project
>>>>> <https://www.osgeo.org/community/getting-started-osgeo/add-a-project/>"
>>>>> instructions here and would very much welcome your feedback! I see your
>>>>> employer already has a service provider page
>>>>> <https://www.osgeo.org/service-providers/eox/>.
>>>>>
>>>>> (If you can confirm about being open to contributors it would be good.
>>>>> We do not wish to promote projects that are "open washed" - source code
>>>>> shared but no ability to work with others).
>>>>>
>>>>> - -
>>>>> Jody Garnett
>>>>>
>>>>>
>>>>> On Sep 13, 2024 at 2:08:48 PM, "Meißl, Stephan via Incubator" <
>>>>> incubator at lists.osgeo.org> wrote:
>>>>>
>>>>>> Dear incubation committee,
>>>>>>
>>>>>> I would like to ask permission to list our project "eodash" (
>>>>>> https://eodash.org/) on the OSGeo website in order to share our work
>>>>>> with more people. The project is based on various open source projects
>>>>>> including OpenLayers. The code repository is located under
>>>>>> https://github.com/eodash and the code is released under MIT license.
>>>>>>
>>>>>> My OSGeo userid is "Schpidi" and I'd need permission to create a
>>>>>> project page. Note that I already created a page for EOxServer in the past
>>>>>> and I also already tried to add a draft of the eodash page prior to sending
>>>>>> this mail but it seems I'm missing some permissions. Thanks for your
>>>>>> support!
>>>>>>
>>>>>> Best
>>>>>> Stephan
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Incubator mailing list
>>>>>> Incubator at lists.osgeo.org
>>>>>> https://lists.osgeo.org/mailman/listinfo/incubator
>>>>>>
>>>>>
>
> --
>
> Daniel Santillan, MSc
> EOX IT Services GmbH - http://eox.at
> 1090 Wien, Thurngasse 8/4, Austria
> Mobile: +43 (0) 660 / 489 8326
> mailto: daniel.santillan at eox.at
> HG Wien - FN 312068z - UID ATU64265057
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20240918/aab52081/attachment-0001.htm>


More information about the Incubator mailing list