Timo wrote:
> Hi who is responsible for writing documentation for OpenBSD? I'd like
> to get involved in writing documentation for OpenBSD as I really like
> OpenBSD and I feel technical writing is one of my strong points.
In case you (or other readers) need more of an introduct
Hi Timo,
Timo wrote on Sat, Jan 23, 2016 at 10:46:55AM +0200:
> On 23/01/2016 10:44, Martijn van Duren wrote:
>> On 01/23/16 09:35, Timo wrote:
>>> Hi who is responsible for writing documentation for OpenBSD?
>>> I'd like to get involved in writing documentatio
Ok makes sense. I'll look over the documentation and see if I find
something I can contribute to.
Regards.
Timo
On 23/01/2016 10:44, Martijn van Duren wrote:
> On 01/23/16 09:35, Timo wrote:
>> Hi who is responsible for writing documentation for OpenBSD?
>> I'd like t
On 01/23/16 09:35, Timo wrote:
Hi who is responsible for writing documentation for OpenBSD?
I'd like to get involved in writing documentation for OpenBSD as I
really like OpenBSD and I feel technical writing is one of my strong points.
Regards.
Timo
The best way would be to just
Hi who is responsible for writing documentation for OpenBSD?
I'd like to get involved in writing documentation for OpenBSD as I
really like OpenBSD and I feel technical writing is one of my strong points.
Regards.
Timo
Like most people, I have my pet peeves. I consider that documentation
is very important to code quality.
I ran into a school-book example a week ago, so I decided to share what I
mean.
There was this problem with dpb where some packages in a MULTI_PACKAGES show
up as Errors when they don't build
