# Final_1

**Repository Path**: zhu-lee-1/final_1

## Basic Information

- **Project Name**: Final_1
- **Description**: Final Project Template Repo for DA402 2025
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 73
- **Created**: 2025-06-24
- **Last Updated**: 2025-06-24

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# Gitee Repository Analysis Report

## Chosen Repositories

### 1. b2b2c
- **Gitee URL**: https://gitee.com/zkmall/b2b2c
- **Short Name**: b2b2c
- **Reason for Selection**: This e-commerce platform project demonstrates a mature development process with contributions from multiple team members. Its 3+ year history and 361 commits provide substantial data for analysis of team collaboration patterns in commercial projects.

### 2. maku-boot
- **Gitee URL**: https://gitee.com/makunet/maku-boot
- **Short Name**: maku-boot  
- **Reason for Selection**: As a rapid development framework, this project shows interesting patterns of a developer-focused tool with a dominant main contributor (阿沐 with 586/622 commits). The 2-year activity period offers insights into solo-driven open source projects.

## Comparative Analysis & Key Findings

### Development Patterns
- **Commit Frequency**: maku-boot shows higher commit frequency (622 commits in 2 years) compared to b2b2c (361 commits in 3+ years), indicating more active development
- **Contributor Distribution**: 
  - b2b2c has more balanced contributions among top 3 contributors (hupeng 154, guchengwuyue 82, taozi 67)
  - maku-boot is dominated by one contributor (阿沐 with 94% of total commits)
  
### Work Habits
- **Weekday Patterns**:
  - Both projects show highest activity on weekdays
  - b2b2c has more consistent weekend activity (15% of commits)
  - maku-boot has minimal weekend activity (3% of commits)

### Code Changes
- **Lines Changed**:
  - b2b2c shows higher median changes (16 lines) vs maku-boot (12 lines)
  - Both have high average changes due to outlier commits (b2b2c 2651, maku-boot 161)
- **Files Changed**:
  - Similar median values (1 file per commit)
  - b2b2c shows higher average (49 files) indicating more comprehensive updates

## Project Structure Implementation

### Repository Analysis Scripts
- `report-b2b2c.py`: Analyzes the b2b2c repository
- `report-maku-boot.py`: Analyzes the maku-boot repository

### Generated Reports
- `report-b2b2c.md`: Contains full analysis of b2b2c project
- `report-maku-boot.md`: Contains full analysis of maku-boot project

### Visualization Files
All charts are stored in the `visuals/` directory including:
- Top contributors charts
- Monthly commit activity
- Weekday distribution
- Cumulative growth
- Lines/files changed distributions

## Technical Implementation

### Core Libraries Used
- GitPython for repository interaction
- Matplotlib and Seaborn for visualizations
- NumPy for statistical calculations

### Key Features
1. **Caching System**: Commit stats are cached in `commit_stats.txt` to avoid recomputation
2. **Error Handling**: Robust try-catch blocks handle various edge cases
3. **Temporary Data**: Intermediate JSON files (`temp_*.json`) store metrics for comparison
4. **Chinese Support**: Special font handling for Chinese contributor names

## Team Collaboration

### Task Division
- Member A: Developed `report-b2b2c.py` and corresponding report
- Member B: Developed `report-maku-boot.py` and corresponding report
- Collaborative: Worked together on comparison logic and README content

### Git Workflow
- Feature branches used for all developments
- Pull requests with clear descriptions for all merges
- Regular commits with descriptive messages

## Visualization Highlights

### b2b2c
![b2b2c Top Contributors](visuals/top_contributors.png)
*Top 10 contributors showing balanced distribution among team members*

### maku-boot
![maku-boot Cumulative Growth](visuals/cumulative_commits.png) 
*Steady growth pattern dominated by primary contributor*

## Conclusion

This analysis reveals two distinct open source development models:
1. **Team-based (b2b2c)**: Balanced contributions across multiple developers with consistent activity patterns
2. **Solo-driven (maku-boot)**: Dominated by primary developer with rapid iteration cycles

The project successfully implemented all required visualizations while adding robust error handling and caching mechanisms. The comparative analysis provides valuable insights into different open source collaboration patterns.