As someone pointed out I should describe what the project is/will do.

AmpFlow takes existing ideas about web wizards and extends them in new and
interesting ways. Specifically:

   - completely decouples the web front-end from the database
   - unifies wizard creation with API definition  (when you create a wizard,
   the equivalent API call is created automatically)
   - completely eliminates the need for @Persist (in our entire code base --
   no @Persists)
   - partitions user session data to allow parts of a user's session to be
   discarded when no longer applicable.
   - defers database object creation until absolutely necessary. (no more db
   cleanup if user cancels a complex operation).
   - eliminates database commits from the user http thread.
   - enables database changes to be reapplied at the *java* object level (as
   opposed to the low-level SQL layer) -- makes "Master/master" db
   configurations easier.
   - enables partial changes to be persisted for later -- *without* changing
   the "real" database objects.
   - supports "cancel/reset" operations in very complex scenarios.
   - completely bookmarkable
   - enables autoamatic support for small screens.
   - will support security model that allows partial access to portions of
   the wizard.

Some of the stuff needs a little more work -- but this is not vaporware --
we use it every day.

We are currently running Tapestry 4. However, the code has been divided
mostly into Tapestry 4 and non-Tapestry code. We do not (yet) have a
Tapestry 5 implementation.

-Pat

P.S. Locale does not matter.

On Mon, Jun 30, 2008 at 1:26 PM, Patrick Moore <[EMAIL PROTECTED]> wrote:

> Hi there --
>
> We would like to donate some code to the community. However, we find
> ourselves just a little strapped for time. If you would be able to help it
> would be great. We will offer a medium amount of money (hundreds of dollars
> -- but not thousands) to help us out. And of course, your name will be
> included as a contributor!
>
> The basics:
>
> Amplafi is open-sourcing a portion of our code base. We need a developer
> that can help complete some refactoring, add additional features needed to
> take product from the 0.8 level to the 1.0 level. You will be given public
> credit for your contribution when the project is open sourced.
>
> Responsibilities will include (in order):
>
>    1. Documentation (package/project level)
>    2. Sample code
>    3. Extending Test Cases
>    4. Refactoring
>    5. New features
>    6. Maven build configuration improvements
>
> Please note - You will be paid to learn this codebase, if
>
>    1. you document as you learn
>    2. you create example code to include in the documentation.
>    3. the code is confusing, you do a good job of refactoring - after
>    first discussing change.
>    4. you discover errors or inconsistencies, create test cases that
>    demonstrate the error and lastly fix the error.
>    5. you discover missing features, you add them (document and test as
>    well)
>
> Current code condition:
>
>    1. The code has been relatively isolated from the main Amplafi code
>    base. The majority of the hard work has been done.
>    2. The code has been isolated into 2 projects - web and core. Web is
>    Tapestry 4 specific. Core is intended to have no dependencies on Tapestry.
>    (but some remain)
>    3. Test cases are low in number - some of them still include
>    dependencies on proprietary code.
>    4. Documentation is extensive at the class level. Package/project is
>    almost completely lacking.
>    5. Functioning Maven project
>
> Success will mean that this code base:
>
>    1. has documentation understandable to the average developer.
>    2. Well-documented test cases with 80-90% code coverage (100% over the
>    key parts)
>    3. has complete sample code that can be run by users.
>    4. the remaining Amplafi dependencies have been eliminated
>    5. Tapestry-specific code has been removed from the 'core' project.
>    6. project is in condition acceptable to Apache.org committers. (HLS
>    should like it :-) )
>
> We think this will be a pretty cool addition to the Tapestry code base but
> we are also isolating parts of the code so it can work with other web
> frameworks. (including obviously Tapestry 5)
>
> This project would be something we would like to complete by mid-August ..
> so lots of time to do it on nights/weekends.
>
> Please contact me if interested.
>
> --
> Patrick Moore
> Amplafi
> 650-207-9792
> "copy/paste"
> blog : http://www.sworddance.com/blog




-- 
Patrick Moore
Amplafi
650-207-9792
"copy/paste"
blog : http://www.sworddance.com/blog

Reply via email to