\

AlisonW

search for tag 'Software' requested

Long time...

2022-08-23 14:56:09 - by AlisonW Open Chyrp Coding Corvd Known Software

...no use. This is my personal playground and, until a recent OS upgrade at the weekend, I was running an installation of "Known" (and before that a heavily modified "Chyrp") But then PHP8.1 came along and screwed me up enough to dust off the software I had been working on and sort out it's issues. Which I mostly have.

This site will, as always, be available at my personal whim. "Age of the geek, baby"

Diary matters

2020-01-13 17:40:49 - by alisonw Open Design Software Privacy

https://shkspr.mobi/blog/2020/01/why-i-make-my-work-calendar-public/

I've kept my calendar online since around 2003, forward events publicly available throughout. Initially it was file-based with a two appointment records per day* in a text file per month, a few years later moving to a MySQL database, where it still resides. Currently at diary.alisonw.uk the domain has changed occasionally depending on which ones I happen to own at the time (!) and though the Internet Archive says it existed in 2005 their earliest copy - looking very similar to the current edition - appears to be from 2007**.

In the past it's been useful for family, friends, and lovers to check where I am (I used to travel a lot) and for me when booking appointments / finding out what I'm supposed to be doing.

* day, evening
** web.archive.org/web/20070320035249/https://diary.alisonwheeler.com/diary

Software licencing revisited

2012-02-06 12:00:00 - by alisonw Open Chryp Licensing Software

Look in the sidebar on the right and you'll see a number of entries for the FLOSS software which runs this blog, Chyrp. Some years ago I wrote some extensions to the base platform, known as 'modules', and released them for free use by others under a ee_software_licence|suitable licence version 3 of the GPL.

At the point I first used the base software – and forked it to add my own tweaks and improvements – Chyrp was also available under the GPL.

So far, so good: I retain full copyright on my work and offer a free licence to others to use it without charge so long as they meet certain conditions, once of which is that under the terms of the GPL any changes others may make to my code are also made freely available to everyone (including myself.)

Now move the clock hands forward four years or so, up to this year. In starting my new blog at shehacks.com ] I decided to use the updated version of Chryp – 2.5beta1 instead of 2.1rc1 – and update my add-ons to suit. Which I have, but then as I was about to make them available to all realised I have an 'issue'.

Shortly after I created my branch of Chyrp, its founder changed the licence it was released under, from GPL to MIT, and where the former is a copyleft licence, the latter one is not, indeed it permits use within proprietary software which is something I object to on principle. All of which means that although I can continue to release my own 'modules' under the GPL it isn't so straightforward where I want to make improvements to the main core.

Looking at the various reference documents – including the GNU licence page ] – tells me that it is OK for Chyrp to have moved from GPL to MIT so long as the full agreement of all contributors had been obtained, but not otherwise. And personally I have no idea whether that was obtained or not (I did ask at the time). Now though I have to decide whether – against my personal principles on FLOSS development – to use two different licences on the same project, depending on whether they are 'core' or 'add-on', or to take some other approach.

That would be either creating a permanent GPL-fork, or not releasing any of the changes I make to the core at all. To me, FLOSS means making available to others the fruits of your labour to the greater benefit of all, and it is fine for a GPL-fork to draw in all of the changes which use the MIT licence as they are made, though not vice-versa.

Fine tuning

2012-02-01 00:00:00 - by alisonw Open Software

Since late last year I've started to get interested again in hardware hacking and the 'maker' movement, up to the point that I've been upgrading my home facilities for woodwork, metalwork, and electronics.

This resulted in my deciding to add a couple of new domains to my stable. One being a cetral resource for those looking for information (which, naturally enough, includes myself!) which is starting to take life at openhax.com in the form of a wiki. Once I've developed suitable templates for each typoe of link – and created some for the stuff I've already found – I'll open it up to others to add stuff too.

The second is another blog for myself, but focussed on my making and hacking. It could have been added here but I reckoned that it was a rather more 'special interest' topic so would suit a separate location. Anyway, if you'd like to see all that wander along to [shehacks.com ], though I'm still fine tuning the css!

Initially I was planning on using Concrete5 (again) for the new maker blog, but a poassing comment from someone at a meeting last week caused me to re-evaluate that decision and, eventually, I decided to return to Chyrp as is used for this blog. And to not re-use the existing fork but to update it to the latest version – four years after I last touched it! So far I've managed to upgrade three of my modules, and I'll be getting around to updating the rest shortly. They will all, of course, remain GPL'd as Open Source.

In brief …

Goodbye to Vox The closing. vox. com/Vox blogging service from SixApart is closing down at the end of this month.…