From: Ariadne Conill <ariadne@dereferenced.org>
To: ~alpine/users@lists.alpinelinux.org
Subject: Re: lack of alpine policy of development tools, cuse lack of time for new collaborations
Date: Fri, 08 May 2020 15:07:50 -0600
Message-ID: <2996244.IqFZyr3sfq@localhost>
In-Reply-To: <CALci+FSVjg3rR7xfhh73QsmVHqvc+NzYrQ2Okw7WFvA_VtPYzw@mail.gmail.com>
References: <CALci+FSVjg3rR7xfhh73QsmVHqvc+NzYrQ2Okw7WFvA_VtPYzw@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

Hello,

On Friday, May 8, 2020 6:29:32 AM MDT PICCORO McKAY Lenz wrote:
> i found that for people that are busy but also need to work and complaint
> with alpine linux it's very ilogic that the only way to people get
> knowledge about the features of alpine development tools and environment
> are a single comment in a pull merge request..
> 
> *> you could take a look at the `/usr/bin/newapkbuild` script for now and
> search for `cmake`*
> 
> the comment above, are a suggestion but are the only documentation, how
> could the only documentation will be "searching in the code" that maybe
> could be too abstract in most cases! i'm not a xpert english writer but i
> made excellent maridb and LAMP focused wiki pages in the alpine wiki, but
> only due are common with my debian targets.. but i cannot spend (and of
> course most people) time that of course i need to work!
> 
> if developer put minimal documentation, rest of people can contribute more
> and enhanced that documentation.. but without any tips. we can not doing
> nothing more serious

Actually, there is a work in progress developer's handbook on https://
docs.alpinelinux.org/ but it's nowhere near complete yet.

Ariadne