Re: [Dynapi-Help] IOElement, get Data

[Leif W <war...@us...>]

> ----- Original Message ----- 
> From: "Raymond Irving" <xw...@ya...>
> To: <dyn...@li...>
> Sent: Friday, September 17, 2004 17:12
> Subject: Re: [Dynapi-Help] IOElement, get Data
>
> Sounds cool. I'll take you up on the offer.
>
> PS. Currently I'm involve in some projects that are
> taking up time. I could drop some of them and spend
> some but the thing is that they help to pay the bills.
> What if I where to startup a paid or donated support
> system on my site, will anyone be interesting? This
> way I'll be able to spend more time, improving and
> supporting the project to the fullest. Anyone agrees?

Sounds like a reasonable idea to have a paid and/or donate site.  I'm
not so fast at coding, and always seem to be sidetracked (hardware
problems, daily living, etc.) despite intending to get my hands back
into the DynAPI.  So for me, I'd just donate my time and not expect
anything but would accept anything.  In any case, if you need to pay
bills, you need to get paid by the hour to ensure you're not going
offline or carless or homeless.  :p  But if you're paying for code to be
written or debugged, you want to pay based on satisfactory results, and
a reasonable time table.  But each result may take variable amounts of
time.

Taking all of this into account, maybe outstanding items that people
want to see fixed could itemized, and a time and cost estimate be
published, and open the task to be donated to at any time (donations
would not guarantee a timeframe), or if someone wants to pay the
remainder in full (payment would guarantee a timeframe), the item could
receive highest priority.  Coders could have an account to log in to,
see what work needs to be done, who's willing to pay, the priority
ranking of each item, see who's working on what, and perhaps request
assignment to the task.  No money would ever change hands until what was
outlined was satisfactorily achieved by both donater and coder.

Maybe a good idea, but could potentially have some pitfalls which would
need to be navigated carefully.  I know people get funny sometimes when
money changes hands.  Clear outlines of specific pieces of work and
expected results are key points, as well not straying to unrelated
features or modifications.

Leif