I think brainstorming on new cards should rather be done in the forum or in CS once its done (just did some coding
). At least I don't see an advantage in doing this in a scheduled meeting.
My bad - I have been unclear on that point: I do not want to schedule meetings to create new cards. Meetings I suggest are there for other reasons, could be pretty much anything, and to make people get in touch in a more structured way at least every now and then. It's just a way to make it easy to meet up and get a chance to catch up as well as discuss whatever needs communication.
And new cards should be proposed whenever someone has a good idea. That's just something you can't schedule.
And I don't see any reason why we should only playtest every two weeks in a row. We should rather do it every time we find a proper timeslot in our busy lives^^.
I don't think that a dev. cycle should be there to prohibit
or somehow hinder people from play testing if they want to - that, as any of the other processes, should be possible and perfectly ok whenever if a person wants to do it and will indeed do it.
From our experience we (ok, maybe just I) have however concluded that too little happens on this front. I turn to myself and know I should have solved plenty of issues long time ago, but haven't, since I know that I as a person need a "push" and some more structure to get more productive. I am easily distracted and also spend time on a lot of stuff that is non-essential.
I only want the cycles there in an attempt to insure more continuity in our work. Not less. I'd consider them as being some kind of "guarantee" that some tasks get the proper attention they deserve, in this case the rules and card dev.