The problem with git is its not designed to work with binary files. It is
designed for source code. What we would need is our own cloud platform,
something like own cloud which is free and open source. Again we would need
infrastructure for it
@Unfa, wasnt your friend setting something up at one point? He seems to
have vanished as he never got back to me if we could use some of his
hardware for LMMS related stuff.
On Fri, May 9, 2014 at 11:03 PM, Tobiasz Karoń <unf...@gmail.com> wrote:
> Oeai, I was thinking about a similar concept. Uncompressed MMP files could
> be edited via git or similar system, however I think it would need a very
> simple, stripped down and straightforward interface to be usable for
> non-tech-savvy LMMS users. I think the "get and lock" or "turn based social
> creativity" concept that was presented elsewhere (who was it? Ohh...) would
> be much simplier and more game-like, more fun and engaging. I hope know
> about that idea.
> On 9 May 2014 22:12, "oeai" <o...@symbiants.com> wrote:
>
>> i was writing about a kind of github before... and it was about getting
>> in touch with musicians inside of lmms.
>> so each new push to song ( as git project) could be seen as a new
>> instrument and amin author could commit it or set a new branch, if he
>> uses this track (sound on) it means that it goes into master branch, so
>> all those commits becomes visual and whole project can be worked in
>> collaborative manner, using lmms as a part of gitk, it isnot so easy to
>> do, so first step was to make it a part of git sharing through web,
>> committing changes not interactively and then adding more functionality
>> (patch, revert changes).
>>
>> open projects could be reachable through main repository and also i
>> thought that users can open their own private repositories to work
>> together in private team if they need it.
>>
>> for instruments presets there could be used a separated open git-repo,
>> that anyone can reach, but commit changes can some group of at least
>> registered users - this can be separated into different branches as well.
>> the use of this can be better analysis of patches, so for one instrument
>> settings will be stored in one place and duplicates can be moved away
>> for example as it will be seen as the same code. using such base can
>> provide some similarity tools - some diff can be used for other
>> instruments and especially there can be implemented pattern base or
>> automation base, that can be used for different purposes.
>>
>>
>>
>> On 01.05.2014 16:38, Tobiasz Karoń wrote:
>> >
>> > I started this message as a reply in another thread, but it has grown
>> > too big, so I decided to start another thread.
>> >
>> >
>>
>>
>>
>> --
>> Symbiants
>> oe ai
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Is your legacy SCM system holding you back? Join Perforce May 7 to find
>> out:
>> • 3 signs your SCM is hindering your productivity
>> • Requirements for releasing software faster
>> • Expert tips and advice for migrating your SCM now
>> http://p.sf.net/sfu/perforce
>> _______________________________________________
>> LMMS-devel mailing list
>> LMMS-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/lmms-devel
>>
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find
> out:
> • 3 signs your SCM is hindering your productivity
> • Requirements for releasing software faster
> • Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> LMMS-devel mailing list
> LMMS-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lmms-devel
>
>
--
Jonathan Aquilina
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
