Infoworld author deleting factual comments

So I came across this ridiculous article, and since the author got his facts all wrong - and I had a few beers - I decided to comment on it:

The author of this "article" hasn't done much research, but is an eloquent click-baiter.
Jolla has been shipping SailfishOS devices to Europe since late 2013 and is now opening markets in India (a pretty big market) and (of all places?) Kazakhstan. China is targeted for later this year.
And it's not low-end devices, but rather mid-range. Us early adopters actually paid €400 to get our hands on it.
The "eco-system" is not a big problem either, as you can run almost all android apps seamlessly.


The author replied soon after:

GGruman: (@GGruman is apparently his personal Twitter account, while his "professional" is @MobileGalen)

You're right about Jolla shipping in Europe. I forgot about that; they've shipped some hundreds there since last fall, at iPhone/Android prices. But they're not in India yet; they're still talking about that. Here's a good review of the hardware and OS: http://www.engadget.com/2013/1...

I was overly focused on the Sailfish OS open source project, which seems very stalled: https://sailfishos.org.


As his "facts" were way off, I tried to make a few more comments to correct them, but they mysteriously went missing...

I tried once more to post my comments in a single post, which also went AWOL:

Since the author seems to be deleting my replies to his reply, I'll repost them here:

@GGruman:
As they (Jolla Oy, Ed.) haven't revealed sales figures, no one really knows how many they've sold, but the production batches - I bet - are more than "some hundreds" and IMEI numbers suggests they're at least well into their second batch.

As for "still talking about that" with India, you can read the joint press release from Jolla and Snapdeal (with 25 million+ customers): http://jolla.com/media/documents/Jolla_Snapdeal_press_release_July18_2014_FINAL.PDF

Have a look at the community platform btw: https://together.jolla.com/
Stalled? Not so much!

https://sailfishos.org/ is mostly documentation. Most communication is on Together, mailing list and IRC (#jollamobile and #sailfishos on freenode).

But yes, SailfishOS - besides the GNU/Linux stack behind - is new in town and has it's bugs and a relatively high learning curve (a couple of days) because it's not just tap-on-buttons, but extends the Meego/Harmattan gesture based interface enabling you to use the phone much more intuitively.

The article you link to is 8 months old, when only a minute portion of the pre-ordered devices had been delivered. Since then Jolla have been making *monthly* updates each improving the stability and user experience.

Flattr this!

Posted in Personal. Tags: , . No Comments »

I’m retracting myself from the ownCloud contributors

As the header says I will no longer be part of the ownCloud contributors. It has been a major - not to say the main - part of of life for the past 2½ years; they do roll by, don't they...
When I started it was as most hobby-programmers just to scratch my own itch, but it has been a great joy and pleasure to work with the many enthusiatic people.
When Frank started his company around the project I was just as happy and gladly signed a contributors agreement for my few contributions to ownCloud core.

The ownCloud project was for me both as mentioned to scratch my own itch regarding many points, but also a way for me to heal my own mind with some brainwork that I hadn't been able to do elsewhere. For personal reasons I'd been out of a job - unable to perform it - but after I had my disability pension I could have some peace and let me try to build some strength.
It helped a lot to work with these great people.

Lately - for the better part of 1½ year - this hasn't been my feeling. I may be wrong but it is my strong feeling that ownCloud Inc. has become the priority, and the community a workbench for improving and taking over the apps.
If this is not so, keep doing your awesome work.
For those having the same feeling as me, I urge you to form an ownCloud Foundation. I don't have the strength myself, but I will gladly join and support it.
Frank, I'd wished you'd seen and supported it

Sorry for all errors in this text; this is for me a very emotional departure.

Edit: I'll explain my reasons for leaving and my wishes for the future of the ownCloud community further soon. At this moment I just need to gather my thoughts first.

Below a redacted excerpt of what triggered it. It may not seem important, but if you know your github-foo your can find find it all

 karlitschek commented 2 days ago

Sorry but we don´t want to dumb more libraries in the ownCloud core only because they might be useful. Apps are free to ship components like that if they want to use it. At the later stage if 4-5 apps ship the same component in the exact same version then we might consider to add the to the ownCloud core, or not.
:-1:

 karlitschek commented 2 days ago

I'm not saying this is not useful, secure, good code or in other ways helpful. But this doesn't mean that we should dump all useful code into the core. The design goal of the owncloud core is to be as small as possible. In fact it is already too big. So if this is useful then we should use it for the news app API first and perhaps other apps. This doesn't mean that we have to dump it into the core to make it heavier, difficult to maintain and to keep stable

 tanghus commented 21 hours ago

As it has been - wisely - decided to move the AppFramework to core, I am interested in having it both lean, but more importantly usable and secure. Therefore I prefer to have great implementations which are closely scrutinized for security issues.
A security issue that would be present in at least 3 apps has already been detected. I think that speaks for itself for including it in core.

 tanghus commented 9 hours ago

In case my point didn't come clearly thru, as I may sometimes try to soften my views when putting them into words.

    The design goal of the owncloud core is to be as small as possible. In fact it is already too big.

Recommendable, but what does that exactly mean? What is not needed in core? archive, migration, memcache, ocs, vobject, activitymanager, api, avatar, backgroundjob, cache, contactsmanager, tags, eventsource or files for that matter? Plus everything else under /apps. Fine, lets scrap it and start from scratch. I can actually mention a few that I wouldn't be missed (including some of my contributions), but that's another matter.

Design-wise it would probably be good, but we would be left with basically nothing.

Some of the good decisions that have been made during the past ~1½ year - from my PoV - are

    The strict adherence to interfaces in new contributions
    The introduction of the Server "container"
    The (partly) inclusion of the AppFramework.

Those - and other - changes can make it possible to actually move towards a mature, trustworthy codebase.
I have no special attachments to including CORS middleware, but I understand from several parties, that I trust, that it is a small, yet important part to include, and rejecting it as bloat is both disrespectful and counter-productive. So my rant is not about CORS - it's about the culture and attitude that I sometimes see in this community. What I seen is community members reluctant to voice their opinions for improvements.
To say it straight out: The community should have priority over both "The Inc." and "The Founder". Otherwise it's not a community anymore, and I don't see a place for myself in it.
Alternatively the two quoted nouns could find better ways for making compromises - without compromising the project - pun intended ;)
If none of those objects are met I frighten for the future culture of this project, but so be it; I find another place to try to keep my mind sound, because quite honestly recently it has done quite the opposite[*]

[*] With exceptions of course. No one mentioned, no one forgotten.

PS: I've tried to keep this rant in a sober tone, although my state might not be so (otherwise I probably wouldn't have written it) and I expect any responses to it to be made in public.

Frank Karlitschek
Owner
karlitschek commented 2 hours ago

@tanghus Thanks a lot. I don´t think this has anything to do with Inc. or anything else.
This is purely about the long term maintainability of the core. And this is something anything who wants that ownCloud still exists in 5-10 years should care about.
We all know several other projects where this framework/libraries bloat went wrong.
Frank Karlitschek
Owner
karlitschek commented 2 hours ago

O.K. Let´s put this into core under this conditions:

    Full documentation how this should be used by app developers is available on doc.owncloud.org at the same time.
    At least two independent apps are fully ported to use this.
    @Raydiation maintains this for the time being exactly as the rest of the app framework.

    Someone actively

    Someone starts to port other pieces of ownCloud to use this so that we don´t have code duplication.

Additionally we should also regularly check which code, frameworks or dependencies in core can be removed. Otherwise we run into a long term problem.

 tanghus commented an hour ago

    Full documentation how this should be used by app developers is available on doc.owncloud.org
    at the same time.

Reasonable and preferable.

    At least two independent apps are fully ported to use this.

I believe that should be the case for oC7 or oC8. Longterm dev is of essence.

    @Raydiation maintains this for the time being exactly as the rest of the app framework.

I think this should be rephrased to "there must always be an active, responsible maintainer." which is documented in the source file. I don't know if there's a @maintainer tag in http://www.phpdoc.org/ ?
That it should always be @Raydiation counts out the bus-factor ;)
Also where would that that place all other core developers including you Frank? We have git blame and I've been personally hit by that recently ;)

    Someone actively

Meaning what? If it's correct it doesn't have to change. This correlates with the maintainer or other developers related to this.

    Someone starts to port other pieces of ownCloud to use this so that we don´t have code duplication.

Agreed.

    Additionally we should also regularly check which code, frameworks or dependencies in core can be removed. Otherwise we run into a long term problem.

This should be addressed in a separate issue and I'm sorry @XXX that I kinda hijacked this issue for that.

 tanghus commented 19 minutes ago

    This is purely about the long term maintainability of the core. And this is something anything who wants that ownCloud still exists in 5-10 years should care about.

To be very forthright I'm not not sure which ownCloud you mean here? Is it to be sure independent developers can produce efficient and secure code, or is it to secure that the Inc. have less dependencies when they use their paid work force to make solid apps for paying customers?
The arguments and motives have become too opaque for me, and after 2½ years of mostly enjoying this project, I'll have to retract myself from it.

@XXX sorry for misusing this PR.
Frank Karlitschek
Owner
karlitschek commented 11 minutes ago

@tanghus I´m not really sure what you mean here. Like I said this has nothing to do with Inc. or anything else.
We all have invested a lot of time and energy into ownCloud. So it is in our all interested that the ownCloud core and the apps will be maintainable and stable and working and mostly bugfree for as long as possible. Because of that we have to do some quality check when architectural changes are done in the core. I think this is good maintainership in general.

Flattr this!

Still not wanting it

Like so many other people have said: It's too little, too late. Google has scared away a LOT of people, including me who wasn't even subject to their name witch hunt. I have deleted my G+ account, and I don't want it back. I don't want to be part of a "community" where I can risk being asked about identification, or if I know the right people. The former sounds like a police state, the latter either as a fancy night club, or the local biker gang - I'm not sure which is worst.

Flattr this!

Posted in Personal. Tags: , . No Comments »

White fish and veggies

This is a very easy dish, where you can pretty much use whatever is in the fridge/freezer - provided of course that you have fish and vegetables 😉
I normally eat it with organic "browne" rice, but you can use basmati rice, jasmine rice or even noodles if you prefer that.
First cut some carrots julienne.
Carrots Julienne
The rest of the vegetables are onions, red peppers, mushrooms and tomatos.
Dice, slice and mix with spices and a generous amount of olive oil.
Dice and Slice
Add the fish on top. It can be any kind of white, firm fish such as pollock or cod. I used some cheap, frozen Alaska pollock.
Add fish
Make a mix of spinach (I use the cheap, frozen stuff), bread crumbs (the stuff you can buy ready-made is just fine), olive oil and season it with salt, freshly ground black pepper and lots of nutmeg.
Spread the mix on top, sprinkle with more bread crumbs and grated cheese and bake at 210° centigrade for around 35-40 minutes or until the the cheese is golden.
Serve with rice.
Cheap, tasty and healthy :-)
 

Flattr this!

Posted in Food, Personal. No Comments »

Kernel hell

Ever since I finally installed Kubuntu 10.4 Lucid Lynx I have had kernel crashes at least once a day, sometimes up to ten times a day. It's very frustrating and effectively breaks your workflow to put it mildly. I could easily come up with other, more harsh ways to describe the situation 😉

I have tried a variety of different kernels:

  • 2.6.35-020635rc1-generic
  • 2.6.34-020634-generic
  • 2.6.32-23-generic
  • 2.6.32-22-generic
  • 2.6.32-22-generic
  • 2.6.32-21-generic

Some I can (sometimes) boot and let me work for 0-20 hours, others never reaches the login screen or goes into an infinite reboot loop.

If anyone experience the same or similar the relevant bug report is at https://bugs.launchpad.net/bugs/585734 and it doesn't look promising. So now I have come to the conclusion that I need to install a pre-Lucid kernel and see if I can get it running. It will probably degrade X performance (if it even runs) and crash other applications but I'd rather live with that than having to reboot all the time.

Is it at all a viable solution to install a pre-Lucid kernel and if so how should it be done. What about graphic drivers (aren't they somehow partly kernel modules now?).

Flattr this!

Posted in KDE, Personal. Tags: , , . No Comments »

Terms I hate – part I

NDA - Non Disclosure Agreement

An agreement is always good. It's nice to agree about something. But what I hate is double negations and what I hate even more is triple negations.

  1. Closure Agreement: You agree to keep the lid closed about a topic/case/job - whatever.
  2. Disclosure Agreement: Hey - let's tell everyone about it.
  3. Non Disclosure Agreement: Eh - I changed my mind. Shut up about it.

Flattr this!

Posted in Personal. Tags: . No Comments »

What’s going on…

Well, yes I got this blog so I thought I ought to write something. Last week I started working out at a local gym. Actually I was sent there by the municipal authorities because I'm unemployed, and in Denmark you have to be "activated" when you're unemployed, or you won't get any money. It's OK to go to the gym. I've never really liked these fitness centers with all the beefed up types, but this one is kinda relaxed. And it's good for me too. Haven't made anything physical for like 7 or 8 years and my computer is on the coffee table so I have no muscles and my shoulders and neck hurt like hell.

Flattr this!

Posted in Personal. Tags: . No Comments »