Your wish list for Infusion 1.0?

Wed Feb 4 17:14:16 UTC 2009

I forgot to add something as well: I would be happy to see a clearer, more
intuitive and more up-to-date directory structure for our content.I started
a discussion about this a few weeks back, but I dont think any decisions
were made.

Jacob

On Wed, Feb 4, 2009 at 11:56 AM, Justin <justin.obara at utoronto.ca> wrote:

> Hello, I meant to add these comments before but forgot and was remind about
> it during the monthly teleconference.
> 1) polish up the current springboards. In some cases they deviate slightly
> from design (bugs have been filed).
>
> 2) create a spring board or demo page that has all versions of the uploader
> on it at the same time (i.e. all levels of the progressive enhancements are
> displayed)
>
> 3) general bug fixes. It would be nice to close out as many bugs as
> possible. I had been working on a set of bugs for a focussed test day for
> the 0.8 release. This may morph itself into a bug fix wish list for the 1.0
> release.
>
> - Justin
>
> On 3-Feb-09, at 4:54 PM, Jacob Farber wrote:
>
> One small addition: We've included the JSR 168 mapping as a deliverable.
>
> This page includes some explanations and addtional deliverables for FSS for
> 1.0
>
> http://tinyurl.com/cmpoop
>
> Anyone interested in UI Options and FSS should have a peek.
>
> Jacob
>
>
>
> On Tue, Feb 3, 2009 at 12:32 PM, Jess Mitchell <jess at jessmitchell.com>wrote:
>
>> This is a great list y'all!
>> What a wonderful start to our rounding out the 1.0 version of Infusion.
>>  To be clear, this is planning for a release -- the work of Fluid and of
>> Fluid Infusion will continue on beyond the end of March.  Having said that,
>> this is a big release for us -- the culmination of a lot of hard work by a
>> great bunch.
>>
>> Many of my wishlist items are already on the list which is wonderful:
>> documentation, documentation, documentation
>> - one of my favorite things about Fluid is our commitment to being open
>> and to sharing our work and our experiences with everyone.  We teach through
>> our documentation and I see that as a very important part of growing our
>> community.
>>  - packaging script.  This has been on a list of mine for quite a while
>> -- it's a return-to item and I'm super-excited to see it on the list and to
>> know it'll be there for 1.0
>>  - licensing. I'm thinking here of the kind of activities that we can do
>> to ensure we've got clarity on licensing of any code we are working with.
>> - website.  We're working now on getting a refresh to the current site.
>>  We need to ensure we're showcasing the products of Fluid Project
>> meaningfully and clearly.
>>
>> That's what I have so far, but I'll continue to think wishful thoughts.
>>
>> Thanks,
>> Jess
>>
>>    ~~~~~~~~~~~~~~~~~~~~~~
>> Jess Mitchell
>> Boston, MA, USA
>> Project Manager / Fluid Project
>> jess at jessmitchell.com
>> / w / 617.326.7753  / c / 919.599.5378
>> jabber: jessmitchell at gmail.com
>> http://www.fluidproject.org
>> ~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>>
>>
>> On Jan 30, 2009, at 6:12 PM, Colin Clark wrote:
>>
>> Hi everyone,
>>
>> As we get closer to the Infusion 1.0 release at the end of March, I have
>> been chatting with various designers and developers in the community to get
>> a feel for the features, bug fixes, and tweaks we are all hoping to include
>> in this milestone.
>>
>> I've posted my notes so far to the wiki:
>>
>> http://wiki.fluidproject.org/display/fluid/Infusion+1.0+Wish+List
>>
>> In my mind, an obvious goal for a 1.0 release is stability: we expect
>> Infusion to be very reliable and stable by this time. But Infusion 1.0 also
>> isn't the end: we'll continue to add new features and cut new releases on a
>> regular basis after March. So our goal is to balance important bug fixes
>> with a few new features that will lay the groundwork for the future.
>>
>> I'd like to make sure this conversation is open to everyone in the
>> community. Now's a great time to share your thoughts; is there a killer
>> feature you think we're missing right now? Bugs that are essential for us to
>> fix? Areas that could use a bit of polish or attention?
>>
>> Let us know,
>>
>> Colin
>>
>> ---
>> Colin Clark
>> Technical Lead, Fluid Project
>> Adaptive Technology Resource Centre, University of Toronto
>> http://fluidproject.org
>>
>> _______________________________________________________
>> fluid-work mailing list - fluid-work at fluidproject.org
>> To unsubscribe, change settings or access archives,
>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>
>>
>>
>> _______________________________________________________
>> fluid-work mailing list - fluid-work at fluidproject.org
>> To unsubscribe, change settings or access archives,
>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>
>>
>
>
> --
> Jacob Farber
> University of Toronto - ATRC
> Tel: (416) 946-3002
> www.fluidproject.org
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
>
>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
>
>

-- 
Jacob Farber
University of Toronto - ATRC
Tel: (416) 946-3002
www.fluidproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20090204/22959964/attachment.html>