Quantify Issues

Recent GitHub Issues Activity

_{Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.}

Quantify commits

Quantified Commit Activity Over 30 Days

Developer	Avatar	Branches	PRs	Commits	Files	Changes
bol-van		1	0/0/0	108	340	53390
SashaXser		1	1/1/0	2	1	4
Dmitry		1	1/1/0	1	1	2
Deleted user (ghost)		0	2/0/2	0	0	0
None (NewUse)		0	0/0/2	0	0	0
[anp/hsw] (anphsw)		0	0/0/1	0	0	0
None (UnkwUsr)		0	0/0/1	0	0	0
ValdikSS (ValdikSS)		0	0/0/1	0	0	0
Andrey Kiryanov (kiryanov)		0	0/0/1	0	0	0
None (GoSSy4691)		0	1/0/1	0	0	0
None (conc3rned)		0	0/0/1	0	0	0
Bubun Das (bubundas17)		0	0/0/1	0	0	0
testing (testing765)		0	1/0/1	0	0	0
totoblabla (totoblabla3)		0	1/0/1	0	0	0
Livia Medeiros (LiviaMedeiros)		0	0/0/1	0	0	0

_{PRs: created by that dev and opened/merged/closed-unmerged during the period}

Report On: Fetch issues

Recent Activity Analysis

The GitHub repository for the zapret project currently has 114 open issues, indicating ongoing user engagement and potential challenges with the software. Recent activity shows a mix of technical inquiries and troubleshooting related to various functionalities, particularly concerning bypassing restrictions on platforms like YouTube and Discord. A notable theme is the recurring issues with specific configurations that affect the performance of the tool across different devices and networks.

Several issues highlight common problems, such as users experiencing difficulties with voice channels on Discord, slow loading times for YouTube videos, and connectivity issues with specific websites. The discussions often reveal a lack of clarity around configuration settings, suggesting that users may struggle to implement effective strategies without more streamlined guidance or examples.

Issue Details

Most Recently Created Issues

1. Issue #677: blockcheck - 0 рабочих стратегий

   • Priority: Normal
   • Status: Open
   • Created: 1 day ago
   • Comments: Users report that no working strategies were found for Discord after running blockcheck.

2. Issue #675: 50-discord ломает часть интернета

   • Priority: High
   • Status: Open
   • Created: 1 day ago
   • Comments: Users are facing errors when using the 50-discord strategy, leading to connection resets on various sites.

3. Issue #672: У всех дс не работает сейчас?

   • Priority: Normal
   • Status: Open
   • Created: 2 days ago
   • Comments: Users are reporting widespread issues with Discord connectivity, suggesting possible blocks by ISPs.

4. Issue #671: Не запускается новый zapret

   • Priority: Normal
   • Status: Open
   • Created: 2 days ago
   • Comments: A user cannot start the new version of zapret, indicating potential installation or compatibility issues.

5. Issue #667: Помощь

   • Priority: Low
   • Status: Open
   • Created: 2 days ago
   • Comments: A new Linux user seeks assistance in configuring zapret for proper functionality.

Important Issues

• Issue #661: проблема с установкой пакета iptables-mod-nfqueue на роутере Xiaomi AX6000

  • Users are unable to install critical packages needed for zapret's functionality on specific routers.

• Issue #657: Не разблокирует Youtube

  • Users report that YouTube is not being unblocked despite attempts to configure zapret correctly.

• Issue #675: 50-discord ломает часть интернета

  • This issue has gained traction due to its impact on multiple users experiencing internet disruptions when using the specified strategy.

Common Themes and Implications

The ongoing issues suggest several common themes:

• Users frequently encounter problems with specific configurations that lead to service interruptions, particularly affecting popular platforms like Discord and YouTube.
• There is a significant need for clearer documentation and examples that can help users navigate complex configurations effectively.
• Many users express frustration over intermittent connectivity issues, which may be linked to ISP actions or inadequate configurations within zapret itself.
• The community appears active in troubleshooting and sharing solutions; however, the reliance on individual experimentation indicates a gap in comprehensive guidance from the developers.

The implications for the project include a potential need for improved documentation, more robust testing of configurations before release, and perhaps a reevaluation of how updates are communicated to users regarding changes in functionality or compatibility.

Report On: Fetch pull requests

Overview

The analysis of the provided pull requests (PRs) for the zapret project reveals a focus on enhancing functionality, improving documentation, and addressing issues related to system compatibility and performance. The PRs cover a range of topics from minor typo fixes to significant feature additions like GitHub Actions for automated builds on Windows.

Summary of Pull Requests

1. PR #666: Update readme.eng.md

   • Significance: Minor documentation fix.
   • Notable: Quick turnaround from creation to closure, indicating active maintenance.

2. PR #654: Add Github Actions builder for Windows

   • Significance: Introduction of automated builds for Windows, enhancing CI/CD practices.
   • Notable: Closed without merging, suggesting either a change in direction or an alternative solution was found.

3. PR #617: Быстрая команда для простой установки на MacOS

   • Significance: Proposed convenience script for MacOS installations.
   • Notable: Closed without merging due to concerns about universality and maintainability.

4. PR #457: feat (blockcheck): add ask skip timeout

   • Significance: Feature addition to blockcheck script for better user control during timeouts.
   • Notable: Closed without merging; discussion indicates differing opinions on the necessity and implementation approach.

5. PR #429: Add simple luci configuration for tpws

   • Significance: Attempt to add a LUCI interface for easier configuration of tpws on OpenWRT.
   • Notable: Closed without merging; highlights challenges in integrating with legacy systems and the preference for separate projects for specific functionalities.

Analysis of Pull Requests

The PRs reflect an active effort to enhance the zapret project through community contributions and internal improvements. However, several PRs were closed without merging, which could indicate:

• A need for clearer contribution guidelines or a more structured process for evaluating PRs.
• Potential disagreements within the core team regarding the project's direction or the inclusion of certain features.
• Challenges in maintaining compatibility with older systems while introducing new features or improvements.

The introduction of automated builds via GitHub Actions, despite not being merged, suggests an interest in improving development workflows. This aligns with broader industry trends towards automation in software development to ensure consistency and reduce manual errors.

The discussions around PRs also highlight the complexity of the zapret project, particularly in terms of its configuration and operation across different platforms. This complexity can be a barrier to entry for new users and contributors, emphasizing the importance of comprehensive documentation and possibly more user-friendly configuration tools.

In conclusion, while the zapret project shows strong community engagement and a commitment to continuous improvement, there are areas that could benefit from more structured processes and clearer communication regarding project goals and contributions.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members:

• bol-van

  • Recent Activity:
  • Code Improvements: Removed unneeded code across multiple files in nfq and tpws.
  • Bug Fixes: Fixed issues related to uninitialized pointers, invalid port filter messages, and crashes.
  • Feature Additions: Implemented reading configuration from a file for both nfqws and tpws.
  • Documentation Updates: Updated various documentation files including README, quick_start, and changes.txt.
  • Binary Updates: Updated binaries for various architectures.
  • Collaboration: Merged a pull request from contributor 2korzhik, indicating collaboration.

• 2korzhik

  • Recent Activity:
  • Contributed a single commit fixing a typo in readme.eng.md.
  • Collaboration: Opened a pull request which was merged.

• SashaXser

  • Recent Activity:
  • Made two commits addressing code scanning alerts.
  • Collaboration: Opened and merged a pull request.

Patterns and Themes:

• Dominance of bol-van: The majority of recent activity (108 commits) is attributed to bol-van, showcasing significant engagement with code maintenance, bug fixes, and feature enhancements.
• Focus on Documentation: A consistent effort in updating documentation suggests an emphasis on user guidance and clarity.
• Collaborative Efforts: While bol-van is the primary contributor, there is evidence of collaboration with other team members through merged pull requests.
• Bug Fixes vs. Features: A balanced approach between fixing bugs and adding features indicates a responsive development cycle aimed at improving both stability and functionality.

Conclusions:

The development team is actively engaged in maintaining and enhancing the zapret project. Bol-van's extensive contributions highlight leadership in the project, while collaboration with others indicates a healthy team dynamic. The focus on documentation alongside code improvements suggests a commitment to user experience.