August 22-23, Wellington NZ
There's a some funding available through nonprofits for the development of civic tech applications, but infrastructure has been largely overlooked.
Applications are often not reusable because of the cost of bespoke infrastructure and implementations. Government security constraints complicate the issue.
Pol.is can be self-hosted or you can use their SAAS.
Users can authenticate within channels of their choice.
Agile deployments would allow citizens to explore more applications.
They've actually moved legacy applications to Linux.
The move to modern technologies is going to open the door for new and different contractors.
You can do a tour!
How do you authenticate?
Staging the deliberation can help, but could take more than one application.
Offline initiatives need to be integrated somehow.
Can you really run a democracy with a centralized server?
Citizens vs. Users
Systems engineering is now about political, not just technological systems. You have to understand the implications of your code.
There's already a crisis in federal IT. Poor digital defense is compromising our most basic citizen privileges.
Political arguments about the safety or security of cloud based systems are delaying necessary innovations.
It's not a luxury or a trend. We need citizen participation for more efficient government, and technology can do it.
We need requirements for security and authentication in exploratory deliberations.
In a democracy, every problem is a problem of the citizen.
We have the talent and skills to build a better government - maybe the most important skills.
Improving government infrastructure can help with the government talent problem.
It's a matter of global leadership.
Citizens pay for the code, they should be able to reuse it.
Trust in government is at an all time low. We need transparency.
Defaulting to open can help purge entrenched interests.
Ele Munjeli @ LinkedIn, munjeli @ Github
https://github.com/devopracy, @elemunjeli on twitter