|−|= Miniconfs/OpenGov = |+|
are . be .
|−|All information that intended for public consumption should be at least |+|
|−|CC-BY (or lGPL for software). I would prefer CC-BY-SA and full GPL for |+|
|−|software so changes are more visible. This is essential for software. |+|
|−|Software disclosure is more important as software can be used to change |+|
| || |
|−|I am a member of an Australian Standards committee BD 58. This |+|
|−|committee wanted to borrow just the electrical safety information from |+|
|−|CPSISC Pocketbook V2 for an annex. As the Australian Standards and the |+|
|−|process is closed it could not be a Share Alike style license like GPL, |+|
|−|CC-BY-SA, etc., but the CC-BY attribution license was ideal. This |+|
|−|licence was recommended by the Government 2.0 Taskforce. |+|
| || |
|−|The document was a DRMed PeDoFile with just copyright and no mention of |+|
|−|a license. To crack it or use it in any way I needed to obtain written |+|
|−|permission to supercede the secret and unknown DRM conditions. |+|
| || |
|−|I obtained advice which also recommended that I seek to obtain the |+|
. and to .
|−|material under the CC-BY license. This was discussed with Standards |+|
|−|Australia and BD 58. Then I had job of finding who to ask. I finally |+|
|−|was able to contact DCCEE - Legal at climatechange.gov.au in Nov 2011. |+|
| || |
|−|I finally got a reply in Jun 2012 which was CC-BY, but with additional |+|
a , .
| || |
|−|> (a) The material must be used in an appropriate context and reproduced |+|
. the . to .
|−|> accurately without distortion of meaning. |+|
|−|There were many factual errors and only some of the electrical safety |+|
|−|section was useful. We had members of wiring committee EL 1 to assist. |+|
| || |
|−|Attribution (b) is reasonable and required by the CC-BY license. By |+|
. be .
|−|attributing the original document any changes would be visible. |+|
| || |
|−|> (c) The material must not be used for commercial sale or profit. |+|
The are and
|−|Australian Standards are not free or open. They cost money and |+|
|−|discussions are confidential. |+|
| || |
|−|This DRMed PeDoFile cost a bomb to produce and only had marginal |+|
to and in the . ,
|−|entertainment value and was in conflict with the Australian Standard |+|
|−|3999 used by competent established thermal insulation installers. |+|
|−|However, inspectors off the dole queues were using this bad fiction. |+|
| || |
|−|They then did another one. This was mentioned at BD 58, but no one else |+|
|−|was interested. I have not reviewed it. We do not use it. |+|
| || |
|−|> Australian Government agencies are required to release copyright public |+|
|−|> sector information under Creative Commons by licence or other open |+|
|−|> content licences, wherever possible. This is in line with |+|
|−|> recommendations of Government 2.0 Taskforce Report. |+|
| || |
|−|I was asked to obtain some aerial photography from a WA state agency. I |+|
|−|requested TIFFs as they come out of the camera as this had meta data |+|
|−|that can be used to stitch the strips together. I had made this clear, |+|
|−|but what I got was photoshopped Adobe "JPEGs". My intention was to |+|
|−|make JFIF JPEGs with the size and balance that I wanted, but what I had |+|
|−|got was already JPEGed! |+|
| || |
|−|Some sources of data are plaintext. This is least obfuscated form of |+|
|−|data. I was told that they will be helpful and paste it in Excel and |+|
, , a
|−|then send you an XLS or worse still an XLSX of it! |+|
|−|These are examples of undisclosed software being used to change data. |+|
|−|Perhaps government agencies can not read my plaintext email as they are |+|
|−|using Outlook? |+|
|−|This is why I always discuss via telephone. |+|
|−|The plaintext version of text/plain media type is described in RFC 20, |+|
|−|822, 2045, 2046 (4.1 Text Media Type), 2822 and 5322. The precedents |+|
|−|for plainetxt go back to teleprinting. In the earliest form you cut |+|
|−|ticker tape on space and that multiple spaces are paragraph breaks |+|
|−|where you skip a line. This was done later with CRLF and CRLFCRLF by |+|
|−|TTY operators. Similar plaintext is also the source code basis of |+|
|−|= Astronomy BoF = |+|
|−|CMOS CPUs are clocked much faster than thermal limits permit so they |+|
|−|must slow down as they heat up. When processes have yielded the CPU |+|
|−|stops and cools down. This means that the CPU can run much faster in |+|
|−|bursts than it could in continuous operation. This mode of operation |+|
|−|was first used in CMOS mainframes where a valid process will yield for |+|
|−|IO. Something similar was done in calculator key-press, get, process, |+|
|−|update display and then sleep to save battery power. |+|
|−|Linux has the ignore_nice_load feature which stops nice jobs breaking |+|
|−|power management that must now be regarded as essential. Linux does not |+|
|−|usually stop, but it does slow the CPU down. This cools the CPU and |+|
|−|allows it to burst up to full speed when priority jobs become ready. |+|
|−|When you are running stuff like https://boinc.berkeley.edu/ you may not |+|
|−|want it to slow down your apps. Running it nice alone will not prevent |+|
|−|your apps from being slowed down. You need to give your CPU a chance to |+|
|−|cool down so that your apps can run faster. |+|
|−|# echo 1 >/sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load |+|
|−|= Contact = |+|
|−|! . ! . ! . ! . ! . ! . ! . ! . ! . ! |+|
|−|! I am the intended addressee of any email sent to me. Such email is my |+|
|−|! property and I may send samples of unsolicited email or randomly |+|
|−|! directed Outlook mail to network news or post on the www in order to |+|
|−|! expose and discourage such behaviour. |+|
|−|! http://n50.bgcaus.com/~andrewb/public.key current or D3572FAE |+|
|−|! Key fingerprint = D6F3 CE30 D359 8288 3C39 34B1 4CED ABD9 D357 2FAE |+|
|−|! Andrew Buckeridge <firstname.lastname@example.org>, Mob +61 4 29370306 |+|
|−|! Work - Tel: +61 8 93344925, Fax: +61 8 93344660 |+|
|−|! Home - Tel: +61 8 92846018, Fax: +61 8 92846011 |+|
This year the lightning talks are being held on Wednesday morning after the Official Opening. There may be a second session on Friday during the closing session.
1. Talks are for 90 seconds.
2. You must put your name and topic on the wiki page if you want to present.
3. If you want to use a set of slides, these must be in a pdf file either emailed to email@example.com by 8:30 on Wednesday or provided on a usb flash drive by 9am. There is absolutely no guarantee your slides will be synchronised with your talk or shown at all so have a 'Plan B'!
4. Presentations for Friday must reach me by 10 am Friday either by email or handed to me at the keynote. I will try to concatenate them into a single file, so please provide in open document as well as a pdf.
5. The video of your talk and slides will be published under a Creative Commons, By Attribution license.
6. The time available on Friday is limited so presentations are limited to 90 secs and we may have to limit the number, so get in quick!
If you wish to give a talk, please put your name and presentation title in the list below. Format as a sequential number, your name, Title of Presentation.
Presentation filename should be in the following format nn_FirstName_Lastname.pdf where nn is the sequential number below.