Why not release on mac store about qlmarkdown HOT 12 OPEN

The Mac App Store doesn't have to be mutually exclusive with Homebrew, and the "notarization" process for the Mac App Store would make Homebrew installs work better by not requiring the user to launch the application in order to manually dismiss the code-signing warning. The main advantage with the Mac App Store would be increased visibility and easier installation for end users who prefer it.

from qlmarkdown.

At the moment this application is not published on the App Store for the following reasons:

• the developer license has an annual cost (which is why the precompiled version is not digitally signed)
• charging the application involves figuring out how much it costs in taxes and it would probably not be worth it anymore
• probably I'm using some security exceptions that would not be accepted by the App Store
• the software is developed as a hobby and would probably need a lot of tweaking

from qlmarkdown.

tl;dr Why not do both Homebrew and the Mac App Store?

Because Apple is an enemy of open source software. The App Store is full of garbage. I've never needed the Apple store.

from qlmarkdown.

Please don't put it on Mac Store, thanks.

from qlmarkdown.

tl;dr Why not do both Homebrew and the Mac App Store?

Because Apple is an enemy of open source software. The App Store is full of garbage.

That would kind of be an answer if you were the maintainer of this, but you aren’t, so it just comes across as kind of bossy?

I've never needed the Apple store.

This is a non-sequitur, given that the benefits of distributing this on the Mac App Store are for people other than you.

Your response is just fundamentally unserious. You didn’t open this issue, so why not just unsubscribe from it? You clearly have nothing productive to add to the conversation.

from qlmarkdown.

@tami5 Homebrew package manager is easier and more practical than Appstore.

from qlmarkdown.

tl;dr Why not do both Homebrew and the Mac App Store?

from qlmarkdown.

That would kind of be an answer if you were the maintainer of this, but you aren’t, so it just comes across as kind of bossy?

@elsiehupp I'm just stating my opinion. within the scope of freedom of expression. I am originator and contributor(theme, logo) of this FOSS project. So who are you?

from qlmarkdown.

That would kind of be an answer if you were the maintainer of this, but you aren’t, so it just comes across as kind of bossy?

You’re telling other people not to do something, which is bossy. And it’s entirely off-topic for this thread if you don’t feel like doing Mac App Store packaging yourself.

Again, nothing you’ve said here contributes to the conversation in any meaningful way. You are deliberately derailing this thread.

from qlmarkdown.

Again, nothing you’ve said here contributes to the conversation in any meaningful way.

I think it is very MEANINGFUL, I put my political attitude on behalf of open source software.

from qlmarkdown.

the developer license has an annual cost (which is why the precompiled version is not digitally signed)

Signing is free and it can be an automated step in your build script or alternatively Xcode provides a nice GUI.

The annual fee is only for hosting apps in the store.

from qlmarkdown.

the developer license has an annual cost (which is why the precompiled version is not digitally signed)

Signing is free and it can be an automated step in your build script or alternatively Xcode provides a nice GUI.

The annual fee is only for hosting apps in the store.

If I remember correctly, however, the certificate to sign the applications expires in a week and then must be regenerated and the application must be recompiled. Or is it a limitation only for iOS applications?

from qlmarkdown.