xblock-mentoring: Add repository to requirements & installed apps - #2136
xblock-mentoring: Add repository to requirements & installed apps#2136antoviaque wants to merge 8 commits into
Conversation
|
While AGPLv3 doesn't prevent us using it, it does prevent us relicensing it, which might be exactly what is intended. So it's fine to use with the edx-platform, we would just have to exclude it if we distributed our code under a license other than AGPLv3. Also note that an AGPLv3 XBlock wouldn't be usable in non-AGPLv3 alternative XBlock runtimes. If you want anyone to be able to use this XBlock (including, say in a commercial or MIT/BSD-licensed LMS that supports XBlock if they ever come to exist), you might want to consider something like Apache 2.0. However if you want to restrict usage to AGPLv3 runtimes like edx-platform, you can leave it as AGPLv3. |
|
@jtauber Good point, thanks for the precisions - I've passed it along to the Harvard team, so they can make sure this is taken into account in their decision. |
|
I've started reviewing the code, and put my comments here: https://gist.github.com/cpennington/cd20e8ec1f07ca6ac390 I'll post again when I add more. |
|
@cpennington Thank you for the first pass on the review! I've made the changes, and added a comment/question to the gist: https://gist.github.com/cpennington/cd20e8ec1f07ca6ac390#comment-986096 |
|
@talbs can you review the linked repo for any css issues that would break edx-platform? |
|
@cpennington and @antoviaque, sorry for the radio silence and delay on my end. @antoviaque, I've taken a quick look through the HTML and CSS portions of the work - nice job overall! Here are a pieces of feedback for you (with the caveat that we're still in the middle of forming some HTML, Sass/CSS and front end UI standards) - https://gist.github.com/talbs/570e0cc65063e42129a9. None of these items are hang ups for you getting this approved, but let me know your thoughts and if they're worth incorporating. |
|
@talbs Thank you for the extensive review! This is really helpful, and helps me to get familiarized with the conventions on edX, which is great. I've fixed the ones I could/knew how to fix, and added follow-up questions or remarks for the others - let me know what you think, I'll be happy to give it another pass: https://gist.github.com/antoviaque/93ed9c0adce463d2f40f @cpennington if you want to proofread the answers related to XBlocks, that would help to make sure that I'm not giving mistaken reasons : ) |
|
@antoviaque can you rebase this onto master? |
|
@cpennington Sure! Done. Note that I haven't implemented the couple of issues we noted last week when we discussed the XBlock - if you see other things to improve, I'll fix everything at once at the end of the week. |
|
@cpennington Done - I have done the fixes we talked about: gsehub/xblock-mentoring@c50f6d5...master Also rebased again. |
|
@antoviaque @cpennington do we have a plan for what to do about children? The XBlock gap and the Mentoring deploy schedule could be tight. |
|
@nedbat Not yet, I wasn't aware that it might not fit the mentoring deploy schedule - which part of handling children would be tight? I think @cpennington mentioned the JS handling of children was already fixed in a PR (maybe even merged already?), so I'm assuming you are talking about having XModules as children ( If that's what might not be possible, I guess writing a replacement as a pure XBlock might not be very difficult? I could take care of it - should I include it in the mentoring XBlock or separately? I guess I would have to use a different tag than |
|
Updated commit hash - this is the first version which should be reasonably functional in the LMS. @cpennington It includes serveral workarounds for the current limitations of XBlock integration in the LMS - can you check that my approach is sane for these?
Also. two additional questions
Also, would this be good to merge? |
|
@cpennington Regarding changes to the XBlock content once the course is live, I was looking at adding edition of the However, it seems that the Studio view changed in the meantime, and I now get "Block is missing data-runtime, data-runtime-version or data-init, and can't be initialized" in the JS console. Do I have a chance of getting this to work? |
|
@antoviaque If you're writing your own studio_view, and it has javascript, then you need to call |
There was a problem hiding this comment.
We now have a file for requirements meant only for edx.org, and not for Open edX in general. Can you move this reference to requirements/edx/edx-private.txt ?
Neither edit nor delete activated on pressing the space key.
…anslation, eg. French
…ey-activation Make forum comment buttons activate by keyboard
making LMS modal buttons more flexible to handle longer strings in trans...
|
Actually, what should have happened (but didn't, yet) was for If you would feel ok making that change, that would be awesome. re: re: Exporting and re-importing: The important thing to make sure of is that no url_names change during the export/reimport, since those are the ids that store student state. As long as you set the |
|
From a frontend perf standpoint, you might benefit from using |
|
re: |
|
@cpennington Thanks!
|
|
Sorry, when I said |
|
@cpennington Thanks, I tried that - with no luck though: I don't claim to understand the error, but I didn't see a declaration of a |
|
Gah. You're right. I got confused about where the xmodule_runtime actually -Cale On Tue, Mar 4, 2014 at 6:42 PM, Xavier Antoviaque
|
|
@cpennington Ok, sounds good. Btw I've added a question for you about activating XBlocks in https://github.com/edx/edx-platform/pull/2723#issuecomment-36733495 Also created the PR for inclusion in the RC later today: https://github.com/edx/edx-platform/pull/2814 |
|
FYI, pushed two last changes - changing a local_resource filename to match naming constraints (was giving a 404) and a small CSS fix: https://github.com/gsehub/xblock-mentoring/commits/master . The rest of the fixes from the testing done by the Harvard team could be handled through changes to the XBlock content. |
|
Also pushed activation of XBlocks (yey!) - cf https://github.com/edx/edx-platform/pull/2723 |
|
@cpennington All done on my side. Do I have the thumb up, to tell @hkim823 that he can merge this to the rc and push? |
|
👍, but you'll need to rebase to get it into master, and you'll need a new pr targeted at the RC branch. |
|
@cpennington Yep, already done for the PR for the RC branch: https://github.com/edx/edx-platform/pull/2814 Thanks! |
Adding to installed Django applications is required due to the use of a Django model by the XBlock
|
Merged to RC |
…port public/private DailyMotion and Youtube. Related to openedx#2136
…port public/private DailyMotion and Youtube. Related to openedx#2136
…port public/private DailyMotion and Youtube. Related to openedx#2136
We now only support public/private DailyMotion and Youtube. Related to openedx#2136
Master isn't ready yet to load the XBlock, but submitting this to start the review of the mentoring XBlock.
The XBlock can be found at https://github.com/gsehub/xblock-mentoring
@nedbat @cpennington Let me know if you see anything wrong, or if you'd like me to do anything differently.
requirements/edx/github.txtalso says "If you open a pull request that adds a new dependency, you should notify: @jtauber to check licensing, one of @e0d, @jarv, or @feanil to check system requirements", so pinging you too. Let me know if you need anything.