<div dir="ltr">I browsed around, and it looks like a number of people "claimed" their email addresses since this thread went live. Unless there are objections, I'd like to see us move to the Git repository for coordination. Over time, we can do some trimming/pruning of branches, etc.<div>
<br></div><div>I used to have huge, lofty goals. Now, I would just like to be able to build releases for each platform again. I have a Windows VM, and started running the build scripts. (Of course, software they download no longer exists, etc., but I'll get there... unless someone else is more of a Windows wiz than me, and wants to be in charge of Windows builds.) Likewise, getting the Mac build running again, and ultimately, having a JEdit package for Linux would be a good thing. (We've never done that.)</div>
<div><br></div><div style>All of that said, I wonder if we should look at something like this:</div><div style><br></div><div style><a href="http://codebender.cc/">http://codebender.cc/</a><br></div><div style><br></div><div style>
Either way, my goal is to get the tree "living" again, so that when we do things that are interesting (or develop a new library for a platform, or hack a new platform in (R-Pi, for example)) we can actually *ship* them. Or, for myself, get students using them in projects.</div>
<div style><br></div><div style>I have two students who have built two new airplanes, and this summer have four students who will be developing a suite of home energy/environment monitors. If we get the tree alive again, I can start looking at putting a grant together that mirrors/supports work back at the Kent mothership. Unfortunately, it's hard to do that when I can't easily involve students in projects on the embedded platforms. </div>
<div style><br></div><div style>Hm. That was longer than intended, and kinda off-thread. </div><div style><br></div><div style>Cheers,</div><div style>Matt</div><div style><br></div></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Sun, Mar 24, 2013 at 12:29 PM, Martin Ellis <span dir="ltr"><<a href="mailto:ellism88@gmail.com" target="_blank">ellism88@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 all,<br><br></div>Are we happy with the git repo now?<br></div>What's the next step?<br><br>--<br></div>M<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Thu, Mar 14, 2013 at 11:31 PM, Matt Jadud <span dir="ltr"><<a href="mailto:matt@jadud.com" target="_blank">matt@jadud.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Well... You know. Those. That I missed somehow.</p>
<p dir="ltr">(O_o)</p>
<p dir="ltr">Cheers,<br>
M<br>
</p><div><div>
<div class="gmail_quote">On Mar 14, 2013 5:46 PM, "Martin Ellis" <<a href="mailto:ellism88@gmail.com" target="_blank">ellism88@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 14, 2013 at 9:26 PM, Matt Jadud <span dir="ltr"><<a href="mailto:matt@jadud.com" target="_blank">matt@jadud.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>How best to handle branches? Do we export those separately, and then use git to merge things together? Or, do we do any branch merging/resolution first, and then move? (The former is easier, in some ways, but I don't know what makes the most sense.)</div>
<div><br></div><div>Some of the branches can go away, but some have things that I would like to hold on to. For example, last year a student started working on library/port of Carl's new scheduler; that code should be brought over. It could be done either by 1) saving the branch and merging the code, or 2) merging into the trunk and then re-running. (At that point, we should think about all of the branches, to save the number of export/import cycles.)</div>
<div></div></blockquote></div><br><br></div><div class="gmail_extra">Which branches are you talking about? All branches under <a href="https://projects.cs.kent.ac.uk/projects/kroc/svn/kroc/branches/" target="_blank">https://projects.cs.kent.ac.uk/projects/kroc/svn/kroc/branches/</a> are already included.<br>
<br>--<br></div><div class="gmail_extra">M<br></div></div>
</blockquote></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>