© 2009 chilts.org | Created with LollySite
Privacy Policy | Terms of Use | Original Design: Free CSS Templates.
Found 13 entries.
Here's another release of cil for your perusal. Staying true to the "Release early, release often" mantra, I hope you have fun playing with it.
I'll quickly go through all the features in this release:
For example:
$ cil list --label=Type-Critical $ cil list --status=New $ cil list --assigned-to=andychilton-at-gmail-dot-com
(Note: --label and --status were in v0.2.1.) These can be combined too. For example, this is the command line I used to make sure there were no outstanding issues for this release of cil:
$ cil list --is-open --label=Milestone-v0.3
and opposite to that, for the changelog I could figure out what had changed since the last release by doing this:
$ cil list --is-closed --label=Milestone-v0.3
If I was on a big project, I'd probably cron something like this to send me an email each morning:
$ cil list --is-open --assigned-to=andychilton-at-gmail-dot-com --label=Priority-Critical
That's a pretty nice filter :-)
To be able to do some of the filters above (e.g. --is-open and --is-closed) cil now reads a config file and can determine which statuses and labels are valid. There are also lists to say which statuses are considered open or closed. Of course, if you want neither of features you can just turn them off (which is the default behaviour).
Cil saves it's issues, comments and attachments in the filesystem which isn't usually a good way for (slightly) relational data. The new 'fsck' command can help you figure out missing entities though. For example, if an issue is missing its comments or attachments and whether comments or attachments have been orphaned. It also runs some validation against each issue. Validation at the moment consists of checking statuses and labels in their respective allowed list.
Here is some example output you might see from this command (usually if you or someone else has not been tracking the right things):
=============================================================================== --- Issue c4fa2e27 ----------------------------------------------------------- * StatusStrict is turned on but this issue has an invalid status 'InProg' * LabelStrict is turned on but this issue has an invalid label 'Something' --- Issue 1f67bc27 ----------------------------------------------------------- * comment '8dfe256c' listed in issue '1f67bc27' does not exist * comment '99b20701' is listed under issue '1f67bc27' but does not reciprocate * attachment '29afc3ef' listed in issue '1f67bc27' does not exist =============================================================================== --- Comment 99b20701 --------------------------------------------------------- * comment '99b20701' refers to issue '893f7ea6' but issue does not exist =============================================================================== --- Attachment 37873839 ------------------------------------------------------ * attachment '37873839' refers to issue '8af89d74' but issue does not exist ===============================================================================
More validation checks will be in v0.4.
(Where 'entities' are issues, commands or attachments.)
As stated in a previous post, there is now bash completion for cil.
As I said earlier, I use a few command lines to let me figure out when I can release a version. For example, the next release is going to be v0.4.0 (barring any bug fixes to v0.3.0) so I tag all of the issues I want done for that release with Milestone-v0.4. This makes it easy to see what needs doing and what is already done:
$ cil list --is-open --label=Milestone-v0.4 $ cil list --is-closed --label=Milestone-v0.4
For example, an issue might have been added at some stage in the past, complete with labels:
$ cil add ... added issue 'cafebabe' ...
I usually commit the new issue to my VCS immediately. When I start working on it, I'll mark it InProgress, even if it is just locally. Sometimes I check this in too if it's going to be longer than a few hours:
$ cil status cafebabe InProgress
Once I've finished hacking on the issue and I'm happy with it, I set it to Finished and add a comment to say what I've done:
$ cil status cafebabe Finished $ cil comment cafebabe ... added comment 'decaf7ea' ...
I use Git for my VCS so prior to check in I stage all the working file changes but also make sure Git is tracking the issue properly too. It already knew about the issue file but I need to add the comment file that goes with it:
$ git add issues/c_decaf7ea.cil
Finally when I commit, I commit the code, the issue and the comment all together. In the message I usually put the text '(closes #cafebabe)'. This keeps everything together.
The next release of cil will be Milestone-v0.4 so I'll add that label to a few items I want in it. If there is something I want for the future but haven't roadmapped them yet (into v0.5, v0.6 etc) then I just put a Milestone-Future label on them so I know I want to do them but just don't know when.
Happy hacking and look out for v0.4 sometime in the next week or so.
Labels: cil, planet-geek, planet-catalyst
Inserted: 2008-06-29 11:05 (3 years, 7 months ago)
Another day, another feature added to cil. It's rocketing along.
I've never written anything for bash completion before (someone else has always done it for me) but I had a go at it tonight. After an hour and 15 I had it working quite well.
I was suitably impressed with the whole thing since even though I knew doing it for commands and/or options would be easy enough, I managed to do it for a few other things too (more later).
For example:
$ cil a<tab><tab> add attach $ cil s<tab><tab> show status summary $ cil --<tab><tab> --filename --help --label --path --status --version
That's all happy and nice but the following feature is the killer and will make working with issues a breeze. It also completes the actual issue/comment/attachment name, giving you the choice of the correct type where necessary.
Let's say your issues/ dir contains three issues, two comments and one attachment:
$ ls -1 issues/*.cil issues/a_85eceee9.cil issues/c_d8dd779f.cil issues/c_feb65ae7.cil issues/i_02ee35bd.cil issues/i_5c88cb30.cil issues/i_98203ce8.cil
When doing the following, it completes to one of the three issue names:
$ cil show <tab><tab> 02ee35bd 5c88cb30 98203ce8
as it also does for the other commands that act on issues (status, edit, comment and attach).
Another example would be for extracting attachments:
$ cil extract <tab><tab>
completes to:
$ cil extract 85eceee9
This is pretty good stuff already but I can already see that it can be used a lot more in the future...
Let's say you allow the following statusus in your issues: New, InProgress, Finished and WontFix. Then, setting the status of an issue would work like:
$ cil status 02ee35bd <tab><tab> InProgress Finished New WontFix
Really straightforward and really fast, which are basically two of the things I wanted cil to be from the start - I just didn't realise it would be so easy :-)
Seeing as I try and credit people where I can, thanks to Francois for the suggestion of adding bash completion. It's given me a chance to learn something new to me but very powerful.
Note: this feature is in Git and will be in the v0.3.0 release.
Labels: cil, bash-completion, planet-catalyst
Inserted: 2008-06-24 23:44 (3 years, 7 months ago)
OpenGeoData has a post today which talks about Google's new MapMaker. It seems the Ad Broker wants to own what you do but gives nothing back.
Needless to say I'm completely disappointed in Google yet again but that's coming as no surprise these days. Head over to OpenGeoData and read the entry for yourself - Google Want to be TeleAtlas
Recently, I've been looking at OpenStreetMap a lot and have tried (and tried) to get something going so that I can map both Seatoun and Mt Vic. I refuse to install Flash to use their web editor but also the version which runs on Java isn't working for me either!
A short while ago, I thought that I'd like to make a nice, small and simple Gtk version but I just had a better idea. What about making a JavaScript version? That would be pretty cool.
Currently I have no time but this might be one of those ideas that simmers for a while and then one day, I try it and see what happens. I fear it will be a big project but wouldn't that be just awesome!
As for helping Google map the world and taking your data, thxb'nothx.
Labels: opengeodata, planet-catalyst, openstreetmap
Inserted: 2008-06-24 22:20 (3 years, 7 months ago)
Already there is a lot of news on the 'cil' front just 24 hrs after releasing v0.2.
I've had a number of enquiries about \l{cil|/software/cil.html} consisting of emails asking for help, emails giving advice but even better fixes from both \l{Francois|http://feeding.cloud.geek.nz/} and \l{Sam|http://vilain.net/}. Thanks guys.
Francois has also already uploaded v0.2.1 to Debian Sid for inclusion in Lenny. Many thanks Francois, it's a pleasure being able to work with someone so passionate and involved in Free Software. We all have lots to learn from you.
Anyway, I'd just like to say that v0.2.1 released earlier tonight had the dependency on Term::CallEditor removed to simplify a couple of things. Also, there really wasn't that much code in there anyway.
If you get the HEAD of the cil git repo, you'll already get some new funky features such as the following:
$ cil list --status=New $ cil list --label=Release-v0.2 $ cil list --label=Type-Enhancement
These, of course, can be combined:
$ cil list --status=InProgress --label=Milestone-v0.3
and you can also use these same filters with the summary command.
From issue #85eceee9, there are also plans to have something like the following too:
$ cil list --assigned-to=andychilton-at-gmail.com $ cil list --has-attachments --has-comments $ cil list --is-open $ cil list --is-closed
(These last two will only happen when there is config to say which Statuses are Open/Closed.)
I'm liking these filters already and with the new ones above it'll be great. Heck, I'm even thinking of cron'ing various filters so I know what I have to work on each day :-)
I have also added an issue, #98203ce8, which describes how to add proper searching to cil. This will supplement the above filters quite nicely.
BTW: I have searched and searched and searched for a nice, small and instant indexing system within the Debian repos. I've tried a couple of things which didn't quite work how I wanted it, so if anyone has any ideas, I'd love to talk to you so get in touch.
e.g something like this would be fantastic:
$ cil reindex $ cil search 'Project Blah refactoring' $ cil search 'screenshot table formatting'
Then we'd just list the issues found. It should be very simple with no setting up (except inside cil itself.) If git can 'init' and cil can 'init' then search should be able to set up real quick too.
I'm already using cil to track itself and I'll be shortly adding it to most of my other little projects too. I'm already getting quite competent at getting at the issues, adding, editing them, making sure they're in the repo and all of that jazz. It's coming together quite nicely.
Labels: cil, debian, planet-catalyst
Inserted: 2008-06-24 01:03 (3 years, 7 months ago)
I'm happy to announce that cil v0.2.0 is now available for download.
When I released v0.1.0 it was a test release for two reasons:
While (1) didn't happen, (2) did. I got lots of feedback even though no-one was using it. I did tell people it wasn't quite where I wanted it to be but this release changes all that.
Now it has all the makings of a tool which can just get better over time. Obviously it being v0.2, there are some things it is lacking but as it is, it's perfectly usable and nicely contained.
Some new features of cil v0.2 (over v0.1):
So far, most of the commands I added to cil were quite obvious but already there are some ideas for commands to allow you to work a lot faster. Such as:
$ cil status ISSUE Finished
Quite neat huh?
See cil for more information and also see this cil example for more of an idea about what cil can do.
Before I sign off I'd just like to point out one commit I did earlier today. My vision for cil is so that you can keep your bug tracking inside your repository. This means you can do things that weren't possible before. For example, closing the bug along with the commit(*).
This commit for example shows you that along with the fix, the bug gained an additional comment and the issue was closed, all in the same transaction. That's pretty cool.
So guys, go and have a play with this one. Thanks to Nigel, Francois and Martyn for allowing me to bounce ideas off you. And please, keep those ideas, suggestions, feedback and more importantly, patches, coming ;-)
(*) Yes, I know you can link your version control with your bug tracking system - usually with sticky-tape and superglue - but when they're in the same place, it's much easier :-)
Labels: cil, planet-catalyst, distributed-bug-tracking
Inserted: 2008-06-22 17:48 (3 years, 7 months ago)
Amazon added the ability to 'copy' a key within or between S3 buckets.
This functionality can also be used to change the metadata of an object too.
For example, using the thin-layer commands in Project AwsSum, you can do things like:
$ s3-rad -b mybucket -k NewKey.jpg -K FromKey.jpg
As I said, you can also copy between buckets (so long as they are in the same location, either the States or Europe currently):
$ s3-rad -b mybucket -B frombucket -k key.jpg
As you can see, you have to specify a destination bucket and key but you may leave off the source bucket and/or key. While the Amazon API requires everything, my S3 library fills in the blanks.
If you try to copy a key onto itself hwoever, you'll get an error back from Amazon:
$ s3-rad copy -b mybucket -k image.jpg InvalidRequest: The Source and Destination may not be the same when the MetadataDirective is Copy.
but you are allowed to do this if all you want to do is change the metadata, in this case, the Content-Type:
$ s3-rad copy -b mybucket -k image.jpg -m REPLACE -c 'image/jpg
Whilst the CopyObject operation in S3 is still beta, there has been much discussion about it on the AWS forums and I suspect the API will be final now.
Note: for those using s3bak you can now add a DefaultBucket to your ~/.awssum config file, thanks to a suggestion from Francois.
Labels: project-awssum, planet-geek, planet-catalyst, s3, aws
Inserted: 2008-06-15 12:30 (3 years, 7 months ago)
Seeing as I had only written 1,283 words so far this month, I will have to make an extra special effort to get this novel out this month.
I have though, made it even harder than that since I have thrown those already written words away and started again. From scratch. With nothing.
This might sound like madness but in fact I'm a big fan of symmetry and round numbers. It turns out, this being the 11th that there were 20 more days left in the month including today.
Of those, 14 are weekdays and 6 are the weekend. Therefore to get 50,000 words I have to write 2,000 words/day each weekday and 4,000 words/day at the weekends.
I don't know about you but those numbers appeal to me and I actually feel better for doing it. Don't ask me why because if you did I'd just reply "Because that's how my brain works!"
This word count is totally do-able and it'll take outside influences and factors to stop me achieving it, much like they have been stopping me so far this month.
Wish me luck and I'll see you again at the end of June.
Labels: symmetry, socnoc, novel
Inserted: 2008-06-11 23:48 (3 years, 8 months ago)
Today at around 12:45 the cumulative total words written in this years SoCNoC passed the one million mark.
Let me say that again, we passed the ONE MILLION words mark. That's just fantastic news and congratulations to all those taking part.
Take a look on the KiwiWriters homepage to see for yourself.
Whilst last year we managed almost a million in the month, we've sailed past it after 10.5 days. Plenty of time to hit two million though I know the word rate will slow down somewhat.
Oh, and I still haven't added my 50,000 words. In fact, I still haven't written them ... but you know, that's only a small problem.
20 days left for me to catch up :-)
Labels: kiwiwriters, one-million, socnoc, planet-catalyst
Inserted: 2008-06-11 14:50 (3 years, 8 months ago)
This month has been hectic. Last month was mad too because I moved house. Work has been crazy recently too.
This month, I signed up for doing a novel. Seeing as I am a founder member of KiwiWriters, I have to do it. So far, I haven't managed to get into it yet but then finally, when I thought work would settle down, it went beserk again. Hopefully it will settle down sometime soon otherwise I'll never get this thing written.
I'm happy and settled into the new flat now though so that helps. Finally I can see the carpet which is always a bonus.
And then, when I thought I'd be able to get into my novel for SoCNoC, I somehow volunteered to do a talk at PerlMongers tomorrow night (Tuesday). Silly me.
Then again, I've just written the talk and I'm happy with it. It's only short but I'm hoping to open it out into a discussion at the end of the presentation. It's about my idea of a distributed issue tracking program, initially conceived as 'cil'. There are already a few people interested in it including both Nigel and Francois so hopefully, they'll ship me patches (hint hint ...) though their ideas have already been immensely invaluable. Thanks lads, it's always a pleasure prying into your brains.
Labels: cil, planet-catalyst, distributed-issue-tracking
Inserted: 2008-06-10 00:12 (3 years, 8 months ago)
And no, I'm not talking about that heavy metal thing over Easter.
I'm talking everything, all the time.
It's just an amazing place.
Labels: planet-catalyst, wellington, happiness
Inserted: 2008-06-07 10:29 (3 years, 8 months ago)
SoCNoC is not yet 5 days old but already we're nearing half a million collective words. Obviously over time, people will either finish, slow down or drop out but so far it's been amazing.
Yesterday I put a collective word count onto the front page of KiwiWriters so everyone could see our total. Not that I'm contributing much - am still only on 1,283 - but I hope things will settle down and I can get writing again to help push that total higher.
Last year we almost made one million words for the whole month so we're well on the way to smashing that figure. Fingers crossed.
We hit a different record on Sunday too, managing to get 3,600 hits in a single day. And the next day we smashed it again with over 4,300 hits on a single day. It's a belter!
I apologise to those people who don't find these figures as interesting as I do so unless we manage even more amazing facts and figures, I'll keep them to myself (yeah, right). Maybe I'll post some totals at the end of the month.
Labels: kiwiwriters, socnoc, planet-catalyst, collective
Inserted: 2008-06-05 21:51 (3 years, 8 months ago)
Just the other day, we were talking how ninety-something participants at the start of SoCNoC was good.
Well, less than two days into it we're already onto 123 participants and I'm sure we'll get a few more too. Last year I predicted that we'd get to 120 - double last years total - but I never actually thought we'd do it.
It just seems to have gone ballistic over the last couple of days. I've tried to write but managed only 1,283 words since the start. There have been so many other things to do, it's plain crazy - but then, that's why we all got into in the first place!
Anyway, I should easily be able to pull it back like I've done in the past but at the moment, I'm just enjoying everything about it. Now I wonder if we'll collectively hit two million words. I would find that staggering.
We've certainly received a lot more hits on the site over the past few days too. I reckon there are some companies out there in New Zealand who don't get as many hits in a year as we're going to get in June but I will post the full figures once the month is out.
As Nigel said to me recently, it'll be a good test for Zaapt too, but in all honesty I reckon it won't push it until we get close to a million or two million hits in the month. Here's hoping!
Labels: zaapt, website, hits, kiwiwriters, planet-geek, socnoc, planet-catalyst
Inserted: 2008-06-02 22:42 (3 years, 8 months ago)
Already, we're underway for the Southern Cross Novel Challenge.
A few people have stayed up to chat in the KiwiWriters chatroom and Kerryn Angell (founder of KiwiWriters) set us all going once midnight passed here in NZ.
Starting the month off with 98 participants is a good start and I think we'll even get a higher percentage of winners compared to last year too. With people all around New Zealand and Australi to Finland, the UK and the US, it's truely a worldwide event now.
To all those participating in SoCNoC 2008, have fun and happy writing.
Labels: kiwiwriters, socnoc, planet-catalyst, kerryn-angell
Inserted: 2008-06-01 00:20 (3 years, 8 months ago)
© 2009 chilts.org | Created with LollySite
Privacy Policy | Terms of Use | Original Design: Free CSS Templates.