|Summary:||Workflow for submitting patches is not documented on http://freebsd.org|
|Component:||Documentation||Assignee:||freebsd-doc (Nobody) <doc>|
|Severity:||Affects Only Me||CC:||emaste, rmm1.bob, smars|
Description gelraen.ua 2014-05-12 11:30:00 UTC
http://freebsd.org is not really friendly to contributors. They have to figure out on their own that they should submit patches via creating PR in GNATS. Ideally, there should be a page that describes what contributors need to do to have their patches considered for adding to base source code.
Comment 1 Eitan Adler 2018-05-28 19:47:21 UTC
batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Comment 2 smars 2020-09-22 04:10:51 UTC
Created attachment 218167 [details] replace children by Xchildren
Comment 3 Robert McIsaac 2021-04-27 17:51:45 UTC
Not sure if this is the best place to comment. I landed on this page because I am interested in adopting a few easy orphan ports ..for example, picocom. There is documentation about the Problem Report Database, Bugzilla actually. And using a PR to submit a patch. The problem for me is to find which version of the code is to be patched and which Handbook link is correct.. I don't see a version number. And there are several repos - svn, github, and another machine running git. The Ports included in Release 13.0 do not have ./git files