openedx / openedx/openedx-events

State of the art repository to exemplify usage

Open
#359 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation
Dominant language
Python
Stars
13
Forks
33
Avg merge
14h 37m
Merged PRs (30d)
4

Description

Description

To aid developers in understanding and effectively utilizing the events library, we propose creating a state-of-the-art repository. This repository will serve as a comprehensive example, showcasing various use cases in different scenarios.

Expected Result

  • A well-documented and organized repository that developers can refer to for guidance on using events.
  • Improved developer understanding and adoption of the events library through practical examples.
  • Enhanced ability for developers to implement and debug events in their own projects.

Key Components

  1. Comprehensive Examples:

    • Include a variety of examples demonstrating different use cases for the events library.
    • Cover basic to advanced scenarios, ensuring a wide range of applications are addressed.
  2. Detailed Documentation:

    • Provide clear and thorough documentation within the repository, including a README file that outlines the purpose and structure of the repository.
    • Include comments within the code to explain the functionality and purpose of each example.

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.

Research direction

Review the existing openedx-events package and its current usage documentation first; the issue names no files, tests, or entry points. Define the example repository's scope and structure, then ensure it contains documented basic and advanced event-library use cases, code comments, and a README explaining its purpose and organization.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.