I agree to a merge which will be the features which exist in your repo that don't exist in music blocks launcher.
-- Ibiam Chihurumnaya ibiamchihurumn...@gmail.com On Wed, Oct 7, 2020 at 6:46 PM Srevin Saju <srevins...@sugarlabs.org> wrote: > Hello > > Hope all are having a safe time. > > I was wondering if we should merge srevinsaju/musicblocks-app to > sugarlabs/musicblock-launcher. Musicblocks launcher depends directly on > my repository, so it would be considerably better to merge both the > repositories. > > Some information > > * *Musicblocks app* (https://github.com/srevinsaju/musicblocks-app > <https://github.com/srevinsaju/musicblocks-app>) is a set of > javascript files and shell scripts to automatically patch the > upstream musicblocks source code to continuously create the Electron > based AppImages, Snaps, Windows Binary Executables (.exe) and macOS > (.dmg) > * *Musicblocks launcher > *(https://github.com/sugarlabs/musicblocks-launcher > <https://github.com/sugarlabs/musicblocks-launcher>), by Christopher > Liu pulls the data from musicblocks-app and then helps to create > flatpaks. > > It would be great if we could unify the process and maintain a single > repository at `sugarlabs`'s GitHub Organization, as it would be > difficult for people to discover the scattered binaries > > What would be your suggestion? I would be glad to fix them, or do any > other changes. > > -- > -- > V/r > Srevin Saju > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel >
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
