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 Wednesday 09 March 2011 00:59:28 Peter Robinson wrote:
> No idea if its suitable but evolution-mapi at least works with
> exchange not sure of the difference between mapi and active sync
> support.
Unfortunately they are very different: MAPI is a very different sort of
protocol
which basicall
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 requirement
On Tuesday 08 March 2011 13:44:44 Vitaly Repin wrote:
> On Tue, 08 Mar 2011, ext David Woodhouse wrote:
> > To be honest, I've found the existing MfE solution on Maemo to be so
> > horridly broken and unreliable that I didn't even explore the option of
> > using it. It loses sync for some reason al
On Tuesday 08 March 2011 13:37:15 David Woodhouse wrote:
> He'll be talking about the GAL, which in our case is an 18MiB download.
> I think our "personal" contacts folders in Outlook are typically
> relatively small.
I respectfully suggest you are not in Sales. While 80K seems unusual, most
sal
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 wha
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 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 compli
On Sunday 19 September 2010 08:55:13 Carsten Munk wrote:
> 2010/9/19 Graham Cobb :
> > 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 pack
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 u
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 th
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 s
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 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
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 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, ev
On Friday 13 August 2010 23:11:52 Ware, Ryan R wrote:
> On 8/13/10 2:53 PM, "Robin Burchell" wrote:
> >Given that MeeGo is arriving a bit late to this game, I think this is
> >something that can be ill-afforded, personally: issues like this aren't
> >going to help us gain developer mindshare. At a
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 thi
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 UP
On Monday 12 July 2010 21:45:01 David Woodhouse wrote:
> (Almost) all decent mail clients support this method of access; how you
> configure it varies. In Evolution it's under the 'receiving options'
> tab, called "Use custom command to connect to server". In Alpine it's
> rsh-command and rsh-path.
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
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
>
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 Do
On Monday 14 June 2010 16:15:25 Tomas Frydrych wrote:
> > I had assumed, from looking mainly at Calendar and
> > Contacts, that that was a requirement. It certainly seems to look nicer
> > that way.
>
> All MeeGo apps have a title bar and a close button; this either comes in
> the form of a WM dec
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 title
On Monday 14 June 2010 12:23:32 Tomas Frydrych wrote:
> The MeeGo netbook model is that if the application asks for less than
> the 60% of screen width, it gets the size it requested; if the window
> requests a size greater than 60% of screen width, it gets resized to use
> the entire screen. This
On Sunday 13 June 2010 12:15:47 Xu Cheng wrote:
> I has been download and set up MeeGo-SDK on my laptop. (Intel T3200,
> GMA4500, Fedora 13 KDE English). But it show white window when
> simulator started.
I saw a similar problem when I first tried using the SDK (Debian Testing,
AMD64, Nvideo grap
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.
Th
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 sam
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 eleph
On Monday 24 May 2010 15:22:42 Dave Neary wrote:
> Let me ask the question this way (re. what Alberto wrote earlier): if I
> used Hildon on top of a stock upstream GTK+, what would be broken?
>
> If the answer is "not much", then as Arjen (almost) said: "Sounds
> perfect for the community repositor
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 Monday 24 May 2010 10:31:32 Arjan van de Ven wrote:
> just to clarify; "GNOME Mobile" is not part of MeeGo really (although on
> the netbook, we've borrowed some components for the UI implementation), and
> nobody should depend on this being there for app development for MeeGo. Use
> Qt for that
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
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 polici
On Friday 30 April 2010 16:38:05 Graham Cobb wrote:
> 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
> > pub
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
> > configurat
On Thursday 13 May 2010 01:38:59 David Austin wrote:
> My two cents' worth as a N900 owner: I feel that the advantages of btrfs
> far outweigh the costs even on a platform like the N900. Losing 30%
> of storage space is not pretty but the /opt "solution" is an ugly hack
> that has wasted consider
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 b
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
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
On Wednesday 05 May 2010 14:11:04 Paul Leeming wrote:
> Thanks for your response. I have actually built a RAW image (I put the
> wrong command line into my original email) My attempts to run the RAW image
> have not fully worked.
I got the same problem as you when trying to boot a RAW image with
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 sor
On Friday 30 April 2010 17:04:14 Andrew Flegg wrote:
> I'm certainly of the mind - though, as you'll know, we've not started
> discussing this yet - that there may well be space for mud in the
> MeeGo world.
>
> There's certainly no reason why it couldn't spit out the .spec file in
> exactly the sa
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
> http://wiki.meego.com/Packaging/Deb_c
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
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 hav
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 27 April 2010 10:16:07 Quim Gil wrote:
> The plan is to have in few weeks a first complete MeeGo release followed
> by a roadmap to work on the next release. Once this is out the MeeGo
> project shouldn't have any obstacle to have all the daily work and
> routines in the open.
I am very
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
cre
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 do
On Tuesday 27 April 2010 00:36:00 Arjan van de Ven wrote:
> I would strongly suggest using sshfs instead of nfs
Thanks, but NFS is what I use in my build setup. I have worked with NFS for
about 20 years and know what I am doing and why NFS is, unfortunately, still
the best tool for my parti
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 foll
On Monday 26 April 2010 08:30:38 Carsten Munk wrote:
> 2010/4/26 Zheng Zhang :
> > 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 t
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 Tuesday 06 April 2010 10:41:21 Dave Joubert wrote:
> On 6 April 2010 10:33, Graham Cobb 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 fl
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] [] kernel_thread_helper+0x6/0
On Wednesday 07 April 2010 18:35:49 Dave Joubert wrote:
> 1) We should apply our brains to getting Debian to boot and run on as
> many pieces of kit as possible.
>
> Take for example the O2 Joggler; it is a reasonably capable machine
> (esp at the current pricepoint), but the boot process is 'hidde
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 syste
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
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 c
On Monday 05 April 2010 23:05:51 Graham Cobb wrote:
> I looked on gitorious but 0.17 seems to be the latest tag. I then tried
> building the mainline but configure complains that it needs yum >= 3.2.24
> (Squeeze includes yum 3.2.23-1).
>
> So, how do I get a working mic-chroot
On Sunday 04 April 2010 01:11:35 Graham Cobb wrote:
> On Saturday 03 April 2010 07:33:30 Carsten Munk wrote:
> > Did you grab the MIC2 git tree? The patch for loopback images is in
> > there whic is needed for -developer images, which didn't make the cut
> > for 0.17 re
On Saturday 03 April 2010 07:33:30 Carsten Munk wrote:
> Did you grab the MIC2 git tree? The patch for loopback images is in
> there whic is needed for -developer images, which didn't make the cut
> for 0.17 release.
I followed http://wiki.meego.com/Image_Creation#Installation, which says to
chec
On Friday 02 April 2010 22:33:48 Samir Faci (Dev) wrote:
...
> which generated a .deb installation file.
>
> which I've uploaded here.
>
> http://www.assembla.com/spaces/dummyMeego/documents/b0Vv4-pP4r35fieJe5d-aX/
>download/pykickstart_1.69.-2_all.deb
>
> I've done this on a Ubuntu 64bit installat
On Friday 02 April 2010 22:59:58 Thiago Macieira wrote:
> Em Sexta-feira 2. Abril 2010, às 23.45.16, Graham Cobb escreveu:
> > On Friday 02 April 2010 21:45:27 Auke Kok wrote:
> > > Our policy was/is to support all the major distros. Nothing more,
> > > nothing less.
&g
On Friday 02 April 2010 20:55:47 Auke Kok wrote:
> On 04/02/10 12:40, Katrina Niolet wrote:
> > I think I’d like to see a standard UI with device manufacturers being
> > able to put their own if they want to, that way device manufactures
> > that either don’t want to spend the money on a custom UI,
On Friday 02 April 2010 21:45:27 Auke Kok wrote:
> Our policy was/is to support all the major distros. Nothing more,
> nothing less.
>
> We want people to be able to build MeeGo images on any current and
> popular distro. Period. No exceptions.
Good news, thank you. Bug 446 logged. Any idea when
On Tuesday 30 March 2010 11:00:56 Dimitris Glezos wrote:
> Just to make sure we have all the options in the table, here's another
> one. Some projects choose to have a carefully selected group of
> editors and accept bugfixes/improvements in the form of comments
> (instead of direct patches or comm
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
> in-ve
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
h
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 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
On Thursday 18 March 2010 23:12:21 Sebastian Lauwers wrote:
> Yay for early mornings during the weekend! 5AM woopdiwoop!
>
> +1 for variable times every month.
It is always tough, although Friday's are most likely to bad for the largest
number of people and should always be avoided! I suggest th
On Monday 08 March 2010 15:13:33 Arjan van de Ven wrote:
> On 3/8/2010 1:31, Mr. Todorov Todor wrote:
> > Hi,
> > does somebody has experience on deployin POCO (C++ libraries
> > http://pocoproject.org/ ) on MeeGo.
> > Or generally what is your oppinion on making this library available on
> > MeeGo
On Saturday 06 March 2010 20:02:44 Carsten Munk wrote:
> * What are you waiting for to happen in the MeeGo project?
Announcement of what code is in/out, what the rules are around what is in/out,
and what the processes are for community addition to the MeeGo base. My view
is that these points c
79 matches
Mail list logo
