ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Transliterator module, 2nd revision
Date: Thu, 11 Mar 2010 12:25:45 +0100	[thread overview]
Message-ID: <6faad9f01003110325g6fbd2ff3m2d13996ba55b50ad@mail.gmail.com> (raw)
In-Reply-To: <B4FE4170-C5A7-4782-91CA-B2A4F66D12C3@gundla.ch>

On Thu, Mar 11, 2010 at 09:06, Patrick Gundlach wrote:
>>>
>>> Can you also add the module to the module section [1] on the wiki,
>>
>> We urgently need to have some "git server" or something similar on the
>> garden for modules. Maybe SVN would also do for a while. The current
>> approach is very clumsy to use.
>
> I don't think that the users should learn git, that means an automatic solution on the server would be needed. But these are not trivial to implement. Perhaps something like auto-versioning svn does the trick?

I partially agree with that, but then again - 99% of module writers
are probably clever enough to be able to apply two or three documented
commands to get the module working on the garden. Also keep in mind
that authors of most modules on the garden (Aditya, Wolfgang, also
Taco) already have their own version controll and just need to go
through the painful process of uploading their modules to the garden
in a proper way, even though the modules are already public on github
or somewhere else.

(I don't know how to use all the functionality that git offers, but
"git add, git commit, git pull, git push and maybe git diff" do enough
to cover all the basic needs. We don't need to ask users to know how
to branch, rebase etc. if they don't want to.)

In any case - we would still need some page with module information
even if we switch to some version-controlled system.

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2010-03-11 11:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  9:47 Philipp Gesang
2010-03-10 16:01 ` Wolfgang Schuster
2010-03-10 22:09   ` Mojca Miklavec
2010-03-11  7:44     ` RCS/git server (was: Transliterator module, 2nd revision) Henning Hraban Ramm
2010-03-11 11:52       ` John Haltiwanger
2010-03-11  8:06     ` Transliterator module, 2nd revision Patrick Gundlach
2010-03-11  9:28       ` VCS for modules (was: Re: Transliterator module, 2nd revision) Peter Münster
2010-03-11  9:31         ` luigi scarso
2010-03-11 11:12         ` Mojca Miklavec
2010-03-11 12:03           ` VCS for modules Hans Hagen
2010-03-11 11:25       ` Mojca Miklavec [this message]
2010-03-11  9:32   ` Transliterator module, 2nd revision Philipp Gesang
2010-03-11  9:58     ` Jelle Huisman
2010-03-11 10:33       ` Hans Hagen
2010-03-12  9:42     ` Modules section login (Was: Transliterator module, 2nd revision) Philipp Gesang
2010-03-12  9:57       ` Patrick Gundlach

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=6faad9f01003110325g6fbd2ff3m2d13996ba55b50ad@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).