Hello gang,

I'm sure some of you have (passively) read some of the discussions
that are occurring on #edevelop from time to time regarding the
direction this project is taking. I am mainly talking about E17, the
window manager, and not the entire EFL.

The main discussion was centered about how we're developing E17 and
where its going. We now have two places where we keep TODO items and
bugs, the TODO file in apps/e, and bugzilla. The way things are going,
we have several "open" features in E17 that are partially done, some
major, some minor. Among those features are EFM, and the First Time
Run Wizard (FTRW).

EFM was supposed to be a simple file selector, it then grew into a
file manager, it then started getting custom directory and window
configuration abilities, and then grew so big it needed its own
process. As it stands, none of its features are 100% complete and
almost without bugs, except the file selector. The file selector is a
core part of E17 (for obvious reasons), but the file manager is really
not. I would classify it as a nice to have feature, along with desktop
icons, but its nothing major that can prevent a release from
happening.

The FTRW is a useful feature to have that has also been started and
has not seen completion yet. It was always on the TODO, but it sprung
out of no where at a certain point in time during the EFM development
cycle. Although its a nice and very useful feature, and I think it
would be a good idea to have it available when we have a release, its
taken development time from EFM and other incomplete features in E,
and is currently not finished. Yet another incomplete and relatively
big feature.

Some other items in the TODO are considered medium sized tasks, and
the majority can be considered small tasks. I don't know about the
state of things in bugzilla, but we can assume the same as with the
TODO.

So the main question I have for everyone is, what now? We're writing
code, time is passing, and we're not closing (or barely closing) any
of the items on the TODO. New features that are not always planned
make their way every now and then, and we're never substantially
closer to a release or a release candidate. What do you folks propose
we do to handle this problem? Should we freeze the addition of new
items to E17 (similar to the freeze done a while back) and concentrate
on closing all the TODO items and the bugs? Whatever decision we make,
we need to do something about the way E17 is being developed, and the
pace at which it is being developed at.

-- 
Hisham Mardam Bey
http://hisham.cc/
+1-514-713-9312
Codito Ergo Sum (I Code Therefore I Am)

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to