Will there be a clear distinction between Governance issues and Code Sprint/Dev issues (can there be?)
Disclaimer: I understand that the issue I'm raising should have been raised long ago and it's likely too late to address/change the schedule.
I'm concerned about the dynamic of having the code/dev sprints after the lengthy discussions and debates about governance issues.
My primary concern is that those of us who plan on coming for the Governance section and not the dev sprints will end up missing out on critical conversations related to governance. I think it would create a better overall dynamic of being cooperative and not oppositional if the sprints happened first -- and the governance conversations had a hard end.
Not only do I have concerns that the stress of the governance discussions will carry over and impact the productivity and fun of the sprints; I also worry that the conversations will carry on without a certain subset of voices and that could impact the future direction of the discussions.
Are there going to be parts of the sprint days focused on continuing governance discussions? Is there any way to prevent that, given the reality that people are people and will be together 24/7 for another 2 days after the governance discussions?
Is it too late to switch the order and have the sprints first? As stated above, my assumption is that it is indeed too late but I hope that by raising this issue we can all do our best to avoid the problematic parts of the dynamics I mention above -- also these issues are making me rethink my travel plans and how many days I'm going to attend and I imagine others are in a similar situation.
Can anyone clarify about if there will be sprints explicitly related to governance?
see you all soon.