Editing
Theory of PR Fermentation
(section)
From H4KS
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== The Process == When a pull request is opened, it is usually met with initial excitement or scrutiny. However, as time progresses, developers may shift their focus to other tasks, causing the PR to remain unattended. This period of inactivity allows the following benefits to develop: 1. **Maturation of Code**: Just as wine matures with age, code can benefit from time to be revisited with a fresher perspective. Developers grow, learn, and may have new insights that improve the proposed changes. 2. **Gathering Community Feedback**: During the waiting period, other community members may notice the PR and provide valuable feedback or suggestions that the original author might not have considered. 3. **Incorporation of New Practices**: Over time, coding practices and standards may evolve. A PR that sits can be adjusted to align with the latest development trends and technologies.
Summary:
Please note that all contributions to H4KS are considered to be released under the Creative Commons Attribution (see
H4KS:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Page actions
Page
Discussion
Read
Edit
History
Page actions
Page
Discussion
More
Tools
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Search
Tools
What links here
Related changes
Special pages
Page information