Re: [DLG-dev] making gnome shell usable
Brought to you by:
casaxa,
evildagmar
From: bart v. d. H. <bar...@ho...> - 2011-09-16 07:58:50
|
Hi All, as saxa knows, I am back in the production aswell. I might have some extra news. I am working at a service provider, and currently have a vm setup for building packages. I think we can all share that VM for building packages, and use that as our development enviroment. We can use this for either the 32bits or 64bits architecture. My personal preference would be 64bit as you will see desktop users use that more. Than the 2nd thought. Now, I am thinking that we should not do any real release untill the next slackware comes out. either being slack 14 or slack 13.xx and have a stable gnome 3.2 on there. before that time come, I think we should build gnome 3.x on 13.37 as developing for our release of gnome 3.2 might even be 3.2 on 13.37 regards, bart/Tyrael > Date: Thu, 15 Sep 2011 20:37:38 -0300 > From: ca...@gm... > To: dro...@li... > Subject: Re: [DLG-dev] making gnome shell usable > > On Thu, Sep 15, 2011 at 10:56 AM, Evan Hisey <eh...@gm...> wrote: > > I just found this link fro extensions that brings back most of the > > good stuff about gnome 2.32 inside Gnome shell. I think this will help > > keep DLg attractive to users. > > Good to know that. I was in fact waiting that gnome 3.2 comes out to > start doing something. > > > > > Now that I have caught up with work again and have sometime, I am > > ready to start helping again for the next DLG. Assuming we are going > > to try and keep it going > > > > Evan. > > Evan, thats great ! I think there is no reason why we should not build > gnome 3.x , I personally have opted to > not loose time to do the first 3.0 release, because I have tried it, > and I have not liked it. Also because there > simply is still work on 2.32 if we want to make it roll out. > > One person can not do the full gnome release alone and even more, on 2 > archs. So in my opinion we need > to restructure the project with roles. > > Personally I'm not here to say what somebody should do. But in my > opinion, firstly we need to see who is > a candidate to do some work. > > Would be nice to see in how many we are before we can do a structured work. > > Just building in 5 all the same thing and then using the built > packages will lead to a big confusion imho. > > We should define roles and select packages we need to build so we can > do a release. > > In the past we had a lot of people and just building some packages > each could work. Gnome became more > complicated also, so this wont work anymore imo. > > I propose we can define maintainers who can concentrate on a small > part of the full desktop and then use > this parts together to make a release. > > We need somebody who can develop and keep up to date the big packages > and some parts of the desktop. > > But to define that we should first know on how many pieces we have to > split the work, therefore how many persons we have. > > Rgds > Saxa > > > > ------------------------------------------------------------------------------ > > Doing More with Less: The Next Generation Virtual Desktop > > What are the key obstacles that have prevented many mid-market businesses > > from deploying virtual desktops? How do next-generation virtual desktops > > provide companies an easier-to-deploy, easier-to-manage and more affordable > > virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ > > _______________________________________________ > > Dropline-gnome-devel mailing list > > Dro...@li... > > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel > > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > http://p.sf.net/sfu/rim-devcon-copy2 > _______________________________________________ > Dropline-gnome-devel mailing list > Dro...@li... > https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel |