Move custom runtimes and infra to eoapi-devseed

Open
#191 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
shell
Domain
documentation, infrastructure

Research direction

Start by auditing the eoAPI repository for its custom runtime and infrastructure content, then compare the target eoapi-devseed repository. Done means the custom runtime and infrastructure material is in eoapi-devseed and eoAPI retains only documentation and issues.

Written by the indexing model from the issue text.

Description

enhancement

let's move all eoapi Custom part to its own repo: https://github.com/developmentseed/eoapi-devseed

/eoapi should just host the documentation and issues

Dominant language
Shell
Stars
330
Forks
33
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from developmentseed/eoAPI

All issues in developmentseed/eoAPI

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.