On Thursday 06 October 2011 07:33:24 Carsten Munk wrote:
We have chosen to move out the hardware adaptations and UX'es out of
the core, into the community surrounding it, to get rid of a lot of
politics - to concentrate on what's technically good and benefits us
all - not having to maintain
On Tuesday 08 March 2011 12:55:45 Philip Van Hoof wrote:
But I have the feeling that we won't see *any* numbers whatsoever.
I realise the question was directed at the MeeGo architects but I would hope
that the Nokia product managers for the PIM/tracker developments had
quantitative
On Sunday 28 November 2010 05:41:44 Alison Chaiken wrote:
My apologies if this is not the best mailing list on which to ask:
I suspect meego-community may be a better list for the first question.
1. Would the Compliance spec prevent the problems that MS has caused
with the encrypted SD card
On Thursday 11 November 2010 22:15:26 Quim Gil wrote:
For the big majority of application developers targeting MeeGo, the Qt /
Qt Mobility APIs should suffice (plus OpenGL ES for the specific segment
willing to use it). If any of these developers is not finding what he is
looking for, then
On Monday 20 September 2010 00:46:32 Skarpness, Mark wrote:
On Sep 19, 2010, at 4:23 PM, Graham Cobb wrote:
Take the compliant word off the table, reduce the heat in this thread,
and let marketing do their job of brand creation, don't try to guess what
they will decide.
Of course we
On Sunday 19 September 2010 08:55:13 Carsten Munk wrote:
2010/9/19 Graham Cobb g+me...@cobb.uk.net:
Personally I don't think Staging is needed as part of the Compliance
definition (it might be needed for other reasons). The rule should be:
an app can depend on any other package which
On Saturday 18 September 2010 19:48:04 Skarpness, Mark wrote:
I don't agree that having MeeGo compliance support componentised
applications is an objective we should take for the near term. I would
rather us focus on solving the core problem (self-contained compliant app
runs on any compliant
On Sunday 19 September 2010 23:30:18 Skarpness, Mark wrote:
I want to make the marketing team job really simple - market MeeGo
Compliant Applications
Sorry, my day job is marketing. We don't let engineers choose names! And for
good reasons!!
I have no idea what brand MeeGo marketing will
On Saturday 18 September 2010 20:58:23 Carsten Munk wrote:
If you have an API you'd like to share with the world, put it in
Staging and take responsibility for it.
But not all the packages that form part of an Application will be built from
the same source package or be suitable for general
On Thursday 16 September 2010 22:44:43 Arjan van de Ven wrote:
this is where you get in trouble if vendor Z ships libbar but in a
different configuration/version for some widgety nifty thing that they
do... ... and that version/configuration is not ABI compatible.
So, instead, you propose that
On Tuesday 14 September 2010 08:26:23 Dave Neary wrote:
I agree - MeeGo Extras should be a repository of compliant applications.
And a compliant application, in this context, should be an application
which uses only MeeGo core APIs or MeeGo compliant libraries distributed
in Extras.
I am a
On Wednesday 15 September 2010 17:13:43 Skarpness, Mark wrote:
But that would mean that app stores would not be able to sell all compliant
apps - which is not what we want.
But app stores are not going to be in the business of selling compliant apps!
Most commercial apps (which is what apps
On Friday 20 August 2010 07:54:00 Patrick Ohly wrote:
This thread is in danger of being off-topic for this list. I'll try to
keep it focused on the Buteo design and source code; hopefully that'll
keep it relevant for this list, otherwise we should move the thread.
Thanks for your response,
On Friday 20 August 2010 13:39:34 Patrick Ohly wrote:
On Fri, 2010-08-20 at 11:41 +0100, Graham Cobb wrote:
On Friday 20 August 2010 07:54:00 Patrick Ohly wrote:
[...]
And it is working because we seem to have uncovered two design bugs
already. One already reported and the other
On Thursday 19 August 2010 13:09:02 sateesh.kav...@nokia.com wrote:
-Original Message-
From: ext Yves-Alexis Perez [mailto:cor...@debian.org]
Sent: 19 August, 2010 17:15
Emphasis on *at a time*. And by the way it's not possible to do that at
the moment to do that, everything as
On Monday 26 July 2010 10:29:19 Jeremiah Foster wrote:
I'm not fully convinced there is a need to maintain NFS in MeeGo and I
think everyone would prefer less complexity so perhaps we can define an end
user use case which clearly demonstrates the need for NFS that sshfs
doesn't fill?
I think
On Saturday 24 July 2010 07:26:21 Yves-Alexis Perez wrote:
On sam., 2010-07-24 at 00:07 +0200, adhyas.avas...@nokia.com wrote:
How do I access my videos/files on that server from my MeeGo handset?
Or do you think this is not a common use case?
Imho that would be a use case for some UPnP
Three of my nine bug reports have now been incorrectly closed as INVALID. I'm
not precious about resolution status, as long as problems are reported and
then resolved but this seems to have got out of hand. Just in case anyone is
using the statuses in any sort of reports it would be useful if
On Wednesday 23 June 2010 16:24:39 Arjan van de Ven wrote:
i can go on and on, but... with devices being almost always on battery,
and your examples very visibly and annoyingly degrading the experience...
(and often NOT being about AC/Battery but about where the device is
at that point in
On Wednesday 16 June 2010 05:34:42 Xu Cheng wrote:
Graham Cobb, thank u very much. But i didn't solve the problem.
I may not have made myself clear. Try either (or both) of the following:
I input command by your way:
$ xhost +local:
$su -c meego-sdk-chroot Downloads/meego-sdk-0524 root
Try
On Wednesday 16 June 2010 11:58:25 Graham Cobb wrote:
The problem is that DBUS_SESSION_BUS_ADDRESS must either be undefined or
must be a null string before invoking startmeego-debug. It seems to be
deliberate that startmeego-debug doesn't start dbus if it is already
running but I am beginning
On Monday 14 June 2010 15:31:14 Tomas Frydrych wrote:
Nope, the WM is not supposed to do that, if you want the window
undecorated (e.g., you providing your own decors), you need to tell the WM.
Oh, so it is not part of the MeeGo style guide that full-screen apps are not
supposed to have
I am trying to port the GPE apps to MeeGo (mainly for my own use, as I
maintain these apps in Maemo, but it is also a learning experience and others
may find them useful). These are GTK-based apps.
So far, I have got gpe-filemanager (a simple GPE app) working in the Netbook
SDK environment.
I am trying to port an application which uses Sqlite2. Does anyone have a
MeeGo rpm for sqlite2?
I realise Sqlite2 is no longer supported or recommended. But this application
uses it (and users may have existing databases they want to move over). I
built Sqlite2 for Maemo and will do the
On Friday 28 May 2010 09:03:59 Wu, Jackie wrote:
Currently, it does not work in a virtual box. The pre-requisites to run the
SDK is at
http://wiki.meego.com/Getting_started_with_the_MeeGo_SDK_for_Linux#Pre-requ
isites.
So, I guess it is time to have this discussion, which has been the elephant
On Monday 24 May 2010 11:43:25 kate.alh...@nokia.com wrote:
As general view, plain applications made with plain desktop UI toolkit will
have very poor usability in mobile device. Usage paradigm with touchscreen
and finger is so different than in desktop with mouse.
Thanks, Kate. Those are
On Wednesday 19 May 2010 18:50:01 Jeff Licquia wrote:
There could be an issue with newer MeeGo releases, say a MeeGo 1.1 app
running on a MeeGo 1.0 device. But there are other hurdles to cross if
we want to support that model (what to do with new 1.1 functionality,
for instance). As long as
David,
A few questions/comments:
1) It is not clear whether this is policy for Meego core packages or for
community packages (or both). I assume it is Core, as that is all that
exists at the moment. And if we end up with multiple community
repositories there may well end up with multiple
On Thursday 13 May 2010 10:44:29 Yves-Alexis Perez wrote:
On jeu., 2010-05-13 at 10:22 +0100, Graham Cobb wrote:
I agree with that decision but we need to realise that that is fine as a
test system for developers, but is not a supportable end user
configuration.
I'm not sure “Meego
On Tuesday 11 May 2010 10:44:04 Neil McGovern wrote:
Bugs shoudn't be subject to a popularity contest. They're subject to a
technical evaluation.
As a developer, I disagree completely. Popularity is one of the factors to be
considered. Knowing that a lot of people are being inconvenienced by
On Tuesday 11 May 2010 14:03:00 Arjan van de Ven wrote:
On 5/11/2010 4:00, Ameya Palande wrote:
Hi,
I wanted to know why Btrfs is selected as default file system for MeeGo.
Following text is copied from Btrfs kernel Kconfig option:
Btrfs filesystem (EXPERIMENTAL) Unstable disk format
On Thursday 06 May 2010 15:00:16 Naresh Mehta wrote:
Do keep updating on if it worked with the VMDK image instead. I guess it
will be the same problem since I suspect the image creation is messing up
somehow (.ks is a definite suspect). BTW, I used 0.17 tag for my mic2
compilation. 0.9 was
On Monday 03 May 2010 10:05:04 Andreas Jaeger wrote:
On Monday 03 May 2010 10:51:38 Jeremiah Foster wrote:
[...]
Good stuff. I look forward to pushing sources into OBS. I think it would
be great if I could just set up a cron job to push a tag from my git repo
into OBS. Is that sort of
On Friday 30 April 2010 11:42:44 Naresh Mehta wrote:
Hi People,
Now the symptoms are different. I don't get a crash, I just get a grey
screen
on which Starting MeeGo... appears briefly and then disappears. But no
terminal.
Has anybody got past this error? I am able to load the image
On Wednesday 28 April 2010 22:12:07 David Greaves wrote:
Well, the build systems team inside Nokia has begun writing some docs to
assist internal developers with much the same issues. We're starting to
publish some of them. A first page came out today
On Tuesday 27 April 2010 00:30:50 Graham Cobb wrote:
I think I have found the answer to my own question. The following two
repositories seem to be the ones:
http://repo.meego.com/MeeGo/devel/trunk/repo/ia32/os/
http://repo.meego.com/MeeGo/devel/extra/repo/ia32/os/
I have now been able
On Tuesday 27 April 2010 03:57:30 Zhang, Austin wrote:
Meego didn't use grub as below said. If you are partitioning _manually_,
please don't format '/' as ext3 instead as btrfs, and please have a
separated '/boot' formatted as ext3.
Purely, out of interest -- why did you go for btrfs? It
On Tuesday 27 April 2010 04:21:08 xin li wrote:
I have only one partition '/' as ext3 and using moblin2.1's grub to
boot it.The syslinux can load kernel at ext3 partition?I conceive it
only work at fat32 partition.
I think MeeGo includes EXTLINUX (it is certainly on the MeeGo CD image I
On Tuesday 27 April 2010 17:59:16 Shaver, Michael R wrote:
I think coming up with the overall name will inform how we name the various
processes and components that make up this. An example would be if the
overall name to end users was called Extras, then for the developer
uploading their
On Tuesday 06 April 2010 10:41:21 Dave Joubert wrote:
On 6 April 2010 10:33, Graham Cobb g+me...@cobb.uk.net wrote:
I am next going to try to see if I can find a bootable MeeGo image I can
stick on a memory card and boot my laptop with so I can try that on a 12
hour flight I have coming up
On Friday 16 April 2010 18:50:31 Greg KH wrote:
Why not just use MeeGo to develop it? That works for me. And again,
just because the distro is RPM based, doesn't mean that MeeGo is based
on it at all.
Greg,
I am trying that now. I have now managed to boot a MeeGo Intel image (in
QEMU).
On Monday 26 April 2010 08:30:38 Carsten Munk wrote:
2010/4/26 Zheng Zhang zwxp...@gmail.com:
Hi,
I run the sudo mic-chroot
meego-codedrop-ia32-developer-201003311106.img following the
instruction Building your package: Step by step, but the error info
is
Error: I can't recognize
On Monday 26 April 2010 20:58:34 Graham Cobb wrote:
I am trying that now. I have now managed to boot a MeeGo Intel image (in
QEMU). Where can I find an RPM repository with all the tools I need (svn
is the first one)?
I think I have found the answer to my own question. The following two
I am trying to follow http://wiki.meego.com/Developing_in_a_Meego_Environment
but, as I can't use mic-chroot on Debian, I am trying to use QEMU to run a
MeeGo VM instead.
If I build a raw image using the standard kickstart file, I can boot it in
QEMU. However, if I use Carsten's X86 kickstart
On Wednesday 07 April 2010 13:35:49 Carsten Munk wrote:
No, as it is not their purpose - the devel-ia32.ks's on the wiki make
a filesystem for chroot development (building), not for running actual
systems. It is comparable to rootstraps. Use the standard kickstart
files for generating system
On Tuesday 06 April 2010 12:43:03 Ross Kendall wrote:
I did manage to successfully make a livecd iso image and mount it under
virtualbox, however that seemed to crash half way through loading the
MeeGo kernel. Got as far as the following line:
[ 0.337016] [c1002cf6]
I am trying to work out how to have a working MeeGo development environment on
my Debian Squeeze desktop. I have found a few problems, reported a few bugs
and documented some issues and workrounds (see
http://wiki.meego.com/MIC_on_Debian). But I am a bit stumped by the latest
problem...
I
On Tuesday 30 March 2010 06:47:37 tero.k...@nokia.com wrote:
There are pretty strict legal regulations, depending on sales location, on
what kind of documentation has to be available to the person purchasing a
mobile phone. The legal requirements for netbooks are different, as are for
On Monday 22 March 2010 09:10:21 Carsten Munk wrote:
We have to make a proper and competitive end-user product with MeeGo
in the short term. We can create world peace in the long term. Time to
strike with a open source platform is now, not in 5 years. Or we'll be
run over by 20% open source
On Friday 19 March 2010 20:13:18 Andreas Osowski wrote:
The meeting will be logged and moderated by Stskeeps, Carsten Munk,
(as I'm unable to attend due to recent changes)
Is the log available?
Graham
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
On Friday 19 March 2010 04:52:52 quim@nokia.com wrote:
The suitable times for the TSG meeting are the times suitable for those
having to take part in there. Obvious? :) The question is: who *must*
attend the TSG meetings?
Sure, the bot suggestion was a bit tounge-in-cheek (but this is a
51 matches
Mail list logo
