[Scummvm-devel] Status of ScummVM Android port
Max Horn
max at quendi.de
Mon Mar 21 10:54:08 CET 2011
Am 10.03.2011 um 01:11 schrieb Angus Lees:
> Ergh. I didn't even see this thread until just now, which isn't a good sign.
I hope you'll see this (late) reply... :)
>
> On Fri, Mar 4, 2011 at 01:17, Max Horn <max at quendi.de> wrote:
[...]
>> I am not familiar with the Android Market, but would it be possible to register a "ScummVM Team" vendor account or something like that, for which the "keys" are shared between some key personnel (e.g. Angus, Andre, and the team leads; the latter for backup) ? How is the current ScummVM version distributed, is it on a personal account by Gus, or what?
>
> So there are two important aspects to the "ownership" of the package:
It would be good to progress on this, indeed, this should be resolved *before* the upcoming 1.3.0 release. Ideally long enough before the release so that we can perform this release using the "new" approach, whatever it is.
As I understand it, there are two options:
Option 1: We try to keep compatibility with the existing market app.
This includes
a) Keep using your existing android private key (which you haven't
used for anything else). I think the private key should then
be shared between you, Andre (assuming he's willing to official
co-maintain the Android port :), Eugene, and me.
[This remind me once more that it would be *highly* beneficial if more
team member had GPG keys, so that we can exchange confidential
information over a secure channel]
b) We keep using the "org.inodes.gus.scummvm" Java package name.
c) We keep using your personal market account (not nice, though),
or maybe (preferably) you can "transfer" the existing ScummVM app
to a new, to-be-created "scummvm" market account. The keys to
which would be shared among the same four people.
Option 2: We make a clean cut now and introduce a new ScummVM version
to the market, where
a) we generate a new, dedicate key (sharing it between the same four
persons listed above, though)
b) Switch Java package to org.scummvm.scummvm or org.scummvm.android.scummvm or so.
c) We create a new ScummVM market account, sharing access to it between
the four named people.
Advantages of option 1: Best continuity for users (upgrading is smooth).
We also get to keep all our market stats, *if* we can switch the download
from one market account to another. This sound like a big "if", though.
Bye,
Max
More information about the Scummvm-devel
mailing list