exist. (My fault for not noticing this section does not exist when
originally committing this.)
Submitted/patched by: Isabell Long (isabell121%gmail!com)
This work was done as part of Google Code-In (GCIN) 2011.
GCIN student: Isabell Long (isabell121 gmail com)
GCIN task mentors: des, rea
Minor rewriting by: gjb (myself) [1]
[1] The original task was to put this in the Developers' Handbook,
but as discussed with des, the CVS information is in the Committers'
guide; the Subversion Primer entry likely belongs here as well.
- Specifically add a step for 'cvs add' of the new files
- Group related steps (category/Makefile, MOVED, LEGAL),
and suggest committing it all in one go.
While here peform some other minor tweaks to wording
- Force column width to improve rendering.
- Remove a number of pieces of information which is either obsolete or
just not important. This includes removing reference to using telnet
which was already obsolete when I got a commit bit in 2003...
- Point people at freefall.
- Remove the hardcoded lists of members of cvsadm and GNATS admins -
this just duplicated administration.html and new committers should
not need to bug the two teams so often that they need to be pointed
out more than the many other active administrative teams. [1]
- Point at dcvs and pcvs for CVS repo's, as those are still in use by
developers.
- Don't use entities for internal mailing lists which expands to the
names as the result is just confusing and not useful. This part
should probably be changed to be a section with more text instead of
trying to include most info inside a table.
- Add information about portmgr monthly reports.
- Add a few links to some useful internal pages with more information.
- Misc minor text cleanup.
Discussed with: linimon, gavin [1]
said project is now long since completed, and there are enough people
with SMP-fu around that there's no need to point everybody at a single
target.
No objection from: jhb
* mention svn-arc-all along with cvs-all, the latter is not applicable for src
* update to 2010
Approved by: hrs, philip (mentor)
No screaming: keramida
* don't use RELENG_5 anymore
* don't mention CVS explicitly when the text applies to any version control system
* introduce Subversion (pointers and its usage in the src tree)
* don't mention ncvs as a CVS commit host anymore
* replace all sys/*fs examples in the practical CVS primer by analogous ports/Tools examples
* use ISO yyyy-mm-dd date format for -D flag of cvs
* mention that Subversion stores metadata in .svn directories
* remove text concerning the -j flag of cvs
* mention svn-committers and that it is a normal read/write list
* remove most of q&a 16.2, point to SubversionPrimer/Merging on the wiki instead
Reviewed by: trhodes, gabor, keramida
Approved by: keramida
* use corpauthor
* add 2009
* capitalize "Ports Management Team"
* the "ports frozen" announcement is also sent to ports@
Reviewed by: trhodes, gabor, keramida
Approved by: keramida
* The CD- and DVD-set are no longer available per subscription, but at conferences
* Remove all contractions but "Who's Who"
* Several language and SGML fixes
* Fix capitalization
* Add 2008, since content changes were made last year
* Fix the logical sense of a sentence.
Reviewed by: trhodes, pgj, remko
Approved by: trhodes
Collection [1]
- Add missing reference to pgpkeys-developers.sgml in connection with
adding a new PGP key [2]
PR: docs/122999 [1], docs/122917 [2]
Submitted by: pgj
document as posted to the developers list about three months ago.
Some comments from that time have not been addressed, but will be in
subsequent commits. I had hoped to get them all ironed out before,
but I've been too swamped.
If you have additional comments, please feel free to send them to me.
This recognizes that FreeBSD is increasingly being used in embedded
targets and starts to define what is expected of these embedded
targets at different tier levels, and recognizes that we may do
releases for them differently than we do for server/desktop.
New committers to FreeBSD may be interested about Coverity
Prevent, but it is not very easy to find out how they register,
what license terms Coverity Prevent SQS is available under, and
how they can use the web interface of the automated analysis
runs.
PR: docs/105447
Submitted by: bz
Reviewed by: remko, netchild
not committers, since only a subset of the information here applies to them.
To date, this has only included people who have been given GNATS access
without a commit bit.
The refactoring of the text is admittedly awkward, but anything else
would probably be a significant rewrite.
Hat: bugmeister
Reviewed by: core
the Committer's Guide ports repo-copy section and in the package naming
section of the Porter's Handbook. In the end, I wrote something that
turned out quite a bit different and somewhat more long-winded than
the suggestions in the PR, but LATEST_LINK was not documented anywhere
until now, so there :)
PR: 66775
Submitted by: eik
There's some useful stuff left in this section still, but we should
seriously consider removing it altogether and moving the important
bits somewhere else, since maintaining redundant information like
this isn't really constructive work.
/usr/share/examples/etc/bsd-style-copyright. There were a number of
minor wording and formatting differences. Provide it in C source
code format.
Add text talking about non-BSD licenses in the tree, including
limitations.
Add a paragraph adding strong caution when it comes to intellectual
property, pointing at the core team as a contact for any problems.
was redundant with text in the Porter's Handbook. Add text about what
portmgr is supposed to do. Provide links to documentation that needs
to be changed. Mention the CVSup examples.
Reviewed for content by: pav
a bit more than "an hour or two".
- The explenation of what needs approval and what not, during
a freeze was ambiguous, so clarify that all patches need
approval during a freeze.
While here:
- Add some links to the Portmgr Quality Assurance page.
- Use "the ports management team" instead of "the ports
manager" as we're more than one person and have been
for quite a while.
Reviewed by: marcus, krion
Approved by: remko
