Lerneaen_Hydra_ is now known as Lerneaen_Hydra
SWPadnos is now known as SWP_Away
Hi jmk - (have a dapper machine running - tonight it might make chips :)
spotted any more problems in halscope?
haven't used it lately
been very busy with real life
I installed VMware Server & dapper today
works really nice
just finished mowing the grass
heh.. nice ;)
wonder what's up with ray
haven't seen him in a while
fuzzybutt (one of the new kittens) stood on my f1 key which opened 99 copies of gnome-help
we used to have a cat we called fuzzbutt
wasn't her real name
I'm not sure it's his real name either
it seems cats around here have several names
but then most of our critters have multiple names anyway
"sfbd" is one of the dog's names
typically names should have at least one vowel
its an acronym
"shit for brains dog"
I'm adding SF "tasks" for the 2.1.0 release
alex pasted some notes from the board meeting into the board channel
can you take a look and see if he missed anything?
I remember the list beeing longer
some of these things could be listed as tasks or as feature requests
tasks is ok
if we decide we want to work on them
feature requests is more like a standby list
I just realized that I put the "end date" for each new task as today (the default)
anybody care to guess at a target date for the 2.1.0 release?
like breezy 5.10
6.10 means 2006, October
2.x.y, where 2 = emc2, x = major version, y = bugfix version
has nothing to do with dates
I know.. but I really meant october
probably the .10 was too cryptic
yeah, it was ;-)
nothing to do with 2.1.0
october seems pretty far away
but on the other hand, the task list is pretty long
and it's not half in there
we may actually decide that after some key features are working we will release 2.1 and leave the rest for 2.2
and there's the summer vacation
not sure about you guys, but I'll be gone about a month :D
I'll set the target dates for these tasks to 1-Oct-2006
how about sept?
then one month for overdue stuff?
30-sept-2006 ? ;-)
I'm setting a few to be earlier
I see you are setting dependencies too...
only added the 2.1.0 release
and set it dependent on the others
but I'll wait for you to finish..
just changed dates on the release task, starts sept 15, ends oct 15
you can add some tasks too
I wonder if we can convince jepler to work on the CL gui?
jmkasunich: we only need to convince him to try it out once
the rest is taken care by his conscience
I think you would have to send him (or me) hardware that requires CL to do something useful
cradek: CL can do usefull stuff without hardware ;)
I think the problem with CL is that it's just so bad it seems like you're starting with nothing
the GUI you mean?
I guess it does work, though, I saw you doing useful things with it
it's UGLY but it works
making CL better is a non-trivial project
but a worthy one IMO
so far, I'm glad he worked on halscope instead
I haven't really tried out all the new features
saw some (the colors) while working on the pwm component
btw, had a chance to try that yet?
same here :(
I think the sample configs (all configs really) should use only a single HAL file
no more ppmc-io.hal, ppmc-motion.hal ppmc-servo.hal, etc, etc
[22:05:28] <jmkasunich> http://sourceforge.net/pm/task.php?group_project_id=46285&group_id=6744&func=browse
that's not too bad..
only 3 in there ;)
assigned to me I mean :D
SWP_Away is now known as SWPadnos
cradek: maybe we should package a symlink emc2 to emc ;)
seems it's rather usual with libs, not bins