<div dir="ltr">On 13 May 2014 00:43, Paul Fox <span dir="ltr"><<a href="mailto:pgf@laptop.org" target="_blank">pgf@laptop.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">daniel wrote:<br>
> * Should we contribute the olpc-os-builder changes back to OLPC or fork it?<br>
> > I don't know if OLPC will do any active development on the linux side of<br>
> > things, if not maybe better to turn this into a sugarlabs thing.<br>
</div> ...<br>
<div class=""> > Yes. I don't really have a strong feeling one way or another. I can send<br>
> patches for the generic parts if they are wanted.<br>
><br>
> I think we also need a place where to put reference configurations. I<br>
> initially had put them in olpc-os-builder, numbered as 14.0.0 but that<br>
> feels wrong... since no official olpc releases are planned. I suppose I<br>
> could edit the examples/f18-[model].ini ones instead, but I would need<br>
> access to whatever repository we use to change those without needing review<br>
> every time.<br>
<br>
</div>in my opinion, the value of not forking would outweigh the risk of<br>
giving commit privs to someone from (gasp!) sugarlabs. ;-) (that really<br>
is just an opinion, of course. it's not my call.)<br></blockquote><div><br></div><div>I don't know... we are kind of dangerous people :P<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
it also seems like this problem could be well solved with branches and<br>
tags. i haven't looked at the o-o-b tree, but i assume the current<br>
13.2.0 point could be frozen (branch or tag) and other work could<br>
continue, and eventually branched or tagged itself.<br></blockquote><div><br></div><div>Yeah, I made my changes on a branch already (v8.0). <br></div></div></div></div>