On Sep 6, 2007, at 11:05 AM, Phillip J. Eby wrote:
At 10:39 AM 9/6/2007 -1000, Brian Kirsch wrote:
The goal as I see it is to gain new sources of funding by the point
the current funding ceases
so that Chandler development can continue with some level of both
community and in-house
support.
Okay, what new sources of funding? What will they want in exchange
for their funds? Let's surface any assumptions being made about
this, so that we're on the same page.
Specifically, what do you want to see happening *after* the funding
window has closed?
Let me rephrase the question:
Specifically what I don't want to happen
But what *do* you want to happen?
The problem with focusing on things we *don't* want to happen, is
that they don't provide a direction. It's like querying Google for
pages that *don't* contain the word "delay", instead of ones that
*do* contain "productivity" -- the second query will be a lot more
productive, no pun intended. :) Don't-wants are also very
difficult to prioritize, especially in a group discussion, and
they're almost never as actionable as do-wants are.
Well the discussion is based on Risk. Do we risk re-architecting for
a long term goal at the potential expense of features,
losing early adopters, and reaching the end of funding.
So considering what I *don't* want to happen is perfectly valid and
appropriate in this discussion.
Now on to what I would like to see by the end of 2008.
Month View, Contacts, Printing, Rich text editing, Localizations,
Cleaner UI experience,
Better UI menu verbiage and tool tips, enhanced detail view
experience, better Triage
capabilities, and incorporation of additional feedback from the
community.
Can we accomplish these and do a major re-architect by the end of 2008?
Of course I would love to see a full featured email client in there
as well but
the realist in me says that probably is not possible. I envision
continued enhancement
to the current plan of mail providing a gateway to bringing in and
sharing data
in Chandler with out fully replacing ones standalone mail client.
-Brian
is that a re-architecture of
Chandler takes a long
enough period that the death threshold is reached before major user
level improvements
(Contacts, Month View, Printing) are complete.
So let's rephrase this as a do-want: you want Contacts, Month View,
and Printing to be completed prior to the end of 2008. Is that
correct?
Yes there are risks either way. That is true. And you are correct
that Preview's delay was in large part due to the lack or
architectual changes
you are proposing. But there is an element of marketing that is
coming in to play now. Once we capture users we do not want to
lose them
because the project from a user visible standpoint stalls for a
period while a re-architecture takes place.
Also rephrasing as a do-want: you want users to feel good about our
progress, perhaps? For them to be confident that the features they
desire will arrive in a timely fashion? Or something else?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
