![]() |
Re: About Sailfish community
Quote:
|
Re: About Sailfish community
Quote:
Not even the KDE team would do that. Vivaldi is a hobbyproject not a commercial project. And as you may now already Vivaldi project had huge problem with find a company that did have fully open gfxdrivers and when they found one, that company changed SoC and they had to restart again. And btw the SoC used in those projects is mediocre often undocumented and may very well disappear before users has got a chance buy those products. However I do like the ideas with what KDE do, but first of KDE should choose some safe SoC like TI OMAP (used in Beagleboard) instead of some unnamed crap SoC because even if OMAP has closed driver its probadly better than undocumented copycats SoC:s. But again this is not valid what Jolla is doing... |
Re: About Sailfish community
While previous post is a tad off, it still has a point.
We (community) don't expect that any of Jolla staff does official announcements or premature disclosure of specs or anything in here. But: Quote:
The rest is not about talking but mainly about listening and an occasional "we hear you". Example: Quote:
Quote:
Ps: sorry when all my examples are pretty hw-centric - I wonder how that might've happened ;D Anyway it has its benefits since it's a genuine Jolla theme /j |
Re: About Sailfish community
Quote:
|
Re: About Sailfish community
actually we were talking
>>About Sailfish community<< and trying to make clear if we're talking about a developer base that Jolla seems to lack and search to "build" while it's already existing in this forum and ready to jump in, or if such "community" is the customer base of Jolla that needs a first level helpdesk (stskeeps' blog post referenced in #1 post of this thread seems to suggest the former) In my book this thread is NOT meant for discussing implementation details that might be highly intriguing and relevant to a developer community but somehow OT to the topic of this thread. |
Re: About Sailfish community
joerg_rw: That's an intertwined subject. I.e. about the interaction of Sailfish community with Sailfish and Jolla. Building it up is important, but it starts with the basics. What are assumptions and expectations, what is the manner of that interaction and so on. Openness of the code, open bugtracker, roadmaps and open development is a common expectation for a project which builds an open source community.
Now, if Jolla doesn't want to mislead anyone, it's better to clarify how this is going to work really in the short or long term. In order to avoid false expectations and so on. Like Fawz said: Quote:
Quote:
|
Re: About Sailfish community
Man, I so want to continue reading & participating in this thread, alas no time, I hope it works out for the best.
Still believe a clean break from maemo.org is the best way to go, BUT with "exceptions" that I already outlined. Quote:
Still, for 1st timers it may be a good nursery_ground/staring_point... |
Re: About Sailfish community
Quote:
|
Re: About Sailfish community
I'm not sure what exactly you're trying to say, your writing style is often unclear to me.
I just refer you back to my original post (& subsequent ones) for better clarity. It was far from exhaustive, I know, but it's all I got, for now... |
Re: About Sailfish community
Quote:
|
All times are GMT. The time now is 01:55. |
vBulletin® Version 3.8.8