On 03/26/2013 03:10 AM, Sebastian Sauer wrote:
On 03/25/2013 07:21 PM, Inge Wallin wrote:On Monday, March 25, 2013 12:16:57 Elvis Stansvik wrote:Calligra Mini is actually a very good name. If you plan to create minimal2013/3/25 Sebastian Sauer <m...@dipe.org>:Since you seem to be trying to cut down on size, perhaps Calligra Mini? :)On 03/25/2013 12:32 PM, Jaroslaw Staniek wrote:Redundant as in Coffice contains already a C==Calligra? Yes, well. Thathi, congrats for publicity but i'm suggesting not introducing redundant brands extra that sound like a fork,name refers also to my preference for coffee & cola while hacking:http://www.urbandictionary.com/define.php?term=coffice :) Also redundancy is something rather common in FLOSS. May it be in Calligra's code (justlook my last review-request, but yes, its way better today then it was years ago), in naming (acronyms, redundancy, jokes - hello libkok :).Anyhow. If that's somehow a problem would renaming solve it? And if yes, what's a better name to show its just another flavor of Calligra just likeCalligra Mobile, Documents on the N9, Calligra Active, Calligra Kids (which is afaik gone but well, we once had plans there with a specialized interface), ...just writing 'experimental calligra words for android' would imho say it clearly what's the effort is about atm...hmmm... Ok, I changed the description from "alpha-version" to "experimentalalpha-version". Now it says "Experimental alpha version with support forWords only, more to come later" or so. FYI: In fact all that started with Sheets and I have a compiling andlinking Sheets already. The reasons why I switched to Words are that a)Sheets makes way lesser use of calligralibs and getting calligralibs working and proper tested was very important cause b) Words and Stageshare quit a lot of code/logic and so having Words done its a small(er)step to Stage. The thing is that I like to first focus on thefoundations, that means get Words proper threaded, before adding more andmore to the mix. That's what I will work on next. For the "for Android" part: That's what I wrote and what most news-articlestook over even in there headlines, no? Anyhow, its also clear that thatisn't 100% true cause I actually did/do most of the work on my KDE desktop,where the app runs and works fine too, and only test on the device fromtime to time or for things like multi-touch where desktop isn't thatgood. Probably would make sense I add it to OBS so there are packages for desktop Linux. Will look at it. Also its clear that BB10 and Sailfish arevery much on top of my list. Anyhow, I think the interesting news here for now is indeed the "runs on Android and heer are the packages" part and that's what most news-articles took over. imho a good message.viewer versions for a number of architectures,Viewer and editor but yes, target is minimal in terms of package size. As lesser bytes as better :)I could get behind it and do some marketing...+0 re name (means no opinion);For marketing I would suggest to wait 2-3 weeks till a new version can be published that is a bit more mature.There is the issue with Google Play: it does not allow to rename the internal package name but that's not visible to the user. In general the question raises up if we like to turn that Google Play account into a Calligra/KDE account rather then assigning it to me cause currently its not only my name but also my private key that signs the packages that are going to Google Play and F-Droid. +0 on that either from me :)
To give a bit more concrete technical insight into the publishing/signing process: That process is actually split. That means those who signs the package doesn't necessarily need to be identical with those who builds the package. But at least there needs to be strong trust more so if Calligra (or KDE by that matter) assigns there name/brand/trust.
The problem I see currently is that the whole publishing is controlled (as in even not myself can change that) by me. It has a bus-factor of 1. If I am hit by a bus or vanish from today to tomorrow or just fail to proper backup my private Play publishing key the account is locked and no updates can be published. Also I have full control over the packaging up to the user-stats and nobody else has. Certainly not the best situation.
iirc KDE signs its releases and so does Calligra. So, there must already be some workflow present to handle all that. That means that the only real problem there may that Calligra/KDE has no Google Play account (or?).
-Inge _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel_______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
_______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
