Well, i would say that Amazon is good for business, because of abilities
to get more, but for FOSS project it's not. That's why i've proposed git
first - there's a 1GB limit for projects, if download into git
!=samples, then for presets it will be enough place and open music
projects can go int
2014-05-02 8:43 GMT+02:00 Tres Finocchiaro :
> There's not even any code in LSP2
There once was, written by Toby. Jonathan removed it, I guess only he knows
why. (It wasn't much code though, but all the necessary models were there)
At this point I see absolutely no purpose in hiding bug reports away in a
code repository we may not even use. There's not even any code in LSP2, it
should be deleted until a dedicated home is warranted.
I don't understand your logic.
I see TODO list out there:
- New theme (try for simpler Goo
Nothing wrong, I think we need to at least in terms of the cloud concept
have that on the lsp tracker as well as its not only integrating it wiht
lmms itself but integration into lsp.
On Fri, May 2, 2014 at 8:13 AM, Tres Finocchiaro wrote:
> 1) collaborato: integration of AWS into the sharing
>
> 1) collaborato: integration of AWS into the sharing platform
>
What's wrong with this one? https://github.com/LMMS/lmms/issues/661
--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run
Hey guys I am going to file some of these ideas in the LSP issue tracker.
1) collaborato: integration of AWS into the sharing platform
2) integration of LSP into CMS
Is there anything else that I am potentially missing?
--
Jonathan Aquilina
-
