On 03/08/2014 04:03 AM, Tres Finocchiaro wrote:
>
> When the link is embedded in our software, the users will get the
> impression that we guarantee the viability of that link.
>
>
> Then let's guarantee it. We've all "been there" in terms of watching
> free services die off (such as the h
To summarize what has been said in this post: If there'd be a port of
ZynAddSubFX to Qt, it would be a subwindow inside LMMS (inside like e.g. the
B&B editor is a subwindow). Inside this ZASF window, we'd have an MDI area
with all ZASF subwindows, so they'd be encapsulated.
I'd like to ask somethi
I have a contact that can provide us with free google apps accounts through
his education account plus purchase the domain for us
On Sat, Mar 8, 2014 at 3:03 AM, Tres Finocchiaro wrote:
> When the link is embedded in our software, the users will get the
>> impression that we guarantee the viabi
>
> When the link is embedded in our software, the users will get the
> impression that we guarantee the viability of that link.
>
Then let's guarantee it. We've all "been there" in terms of watching free
services die off (such as the hypothetical SourceForge unavailability), so
lets buy the doma
David you are wrong it does check. What it does is places a download
looking icon where if clicked will let you know what version is out and
provides a link.
This would apply to windows and mac mostly.
On Fri, Mar 7, 2014 at 11:37 PM, David Gerard wrote:
> So what do other projects do?
>
> Fir
Could we generate a pgp key for each release and have it be verified upon
installation or by the user after download?
On Sat, Mar 8, 2014 at 1:15 AM, Vesa wrote:
> On 03/07/2014 10:33 PM, Tres Finocchiaro wrote:
>
> There is no centralized keysigning authority that we could trust.
>
> Speak
On 03/07/2014 10:33 PM, Tres Finocchiaro wrote:
>
> There is no centralized keysigning authority that we could trust.
>
> Speak for yourself please.
> This is what OCSP and CRL is for. Nearly every secure communication
> one uses to the web uses trusted certificate. Too expensive? Valid
> c
So what do other projects do?
Firefox has a button you can press to check for upgrades. It *also*
checks itself for new versions, but a browser is a rather more
threat-ridden environment than a music application.
LibreOffice doesn't check at all, AFAIK.
Perhaps a check box "do you want this app
Very good after my opinion. Might as well add two links more?
Help --> Forum
Something --> lsp
Tres Finocchiaro wrote
> Help --> Report a bug --> Opens browser to github/lmms
> Help --> Check for updates --> Checks for new version
--
View this message in context:
http://linux-multimedia-st
>
> There is no centralized keysigning authority that we could trust.
Speak for yourself please. This is what OCSP and CRL is for. Nearly every
secure communication one uses to the web uses trusted certificate. Too
expensive? Valid concern. Can't trust them? I'd argue we already do.
> Your a
On 03/07/2014 05:42 PM, Tres Finocchiaro wrote:
>
> that is must be absolutely secure. No compromises, no excuses, it
> MUST be secure: we can't just put a server address there that LMMS
> checks - it must be future proof (what if our server address
> changes? well, the users will
Help --> Report a bug --> Opens browser to github/lmms
Help --> Check for updates --> Checks for new version
Pseudo code:
if (http://lmms.sourceforge.net/latest_version.txt != getVersion()) {
alert("A new version is available, please download it here:
http://lmms.sourceforget.net";);
}
I do like the idea of the LED, and I think that is a good way to go. I
think also we will need to then get in the habit if someone reports a bug
to have them try against the newest release to see if it still exists.
On Fri, Mar 7, 2014 at 8:20 PM, Bill Y. wrote:
> My feeling is that having a di
My feeling is that having a direct download link inside of LMMS is a bad
idea because it forces all the issue Vesa mentioned on us, several of which
are near impossible to guarantee at this point. My thought was in the paths
there can be a user definable url that points to a simple version number.
>
> that is must be absolutely secure. No compromises, no excuses, it MUST
> be secure: we can't just put a server address there that LMMS checks - it
> must be future proof (what if our server address changes? well, the users
> will get the new one in the next update... oh wait), so there must be
Hey Toby,
Are we goign to get another RC at some point?
--
Jonathan Aquilina
--
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actu
I really like this suggestion Bill. What do the rest of you think?
On Fri, Mar 7, 2014 at 12:55 AM, Bill Y. wrote:
> How about a little LED graphic in a corner that lights up when there is an
> update, and the user has the option to set it's brightness level? It could
> have a user definable di
You guys are aware that we are going to get a massive amount of bugs for a
version that we are not going to continue supporting when something new is
released.
On Fri, Mar 7, 2014 at 5:54 AM, Israel wrote:
> Absolutely!!! That is so right on Vesa!
> I'm so glad you are around to think of thing
Then what you are saying Vesa is that we need to support versions, the
suggestion makes it easier to ensure people are aware of a new version and
if we are going to do rolling releases so to speak we will need to suggest
to people to upgrade to a new version to ensure bugs they see do not occur
in
19 matches
Mail list logo
