utility." cperciva acts as technical contact for the freebsd-update part of
the project, but it would be nice to have someone with experience from
writing GNOME/KDE applications as a technical contact/mentor as well.
Submitted by: cperciva, kris
instead of the PR form directly. Each user should read these
guidelines before sending a PR, but currently it seems they don't
do it always. We receive questions via PRs, which should be sent to
mailing lists instead, or PRs with not enough information and
rarely non-English PRs as well. I hope this will help a bit.
PR: www/97233
Submitted by: Gavin Atkinson <gavin@mod3.co.uk>
No objection from: freebsd-doc, freebsd-www, bugmeister
Approved by: keramida (mentor)
- Remove unnecessary dots, since these texts are not sentences
PR: www/97234 (related)
No objection from: freebsd-doc, freebsd-www, bugmeister
Approved by: keramida (mentor)
extract ideas from the ideas list which include the class='soc'
attribute. Display the title of those projects which are deemed
suitable for summer of code projects and then link to the ideas page
for the full description, technical contacts, requirements, etc.
source and extract and display the projects listed here in multiple
ways. For example, those projects that are suitable for summer of
code can be designated with an attribute and then extracted to
automatically be displayed on the summer of code pages, so that we
only have to maintain one list instead of two.
Correct a typo in one of the idea descriptions while here.
Suggested by: rwatson
Discussed with: joel
hub.freebsd.org:/root/autoreply/admin.vacation.msg) do not include
complete admins mail addresses.
To avoid any problems with broken links in browsers / MUAs remove mailto
links entirely for these addresses.
the different teams do and what their responsibilities are. Our developers
are generally very confused when it comes to finding the right person to
talk to, for example when requesting repo-copies or new perforce accounts
etc. This will hopefully improve the situation somewhat.
This is meant to replace certain sections of the contributors article, as
this contains more up-to-date information and more teams etc. I'll take
a look at removing the sections in question and all references to them soon.
Also, the translation teams generally don't translate the contributors article
since it doesn't seem to be worth the effort. Hopefully this will change now,
since this can be quite important information even for non-English speaking
people.
I've based my work on comments from many developers and patches have been
floating around on the doc list for a while, so it's about time I commit it.
Reviewed by: doc@
