Reminder: This Month in Forest Submission

Open
#7,823 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
10/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation

Research direction

This is a recurring maintainer checklist, not a code change, and no files or tests are named. Start by reviewing the past month's merged pull requests and issues in the ChainSafe/forest repository and the Forest Slack channels for notable updates. Done means a draft summary is shared with the team, published in the Forest announcements category of GitHub Discussions, pinned, and posted to #fil-forest-announcements.

Written by the indexing model from the issue text.

Description

Type: Task

Each month, we put together a summary of the latest Forest updates for our community. Use this reminder and checklist to get ready for the next This Month in Forest post. Ensure that you include it in the final sprint of the month.

Checklist for This Month in Forest

When preparing the summary, keep these points in mind:

  • Review the past month's pull requests and issues on the Forest GitHub repository. Is there anything notable to highlight?
  • Check the Forest Slack channels for any significant discussions or announcements.
  • Is there any event upcoming or recently held that should be mentioned?
  • Are there mandatory updates or changes that users should be aware of?
  • Are there new contributors or community members to recognize?

After gathering the information:

  • Organize the collected information into a coherent summary.
  • Gather any relevant statistics or metrics that showcase the project's progress.
  • Draft the summary and share it with the team for feedback.
  • Publish it to the Forest announcements on GitHub Discussions
  • Pin it in the discussions tab for visibility.
  • Re-publish on other channels, e.g., #fil-forest-announcements on Slack.
  • Let the content team know for further dissemination.
Dominant language
Rust
Stars
700
Forks
201
Avg merge
1d 17h
Merged PRs (30d)
65

Getting set up

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 ChainSafe/forest

All issues in ChainSafe/forest

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.