Australian government likely to standardise on Drupal
computerworld.com.au
Australian government likely to standardise on Drupal
1–10 of 51 posts
Re: Australian government likely to standardise on Drupal
#2"GovCMS is intended to support more effective web channel delivery functions within Government, and enable agencies to redirect effort from non-core transactional activities, towards higher-value activities that are more aligned with core agency missions," a draft statement of requirements issued by AGIMO states.
'''
It appears buzzword abuse is becoming an international problem across multiple industries and agencies. I recommend a UN task force to look into it and take the appropriate measures. Sanctions are defiantly in order, but at this point nothing should be off the table.
Re: Australian government likely to standardise on Drupal
#3Re: Australian government likely to standardise on Drupal
#4Re: Australian government likely to standardise on Drupal
#5The Australian government is particularly stupid at the moment. I leave as an exercise for the reader the question of whether this is example or counter-example of that.
Re: Australian government likely to standardise on Drupal
#6Meanwhile, they had a grand opening at Parliament House to which all the media were invited -- and I was very pointedly not invited, presumably because they were worried I'd say rude things about them (spoiler: I would have). Then the leader of the National Party chose that morning to resign, and nobody from the media came to the launch party because they were busy over the other side of the House interviewing him. So I felt a certain degree of whatever that German word is for "serves you right, you bastards".
Meanwhile, australia.gov.au had a bunch of redesigns and is even better now, so the three guys they brought in to replace me obviously did good work...
Re: Australian government likely to standardise on Drupal
#7The Australian government is particularly stupid at the moment. I leave as an exercise for the reader the question of whether this is example or counter-example of that.
But you'd imagine (or hope?) decisions like this aren't being made by any MPs, who probably know little about IT.
Re: Australian government likely to standardise on Drupal
#8The draft Statement of Requirements for GovCMS: http://www.finance.gov.au/sites/default/files/GovCMS%20State...
Some notable tidbits:
- No analysis seems to have been done on the approach of hiring their own developers to develop a custom-yet-cohesive solution, a la Gov.uk.
- The CTO says "Drupal appears to offer the best enterprise-level as shown by our previous extensive analysis". Can someone refer me to this extensive analysis? Have they considered the security risks of standardizing on a single platform? http://www.cvedetails.com/vulnerability-list.php?vendor_id=1...
- "A solution hosted offshore would not be excluded from consideration" So, putting Australian Government infrastructure in the US is OK. Subject to US laws. Fantastic.
- Does anyone know if the government intends to contribute to Drupal development? They say that they expect some "feature rich" sites to require custom modules, but what about Drupal itself?
Re: Australian government likely to standardise on Drupal
#9However, there used to be more U.S. Drupal sites, including Data.gov...there was even some hubabaloo about them releasing the source code:
http://www.whitehouse.gov/blog/2011/12/05/datagov-goes-globa...
https://groups.drupal.org/node/194808
Viewing the source code of the current data.gov (view-source:http://www.data.gov/), it looks like the moved it to WordPress. That's a pretty damning migration.
Edit:
The current repo for Data.gov can be found on Github - https://github.com/GSA/data.gov/
Here's the shit-show that was apparently Data.gov's Drupal installation: https://github.com/opengovplatform/ogpl-d7
And quite humorously, it seems to be something that we're exporting to other governments, such as India https://github.com/opengovplatform/opengovplatform-beta
Re: Australian government likely to standardise on Drupal
#10They do a lot of research, produce a lot of reports, publish a lot of "standards", and then everyone else just ignores them and stumbles on with whatever they were doing before.
The people who are already married to some solution will remain married to their solution; they will successfully argue for exemptions.
Those who are determined to use something else will use political capital to get another exemption.
Those who are forced to make the switch will make the switch, but the old system will probably hang around for a long time, more than doubling the overall cost due to double-entry and errors.
Some will make the transition, it will fail, then transition back.
In the end the government standard will be taken up by a handful of sites, AGIMO or its heirs and successors will declare total success, the Minister will have been rotated to something else or kicked out at an election and nobody will give two hoots.
Welcome to public sector computing! It's like enterprise, except even crazier.