From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/6547 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: Modules Date: Sun, 20 Jan 2002 21:05:09 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <5.1.0.14.1.20020120205143.02ba6cd0@server-1> References: <20020117215748.GA762@localhost> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Trace: main.gmane.org 1035397072 11583 80.91.224.250 (23 Oct 2002 18:17:52 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:17:52 +0000 (UTC) Cc: ConTeXt ML Original-To: Marco Kuhlmann In-Reply-To: <20020117215748.GA762@localhost> Xref: main.gmane.org gmane.comp.tex.context:6547 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:6547 At 06:57 AM 1/18/2002 +0000, Marco Kuhlmann wrote: >What I propose it that we should think about going public. eh ... it *is* public >ConTeXt has so much to offer, it should become more widely >used. A promising way to achieve this is to get more and more >people involved in enhancing and documenting it. That does not >say, of course, that base ConTeXt could and should not remain >in the hands of PRAGMA. But an active community of developers >working on extensions to the core is a good thing. And if it is >well organised, it does not have to threaten the integrity of >the system as a whole. because at pragma we depend on this system this is a tricky thing to do; i already changed the policy by making code public faster that we used to do, which troubles me because i hate to maintain unstable code. when something new is cooked up (currently some new things are being worked on), the process is rougly as follows: 1 program an experimental framework 2 use it in a project, experiment with features 3 redo the whole thing (mostly) from scratch 4 write a manual and in the process rewrite again now, esp stage 4 takes quite some time, but is also the stage where the interfacing (and hooks) becomes stable. Involving more people in stage 1-3 (currently only a few people are involved in these steps; participants can be customers, people on this list, others) would slow me down so much that it would limit my free time even more. In the process i clean up core code; once this is done (and documented) other development processes can be considered. In the end, given enough hooks into the kernel, i can imagine multiple solutions showing up for the same typo problem, either or not written by me or others. The main thing here is to guard the interface, i.e. control the naming of commands and key/values. > What do you think? ^^^ i suppose you mean me -) Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- fall-back web server: www.pragma-pod.nl -------------------------------------------------------------------------