On Mon, 7 Nov 2005 12:09:07 -0600 Brian Mattern <[EMAIL PROTECTED]> babbled:
> A few things. > > A) if you want to take over maintainance of a project, send an email to the > list (or better, send an email to the current maintainer / author) in this case i don't think there is any need to announce taking over as such - just start working on it. fix things. improve things. xcomp can get cvs commits mail :) given enough work on it and lack of work by anyone else - you end up becoming the owner anyway by defacto. given that entrance does have a pretty much static development position - and has for many months. most of the year, i see no probolem. i know xcomp did a lot of good work on entrance and deserves kudos, but as per his own words - he's become very busy with real life and can't find time to do E work. people simply picking up things and working on them makes things happen. Entrance has many things that need doing to it to bring it forward and make it usable for the average person and not just a geek toy (like detecting RUNTIME existing system sessions, adapting to multiple distributions and their different ways of doing sessions, handling xinerama (splitting bg and fg login widgets in the theme and layoung them out specially with login widgets on 1 screen region at a time in xinerama only - maybe?), handling x restart loops and/or entrance restart loops (when somehting is going wrong with continual restarts of x and/or entrance client), handling userlists properly with their faces (remember a userlist may be MASSIVE - eg at university. this is also where admins may just want to turn it off). being able to handle aborted session logins (user logs in, wm startes then segvs, or the session scrit starts but the wm command is not found, or something) and then be able to provide a way to debug this or at least knwo what's going on (capture the stdout/err of the session script as WELLas pipe it to a log file - or maybe always ensure its going to a log file, which file and if a session login is too short (eg less than 10 seconds) when taking over again pick up the log info and display something to let the user see what was going wrong - then maybe even add some smarts to parse SOME errors (command not found, segfaults, ld.so linker/symbol errors - common stuff) and even maybe provide possible solutions (hunt the disk for the command and add that to the PATH for the user - if found and the user says ok), or re-run ldconfig, or hunt libraries for that symbol and then add it to /etc/ld.so.conf (if suers says ok) and re-run ldconfig etc (this is dangerous and might be better done with an LD_LIBRARY_PATH - as adding it ld.so.conf shoudl be approved byt he system owner only). frankly some useful additins might be modules - literally i could see the use of a battery module for laptops, the ability to not just shutdown or reboot but also suspend and hibernate. also code to detect x screenblanking and if x screenblank - shut down edje's animation to save cpu (good for laptops - again). this is just a quick list of things i can think of to improve entrance so it moves towards being a shippable bit of software - ideas off the top of my head. i ams ure others can find ideas too, withotu going crazy - just focusing on what woudl make it simply better and more usable without adding insane features (eg no tetris games in entrance if u are bored) etc. :) basically entrance has been pretty static when it coems to moving forward - or even just having its current system interaction improved (even the pam stuff could be better in auto-detecting what kind pf pam auth file is needed for the system and generating it at build time) :) as i said. xcomp has done a great job on entrance. but as he said himself - he's run out of time - he would like to come back to it but until that day really comes - i see no harm - in fact, i see much benefit in others taking over. > B) you could have tested and committed that patch in the time it took you to > write that email. Just because e17 the window manager is in a pseudo-freeze > doesn't mean that entrance is, and its much easier to commit the patch now, > then string along the author for a few months while you clean up stuff... indeed. remember - everyone (who is a dev andf cares) SEEs the commits - where they go AND the diff's. if they dont like it its trivial to reverse them. if u put lots of changes into 1 commit - it's harder. lots of small commits make light work. > -- > rephorm > > On Monday 07 November 2005 01:08, David Seikel wrote: > > On Mon, 07 Nov 2005 14:42:23 +0800 Phuah Yee Keat <[EMAIL PROTECTED]> > > > > wrote: > > > One of the features that I missed from KDM is the preselect > > > previously logged in user, I have added that support in Entrance cvs, > > > here's the output that I get from cvs diff, please tell me additional > > > things that are needed to get this committed. > > > > Until a few hours ago entrance was unmaintained. Apparently xcomp, the > > previous maintainer, has become too busy with other things to do much > > with it. Earlier today I adopted it. However, I made it perfectly > > clear when I adopted it that it will be a few weeks before I can get > > stuck into it fully. > > > > At the moment there are bug fixes I can do now that take priority over > > new features. Also, E17 as a whole is partially in a feature freeze. > > We want to keep adding features to make it feature complete, but not > > add features just because they are nice to have. This is in an effort > > to start on the road to a release. Your patch is border line, and > > probably closer to "nicer to have" than "feature complete". On the > > plus side, it is quite small. > > > > However, there are many, mostly small, things that need to be done to > > entrance in order to get it into shape, as it's development has stalled > > for a while without a maintainer. On the other hand, your patch is > > something that I would like to, but it is quite a low priority. By the > > time I get around to doing it, the code you have patched may be > > completely different. > > > > I suggest that you be happy that it will get done eventually and spend a > > small amount of time every now and then keeping your patch up ta date > > with what ever is changing in entrance. When I get around to > > implementing that feature, you will have a good patch ready to go. > > > > Thank you for your efforts. > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
