There are many different criteria by which voting systems can be evaluated.
One of the most important criteria to me is proportional representation. Closely related to this are transferrable vote systems, which help maintain proportionality.
I was surprised to find out, after moving state within Australia to Queensland, to find out that it was the only state without some form of proportional representation!
All other states have an Upper House elected by proportional representation. The Lower Houses are formed from single member electorates, and so absolutely dominated by the major parties with no proportionality, but the bicameral parliament ensures some measure of democracy is maintained.
(Effectively, with the Lower House always dominated by one party or the other, there is never any possible meaningful debate there; the government will always win, every time. The only real debate, negotiation and compromise, or possibility of failure, occurs in the Upper House.)
As shown in the graphs below, at a federal level, there is already a degree of bias towards the major parties (getting more seats than the proportionally should), due to the high quotas (low number of positions) in the Senate. Recent proposed changes will make this even worse, with the 18% of voters for minor parties reduced to a single seat (2% of the parliament).
The common stack I am currently using to build SharePoint Online solutions generally consists of the following components:
- Visual Studio console application for remote provisioning
- IonFar Migration framework, https://www.nuget.org/packages/IonFar.SharePoint.Migration/
- Office Dev PnP PowerShell Commands, https://github.com/OfficeDev/PnP/tree/master/Binaries
- SharePoint Online Management Shell, https://technet.microsoft.com/en-us/library/fp161372.aspx
- An Office 365 Developer subscription (essential for anyone doing SharePoint development)
- A central Git repository (e.g. Visual Studio Online), for source control
- TeamCity build (e.g. hosted in Azure), for builds
- Octopus Deploy, for deployment
This stack allows automated deployment of the project against a continuous integration (CI) environment. Simple migration scripts (written in PowerShell) are cumulatively run against the environment, and can be easily promoted to a UAT and then Production environment.
A SharePoint deployment typically has different types of sites, with different levels of governance. The central published site usually has tight governance over structure and information, whereas group and team sites have less restrictions and more flexibility.
This guidance is around team sites, where although the site collection must initially be set up by a SharePoint administrator, at least some team members have administration permissions to the site and can manage the site schema and structure. Read the rest of this entry »
An expanded client-side development model, which includes Apps as well as techniques such as remote provisioning, was released with SharePoint 2013. SharePoint Online does not support server-side development, apart from limited sandbox solutions, so client-side development must be used, whereas for stand alone SharePoint both the new client-side model as well as the original server-side model are available.
I have used several of the different alternatives for client-side development, and thought I would provide my overview of when each is suitable and my current preferred approaches.
Read the rest of this entry »
Based on the liberalism index (freedom-leaning vs control-leaning) from the ABC Vote Compass data, Jack Mackay (https://www.facebook.com/jack.mackay.378) has created a map of the electorates coloured by their rank on the liberalism index.
For contrast I’ve included the original map, with colours by political party (although from an older source, for the 2010 election).
The ABC Vote Compass consisted of 30 questions: 15 related to social freedom and 15 related to economic freedom. Each question had five possible answers: strongly agree/disagree, somewhat agree/disagree and neutral, with ‘sometimes’ given a value half as much as a ‘strongly’.
Some of the summary data now is available, allowing an initial analysis, such as an overall liberalism index, showing the most control-leaning vs freedom-leaning seats, the compliment to the most left-leaning and right-leaning seats reported by the ABC.
Electorates such as Curtin (Julie Bishop), Wentworth (Malcolm Turnbull), Melbourne (Adam Bandt), Griffith (prev. Kevin Rudd) and North Sydney (Joe Hockey) are some of the most freedom-leaning seats, whilst Kennedy (Bob Katter), McMahon (Chris Bowen) and New England (Barnaby Joyce) are at the other end of the spectrum.
This post details my thoughts on where to start with branding for SharePoint 2013. In particular, I think Themes (.spcolor, .spfont) are now usable, and recommend to start there, linking to a couple of resources. But first, I talk about what not to do.
What not to do
It might seem like a good idea to get a graphic design company to develop a whiz-bang look for your intranet, then turn around and ask a web development company to turn it into a SharePoint branding. Often this starts out with an HTML reset or HTML boilerplate.
The core SharePoint stylesheets have over 10,000 lines of CSS — unless you want to rewrite all of that, you do not want to be doing a CSS reset. You never know when BI dashboard widget XYZ is going to need to display a green/red traffic light based on some CSS buried deep within the core files.
Don’t do it.