-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
92c9b96
commit e9a7a92
Showing
4 changed files
with
209 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,90 @@ | ||
# DataHive Community Code of Conduct | ||
|
||
The DataHive community is committed to fostering a welcoming, inclusive, and collaborative environment. This Code of Conduct outlines the expectations for all participants to ensure a positive and respectful community experience. | ||
|
||
--- | ||
|
||
## Our Standards | ||
|
||
### 1. **Be Respectful** | ||
- Treat all members of the community with respect, regardless of background, experience, or opinions. | ||
- Avoid derogatory or discriminatory comments based on race, gender, ethnicity, religion, disability, or any other personal characteristic. | ||
|
||
### 2. **Collaborate Openly** | ||
- Engage constructively in discussions, offering feedback and suggestions in a professional and courteous manner. | ||
- Be open to different viewpoints and work towards consensus whenever possible. | ||
|
||
### 3. **Maintain Integrity** | ||
- Be honest and transparent in all interactions. | ||
- Give credit where it is due and avoid plagiarism or misrepresentation of ideas. | ||
|
||
### 4. **Promote Inclusivity** | ||
- Encourage participation from diverse groups and ensure everyone feels valued and included. | ||
- Provide support and mentorship to new or less experienced community members. | ||
|
||
### 5. **Respect Privacy** | ||
- Avoid sharing sensitive or personal information without explicit consent. | ||
- Respect the confidentiality of private discussions and contributions. | ||
|
||
--- | ||
|
||
## Unacceptable Behavior | ||
|
||
The following actions are strictly prohibited in the DataHive community: | ||
|
||
- **Harassment**: Unwelcome comments, personal attacks, or any form of intimidation. | ||
- **Discrimination**: Behavior that excludes or marginalizes others based on personal characteristics. | ||
- **Spamming**: Posting irrelevant or excessive messages that disrupt discussions. | ||
- **Trolling**: Deliberately provoking or inflaming arguments. | ||
- **Unauthorized Sharing**: Distributing private or proprietary information without consent. | ||
|
||
--- | ||
|
||
## Reporting Violations | ||
|
||
If you experience or witness behavior that violates this Code of Conduct, please report it promptly: | ||
|
||
1. **Contact Moderators**: | ||
- Use the “Report” feature in the [community forums](/docs/onboarding/community/forums.md) to notify moderators. | ||
|
||
2. **Email Support**: | ||
- Send a detailed report to [[email protected]](mailto:[email protected]). | ||
|
||
3. **Anonymous Reporting**: | ||
- Submit an anonymous report through the [DataHive Support Portal](https://www.datahive.network/support). | ||
|
||
All reports will be treated confidentially and investigated promptly. | ||
|
||
--- | ||
|
||
## Consequences of Violations | ||
|
||
Violations of this Code of Conduct may result in: | ||
|
||
1. **Warning**: | ||
- A formal warning issued by moderators. | ||
|
||
2. **Temporary Suspension**: | ||
- Loss of access to community platforms for a specified period. | ||
|
||
3. **Permanent Ban**: | ||
- Removal from the community for repeated or severe violations. | ||
|
||
--- | ||
|
||
## Moderation | ||
|
||
Community moderators are responsible for ensuring adherence to this Code of Conduct. Moderators have the authority to: | ||
- Remove inappropriate content. | ||
- Issue warnings or suspensions. | ||
- Resolve disputes and mediate discussions. | ||
|
||
--- | ||
|
||
## Acknowledgment and Agreement | ||
|
||
By participating in the DataHive community, you acknowledge and agree to abide by this Code of Conduct. Let’s work together to build a thriving and supportive network. | ||
|
||
--- | ||
|
||
For questions or clarifications, please contact the moderation team via the [community forums](/docs/onboarding/community/forums.md) or email [[email protected]](mailto:[email protected]). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,7 +2,11 @@ | |
|
||
The DataHive network relies on a robust and efficient consensus mechanism to validate transactions, maintain integrity, and ensure decentralized governance. This guide outlines the consensus process, its importance, and the roles of node operators. | ||
|
||
--- | ||
[](https://www.datahive.network/nodes) | ||
[](https://x.com/getdatahive) | ||
[](https://t.me/datahiveofficial) | ||
[](https://quest.intract.io/project/datahive-h_lpnt) | ||
[](mailto:[email protected]) | ||
|
||
## Overview of the Consensus Mechanism | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,113 @@ | ||
# Support Tickets | ||
|
||
The DataHive support ticket system is designed to help node operators and stakeholders resolve issues, seek guidance, and provide feedback. This guide explains how to create, manage, and track support tickets effectively. | ||
|
||
--- | ||
|
||
## Overview of the Support Ticket System | ||
|
||
The support ticket system enables users to: | ||
- Report technical issues. | ||
- Request assistance with node setup or performance. | ||
- Submit feedback or feature requests. | ||
- Track the resolution progress for submitted tickets. | ||
|
||
--- | ||
|
||
## How to Submit a Support Ticket | ||
|
||
1. **Access the Support Portal**: | ||
- Visit the [DataHive Support Portal](https://www.datahive.network/). | ||
|
||
2. **Log In**: | ||
- Use your registered node operator credentials to log in. | ||
|
||
3. **Create a New Ticket**: | ||
- Click on the “New Ticket” button and fill out the required details: | ||
- **Category**: Select the type of issue (e.g., technical, billing, general support). | ||
- **Priority**: Indicate the urgency (low, medium, high). | ||
- **Subject**: Provide a brief summary of the issue. | ||
- **Description**: Include detailed information, steps to reproduce the issue, and any relevant screenshots or logs. | ||
|
||
4. **Submit the Ticket**: | ||
- Review the details and click “Submit.” | ||
|
||
--- | ||
|
||
## Ticket Categories | ||
|
||
| **Category** | **Description** | | ||
|-------------------------|-------------------------------------------------------------------------------| | ||
| **Technical Support** | Issues with node setup, performance, or software errors. | | ||
| **Billing and Payments**| Questions or issues related to license fees, rewards, or staking. | | ||
| **Feature Requests** | Suggestions for new features or improvements to the network. | | ||
| **General Support** | Miscellaneous queries or concerns not covered in other categories. | | ||
|
||
--- | ||
|
||
## Managing and Tracking Tickets | ||
|
||
1. **View Ticket Status**: | ||
- Log in to the support portal and navigate to the “My Tickets” section. | ||
- Check the status of each ticket: | ||
- **Open**: Ticket has been submitted and is awaiting review. | ||
- **In Progress**: Ticket is being actively worked on by the support team. | ||
- **Resolved**: Issue has been addressed, and the ticket is closed. | ||
|
||
2. **Respond to Updates**: | ||
- Reply to support team questions or provide additional information directly within the ticket. | ||
|
||
3. **Reopen Tickets**: | ||
- If an issue persists after resolution, reopen the ticket for further investigation. | ||
|
||
--- | ||
|
||
## Best Practices for Submitting Tickets | ||
|
||
1. **Provide Detailed Information**: | ||
- Include all relevant details to help the support team understand and resolve your issue quickly. | ||
|
||
2. **Categorize Accurately**: | ||
- Select the appropriate category and priority level to ensure your ticket is routed correctly. | ||
|
||
3. **Attach Supporting Documents**: | ||
- Upload logs, screenshots, or other files that can aid in diagnosing the issue. | ||
|
||
4. **Monitor Responses**: | ||
- Check for updates regularly and respond promptly to avoid delays. | ||
|
||
--- | ||
|
||
## Escalation Process | ||
|
||
If your issue is not resolved within the expected timeframe: | ||
1. **Contact Support**: | ||
- Reach out via the support portal to escalate your ticket. | ||
|
||
2. **Community Assistance**: | ||
- Engage with the [community forums](/docs/onboarding/community/forums.md) for additional support from peers. | ||
|
||
3. **Email the Support Team**: | ||
- Send an email to [email protected] for urgent concerns. | ||
|
||
--- | ||
|
||
## Frequently Asked Questions (FAQs) | ||
|
||
| **Question** | **Answer** | | ||
|--------------------------------------------|---------------------------------------------------------------------------| | ||
| How long does it take to resolve a ticket? | Resolution times vary based on priority and complexity. Most tickets are addressed within 24-48 hours. | | ||
| Can I submit tickets without logging in? | No, a registered account is required to submit and track support tickets. | | ||
| What if I submitted a ticket to the wrong category? | The support team will reassign it to the correct category. | | ||
|
||
--- | ||
|
||
## Additional Resources | ||
|
||
- [Monitoring Dashboard](/docs/onboarding/monitoring.md) | ||
- [Setup Guides](/docs/setup/README.md) | ||
- [Community Forums](/docs/onboarding/community/forums.md) | ||
|
||
--- | ||
|
||
The support ticket system ensures a smooth experience for all DataHive participants. For further assistance, visit the [DataHive Support Portal](https://www.datahive.network/support) or engage with the [community forums](/docs/onboarding/community/forums.md). |