Log in

No account? Create an account

Previous Entry | Next Entry

My first screen cast

If the title of this entry puts you in-mind of a giddy school girl, well, that's intentional. Anyway, I'm looking for feedback on my first screen cast: Creating a Patch for a Gnome Module. What I would like to hear are what you like and do not like--and suggestions for improvement, of course. It's in OGG since that works on every FreeDesktop with zero effort. Once I am happy with it, I would be happy to convert it to innumerable other formats.

Let's get some new blood in Gnome!


( 8 comments — Leave a comment )
Jul. 7th, 2008 09:28 am (UTC)
Great screencast. Some comments/questions.
1) I'm running Ubuntu Gutsy (7.10) and following this screencast to a T I did not have all the needed dependencies to build gnome-games (gnome-devel isn't sufficient). Disappointingly I also didn't manage to pull these in through 'sudo apt-get build-dep gnome-games', it was still complaining about libraries needed for "GGZ Gaming Zone support". Eventually I managed to manually pull in these dependencies though (libgzz-dev, libggzmod-dev). Would it also have been possible to pass a --without flag to ignore these libraries?

2) Do I have to checkout gnome-games entirely and compile it? Or could I just compile a specific game by itself?

3) Just like you when executing 'make install' I did see a lot of 'WARNING: failed to install schema', could you elaborate?
Jul. 7th, 2008 02:13 pm (UTC)
Re: Great screencast. Some comments/questions.
Due to this screencast I decided to look at one of the bugs for gnome-games marked trivial (Bug #469994). However, turns out it might not be all that trivial after all. See my comment at: http://bugzilla.gnome.org/show_bug.cgi?id=469994#c2
Jul. 7th, 2008 02:30 pm (UTC)
Re: Great screencast. Some comments/questions.
Sorry for replying to my own replies but there doesn't seem to be a way to edit a previously submitted reply. I just wanted to say that I seemed to have confused 'impact' or 'severity' with 'ease to fix'. I should have known better. Doesn't Bugzilla offer a way to mark bugs as easy? That would probably be quite helpful for new contributors.

I'm somewhat thinking of Launchpad's bug mentoring functionality, see: Mentoring available in Ubuntu (https://launchpad.net/ubuntu/+mentoring)
Jul. 7th, 2008 11:30 am (UTC)
well done
Very clear, well executed screencast. Keep them coming :) Thank you!
Jul. 7th, 2008 12:57 pm (UTC)
These are the sort of things that newbies like myself love to see. Sure it's a bit of spoon feeding but I've done some hacking on gnome stuff before but even I was unfamilar with the gnome-devel metapackage and how I should be looking at using a make install to test packages. If you show someone something, they can always gain the deeper understanding later via google of the docs but it's that initial push that the screencast tutorial provides.

I'd love to see some more screencasts from either yourself or others, fantastic pace, well executed and most of all - incredibly useful.

Thank you.
Jul. 8th, 2008 06:03 am (UTC)
Constructive criticism
Much of this you probably already know.

* Launching klotski (gnotski? thats unfotunate) off screen is a bit confusing. You might try moving the recording window, or recording with a new user on a smaller resolution screen.
* check the mic levels during recording. Sometimes your voice seems to max out the channel, leading to slight distortion. We can also hear you breathe
* Fewer verbal pauses ("uh, um") would be nice. A script might help, as might having someone to talk
* Textual elements escape poorly from sound or video. The best I've seen of this bad situation is to provide "show notes" with URLs, simple commands etc for selection and so on.
* A transition during the pause would be nice.

* know your audience. do new Linux developers really want to participate in maintaining a package, or do they want to know how to identify, fix and return fixes to programs they use?
* Be representative. It appears you've cherry picked the easiest bug to fix, with a simple one line removal fix.

Information specific to this episode:
* You've chosen to use the incremental search in gedit -- it's not something I knew about but it's also not very intuitive. Control-F might make more sense if it's not critical to the project.
* it might have been nice to demonstrate devhelp's use in context of fixing the bug.
* Is SVN going to be around for much longer? Also, it's not easy to see how to use it at the command line. as you point out, you need a viewvc to figure out tags or branches etc.
* The presentation has a clear Debian bias, but doesn't give enough information to the stated audience of "new linux developers" to figure out things like development header packages or build-essential. The right way to fix this might be to offer up explicit viewership dependencies with links to videos describing that information.

Just so everyone understands the point of constructive criticism, here's some praise:
* You've done a good job explaining when using keyboard shortcuts
* explaining the path option to config was handy
* You've done a pretty good job making the screencast large enough to be legible. Make sure that doesn't go away if you choose to use a hosting service!
Jul. 13th, 2008 05:31 pm (UTC)
GNOME/Linux needs more things like this! Very well done. Thank you.
Jan. 9th, 2009 12:58 pm (UTC)
Great screencast
That's a great way to put all things together, i'm a beginner in Gnome, had a few notions of all the tools but was having troubles to understand how everything was working together.

This screencast was very helpful and valuable, thanks a lot!
( 8 comments — Leave a comment )


color, uphair, smile
Jason D. Clinton

Latest Month

September 2011


Powered by LiveJournal.com
Designed by Tiffany Chow