[Building Sakai] Entity Broker Future - In Kernel / Main SVN

Stephen Marquard stephen.marquard at uct.ac.za
Thu Nov 25 10:49:33 PST 2010


If we want to "evolve EB forward" then we specifically should NOT move
it into the kernel, to facilitate more frequent releases.

The only real reason to put something into the kernel is to simplify
the dependency tree, or if we want kernel code to depend on it. Is this
the case here?

Regards
Stephen 
 

-- 
Stephen Marquard, Learning Technologies Co-ordinator
Centre for Educational Technology, University of Cape Town
http://www.cet.uct.ac.za
Email / IM (Jabber/XMPP): stephen.marquard at uct.ac.za
Phone: +27-21-650-5037 Cell: +27-83-500-5290 


>>> csev <csev at umich.edu> 11/25/2010 6:39 PM >>> 
Back in June in Denver we talked about "moving EntityBroker to Kernel"
- but then we also decided that we wanted 2.8 out quickly and so we
tabled anything that felt a little complex and EB in kernel fell into
that category.

But now with 2.8 properly branched and in QA, it is probably time to
pick it back up so we can re-factor the EB code early in the 2.9 release
process.  I am not an expert on EB - but these are the things that seem
like a starting point to this effort based on my limited understanding
and use of EB:

- Move GenericDAO and the EB Registry to Kernel

- Pull a copy of reflectutils from Google code into kernel

- Move /direct to its own indie project under /svn

Aaron would be the project lead on /direct and become an official
kernel committer to keep work on EB registry and GenericDAO.  Aaron
already has super-commit to everything as a maintainer - this would
simply mean he is also listed a formal member of the Kernel team (for
votes and such).

For me, once this is done, I can see increased use of EB in lots of
areas like portal and LessonBuilder and other emergent areas of the code
- I can imaging that these new uses will expose new EB use cases and we
can evolve EB forward together to meet those new use cases.

Comments welcome.

/Chuck

_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to
sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
"unsubscribe"



 

###
UNIVERSITY OF CAPE TOWN 

This e-mail is subject to the UCT ICT policies and e-mail disclaimer
published on our website at
http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from
+27 21 650 9111. This e-mail is intended only for the person(s) to whom
it is addressed. If the e-mail has reached you in error, please notify
the author. If you are not the intended recipient of the e-mail you may
not use, disclose, copy, redirect or print the content. If this e-mail
is not related to the business of UCT it is sent by the sender in the
sender's individual capacity.

###
 


More information about the sakai-dev mailing list