IANAL, This may have been said already, but if the code is all yours(or if contributors have signed over the copyright), its yours to do with as you see fit. That includes relicensing(maybe for a fee, maybe not) with companies doing embedded systems. Now what gets sticky is if you have accepted patches not written by you, then you are bound by LGPL on that code, and thus can't do that, but if all the code is yours go for it.
A quick perusal of their website doesn't reveal any thing that would allow someone do their own coding. Toys like this are only worth having if they are hackable:). Anyone know of any projects to hack them or provide dev. tools. Heck does any SELL dev tools for the sucker?
Well, I have a professor(who is a jerk in many other ways) who has a good way of grading group assignments(he teaches the Electrical Engineering Senior Design course for Digital, i.e. design a microprocessor on an FPGA). He has a grade for the group as whole, and then an individual grade. As part of the grading, you document what each person does. Then he talks to each member of the group about what they did, and whether they have any clue or not.
I would argue that thats pretty effective, its generally easy to tell whether they did what they said they did by how they talk about it, and it lets those who did all the work get the credit they deserve and those who didn't get what they deserve.
But more important than team assignments, I would appreciate a class on WORKING as a team, not some pansy basic class, but how real effective teams work, and do a project(Our software engineering class is BS, its the "throw everyone into a team, let them go, let God sort 'em out" methodology). Of course the problem is not many people know HOW to get programmers to work as a team(especially ones of varying skill levels).
From what I've seen, what one school calls computer engineering varies dramatically from the others. I go to an ABET accredited engineering school. Our computer engineering program is ABET accredited and handled by our Electrical Engineering deptartment in the College of Engineering. They have to take a crapload of Computer Science classes, but they also have to take almost exactly the same classes as an Electrical Engineer.
At my school, thats the way I would go since our Comp Sci. department sucks a big one. The ABET accreditation may be overrated, but at least you'll learn something(our EE classes are not for the weak minded. Lots of math too.)
Slashdot Mirror
IANAL, This may have been said already, but if the code is all yours(or if contributors have signed over the copyright), its yours to do with as you see fit. That includes relicensing(maybe for a fee, maybe not) with companies doing embedded systems. Now what gets sticky is if you have accepted patches not written by you, then you are bound by LGPL on that code, and thus can't do that, but if all the code is yours go for it.
A quick perusal of their website doesn't reveal any thing that would allow someone do their own coding. Toys like this are only worth having if they are hackable :). Anyone know of any projects to hack them or provide dev. tools. Heck does any SELL dev tools for the sucker?
Well, I have a professor(who is a jerk in many other ways) who has a good way of grading group assignments(he teaches the Electrical Engineering Senior Design course for Digital, i.e. design a microprocessor on an FPGA). He has a grade for the group as whole, and then an individual grade. As part of the grading, you document what each person does. Then he talks to each member of the group about what they did, and whether they have any clue or not.
I would argue that thats pretty effective, its generally easy to tell whether they did what they said they did by how they talk about it, and it lets those who did all the work get the credit they deserve and those who didn't get what they deserve.
But more important than team assignments, I would appreciate a class on WORKING as a team, not some pansy basic class, but how real effective teams work, and do a project(Our software engineering class is BS, its the "throw everyone into a team, let them go, let God sort 'em out" methodology). Of course the problem is not many people know HOW to get programmers to work as a team(especially ones of varying skill levels).
From what I've seen, what one school calls computer engineering varies dramatically from the others. I go to an ABET accredited engineering school. Our computer engineering program is ABET accredited and handled by our Electrical Engineering deptartment in the College of Engineering. They have to take a crapload of Computer Science classes, but they also have to take almost exactly the same classes as an Electrical Engineer.
At my school, thats the way I would go since our Comp Sci. department sucks a big one. The ABET accreditation may be overrated, but at least you'll learn something(our EE classes are not for the weak minded. Lots of math too.)