Create a SciTools developer diary

Open
#6,992 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
documentation

Research direction

Start by reviewing the linked SciTools/.github#174 prototype and the Peloton Recent Changes view. Define the diary’s update checklist or formula and how it will be maintained, including the proposed driver and timekeeper roles; done means a documented, repeatable process is agreed and ready for core developers to use.

Written by the indexing model from the issue text.

Description

Dragon Sub-Task 🦎 Type: User Experience
  • Prototype: SciTools/.github#174

This is important to reflect what SciTools core devs are working on, to show that there plenty of life in these repositories (even when it is under the surface), and to give a better idea of delivery timelines.

How to keep it updated?

Suggest dovetailing with this Peloton view: 1️⃣ Recent Changes 📢 · 🚴 Peloton. Attendees can swarm on it, as we do with other comments during that meeting.

Introducing this will make timekeeping more important: perhaps we have rotating roles of 'driver' and 'timekeeper'.

Need to make the updates as easy as possible via a checklist/formula for what to include / what to update.

Dominant language
Python
Stars
724
Forks
317
Avg merge
3d 20h
Merged PRs (30d)
9

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 SciTools/iris

All issues in SciTools/iris

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.