GithubHelp home page GithubHelp logo

Comments (4)

prisae avatar prisae commented on August 15, 2024 1

Thanks for writing this down @JustinGOSSES. I am hardly active at all I have to admit. Would a #AwesomeOpenGeoscience chanel in the Swung-Slack help to ping/push people, or just be yet another distraction? I am not sure myself.

Either way, I think to post it in #general or in #open-geoscience trying to find additional maintainers would definitely be a good idea!

from awesome-open-geoscience.

JustinGOSSES avatar JustinGOSSES commented on August 15, 2024 1

Having a separate Slack channel is an interesting idea. It might help as back channel where maintainers can say "can't take this one" or we need someone with experience in X?

On one hand, I like to keep all discussion in one place. On other hand, a Slack channel is going to encourage certain discussion that will not happen in issues, which tend to be more formal & controlled.

There's a channel in SoftwareUnderground for welly & lasio things. I'll ask in there for feedback.

from awesome-open-geoscience.

JustinGOSSES avatar JustinGOSSES commented on August 15, 2024

I'm going to risk being rude and ping a few people who have spent some time on this repository who I would expect may have thoughts just as a I know otherwise the onslaught of GitHub notifications can hide things. @amoodie @EvanBianco @prisae @JesperDramsch @banesullivan @mycarta

from awesome-open-geoscience.

JustinGOSSES avatar JustinGOSSES commented on August 15, 2024

It occurred to me during a recent PR that I figured out where to go to figure out what links have broken a PR, which can be not at all obvious for a new maintainer. As part of this issue, it might help to have documentation for (1) how to fix merge conflicts and (2) where to find out what links are the problems when links breaking stops the PR.

This is what I put in a PR today and could be used as a starting point for documentation:

I clicked on the area that says DETAILS next to .github/workflows/link_checker.yml / linkChecker (pull_request) Failing after 27s then clicked on Lychee Link Checker then looked at the bottom of that output, where I found the message below:

[README.md]:
✗ [404] http://fuzzylas.appspot.com/ | Network error: Not Found
✗ [404] https://www.equinor.com/en/what-we-do/digitalisation-in-our-dna/volve-field-data-village-download.html | Network error: Not Found

from awesome-open-geoscience.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.