On Fri, 18 Jan 2008 17:55:11 GMT "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> babbled:
> > > What: Gareth from SCALE has really kindly offered Enlightenment.org > > (that's use guys) free floor/booth space @ SCALE ( http://www.socal > > linuxexpo.org/ ) Next February (2008). So it looks like I will be > > there. Also Nathan of EWL fame and work will likely be there. > > Is there anyone else in the area (This is southern califronia) who > > wants to join and help put together/man a booth and at an expo? > > Hands up now? > > > I can make it there if need be. why don't you come just to hang out - since you're there :) > > Suggestions on things to do are welcome. > > > How about taking the opportunity to discuss "what could be > done" to improve the project, to address its weaknesses, to enhance > its strenghts, etc.? How about coming up with some concrete short > and long-term goals that people can see as real things that can be > worked on? (and I don't mean just e17-todos) at SCALE? that would require enough people are there to make that talk productive as such. that's really hard with everyone so distributed and most people not going to make it there. > I'll even start it here by listing some of the next-generation > projects in e's cvs. > > 1. The "core" efl libs: > evas, ecore, eet, embryo, edje, and some language bindings. e./org's trac is 100% intended for this kind of discussion. not day to day bug hunting and such - but a set of things to enhance/fix/do and when (eg do it for e17 - do it for e18, do this post evas 1.0.0 etc.) > 2. The "utility" libs: > esmart, efreet, e_dbus, epsilon, evfs, exml, ...? > What else belongs here? > > 3. The main toolkits: > ewl, etk, and some language bindings. > What are utility libs for these? > > 4. The "important" apps: > e17, entrance, ...? > What else belongs here? > > 5. The "utility" apps: > edje_cc, ... > What else should go here? > > 5. Other apps: > What should go here? > > > What are short/long-term goals, aims, roadmaps, progress, ... > for these things? What about for how they 'fit together'? What's > important in E and what's just incidental? > > Let's take epsilon for example. There was recent discussion > on how to perhaps improve epsilon in this or that way, some ideas > and whatnot... But, will anything come of that? Why should anything > be done to this lib at all? someone needs to take the ideas and discussion and basically - turn it into code. if someone is going to do that - and ACTUALLY do it (follow through) then they should speak up and so we know who is doing it :) it's not going to be me - as i said before i need to keep myself limited to what i already have on my plate :/ > I'm starting to think that having certain of these special- > purpose libs is a "bad thing". It just seems to lead to projects > falling by the wayside because there's little or no mechanism, > or community built around them, to ensure that their fires keep on > burning. possibly. > It might've been better if epsilon had been an 'ecore_thumb'. > Maybe then there would've been more attention paid to it over time. possibly. > Ecore may be a mish-mash of things, and some dependencies > there might be a bit twisted... But it's ONE identifiable important > thing that many people look at and work on. Much the same could be > said about e17 as well.. it at least manages to stay focused and > un-fragmented. mostly - but splitting can be good too - things that die then just die - they dont follow as dead-weight baggage. you can have separate development timelines and so on. so tis a give and take there of gains and losses. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
