mirror of
				https://github.com/karl0ss/homepage.git
				synced 2025-11-04 08:20:58 +00:00 
			
		
		
		
	Update PR guidelines
This commit is contained in:
		
							parent
							
								
									6e8fe45818
								
							
						
					
					
						commit
						f473569cb2
					
				@ -48,15 +48,14 @@ self-hosted / open-source alternative, we ask that any widgets, etc. are develop
 | 
				
			|||||||
 | 
					
 | 
				
			||||||
## New Feature Guidelines
 | 
					## New Feature Guidelines
 | 
				
			||||||
 | 
					
 | 
				
			||||||
- New features should be linked to an existing feature request with at least 10 'up-votes'. The purpose of this requirement is to avoid the addition (and maintenance) of features that might only benefit a small number of users.
 | 
					- New features should usually be linked to an existing feature request. The purpose of this requirement is to avoid the addition (and maintenance) of features that might only benefit a small number of users.
 | 
				
			||||||
- If you have ideas for a larger feature, please open a discussion first.
 | 
					- If you have ideas for a larger feature you may want to open a discussion first.
 | 
				
			||||||
- Please note that though it is a requirement, a discussion with 10 'up-votes' in no way guarantees that a PR will be merged.
 | 
					 | 
				
			||||||
 | 
					
 | 
				
			||||||
## Service Widget Guidelines
 | 
					## Service Widget Guidelines
 | 
				
			||||||
 | 
					
 | 
				
			||||||
To ensure cohesiveness of various widgets, the following should be used as a guide for developing new widgets:
 | 
					To ensure cohesiveness of various widgets, the following should be used as a guide for developing new widgets:
 | 
				
			||||||
 | 
					
 | 
				
			||||||
- Please only submit widgets that have been requested and have at least 10 'up-votes'. The purpose of this requirement is to avoid the addition (and maintenance) of service widgets that might only benefit a small number of users.
 | 
					- Please only submit widgets that target a feature request discussion with at least 10 'up-votes'. The purpose of this requirement is to avoid the addition (and maintenance) of service widgets that might only benefit a small number of users.
 | 
				
			||||||
- Note that we reserve the right to decline widgets for projects that are very young (eg < ~1y) or those with a small reach (eg low GitHub stars). Again, this is in an effort to keep overall widget maintenance under control.
 | 
					- Note that we reserve the right to decline widgets for projects that are very young (eg < ~1y) or those with a small reach (eg low GitHub stars). Again, this is in an effort to keep overall widget maintenance under control.
 | 
				
			||||||
- Widgets should be only one row of blocks
 | 
					- Widgets should be only one row of blocks
 | 
				
			||||||
- Widgets should be no more than 4 blocks wide and generally conform to the styling / design choices of other widgets
 | 
					- Widgets should be no more than 4 blocks wide and generally conform to the styling / design choices of other widgets
 | 
				
			||||||
 | 
				
			|||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user