ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt ML <ntg-context@ntg.nl>
Subject: Re: Modules
Date: Sun, 20 Jan 2002 21:05:09 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20020120205143.02ba6cd0@server-1> (raw)
In-Reply-To: <20020117215748.GA762@localhost>

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
-------------------------------------------------------------------------


  parent reply	other threads:[~2002-01-20 20:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 21:57 Modules Marco Kuhlmann
2002-01-18 18:30 ` Modules Giuseppe Bilotta
2002-01-19 23:20   ` Modules Hans Hagen
2002-01-21 10:13     ` Modules Taco Hoekwater
2002-01-21 14:31       ` Re[2]: Modules Giuseppe Bilotta
2002-01-21 18:07         ` Berend de Boer
2002-01-22  9:38           ` Re[4]: Modules Giuseppe Bilotta
2002-01-21 14:47       ` Modules Hans Hagen
2002-01-22  9:10         ` Modules Taco Hoekwater
2002-01-22 11:03       ` Modules Eckhart Guthöhrlein
2002-01-19 18:07 ` Modules Berend de Boer
2002-01-19 18:17   ` Modules Marco Kuhlmann
2002-01-20 16:03     ` Re[2]: Modules Giuseppe Bilotta
2002-01-20 22:04     ` Modules Hans Hagen
2002-01-20 21:57   ` Modules Hans Hagen
2002-01-20 20:05 ` Hans Hagen [this message]
2006-04-04  8:02 modules Hans Hagen
2006-08-08 23:33 ` modules Nikolai Weibull
2006-08-09  1:53   ` modules Sanjoy Mahajan
2006-08-09  7:08   ` modules Taco Hoekwater
2006-08-09  8:38     ` modules Nikolai Weibull
2006-08-09 10:16       ` modules Hans Hagen
2006-08-09 10:21       ` modules Taco Hoekwater
2006-08-09 11:57         ` modules Nikolai Weibull
2006-08-09 12:07           ` modules Taco Hoekwater
2006-08-09 12:28             ` modules Nikolai Weibull
2006-08-10 14:06               ` modules Patrick Gundlach
2008-08-06  8:37 modules luigi scarso

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=5.1.0.14.1.20020120205143.02ba6cd0@server-1 \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    /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).