On Sun, 2015-07-19 at 23:17 +0800, Oliver Luo wrote:
> I've been spending several days working on the migration from GConf
> to GSettings/DConf in our project evolution EAS...
Hi,
I suppose you mean evolution-activesync, as it's named in the GNOME
repositories.
> 1. Use relocatable schem
Hi all!
FOSSGBG is a local free software group here in Gothenburg that has
meetups every month or so to discuss various FOSS subjects. They're
having an event on the 11th of August [1].
Since this overlaps with the GUADEC hackdays, the organizers of FOSSGBG
thought it'd be nice to make this edi
Hi Milan,
Thanks for your comprehensive response.
On Mon, 2015-07-20 at 09:04 +0200, Milan Crha wrote:
> Briefly grepping the evolution-activesync code, the keys being read
> from the GConf look like:
> /apps/activesyncd/accounts//
> /apps/activesyncd/accounts//
> ...
> so you can have a re
On Mon, Jul 20, 2015 at 8:34 AM Andreas Nilsson wrote:
> Hi all!
> FOSSGBG is a local free software group here in Gothenburg that has
> meetups every month or so to discuss various FOSS subjects. They're
> having an event on the 11th of August [1].
> Since this overlaps with the GUADEC hackdays,
On Mon, 2015-07-20 at 19:41 +, Sriram Ramkrishna wrote:
>
> Are the ones that come to mind. Maybe Bastien Nocera has some
> hardware related type talk that he could talk about?
I'm afraid I won't be in town any more by that time.
Cheers
___
des
As we move to Wayland, some of the ways we used to work on the core parts of
GNOME (like gnome-shell --replace) no longer work. I think this is a good time
to look at how we hack on GNOME, how we can make it more standard and obvious
for newcomers, and how we can make it easier.
We can classify
I've hacked on things all the from 1-5. Everything has a different
development process, as usual, and I don't think there's any sense in
trying to unify them. Writing documentation and getting people started
quicker is always great, but everybody's going to have their own
little things.
As for she
On Mon, 2015-07-20 at 16:35 -0700, Jasper St. Pierre wrote:
> I've hacked on things all the from 1-5. Everything has a different
> development process, as usual, and I don't think there's any sense in
> trying to unify them. Writing documentation and getting people
> started quicker is always grea
On Mon, 2015-07-20 at 17:34 +0200, Andreas Nilsson wrote:
> They are looking for people from the GNOME community who would like
> to
> present their work at the meetup. Let me know if you'd like to
> volunteer. We'd like to have three 20-30 minutes talks. Subjects that
>
> would be interesting
It'd be really nice if we could team up with the people working on
container technology so that we were able to run a full GNOME session
within a container. Even if it was privilleged.
We could serve GNOME Continuous images as docker or lxc images with the
latest stuff built in so that people can
On Tue, 2015-07-21 at 02:04 +0100, Alberto Ruiz wrote:
> Relying on jhbuild from my point of view is a waste of everybody's
> time, we've got all these developers building the same version of the > same
> module in the same architecture again and again and again, to > reach more or
> less the sa
On Mon, 2015-07-20 at 19:11 -0400, Owen Taylor wrote:
> 1) Hacking on system components that require hardware access (kernel
> drivers, NetworkManager)
> 2) Hacking on system components that don't inherently require
> hardware access (kernel filesystems, systemd, polkit, gdm)
> 3) Hacking on s
build.gnome.org used to have auto builders for jhbuild. The problem is that
jhbuild building requires maintenance. Everyone I've talked to said that
after a few months of trying to have a jhbuild autobuilder, they gave up.
In my opinion, the way to fix this is to make jhbuild more like Continuous.
Hi,
On Mon, Jul 20, 2015 at 7:11 PM, Owen Taylor wrote:>
> We can classify hacking on "GNOME" (taken very widely) into the following:
>
> 1) Hacking on system components that require hardware access (kernel
> drivers, NetworkManager)
> 2) Hacking on system components that don't inherently requ
Are there specific reasons why KVM doesn't cut it for shell developers? GPU
access?
2015-07-21 2:44 GMT+01:00 Ray Strode :
> Hi,
>
> On Mon, Jul 20, 2015 at 7:11 PM, Owen Taylor wrote:>
> > We can classify hacking on "GNOME" (taken very widely) into the
> following:
> >
> > 1) Hacking on system
On Tue, 2015-07-21 at 03:00 +0100, Alberto Ruiz wrote:
> Are there specific reasons why KVM doesn't cut it for shell
> developers? GPU access?
As mentioned in the original mail, there are two main issues:
A) Indirection from the hardware: network, sound, monitors,
webcams, bluetooth, touchs
Hello Michael,
Another problem I didn't mention which is that sometime the checkout dir
makes "make" go bonkers at some point even with jhbuild build -fac. It is
quite often that I update my jhbuild setup after ages of not touching it
and I have to basically "rm -rf * && git reset --hard" and conf
On Tue, 2015-07-21 at 02:04 +0100, Alberto Ruiz wrote:
> It'd be really nice if we could team up with the people working on
> container technology so that we were able to run a full GNOME session
> within a container. Even if it was privilleged.
I'm intimidated by the amount of work there. For e
On Tue, 2015-07-21 at 03:11 +0100, Alberto Ruiz wrote:
> Another problem I didn't mention which is that sometime the checkout
> dir makes "make" go bonkers at some point even with jhbuild build
> -fac. It is quite often that I update my jhbuild setup after ages of
> not touching it and I have to
19 matches
Mail list logo
