sligter/LandPPT - Open Source PR Review Scorecard

一个基于LLM的演示文稿生成平台,能够自动将文档内容转换为专业的PPT演示文稿。平台支持多种AI模型,提供丰富的模板和样式选择,让用户能够创建高质量的演示文稿。

C-Rank Grade: B (Solid) - 50/100

External PR Merge Rate: 79%

Response Time: 17h

First Timer Success: 67%

Frequently Asked Questions

Is sligter/LandPPT welcoming to first-time open-source contributors?

sligter/LandPPT has a recorded first-timer success rate of 66.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in sligter/LandPPT respond to incoming external pull requests in approximately 16.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 50.0 C-Rank™ score (B Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 50.0 places sligter/LandPPT in the B tier.

What is the external contributor pull request merge rate for sligter/LandPPT?

The external contributor pull request merge rate for sligter/LandPPT is 78.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in sligter/LandPPT?

sligter/LandPPT does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

sligter
sligter/LandPPTB•Solid3.6k
GitHub
Back to Explorer
sligter

sligter/LandPPT

3,617
InactiveB•Solid(50/100)Low Sample (<20 PRs)Python

一个基于LLM的演示文稿生成平台,能够自动将文档内容转换为专业的PPT演示文稿。平台支持多种AI模型,提供丰富的模板和样式选择,让用户能够创建高质量的演示文稿。

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Mentor

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
25%

Responsive & active maintainer team in sligter/LandPPT. Reviews pull requests with focus on project architectural goals.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Use conventional commit messages and clean branch names
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
16 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
78.6%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
66.7%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
CRITICAL BUS FACTOR
Single maintainer
No active GitHub maintainers found (may review internally on Gerrit or internal tools)
Diagnostic Health HUD
78.6%
Merge Gauge
66.7%
1st-Timer
Community Vibe69/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for sligter/LandPPT
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/sligter/LandPPT)](https://getmerged.abhishekco.de/sligter/LandPPT?utm_source=github&utm_medium=badge)

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for sligter/LandPPT.

View all good first issues directly on GitHub

Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for sligter/LandPPT

When evaluating whether to contribute to sligter/LandPPT, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of sligter/LandPPT acknowledge new external contributions in approximately 16 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.6% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to sligter/LandPPT

01

Is sligter/LandPPT welcoming to first-time open-source contributors?

sligter/LandPPT has a recorded first-timer success rate of 66.7%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~16 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 50.0 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 50.0 places sligter/LandPPT in the Solid tier.

04

What is the external contributor pull request merge rate for sligter/LandPPT?

The external pull request merge rate is 78.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in sligter/LandPPT?

sligter/LandPPT does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for sligter/LandPPT are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.