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

chore: test workflow [DO NOT MERGE] #60

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 19 additions & 19 deletions cips/cip-1.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
cip: 1
title: Celestia Improvement Proposal Process and Guidelines
title: Celestia Improvement Proposal process and guidelines
status: Draft
type: Meta
author: Yaz Khoury <[email protected]>
Expand All @@ -10,32 +10,32 @@ created: 2023-04-13
## Table of Contents

* What is a CIP?
* CIP Rationale
* CIP Types
* CIP Work Flow
* CIP rationale
* CIP types
* CIP workflow
* Shepherding a CIP
* Core CIPs
* CIP Process
* CIP process
* What belongs in a successful CIP?
* CIP Formats and Templates
* CIP Header Preamble
* CIP formats and templates
* CIP header preamble
* author header
* discussions-to header
* type header
* category header
* created header
* requires header
* Linking to External Resources
* Data Availability Specifications
* Consensus Layer Specifications
* Networking Specifications
* Digital Object Identifier System
* Linking to external resources
* Data availability specifications
* Consensus layer specifications
* Networking specifications
* Digital object identifier system
* Linking to other CIPs
* Auxiliary Files
* Transferring CIP Ownership
* CIP Editors
* CIP Editor Responsibilities
* Style Guide
* Auxiliary files
* Transferring CIP ownership
* CIP editors
* CIP editor responsibilities
* Style guide
* Titles
* Descriptions
* CIP numbers
Expand All @@ -54,7 +54,7 @@ of the feature and a rationale for the feature. The CIP
author is responsible for building consensus within the
community and documenting dissenting opinions.

## CIP Rationale
## CIP rationale

We intend CIPs to be the primary mechanisms for proposing
new features, for collecting community technical input on
Expand All @@ -70,7 +70,7 @@ that they have implemented. This will give end users a
convenient way to know the current status of a given
implementation or library.

## CIP Types
## CIP types

There are three types of CIP:

Expand Down
Loading