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.

Sign up for GitHub

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

Update README.md #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 14 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,24 @@

### Processes

- workflow for patching/maintaining leaves some details out such as what automated steps take place, and what manual steps are present
- how to accept a patch, or as a non-committer maintainer, to indicate it's ready for the next stage? refer to maintainer flags, keywords, patch attributes
- who can mark a patch attachment as obsolete?
- what is the BZ keywords field for?

### Contributing

- please recommend some reasonably complex ports that are considered best practice; we all copy-pasta but it helps to have good sauce to refer to.
- a default / simple poudriere set up makes a huge difference to this

## Port Maintenance

Need a one-stop checklist for what to do before submitting a port
- portlint
- poudriere output
- confirming `sudo make deinstall clean fetch makesum stage stage-qa check-orphans check-plist package install` works fine
- what variants of FreeBSD should be checked (9,10,current ?) amd64? poudriere does make this easy

## Issue Tracking

### Workflow
Expand Down