I there a way to test new GIMP 2.7/2.8 in Fedora? I looked in Rawhide
repos and I still see only 2.6x versions there. Any plans to put 2.7 in
Rawhide repost for testing purposes?
pratite me na twitteru - www.twitter.com/valentthttp://kernelreloaded.blog385.com/
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic
My Red Hat office, the Boston office, is going to be doing a program
with a local middle school / jr. high (students are 11-14 I think) and
I'm going to be teaching a 9 session (45 minutes a piece) course in
Inkscape to the students. We are trying to introduce the students to the
concept of free software & open content licenses such as Creative
Commons, plus teach them how to use this useful tool that might help
them in their academic career.
I'm trying to put together a lesson plan for the course. But I fear that
it moves way too fast, especially for 45-minute sessions. I know many of
you, I am sure, have given Inkscape tutorials to other folks, and I am
wondering if any of you would have time to give me advice or even help
me develop the lesson plan.
I set up a wiki to store all the materials:
(I also have materials from a 1-week class I taught at Red Hat High with
John Bintz and MentalGuy from Inkscape:
So, to start the thread here on list, here's my feedback.
I think the F12 schedule worked rather well, we slipped a few times a
few days or a week and skipped most of the wallpaper refreshes -- I
think it's unnecessary to have that many wallpaper refreshes. I've tried
to keep in sync with our work the Key milestones  so you can compare
what we did in time and when we did it.
So the basic outline should IMHO be:
* concepts submission for default wallpaper till month and a half
* designs for alpha submission till month before alpha, WIP design
submission deadline for extras wallpapers
* in a following fortnight discuss what gets selected for default
concept/design and package it for Alpha (ideally we should be
able to make the package before alpha freeze)
* Make only one or two refreshes in the following month and a half
* Create beta wallpaper -- supposed to be nearly final --
submission deadline for final extras designs; create supporting
graphic in time to be packaged before the beta freeze
* Based on beta feedback finalize beta wallpaper, make a final
selection of extras wallpapers, package a two or three weeks
Note, that the dates above are for orientation only, if the general
schedule will be more/less tight we'll reflect it.
I believe these six points need to be in bold face in our schedule as
they are somehow important milestones. The rest of the schedule for F12
IMHO worked without much issues. Plus, it's nice poelstra e-mailed us
weekly with our upcoming design tasks.
If there's a calendar instance at our sites (I remember folks were
talking about it on infra, but don't know whether they implemented it),
it would nice to load the schedule there -- calendar with highlights is
faster to follow than table with dates and not everyone uses one
Just as a head's up, myself, Nicu, Ian, and some other folks had some
discussion in IRC this morning about applying some polish to the
wallpaper for F12.
You can see some of the work-in-progress here:
I'd love to hear your thoughts. I think we want to stay with the order &
chaos concept; Nicu and I brainstormed a bit and I started taking this
direction where you have close-together/orderly bokeh bursting out onto
I would love to hear what you think - could this work for F12? How could
we push it further?