The Contributor Hub is the central collaborative platform for gathering and managing community-driven contributions within the midnightntwrk organization. It serves as the primary entry point for proposing new content, requesting features, reporting issues, or ideating for dApps on the Midnight Network.
- Public Boards: For transparency in triage and task management.
- Automated Workflow (coming soon): Issues are automatically added to boards and moved based on labels.
- Inclusive Contribution: Open to all, with guidelines for high-quality submissions.
We welcome contributions of all types, including code, documentation, and technical content.
Use our GitHub Issue Forms to submit:
- Bug Reports: Provide detailed information including steps to reproduce and expected behavior. Note: if a bug pertains to a specific repo (like
midnight-js), report it there directly. - Feature Requests: Clearly describe the proposed feature, its benefits, and the expected outcome.
- Content Proposals: Propose new tutorials, blog posts, or documentation improvements.
- Fork the Repo: Create your own fork of the repository.
- Create a Branch: Use a descriptive name prefixed with a short moniker (e.g.,
jill-my-feature). - Follow Standards: Adhere to the coding style guides and ensure new functionality includes unit and integration tests.
- License Header: Ensure all new files include the Apache-2.0 license header.
- Submit: Open a PR to the main repository. Avoid
--forcepushes to assist the review process.
If you are participating in a Midnight event (such as Hacktoberfest or the Midnight Summit), you can showcase your work here:
- Navigate to the
/eventsfolder. - Create a Markdown file in the specific event sub-folder (e.g.,
events/hacktoberfest-2025/your-handle.md). - Fill out the submission template found in the
events/README.md.
We run content and development bounties rewarded in NIGHT tokens. All participants must complete KYC verification before receiving tokens.
- Bounty Program Terms: Standard terms for all bounty participants.
- Contributor Agreement: Additional terms for premium-tier engagements.
- Submit a Bounty: Use the Content Bounty issue template to submit your work.
- Code of Conduct: We are committed to a positive, inclusive, and harassment-free environment. Please review our CODE_OF_CONDUCT.md.
- Security Policy: Report security vulnerabilities privately via GitHub's private reporting or by emailing
security@midnight.foundation. - License: This project is licensed under the Apache License, Version 2.0.
To standardize submissions and make it easier for contributors, we provide the following issue templates:Content Proposal: For suggesting new content like articles, tutorials, or resources. Use this to propose ideas that educate or engage the community.
- Feature Request/Suggestion: For proposing new features, enhancements, or suggestions to improve existing tools or processes.
- Bug: For reporting defects, errors, or unexpected behavior. Include reproduction steps, environment details, and screenshots if possible.
- dApp Proposal: For ideas related to decentralized applications, including concepts, integrations, or improvements for dApps in our ecosystem.
When creating an issue, select the appropriate template from the "New Issue" page. This auto-applies relevant labels (e.g., bug, feature-request-suggestion) for better categorization.
Our workflow ensures every submission is reviewed fairly and efficiently. Issues start in the Contributor Board for triage and, if approved, move to the Grab n Go Board for contributors to pick up. Both boards are public for transparency.
Columns (based on the "Status" field):
- New: Entry point for fresh issues. Community members can view and comment.
- In Triage: Active review by the triage committee (validity, priority, labels).
- Needs Discussion: For issues requiring broader feedback or clarification.
- Rejected: Invalid or out-of-scope issues, with explanations for transparency.
The triage committee meets periodically to review and move issues. If legitimate, they add a triaged label, triggering an automation to move it to the Grab n Go Board.
The Grab n Go Board showcases approved, ready-to-work-on tasks. It's a backlog for contributors.Columns (based on the "Status" field):
- Ready: Triaged issues awaiting pickup (e.g., labeled good-first-issue for beginners).
- In Progress: Tasks being worked on (assign yourself and update via PRs).
- Done: Completed issues (auto-moves on close).
Automations handle movement between boards and status updates for efficiency.
We are committed to a positive, inclusive community. Please adhere to our CODE_OF_CONDUCT.md.
We welcome contributions from everyone! Follow these steps:
- Fork the Repo: Click "Fork" on the top right.
- Create an Issue: Use templates to submit ideas or bugs.
- Work on Tasks: Browse the Grab n Go Board, assign yourself to a "Ready" issue.
- Submit a Pull Request: Want to improve Community-hub? Submit a PR and follow our CONTRIBUTING.md for details on code style, testing, and commits.
- Labels and Priorities: Use labels like priority:high, help-wanted, or good-first-issue to guide contributions.
For non-code contributions (e.g., docs, proposals), submit via issues. All PRs require review by at least one maintainer.
If you’re participating in a Midnight event such as a hackathon, summit, or Hacktoberfest, you can showcase your work and contributions directly in this repository.
Steps:
- Navigate to the
/eventsfolder. - Open the folder for your event (e.g.
events/hacktoberfest-2025/). - Inside, create a new Markdown file named after your handle or team: events//.md
- Copy and fill out the submission template. It works for projects, tutorials, threads, or any other type of contribution.
- Commit and open a Pull Request.
Once your PR is merged, your submission will appear in the event’s showcase page automatically.
Tip: Keep filenames lowercase and hyphenated, and make sure your front-matter fields match the example format.