As we discussed in our call on Tuesday, it is time that we held a
face-to-face developers meeting. Now that we have a fully functioning
committers group that has done its first community managed release, I
think that it would be good to have a meeting where we could plan the
bigger picture for the Fedora roadmap. When I recently attended the
joint UK/Ireland and EU users group meeting in Oxford, several of us
talked about having a meeting to move the content model functionality
ahead more quickly. In the planes and trains after that, I thought
more about it and think that we should have a more general meeting, at
which the content model stuff would be a major part.
Chris and I have to be in London for a meeting on Monday, February
22nd, so we would like to organize a meeting on the 23rd and 24th. I
think it would be good to have such a meeting then, so that we could
count on a followup meeting in July, at OR2010, where most of us will
be likely to be present anyway. Being able to have two meetings with
some time in between will give us a chance to get everyone going, then
boosting things again 3-4 months later.
I think it would be good to think of such a meeting as sponsored and
organized by the committers group. Each of you committers should think
of likely contributors who should also be invited. My role in all of
this is to work on ways of making it happen. I will be looking for
place to hold the meeting on those two days in London, so if any of
you can help with that, please let me know.
As a starting point (please, take all of this as a strawman to get us
started), I propose that this meeting concentrate on three big topics,
which I keep hearing about in my travels:
1. Moving the content model stuff to the next level, specifically
considering Asger's ECM stuff and the development of a set of tools
that would make it more user friendly, like integrated object builders
for CModel, SDef and SDep objects, as well as tools for managing
related ontologies, etc.
2. Caching strategies for Fedora that make it easier to handle very
large datastreams and generally improve performance.
3. Expanding the possibilities for handling different back-end storage
strategies, to include consideration of things like hierarchical
storage, the grid, CDL's BTrees, etc., as well as things like
multiplexing backend store to be able to include more than one
strategy for managed content. This may be an Akubra-related topic but
it is definitely very important to the future of Fedora.
I welcome any conversation on the list in the meantime, but let's talk
about all of this in our next meeting on Tuesday.
Thorny
____________________________________
Thornton Staples
Director of Community Strategy and Alliances
Director of the Fedora Project
DuraSpace, Inc.
[email protected] (202) 684-6952
skype: thorny.staples www.duraspace.org
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Fedora-commons-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
