From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alexander Poslavsky Newsgroups: gmane.emacs.devel Subject: Re: Trunk still not open Date: Wed, 19 Mar 2014 16:54:10 +0200 Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0141a46c76996804f4f6d4c3 X-Trace: ger.gmane.org 1395240866 21281 80.91.229.3 (19 Mar 2014 14:54:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 19 Mar 2014 14:54:26 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 19 15:54:35 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WQHt5-000741-2T for ged-emacs-devel@m.gmane.org; Wed, 19 Mar 2014 15:54:35 +0100 Original-Received: from localhost ([::1]:41907 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQHt4-0005jS-Oa for ged-emacs-devel@m.gmane.org; Wed, 19 Mar 2014 10:54:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47975) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQHt1-0005jN-Qm for emacs-devel@gnu.org; Wed, 19 Mar 2014 10:54:32 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WQHt1-0002l5-4Y for emacs-devel@gnu.org; Wed, 19 Mar 2014 10:54:31 -0400 Original-Received: from mail-qc0-x231.google.com ([2607:f8b0:400d:c01::231]:36025) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQHt0-0002kv-V4 for emacs-devel@gnu.org; Wed, 19 Mar 2014 10:54:31 -0400 Original-Received: by mail-qc0-f177.google.com with SMTP id w7so9761099qcr.36 for ; Wed, 19 Mar 2014 07:54:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=evSIoezCfLqkv9yuSkBtr85SBHfrwyNsfLTa2e2Gyc0=; b=wkN9D5kK8BT0Xvp+okJ5jkx9Amo5x3EUCFNh2mgqoTVHgp4Nspynscg3eGil8MBJkl uFvY5mK7/qHtGn8ITmSArjGPlS2GLMIvjSTb2YARN5T8YLzj2X4Ply27yI0MQRO+waJ7 U74FI+0Lphmk6+wiY5nmSwq6mRlVkvVvA3PCnsv0P84aaEcRSJomZGWL0zTOm++GBHrp lYUA1jqZfg4+0Fy2WDs9+FFXv9BrmXDxjHgnpaDMUz2gcoXufLJdNvw272JC/g25wNrl qiln+W84pLc7RpIwmPzojCmGKMl0tW1tHTrLhs0oV3BKorp3fC7zWV8ugl8J4iyI5hf8 Pzgg== X-Received: by 10.224.151.79 with SMTP id b15mr3284390qaw.91.1395240870515; Wed, 19 Mar 2014 07:54:30 -0700 (PDT) Original-Received: by 10.96.97.193 with HTTP; Wed, 19 Mar 2014 07:54:10 -0700 (PDT) X-Google-Sender-Auth: SjP0-nT2AjF9DxSwD4Em_-NuQ-k X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400d:c01::231 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:170529 Archived-At: --089e0141a46c76996804f4f6d4c3 Content-Type: text/plain; charset=UTF-8 There might me people lurking on the list who might be interested in writing (some) documentation. Is there some low-hanging fruit and / or documentation how people could start? Looking in the bug-tracker for documentation bugs shows several of them, but none that actually involve writing docs, instead they seem to be bugs related to how docs are being shown. Reading the source when writing documentation is fine, but reading *all* the source to find things to document is a bit much. Newbie Alex --089e0141a46c76996804f4f6d4c3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
There might me people lurking on the list who might be int= erested in writing (some) documentation. Is there some low-hanging fruit an= d / or documentation how people could start?=C2=A0

Looki= ng in the bug-tracker for documentation bugs shows several of them, but non= e that actually involve writing docs, instead they seem to be bugs related = to how docs are being shown.

Reading the source when writing documentation is fine, = but reading *all* the source to find things to document is a bit much.

Newbie Alex
--089e0141a46c76996804f4f6d4c3--