Changes

** making a statement that current ASLO workflow is pretty unreliable, since ASLO is deployment agnostic, trying to bundle binaries to .xo is pretty fragile practice. At the same time taking one particular decision would either affect basic sugar workflows (fully bundled .xo) or leave situation fragile

** making a statement that current ASLO workflow is pretty unreliable, since ASLO is deployment agnostic, trying to bundle binaries to .xo is pretty fragile practice. At the same time taking one particular decision would either affect basic sugar workflows (fully bundled .xo) or leave situation fragile

** thus it (could)requires non tech agreement to follow either "activities should not rely on non-SP dependencies and we should make it clear that we are not going to deploy Java/Qt/etc activities from ASLO" or "we will deploy Java/Qt/etc activities from ASLO and lets take the right tech decision(out of SLOBs) but (maybe) accept moratorium like [http://thread.gmane.org/gmane.linux.laptop.olpc.sugar/21243] to not make situation worse until we take right tech decision" ways

** thus it (could)requires non tech agreement to follow either "activities should not rely on non-SP dependencies and we should make it clear that we are not going to deploy Java/Qt/etc activities from ASLO" or "we will deploy Java/Qt/etc activities from ASLO and lets take the right tech decision(out of SLOBs) but (maybe) accept moratorium like [http://thread.gmane.org/gmane.linux.laptop.olpc.sugar/21243] to not make situation worse until we take right tech decision" ways

* Review of Google Summer of Code planning

* Review of Google Summer of Code planning

* Review of our Goals for 2010 ([[Oversight_Board/Meeting_Minutes-2010-01-22#Goals_for_2010_2|goals]])

* Review of our Goals for 2010 ([[Oversight_Board/Meeting_Minutes-2010-01-22#Goals_for_2010_2|goals]])