<div dir="ltr">I agree to a merge which will be the features which exist in your repo that don't exist in music blocks launcher. <br clear="all"><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><pre style="color:rgb(46,52,54);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px"><span style="font-family:monospace,monospace">-- <br></span></pre><div style="color:rgb(46,52,54);font-size:14.6667px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;width:71ch"><span style="font-family:monospace,monospace"><span></span><span></span>Ibiam Chihurumnaya <br></span></div><div style="color:rgb(46,52,54);font-size:14.6667px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;width:71ch"><span style="font-family:monospace,monospace"><a href="mailto:ibiamchihurumnaya@gmail.com" style="color:rgb(42,118,198)" target="_blank">ibiamchihurumnaya@gmail.com</a></span></div><div style="color:rgb(46,52,54);font-size:14.6667px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;width:71ch"><span style="font-family:monospace,monospace"><br></span></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Oct 7, 2020 at 6:46 PM Srevin Saju <<a href="mailto:srevinsaju@sugarlabs.org">srevinsaju@sugarlabs.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello<br>
<br>
Hope all are having a safe time.<br>
<br>
I was wondering if we should merge srevinsaju/musicblocks-app to <br>
sugarlabs/musicblock-launcher. Musicblocks launcher depends directly on <br>
my repository, so it would be considerably better to merge both the <br>
repositories.<br>
<br>
Some information<br>
<br>
* *Musicblocks app* (<a href="https://github.com/srevinsaju/musicblocks-app" rel="noreferrer" target="_blank">https://github.com/srevinsaju/musicblocks-app</a><br>
<<a href="https://github.com/srevinsaju/musicblocks-app" rel="noreferrer" target="_blank">https://github.com/srevinsaju/musicblocks-app</a>>) is a set of<br>
javascript files and shell scripts to automatically patch the<br>
upstream musicblocks source code to continuously create the Electron<br>
based AppImages, Snaps, Windows Binary Executables (.exe) and macOS<br>
(.dmg)<br>
* *Musicblocks launcher<br>
*(<a href="https://github.com/sugarlabs/musicblocks-launcher" rel="noreferrer" target="_blank">https://github.com/sugarlabs/musicblocks-launcher</a><br>
<<a href="https://github.com/sugarlabs/musicblocks-launcher" rel="noreferrer" target="_blank">https://github.com/sugarlabs/musicblocks-launcher</a>>), by Christopher<br>
Liu pulls the data from musicblocks-app and then helps to create<br>
flatpaks.<br>
<br>
It would be great if we could unify the process and maintain a single <br>
repository at `sugarlabs`'s GitHub Organization, as it would be <br>
difficult for people to discover the scattered binaries<br>
<br>
What would be your suggestion? I would be glad to fix them, or do any <br>
other changes.<br>
<br>
-- <br>
--<br>
V/r<br>
Srevin Saju<br>
<br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</blockquote></div>