kopia lustrzana https://github.com/collective/icalendar
				
				
				
			rename contributor to collaborator
							rodzic
							
								
									ce0de32248
								
							
						
					
					
						commit
						b8be6256a9
					
				| 
						 | 
				
			
			@ -11,6 +11,8 @@ Minor changes:
 | 
			
		|||
- Augmented fuzzer to optionally convert multiple calendars from a source string
 | 
			
		||||
- Added additional exception handling of defined errors to fuzzer, to allow fuzzer to explore deeper
 | 
			
		||||
- Added more instrumentation to fuzz-harness
 | 
			
		||||
- Rename "contributor" to "collaborator" in documentation
 | 
			
		||||
 | 
			
		||||
Breaking changes:
 | 
			
		||||
 | 
			
		||||
- ...
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
| 
						 | 
				
			
			@ -31,10 +31,15 @@ Maintainers need this:
 | 
			
		|||
    by adding the GitHub username to the list of "Required Reviewers".
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
Contributors
 | 
			
		||||
------------
 | 
			
		||||
Collaborators
 | 
			
		||||
-------------
 | 
			
		||||
 | 
			
		||||
Collaborators are people with write access to the repository.
 | 
			
		||||
As a collaborator, you can
 | 
			
		||||
 | 
			
		||||
- merge Pull Requests,
 | 
			
		||||
- initiate a new release, see below.
 | 
			
		||||
 | 
			
		||||
Contributors here are people with write access to the repository.
 | 
			
		||||
We want to have as many knowledgeable people with write access taking responsibility as possible for these reasons:
 | 
			
		||||
 | 
			
		||||
- a constant flow of fixes and new features
 | 
			
		||||
| 
						 | 
				
			
			@ -44,14 +49,14 @@ We want to have as many knowledgeable people with write access taking responsibi
 | 
			
		|||
 | 
			
		||||
Nobody should merge their own pull requests.
 | 
			
		||||
If you like to review or merge pull requests of other people and you have shown that you know how to contribute,
 | 
			
		||||
you can ask for becoming a contributor or a maintainer asks you if you would like to become one.
 | 
			
		||||
you can ask for becoming a collaborator or a maintainer asks you if you would like to become one.
 | 
			
		||||
 | 
			
		||||
New Releases
 | 
			
		||||
------------
 | 
			
		||||
 | 
			
		||||
This explains how to create a new release on `PyPI  <https://pypi.org/project/icalendar/>`_.
 | 
			
		||||
 | 
			
		||||
Since contributors and maintainers have write access the the repository, they can start the release process.
 | 
			
		||||
Since collaborators and maintainers have write access the the repository, they can start the release process.
 | 
			
		||||
However, only people with ``PyPI environment access for GitHub Actions`` can approve an automated release to PyPI.
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			@ -147,7 +152,3 @@ This section contains useful links for maintainers and contributors:
 | 
			
		|||
 | 
			
		||||
- `Future of icalendar, looking for maintainer #360 <https://github.com/collective/icalendar/discussions/360>`__
 | 
			
		||||
- `Comment on the Plone tests running with icalendar <https://github.com/collective/icalendar/pull/447#issuecomment-1277643634>`__
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Ładowanie…
	
		Reference in New Issue