EdX Source Code Released
code.edx.org
EdX Source Code Released
1–10 of 17 posts
Re: EdX Source Code Released
#2Re: EdX Source Code Released
#3Re: EdX Source Code Released
#4I wrote the open source alternative to major vendors (ETS, Pearson, etc.) that competed in the Hewlett Foundation's ASAP competition last year. I started a company around that technology earlier this year (http://lightsidelabs.com/) and have been eagerly awaiting the release of EdX source code.
(as disclaimer, I wrote some preliminary thoughts on the announcement several weeks ago at http://bit.ly/ZJTt8E which are probably useful for gauging my pre-existing bias)
Looking through this codebase, it's roughly the level of machine learning work that I'd expect from a first-year graduate student; it gets the job done but is really only tailored to the very narrow task of essay grading and doesn't offer much extensibility. My guess is that for that narrow task, it does a pretty good job, but in my experience teachers are rarely satisfied with just getting a machine learning-generated score and nothing else. The frontend API is a nice addition and the Django service around it is sure to be beneficial, but it's not really ready for primetime yet.
I'll be eager to see if they continue to develop it or leave this as their open source contribution and continue on to other flashy announcements.
Re: EdX Source Code Released
#5cool it's using django! wait a sec... rake django-admin[syncdb] ???
>You'll also need to install MongoDB, since our application uses it in addition to sqlite.
I thought the same...I feel sorry for whoever will be trying to make it run in actual - you know - production and stuff...
Re: EdX Source Code Released
#6cool it's using django! wait a sec... rake django-admin[syncdb] ???
[1] As a side note, apparently I'm the #23rd most frequent committer, and I only worked on edX for a couple months, that's pretty cool :)
Re: EdX Source Code Released
#7cool it's using django! wait a sec... rake django-admin[syncdb] ???
As someone who contributed a bit to edX last year[1], it seems that they found rake to be a nicer way to encapsulate scripts than, for some reason, shell scripts or something. IIRC it was just setting some environment variables to manage the dev environment. Personally I would have wished that they used Rails instead of Django but this bit of oddity was kind of amusing for me. [1] As a side note, apparently I'm the #…
Re: EdX Source Code Released
#8Earlier quoted context omitted.
As someone who contributed a bit to edX last year[1], it seems that they found rake to be a nicer way to encapsulate scripts than, for some reason, shell scripts or something. IIRC it was just setting some environment variables to manage the dev environment. Personally I would have wished that they used Rails instead of Django but this bit of oddity was kind of amusing for me. [1] As a side note, apparently I'm the #…
Actually you were the 23rd /unique/ committer - we made the authors list in order of people's first contribution :)
Re: EdX Source Code Released
#9However, it's AGPL (Affero GPL) which is really quite an onerous license. As far as I understand it AGPL requires you to release your changes at the time you make them rather than at the time you distribute the resulting software. This will have a big impact on how useful the codebase is to anyone else. It'll be interesting to see how and which communities develop around it.
The use of the AGPL will mean that it'll be slightly harder to form companies around edX solutions: there won't be much advantage of hosting/outsourcing companies over regular on-site consulting companies. I'd expect these licensing terms to result in most users (i.e. institutions) having to install and maintain their own solutions on site. As a result, I'd expect it to be more expensive than other existing open source LMS systems.
Re: EdX Source Code Released
#10It's great to see the edX release! Good work guys! However, it's AGPL (Affero GPL) which is really quite an onerous license. As far as I understand it AGPL requires you to release your changes at the time you make them rather than at the time you distribute the resulting software. This will have a big impact on how useful the codebase is to anyone else. It'll be interesting to see how and which communities develop ar…
Notwithstanding any other provision of this License,
if you modify the Program, your modified version must
prominently offer all users interacting with it remotely
through a computer network (if your version supports such
interaction) an opportunity to receive the Corresponding
Source of your version by providing access to the
Corresponding Source from a network server at no charge,
through some standard or customary means of facilitating
copying of software.
Is it really that hard to read/interpret? It seems to me as very simple. If you use AGPL software and provide a service to users, and you have modified the software, then those users after accessing your service has a right to access the source code. If you don't modify it, or do not let users interact with the service, then you can happy ignore the (A)GPL part of the license and treat it as GPL.