discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: TODO annotated for difficulty
Date: Tue, 14 Oct 2014 18:32:41 +0200	[thread overview]
Message-ID: <20141014163241.GE28294@iris.usta.de> (raw)

Hi,

now and again, people have expressed interest to contribute patches.
One obstacle for doing so probably is to find tasks that one might
be able to tackle.  So i'd like to briefly announce that i just
added rough difficulty estimates to most of the talks in TODO.
Beginners should take any (**) annotation seriously, and anything
having any (***) annotation is likely challenging even for experienced
mandoc developers.  Bear in mind that i often fix trivial stuff
right away, so don't be surprised if even (*) stuff turns out to
require a bit of work.

In case you want to work on any patches, feel free to ask for
specific advice about specific issues on tech@.

Since there was noticable traffic regarding bug reports lately and
since a few people have unsubscribed, i have slightly tweaked the
instructions on http://mdocml.bsd.lv/contact.html what to post
where.  It now reads:

  discuss
    Post important bug-reports that are likely to affect many users
    and general questions to this list.

  tech
    Post source code patches and minor bug reports to this list.

The idea is to reduce traffic and improve the signal-to-noise ratio
on this list for users who do not intend to hack on the code.

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

                 reply	other threads:[~2014-10-14 16:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141014163241.GE28294@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mdocml.bsd.lv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).