The Following 5 Users Say Thank You to w00t For This Useful Post: | ||
![]() |
2014-08-28
, 18:21
|
|
Posts: 1,055 |
Thanked: 4,107 times |
Joined on Oct 2009
@ Norway
|
#242
|
I guess it shouldn't be. Jolla has been shown to try and protect their pristine image in ways that I have a hard time fitting with an idea of modern, agile, social tech company. They are indeed quite closed and controlled in their comms policy, very old world aside from the fluffy stuff. I'd rather see something different from them.
No no, I do think it warrants care. I just think it was shooting a fly with artillery in the context of a guy loaning his Jolla to a blogger.
The Following 5 Users Say Thank You to w00t For This Useful Post: | ||
![]() |
2014-08-28
, 18:26
|
Posts: 114 |
Thanked: 37 times |
Joined on Aug 2014
|
#243
|
Fine, but offering that one thought for 24 pages? I'm sure it's more than enough for Jolla to pick it up, if they're interested.
![]() |
2014-08-28
, 18:29
|
|
Posts: 7,075 |
Thanked: 9,073 times |
Joined on Oct 2009
@ Moon! It's not the East or the West side... it's the Dark Side
|
#244
|
![]() |
2014-08-28
, 18:33
|
Posts: 114 |
Thanked: 37 times |
Joined on Aug 2014
|
#245
|
I don't think I know of *any* company that would happily say "sure, here's a prototype of software we might ship in two months. It crashes all the time, don't mind that. I promise the real software doesn't do that."
That's a way to end up going out of business really fast, as well as being really open at the same time.
Why does it matter who this person is? If they're about to write a review, which thanks to the "modern, agile, social tech" internet, can appear all over the world if it goes viral, then they need to go through just the same precautions as anyone else: they must be running stable software, and they must go through the tutorial. I don't see why that's such a major drama for you.
I think if that's your opinion, then instead of trying to make any more points, I'll just say that it's time to say that we'll have to agree to disagree. And I think the fact that you're getting actual replies from past and present employees on this thread should speak volumes about that.
![]() |
2014-08-28
, 18:35
|
Posts: 114 |
Thanked: 37 times |
Joined on Aug 2014
|
#246
|
There are some things I think Jolla does very well.
Working with upstream projects in collaboration with other stakeholders is generally a pretty good example of that. We've seen a pretty good track record with ofono (+ Ubuntu Touch), Qt (+ Qt Project), and a bunch of other projects.
I also think Jolla do a reasonable (if not great) job at communicating upcoming software progress, considering how frequent releases are: changes are always visible in the repositories, a view into the next update's changes is generally available before it comes (still a relatively new development and not a perfect one), larger technical announcements are sometimes made if there's any hint of problem or interest. And there's changelogs with a fair amount of detail at release time.
But there's also things that I think could be done better.
In particular, I think things like a public platform SDK (similar to what is generally used internally for development at the OS level) could be helpful.
I'd also like to see some work done on making a more cohesive OS development environment (software is available from a spatter of repositories all over the place, often with incredibly blurry lines about what goes where - sometimes to the point of being completely arbitrary) and so on and so forth...
![]() |
2014-08-28
, 19:26
|
Posts: 114 |
Thanked: 37 times |
Joined on Aug 2014
|
#247
|
![]() |
2014-08-28
, 19:38
|
Posts: 285 |
Thanked: 1,900 times |
Joined on Feb 2010
|
#248
|
Again, this is a case where Jolla themselves said they know the root cause. Nobody was asking them to comment on each and every phone that might be sent in, simply to provide an explanation as to what kind of root cause that was - so that people know what they are sending their phones in for.
I think there is perfectly good balance out there to be struck between transparent, open and respectful community relations and comms on one hand, and business interests on the other.
As for community relations and communications failures, how is the current strategy working for Jolla? Any disgruntled people out there? I know there are people on this thread who believe Jolla couldn't have done any better and it is an impossible mission to do any better, but I do think they could have done better. Some of the vitriol could have been avoided. Less secrecy would be one key. Now the silence leaves voids that will be filled by other voices.
The Following User Says Thank You to JulmaHerra For This Useful Post: | ||
![]() |
2014-08-28
, 19:59
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#249
|
Is this true? I did not know about this. Philippe?
That sounds very strange and indeed ...
Oh dear.
![]() |
2014-08-28
, 20:05
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#250
|
Apparently they do read:
Steskeeps @ Twitter:
https://twitter.com/stskeeps
Working with upstream projects in collaboration with other stakeholders is generally a pretty good example of that. We've seen a pretty good track record with ofono (+ Ubuntu Touch), Qt (+ Qt Project), and a bunch of other projects.
I also think Jolla do a reasonable (if not great) job at communicating upcoming software progress, considering how frequent releases are: changes are always visible in the repositories, a view into the next update's changes is generally available before it comes (still a relatively new development and not a perfect one), larger technical announcements are sometimes made if there's any hint of problem or interest. And there's changelogs with a fair amount of detail at release time.
But there's also things that I think could be done better.
In particular, I think things like a public platform SDK (similar to what is generally used internally for development at the OS level) could be helpful.
I'd also like to see some work done on making a more cohesive OS development environment (software is available from a spatter of repositories all over the place, often with incredibly blurry lines about what goes where - sometimes to the point of being completely arbitrary) and so on and so forth...
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.