<div dir="ltr">Thanks for getting this project started---I think there's a real need for it, and I look forward to contributing.<div><br></div><div>My GitHub username is: thephoeron</div><div><br></div><div><br></div><div class="gmail_extra"><div><div class="gmail_signature"><div dir="ltr">"the Phoeron" Colin J.E. Lupton<div><a href="mailto:sysop@thephoeron.com" target="_blank">sysop@thephoeron.com</a></div><div><a href="http://thephoeron.com" target="_blank">http://thephoeron.com</a></div></div></div></div>
<br><div class="gmail_quote">On Wed, Jul 29, 2015 at 2:56 PM, SANO Masatoshi <span dir="ltr"><<a href="mailto:snmsts@gmail.com" target="_blank">snmsts@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi,<br><br></div>Thank you for invitation to the team.<br></div>I take this would be an opportunity to promote my product Roswell.<br><a href="https://github.com/snmsts/roswell" target="_blank">https://github.com/snmsts/roswell</a> which have almost same functionality as CIM.<br></div><div></div><div>I really want to improve Roswell to fit for CI and this project.<br><br></div><div>I'll look into the documents. and check what is lacking features to implement.<br><br>Roswell is already used for some CI work<br> * <a href="https://travis-ci.org/fukamachi/woo" target="_blank">https://travis-ci.org/fukamachi/woo</a><br> * <a href="https://circleci.com/gh/Rudolph-Miller/jonathan" target="_blank">https://circleci.com/gh/Rudolph-Miller/jonathan</a><br><br></div><div>Thank you.<br></div><br><div><div><br><div> <br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Jul 29, 2015 at 10:59 PM, Stelian Ionescu <span dir="ltr"><<a href="mailto:sionescu@cddr.org" target="_blank">sionescu@cddr.org</a>></span> wrote:<br></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Hello,<br>
<br>
Thank you for your interest and for joining this list.<br>
<br>
I've forked the 3 repositories that we will have to contribute to. We'll work on the branches collaboratively, then when we think we're ready we'll send a pull request to TravisCI. This way we have all changes in one fork and we don't develop from our private forks.<br>
Luis and Masatoshi have already been added to the team, all the others please send me your Github usernames so I can invite you to the team.<br>
<br>
Let's keep the relevant discussion on this mailing list or on TravisCI pull requests so that everybody is aware of issues: e.g. if you have an idea and tweet about it please also send an email to this list or open an issue as feature request.<br>
<br>
Here's my initial development plan:<br>
<br>
We can start with re-implementing the exact functionality of cl-travis:<br>
* for each implementation, only use a hard-coded version<br>
* use CIM as command-line wrapper<br>
* install Quicklisp<br>
<br>
We'll need to work on the travis-build project and create<br>
* lib/travis/build/script/lisp.rb<br>
* spec/build/script/lisp_spec.rb<br>
then add an include in lib/travis/build/script.rb<br>
<br></span>
According to the documentation in <a href="http://docs.travis-ci.com/user/languages/community-supported-languages/" rel="noreferrer" target="_blank">http://docs.travis-ci.com/user/languages/community-supported-languages/</a>, the build process has 5 phases:<span class=""><br>
* configure: here we must do all system changes like installing packages with apt-get. After this phase sudo will be disabled in container-based builds<br>
* setup: install the lisp implementations, the implementation manager and Quicklisp<br>
* announce: print some useful message about what just happened, like the lisp-implementation-name and lisp-implementation-version<br>
* install: nothing for us here. This phase is just for the individual project to install more stuff<br>
* script: the main phase. We could add a default implementation that quickloads the test ASDF system and runs the test suite, assuming some common naming scheme for the packages<br>
<br>
Once we have this done, we can think about implementing the more advanced features of TravisCI like a build matrix, UI changes, or supporting more versions for each implementations, etc... I'll setup a wiki too so that we document the current features.<br>
<br>
Thank you again.<br>
</span><span><font color="#888888"><span class=""><br>
--<br>
Stelian Ionescu a.k.a. fe[nl]ix<br>
Quidquid latine dictum sit, altum videtur.<br>
</span><a href="http://common-lisp.net/project/iolib" rel="noreferrer" target="_blank">http://common-lisp.net/project/iolib</a><br>
<br>
</font></span></blockquote></div><br></div>
</blockquote></div><br></div></div>