Here is Jolla’s answers to the questions asked (07:33:41).
Would you like my money, say $50, for some improvements to Suburban Trains? Its author has responded but he’s left the boat and wasn’t interested a lot it seems.
I need one bugfix (Moscow has bumped the intensity of those trains in some directions several times up and some buffer I couldn’t figure out seems to have become too small) and got a few optional improvement proposals, like the current time display in a (pretty terse) selection form, a button to quickly interchange the stations, and maybe the favourite routes.
Please drop me a line at mike@altlinux.org if interested; others can consider this a public offer if you’re not
Привет из России!
I think this illustrates that people are prepared to pay for Sailfish apps and their upkeep. For example I use Tidings quite a lot, but the reader mode for articles is not good - all the pictures are blue and every HTML link is shown in fully expanded form so it is quite difficult to actually read an article in this mode. Would I be prepared to pay for a fix, or even a fully working app in the first place? Yes, I would be - and I’m sure others would be too. OK, so we’re not talking huge amounts of money here (although you only need 400 people to buy a good app at £5 - and with, say, £1 of this going to the store for their costs, that’s still £400 for the dev). Yes, I know there are costs in setting up and running paid app stores, and yes I know it is probably not easy, and yes, I’m sure this has been discussed many, many times before … but it would almost certainly bring more people to SFOS (which I am constantly reminded is the point of this thread!) and recognise at least some of the effort the app developers put into Sailfish apps. Start small with a restricted set of really popular app types perhaps?
OK, so my maths is rubbish … you only need 100 people, not 400 … (maybe I should have just said it was a typo )
Maybe we should start a fundraising for stuff like this on https://www.bountysource.com/ so people can join up to collect money for improvements and bugfixes. Even if Jolla doesn’t support paid apps at the moment, this could be interesting for some devs.
Case in point:
Serious problem identified: scattered developer documentation. Desired results identified/obvious. Expertise to produce desired results present.
If we had a community liaison, we’d ask them how Jolla can help. Do they have plans?
Based on their answer, we could quickly set up a little project to collate the information. Crowdfund it if needed.
I agree with you @Steve_Everett: I would also be willing to pay for an app that is missing. I also think that, @sailr 's proposition, is a nice step to have more apps and engage more people on SFOS (for example QML developers that may not use Sailfish).
Maybe by posting the link for the bounty in the [Applications] category more people can see it. I will definitely try it next month with a 50€ bounty that others can join in, for a new app.
@David in a way we all have a community liaison with Jolla: the IRC meetings. For the documentation scattering, I made a post a very long time ago about the same issue. Perhaps a solution would be to :
- Create a topic about documentation
- In this topic we all gather the links/articles that we have on developing for Sailfish
- There is a need for “internet archive” it for no future loss
- A more tricky part would be to organize all this information (by language or topic for example)
- An even trickier part would be to create an extensive documentation such as the one available on Jolla’s website
This is a draft and one idea, maybe there are way better ones.
true, but then might aswell try UBports or PostmarketOS or something else with a larger active communitiy that is actively being cared for. Whereas Jolla break our much beloved Patchmanager without any hesitation or information or support. Sometimes, I feel they are a bit too rude to us.
Working on it new release just out with some fixes from others. I’m looking at the pictures bug.
I’ve tried Ubuntu Touch and Postmarket.
Not. Even. Close.
I’m putting my money where my mouth is. I run Fairphone and Volla. I run Sailfish because, buggy or not, it’s just better. Neither of my phones has support from a company so it’s a LOT of DIY. I understand that’s not consumer grade. My hope is:
- Jollas 4 relase
- The excellent porters
- A couple of fanatics like me
will get another couple of companies like Volla on board.
agreed, Sailfish is way better. But then, why don’t Jolla care a bit more about their private customers? A good enthusiastic customer base is good for sales and for platorm acceptance alike But those relatively unfinished Linux OSes exactly have that: A active and enthusiastic user base… though quite small in many cases.
Myself, having quite a bit of fun with Postmarket sxmo currently: Fringe OS’s always have less features. just compare Sailfish to the big two.
Believe I read somewhere about an Open Wiki that Jolla was considering which could be updated by community (guess, from the last community meeting). This might be a great tool to have useful information collated.
They certainly care, they just don’t have the resources (those being: time, money, employees) to do (much) more than they’re already doing right now.
What about Jolla just adding a new ‘Wiki’ category to this forum? A template, like the one for bug reports, could be used, and then the more knowledgeable and expert community members could post wikis covering how to work around common problems, explain how this or that function works, and so on. This could then be ‘the place to go’ for people who want to know how to do something or work around a problem. Cheap, easy, and requires no effort by Jolla folk unless they want to contribute to a wiki.
The forum wikis could even be given a searchable category in the template … e.g. app development, workarounds, SFOS usage, etc
Yeah, it’s missing. I got some help at: Application SDK bash: sdk-deploy-rpm: command not found
that contains the information that is missing from faq and dev docs. I immediately wanted to file this in a wiki page for app devs.
in a way we all have a community liaison with Jolla: the IRC meetings
This is getting beyond my ability to help but, to state the obvious, something isn’t working very well.
One obvious step missing is someone following through: The problem has to be raised with Jolla and waiting for the next IRC may take too long. How Jolla answer determines the next step but somebody has to lead the project from there.
The Wiki sounds like an obviously good idea. The Wiki code isn’t the easiest to handle.
Fandom will give us a free one and we can get it moved to the Wikia domain ultimately.
It’s - literally - next week.
Both iOS and Android have standardized badges (logos), which app developers can use to advertise that their app is available for the respective system (“Get it from the App Store”, “Available on Google Play”). Sailfish OS needs such badge too, so that its native apps become more easily visible to the people.
It’s - literally - next week.
Even 24 hours delay can damage momentum – depends where everyone is on the ADHD scale.
1-2 weeks is problematic if nobody’s pushing the ‘project’ through, and particularly if Jolla can’t give an answer straight away.
Jolla can afford to pay someone to spend half an hour a week to be a liaison for this community group we’re talking about. That half an hour might enable a dozen extra man hours from the community. And the IRC might not be terribly productive for Jolla either…
Discord has changed things for some developers. You can now get almost real-time feedback from select customers. You can test bug-fixes in minutes. Probably a bit far for Jolla but I’m trying to point out that doing things the way you’ve always done them isn’t necessarily the best way.