JuliaClimate / JuliaClimate/meta
Transferring some repositories over
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
I plan to transfer over both the ClimateSatellite.jl, GeoRegions.jl and ClimateERA.jl repositories into the JuliaClimate organization. Would like to request permission to modify settings for them as well.
I might be renaming the ClimateERA.jl repository, however. Does anyone have suggestions for names? Or do people think that ClimateERA is fine?
The following things still need to be done for these repositories:
ClimateSatellite.jl- Documentation
- Jupyter Notebook Examples
- TRMM, RSS and MODIS Satellite retrieval algorithms
ClimateERA.jl(or whatever name I finalize on)- Documentation
- Jupyter Notebook Examples
- Calculations for basic variables not given (e.g. meridional streamfunction, eddy kinetic energy, etc.)
All questions and comments are welcome.
On a separate but related notebook, where should I put Jupyter Notebook examples? In a separate repository here? Or inside my packages?
Tagging @gaelforget, @Balinus and @Datseris as they are the main contributors to most of the packages of the JuliaClimate community thus far.
Edit: Transferring GeoRegionsjl over as well. Same issues with Documentation and examples also apply, but I plan to get them up once the semester ends.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the transfer and settings requests for ClimateSatellite.jl, GeoRegions.jl, and ClimateERA.jl, including the possible ClimateERA rename. The issue also lists documentation, Jupyter Notebook examples, satellite retrieval algorithms, and basic-variable calculations; the work is complete only after those priorities and the notebook location are decided and addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia, jupyter-notebook
- Domain
- data, developer-experience, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100