Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address Project Maintenance Concerns and Improve Community Engagement #723

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

MalloryHuston
Copy link

This PR aims to address concerns regarding the Pyshark repository's maintenance and enhance its alignment with community expectations. Since the last release on April 26, 2023 (v0.6), there have been no significant updates, raising questions about the project's ability to keep up with dependency updates and user needs.

Key Changes Proposed:

  1. Documentation Updates: Addition of a CONTRIBUTING.md file to encourage and guide community contributions effectively.
  2. Issue Review: Initial review and categorization of open issues to identify priority areas for bug fixes and feature enhancements.
  3. Community Update: Suggest creating a project roadmap or a pinned issue to inform users about the current state and future direction of Pyshark.

Why This Change is Needed:

  1. Addressing Stagnation: The repository lacks updates, which may impact functionality with modern dependencies and compatibility with newer Python versions.
  2. Encouraging Contributions: Adding a CONTRIBUTING.md will lower the entry barrier for new contributors, fostering a collaborative environment.
  3. Improved Communication: A clear roadmap or pinned update will keep users informed and maintain their trust in the project's utility.

Proposed Actions:

  • Add CONTRIBUTING.md file (draft attached or linked).
  • Review and categorize existing issues for easier prioritization.
  • Collaborate on creating a roadmap or community update.

Benefits:

  • Increased project visibility and trust within the community.
    
  • More active engagement from contributors and users.
    
  • Improved issue tracking and prioritization.
    

Checklist:

  • I have reviewed the open issues and existing PRs to avoid duplication.
  • I followed the repository's documentation and style conventions (as observed in the codebase).
  • This PR includes actionable and specific recommendations.
  • I am available to respond to maintainers' feedback and collaborate on further improvements.

References:

  1. Repository Last Release: v0.6 on April 26, 2023
    
  2. GitHub Docs on Open Source Contributions: Contributing to Projects
    

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant