Email list hosting service & mailing list manager

Continuous Integration, markdown and Makefile Amirouche Boubekki (20 Apr 2019 11:52 UTC)
Re: Continuous Integration, markdown and Makefile Marc Nieper-Wißkirchen (20 Apr 2019 12:10 UTC)
Re: Continuous Integration, markdown and Makefile Amirouche Boubekki (20 Apr 2019 12:18 UTC)
Re: Continuous Integration, markdown and Makefile Lassi Kortela (20 Apr 2019 12:38 UTC)
Re: Continuous Integration, markdown and Makefile Amirouche Boubekki (20 Apr 2019 12:51 UTC)
Re: Continuous Integration, markdown and Makefile Lassi Kortela (20 Apr 2019 13:05 UTC)
Re: Continuous Integration, markdown and Makefile Amirouche Boubekki (20 Apr 2019 13:16 UTC)
Re: Continuous Integration, markdown and Makefile Lassi Kortela (20 Apr 2019 12:28 UTC)
Re: Continuous Integration, markdown and Makefile Arthur A. Gleckler (20 Apr 2019 23:07 UTC)
Re: Continuous Integration, markdown and Makefile Lassi Kortela (21 Apr 2019 06:25 UTC)
Re: Continuous Integration, markdown and Makefile Frank Ruben (21 Apr 2019 04:35 UTC)
Re: Continuous Integration, markdown and Makefile Lassi Kortela (21 Apr 2019 06:21 UTC)

Re: Continuous Integration, markdown and Makefile Marc Nieper-Wißkirchen 20 Apr 2019 12:10 UTC

Am Sa., 20. Apr. 2019 um 13:53 Uhr schrieb Amirouche Boubekki
<xxxxxx@gmail.com>:
>
> Hello all,
>
>
> I have three requests to make that are somewhat related but could be dealt separately:
>
> Is it possible to setup Continuous Integration at http://travis-ci.com/ for SRFI repositories or another service that possibly support windows and other platforms. As far as know there is no service offering free CI for windows platform. I read there is an experimental CI server at https://github.com/srfi-explorations/srfi-server maybe we can use that already?
> Is it possible to include a markdown file in the SRFI repository that will be translated to html by pandoc
> Is it possible to include a simple Makefile that will allow:
>
> Translate markdown to html via pandoc
> Run SRFI tests against various scheme implementations

Whatever is planned, I think it is very important to choose
technologies that are not tied to GitHub but that work with other Git
providers at least as well. GitHub is not free software, and we don't
want to have a vendor lock-in.

-- Marc

>
> I looked at the archive https://srfi-email.schemers.org/srfi-discuss/ but could not find any discussion related to this.
>
> All the best,
>
>
> Amirouche aka. amz3