Hello,

Regardless that firm pencil's down date has come for this year's GSoC as
discussed with my mentor I will continue coding. These final weeks will
be split between coding, documentation, sample module creation and
polishing. Also a live ebuild creation is in progress.

Comparing uselect with eselect:

* uselect is much faster (even with lots of modules)
* uselect can already use (in a very ugly way) all eselect's modules
with a copy/paste step. It's still faster in this way.
* uselect menu is much more user friendly even though it's based on
eselect/ecletic.
* uselect has a general user-profile schema (using a ~/.uselect/
folder).
* uselect does not have a base function libraries as eselect does.
uselect objective was to create a simple framework that needs no logic
coding within modules.
* uselect can be easily expanded with more action classes with not much
coding as we are using an object based language with great inheritance
features.

Uselect is far from ready, but it's current state (besides usable) is
"presentable". What do I mean by presentable?

Uselect and Uprofile are a Proof of Concept of what both can be. I was
expecting better interaction and belief in the Universal Select Tool
project during all SoC. As most ideas/suggestions were purely based on
necessity and not on community-wide contribution as suggestion for new
action types templates a very solid and flexible framework was not
achieved. A solid example (symlinking modules) is fully supported either
user-wide and system-wide. A fine structure for .uselect folders
and .uprofile folders was not strictly defined as it is a very
decisional matter for general gentoo usability. Automatic module
creation during emerge is not possible without major changes to ebuilds
due to the lack of a list of "to-be-installed" files (there are ugly
workarounds, but none are worth implementing). Module's API is very
simple and can be easily changed from plain python to json or a similar
markup language. Uprofile (as current concept was not in my initial
proposal) is strictly a proof of concept of the interaction beween
uprofile and uselect's API. Once documentation and examples are done
uselect and uprofile will be ready to be presented to the gentoo
community and to be discussed within gentoo's decision organs.

It's been great to be working with gentoo. I hope that this tool gets
integrated in gentoo and I am willing to continue developing it after
SoC's end.

Thanks to everyone that helped, especially my mentor bicatali, people at
gentoo-dev@ and gentoo-soc@ and a few unknown folks at #python that
helped me solve complex python class mutation problems and recursiveness
paradoxes (this was the real deal).

Will also continue posting weekly reports on gentoo-soc@ until soc ends.

Cheers,
Sérgio
-- 
Sérgio Almeida - mephx.x@...
mephx @ freenode