• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

What category do I post in, if I have ?#! on FreeBSD docs?

Chris_H

Aspiring Daemon

Thanks: 111
Messages: 829

#1
I was wondering if there should possibly be a category for FreeBSD Docs, or what category to use for such related questions, or contributions?

Thank you for all your time, and consideration.

--Chris
 

DutchDaemon

Administrator
Staff member
Administrator
Moderator

Thanks: 2,462
Messages: 11,087

#2

Chris_H

Aspiring Daemon

Thanks: 111
Messages: 829

#3
Re: What category do I post in, if I have ?#! on FreeBSD doc

Greetings, @DutchDaemon, and thank you for the reply.
Ahh. I see. I'm already subscribed to about half a dozen of the higher volume ones now. I think my INBOX is pretty much at it's limit. :(
Technically speaking; you might be able say the same, for many of the other forum categories here. ;)

Seriously tho, thanks for taking the time to reply.

--Chris
 
Last edited by a moderator:

DutchDaemon

Administrator
Staff member
Administrator
Moderator

Thanks: 2,462
Messages: 11,087

#4
Re: What category do I post in, if I have ?#! on FreeBSD doc

Most of the forum topics here do not necessitate involvement from developers or people with commit bits to the source tree repository. As far as getting official documentation accepted is concerned, a user-to-user forum will not provide an avenue for that ..
 

Chris_H

Aspiring Daemon

Thanks: 111
Messages: 829

#5
Re: What category do I post in, if I have ?#! on FreeBSD doc

Fair enough. Point well taken.

Thanks @DutchDaemon
 
Last edited by a moderator:

jb_fvwm2

Daemon

Thanks: 171
Messages: 1,672

#6
Re: What category do I post in, if I have ?#! on FreeBSD doc

A chance to chime in for an expansion of the forum to ports subcategories... for instance some of this week's posts could be put into:
converters (libiconv questions)
security ( openssl questions)
ports-mgmt (pkg questions)
sysutils ( jail questions ), maybe even ext3, zsh, ...
mail ( ... )
shells ( ... )
... maybe one could see immediate issues and fixes in a check-first less-effort-later (hopefully) scenario(s).