On Mon, 11 Feb 2019 09:11:53 +0100
Taco Hoekwater <t...@elvenkind.com> wrote:

> Hi,
> 
> > On 11 Feb 2019, at 07:43, Hans Hagen <j.ha...@xs4all.nl> wrote:
> > 
> >   
> >> The wiki should reflect that, at least the old repo information
> >> (foundry.supelec.fr) should go. The manual can stay. But before
> >> removing the info on the wiki someone needs to confirm there's no
> >> repo any longer.  
> 
> Yes, the repo is gone.

Thanks for confirming. In case someone needs the sources, I uploaded
them to github (if no one objects). But I doubt I'll find the time
to keep it updated.

  https://github.com/mpfusion/context-contextman

> The page at https://wiki.contextgarden.net/Manuals feels a bit
> out-of-date anyway, but I removed the reference to supelec.fr
> right now.

While you're at it. This one points to supelec, too:

  https://wiki.contextgarden.net/Improving_the_manuals

> Clearly more work is needed on how to present the ConTeXt
> documentation, and that is something that we are still working on.

Never-ending story. But at least we should remove obviously
wrong/outdated information. If my wiki login still works and have
the permission, I can have a go myself some time this week.

> > Sure, so best coordinate this with taco who is cleaning up /
> > upgrading the wiki andhas a shadow to play with running. Actually
> > some more input on / help with that is welcome.  
> 
> And there is a mailing list to go with it:
> 
>   https://lists.contextgarden.net/mailman/listinfo/wiki

I didn't know there's a list for the wiki. Signed up.

Marco
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to