Quote by: Laugh
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 actually can't say. I expect there to spurts of great activity and then droughts of nothing. Over the course of the whole thing it will probably average 10 hours a week. But there's nothing I can put a schedule to.
I've started mocking up the entry screen for recurring events but there's nothing there yet. I do plan to make the recurring period extensible so I can just code something like weekly. Get everything working around weekly events and then start adding in the weirder ones. This way, if someone has an event that's only on third wednesday of months whose names ends in 'y', they can just code the extension themselves.
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.
That reminds me. I'm going to turn the feature list into a set of bullet points so I can arrange them in a better order. Currently there are three big chunks and that will make it hard to determine if it's finished or not. The purpose of the list is to not forget anything. Stuff like: mssql supprt (and hopefully we have someone around who can test that), mbyte support, etc. I'll go through the original posts and followups to come up with a hopefully complete list. This will give me a guide and a way to say I'm xx% done.