<div dir="ltr">Hi Laura, Hi Tim,<div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 16, 2016 at 10:09 AM, Laura Perez Cerrato <span dir="ltr"><<a href="mailto:lauraperezcerrato@gmail.com" target="_blank">lauraperezcerrato@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br><div dir="ltr">Hi everyone,<div><br></div><div>First of all, thanks a lot! </div><div><br></div><div>Meaning to ask the same question as Serge, what's the preferred way of collaborating for anyone who's not a contributor? forking and then submitting a pull request?</div></div></blockquote><div><br></div><div>thats on you, Tim, and I to update the README.md with a description of the contributor and change staging process. I'm going to be checking out the repository for the first time in a few minutes. I guess we can bat aroun drafts between us using git itself, but perhaps email would be more sensible ;-)</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Cheers!</div></div><div class="gmail_extra"><br clear="all"><div><div data-smartmail="gmail_signature"><div dir="ltr"><font size="2" face="arial, helvetica, sans-serif" color="#000000">-Laura Perez Cerrato</font></div></div></div>
<br><div class="gmail_quote">On 16 June 2016 at 06:10, Serge Stinckwich <span dir="ltr"><<a href="mailto:serge.stinckwich@gmail.com" target="_blank">serge.stinckwich@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On Thu, Jun 16, 2016 at 9:24 AM, Tim Felgentreff<br>
<<a href="mailto:timfelgentreff@gmail.com" target="_blank">timfelgentreff@gmail.com</a>> wrote:<br>
> Hi all,<br>
<br>
Very impressive work, Tim&Fabio ! The power of full-automation !<br>
<br>
> as of 7:30 UTC the entire history of the SVN up to SVN revision 3745 was<br>
> migrated to GitHub. Automatic builds are running<br>
> (<a href="https://ci.appveyor.com/project/timfel/vm/branch/Cog" rel="noreferrer" target="_blank">https://ci.appveyor.com/project/timfel/vm/branch/Cog</a>,<br>
> <a href="https://travis-ci.org/OpenSmalltalk/vm" rel="noreferrer" target="_blank">https://travis-ci.org/OpenSmalltalk/vm</a>) and binary artifacts are uploaded<br>
> (<a href="https://bintray.com/opensmalltalk/vm/cog/_latestVersion#files" rel="noreferrer" target="_blank">https://bintray.com/opensmalltalk/vm/cog/_latestVersion#files</a>).<br>
<br>
About uploading binary artifacts, this is something I asked and this<br>
nice that Fabio<br>
make it work :-)<br>
<br>
Apparently there is some problems with some artifacts that have a<br>
double .zip extension.<br>
<br>
> Right now we have enabled all platform, object memory and bytecode set<br>
> combinations that I found build scripts for - most work, but OS X 64-bit<br>
> Sista is failing right now (32-bit works). At some point we'll have to<br>
> decide which combinations to put into the CI config as "allowed failures" to<br>
> get a green badge :)<br>
><br>
> Another thing for those not familiar with Git: Right now the entire<br>
> repository is 360MB, including all history. Most of that is old images that<br>
> were at one point committed to SVN and that have been pulled into the<br>
> repository. We could clean those out (removing them from the history) to<br>
> make the repository smaller, but I felt ~400MB is still ok (albeit<br>
> technically over the Github quota. We'll see of they complain). I would like<br>
> to ask everyone to stop committing large binary files into the repository,<br>
> however. Git is simply not very suited to dealing with binaries. If there is<br>
> a need for that, Github has support for git-lfs, which offers 1GB of free<br>
> storage with a 1GB bandwith limit per month. If we need more, we can look at<br>
> the different billing levels.<br>
><br>
> If you're familiar with Git, the only new thing to watch out for is the<br>
> updateSCSSVersions script as described in the README. It's not relevant for<br>
> the CI, but your own binaries will only show correct versions if this script<br>
> runs at appropriate times.<br>
><br>
> If you are not familiar with Git and don't care, there are scripts for<br>
> committing that should take care of everything as described in the README.<br>
> Again, let us know if anything doesn't work. The only difference vs SVN to<br>
> watch out for for you will be that the old scripts/svnci would commit your<br>
> changes to the server, whereas the scripts/gitci script only commits them<br>
> locally. You'll have to run `git pull` and `git push` to get them up to the<br>
> server.<br>
><br>
> If you have any questions regarding the repository setup please don't<br>
> hesitate to ask. You shouldn't be able to break anything, since we've<br>
> disabled force pushes to both master and Cog (and thus any chance of<br>
> destroying history).<br>
<br>
What is favorite way of contributing for people outside the vm team ?<br>
pull-requests ?<br>
<br>
Regards,<br>
<span><font color="#888888">--<br>
Serge Stinckwich<br>
UCBN & UMI UMMISCO 209 (IRD/UPMC)<br>
Every DSL ends up being Smalltalk<br>
<a href="http://www.doesnotunderstand.org/" rel="noreferrer" target="_blank">http://www.doesnotunderstand.org/</a><br>
</font></span></blockquote></div><br></div>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><span style="font-size:small;border-collapse:separate"><div>_,,,^..^,,,_<br></div><div>best, Eliot</div></span></div></div></div>
</div></div>