apache/fluss

Add documentation for FIP (Flink Improvement Proposal) contribution guide

Open

#3,179 opened on Apr 23, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (570 forks)auto 404
component=websitegood first issue

Repository metrics

Stars
 (1,979 stars)
PR merge metrics
 (PR metrics pending)

Description

Search before asking

  • I searched in the issues and found nothing similar.

Description

Summary

The Fluss project currently lacks a formalized process and clear guidelines for submitting and reviewing Fluss Improvement Proposals. New contributors and community members often struggle to understand the proposal lifecycle, required format, and review criteria. This issue tracks the creation of comprehensive documentation to streamline FIP contributions.

Willingness to contribute

  • I'm willing to submit a PR!

Contributor guide

Research direction
Read existing contribution guidelines and the FIP template from other Apache projects. Draft a new documentation page outlining the FIP lifecycle, required sections, and review process.
Tech stack
java
Domain
backenddocumentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80