Hi...
There are s many things I would like to add to this conversation (from the
educator's perspective). But there is another, more important issue I would
like to address, recruitment of developers and other talent.
I have been watching with fascination the wonderful progress the folks
Martin - I'm not worried about developers trying Sugar, they can
figure it out. I'm worried about teachers doing so. The devil is in
the details of course. I agree that the splintered e-book reader
Activities situation doesn't help us, and iffy Record too. But these
are symptoms of our limited reso
Peter,
The incoherence I am talking about is marketing, not engineering. We
had identified e-book readers as key and promoted SoaS that way.
Dropping those six months later is incoherent. Credibility counts.
FOSS marketing (in the sense of targeted marketing, not contributor
recruitment) has a mo
On Mon, May 24, 2010 at 08:56:27PM +0200, Sean DALY wrote:
> Our problem is the incoherence between the two previous versions of
> SoaS and this one
"Versions" between which there is "incoherence"? You're talking
software to developers, and your marketing is showing.
> and the incoherence with o
Sean,
On Mon, May 24, 2010 at 7:56 PM, Sean DALY wrote:
> Sebastian,
>
> Our problem is the incoherence between the two previous versions of
> SoaS and this one, and the incoherence with our marketing strategy
> which is to promote a rich ecosystem of Activities for which Sugar is
> the support.
Sebastian,
Our problem is the incoherence between the two previous versions of
SoaS and this one, and the incoherence with our marketing strategy
which is to promote a rich ecosystem of Activities for which Sugar is
the support. We can't talk about new SoaS features or large
deployments, so there
