I'd make it available to everyone
why not do a ransom type plugin. Develop the plugin, then hold it for ransom. When your minimum is reached, then release the plugin. People would probably give up some cash quicker if they knew the code was already good to go.
It's the same thing really. You just don't have to listen to all this pledge back and forth stuff.
Really I'd rather just put up some dough and have you do it. That way we get a quality product and you make a few bucks.
why not do a ransom type plugin. Develop the plugin, then hold it for ransom. When your minimum is reached, then release the plugin. People would probably give up some cash quicker if they knew the code was already good to go.
It's the same thing really. You just don't have to listen to all this pledge back and forth stuff.
Really I'd rather just put up some dough and have you do it. That way we get a quality product and you make a few bucks.
Oh, come on, no one here will have the heart to let jmucchiello work for months and then tell him "sorry, buddy, it's not good enough, no money for you."
I mean, unless he ends up tricking everyone, no one will take his (yes, his) money away because the script works in 80% capacity and not in 100%.
I'm sure that's why samstone isn't willing to pay. He knows once he commits, it wouldn't be right to eventually not pay.
Dirk, we need your paypal account info.
Lets say we will collect funds till the end of August, if not enough funds are received, the first week in Sept the funds will be returned to all people minus any paypal charges, if there are any.
Here's my task list. There are a few outstanding issues here. I don't know if this is the right thread though to discuss them. Let me know if I've missed anything critical.
If you have already attended the dropdown will display your current indication (with text like "Your RSVP of "will attend" is already recorded") and the submit button becomes a modify button.
For that reason and because it doesn't take much effort I suggest something like the evite.com model: Include a "# of guests" field and a "remarks" field so people can leave comments.
This means we now have "Allow members to RSVP for this event", "Allow members to bring guests", "Allow remarks"
weekly: accepts list of days (M,T,W,H,F,S,U) Days can be followed by *2 or *3 to indicate every 2nd or 3rd that day.
monthly: accepts list of days where the day by itself means every week on that day. Day can be followed by 1,2,3,4,5 or L mean the 1st, 2nd, 3rd, 4th, 5th or last occurrence of that day in the month. Monthly can also take specific number 1-31 as well as L and L-1, L-2, etc.
yearly: accepts a list of dates in MON ## format (Jan 1, Dec 31) or WEEK ## D (week 16 M)
list: accepts a list of dates in YYYYMMDD format (20070801,20070809,20070820) Events only occur on specified dates
daily: accepts a number as it's list and the number is skip period so by default it is 1.
Other examples: (weekly: M,T,W,H,F) (weekly: S,U) (weekly: M*2: start=20070820) (monthly: F2,F4) (monthly: 1,15) (monthly: 15,L) (yearly: Jan 1) (yearly: Jan 1,Apr 1,Jul 1,Oct 1) (and: (weekly: M*2,W*2,F*2: start=20070820),(weekly: T*2,H*2: start=20070827))
Modifiers such as start= allow for stuff like every other Monday. The date after start tells you which Monday it first occurs so you can find every other Monday there after.
The code will have event_recurring_weekly and event_recurring_monthly style functions so to handle unusual recurring needs. Stuff like holidays based on lunar calendars (Easter, Passover, Ramadan). Implemented correctly, I can imagine someone making events selectable based on a non-western calendar.
Another example would be something like event_recurring_usholdiday which defines all the federal US holidays and allows you specify events based on those key words. They don't even have to be recurring at that point. (usholiday: thanksgiving)
The event_recurring_xxxx function will return various things depending on its inputs. One mode would be to return a partial HTML form (hopefully using a template) so users can create an event of that type. Another mode would be to parse the form data into the above tuple format. A 3rd mode would take the tuple and a date and return the next occurrence of that event. Other modes may be needed but those are the main 3.
If no one objects, I hope you'll even let admins add reminders (that way, an admin could create fake users just to send reminders to people).
Also, will you have a snooze feature? Something like "here's your e-mail reminder. Click on this link to be reminded again in X time." If not, at least you provide a link to the edit the event.
What do you mean by "one-off"? When you say "people", do you mean admins (who can just mass mail)?
I wish you'd let the admin just subscribe users to reminders, just like the admin can sign them up for groups. Not everyone is a power user (or: sometimes people want reminders from you, but you can't tell them to do it themselves).