Ok, lets give everyone till Wednesday for a chance to Vote (I go on vacation this Friday). I'll tally up the votes and post the results. I'll help Text out with the requested features since I feel we need at least 2 doing this.
jmucchiello has taken up the bounty so that is set. The bounty has been talked about for awhile and there have been no other takers. Hopefully he can get things done as soon as his schedule allows (as he mentioned in previous post).
Quote by: Laugh
I am assuming everyone is fine with jmucchiello coding this project.
Once jmucchiello takes the project, the feature list should be locked (unless the developer agrees with an addition)
jmucchiello what is your schedule here? Have you started or are you waiting until the pledges are collected or until your schedule opens up. Also, what is your ROUGH estimate of a time line to getting something for testing, as example, 20 hours in 1 week or 20 hours spread over a month.
I am sure one of us can hold the money but I think Dirk would be the best choice (if he has the time) since he has the account etc.. in place and is dealing with other bounties. Plus he will have to check the coding to make sure it meets the geeklog coding standards before incorporating into the build (unless he is spinning off this plugin).
Maybe 3 of the people who have time and who have made some of the larger pledges (they have more at stake) would like to take control of the requested features list. When any 2 says all features have been implemented, are bug free, and Dirk OK's the code, then the bounty can be paid.
So lets vote:
Feature List Locked?
- My vote is for Dirk (if he wants too) or ttOne.
- Maybe a few people who submitted $200 would like to take this up?
One of the Geeklog Core Developers.