Add xblock-vectordraw to requirements.

[itsjeyd]

Replaces #10515.

The Vector Drawing XBlock was reviewed in this PR: open-craft/xblock-vectordraw#1.

[openedx-webhooks]

Thanks for the pull request, @itsjeyd! It looks like you're a member of a company that does contract work for edX. If you're doing this work as part of a paid contract with edX, you should talk to edX about who will review this pull request. If this work is not part of a paid contract with edX, then you should ensure that there is an OSPR issue to track this work in JIRA, so that we don't lose track of your pull request.

To automatically create an OSPR issue for this pull request, just visit this link: https://openedx-webhooks.herokuapp.com/github/process_pr?number=10932&repo=edx%2Fedx-platform

[sarina]

@itsjeyd can you link to the review PR for the xblock itself, so that context is present here?

[itsjeyd]

@sarina Sure thing, added a note to the description.

[nedbat]

How are we deciding between github.txt and edx-private.txt for these XBlocks?

[sarina]

OK, contingent on tests passing and the promise that your team will follow up on final a11y work next week with Mark (cc @antoviaque FYI), 👍

Go ahead and merge when it's ready.

[sarina]

Oh, right. @itsjeyd this should go in edx-private; it's not an XBlock we want to force on every Open edX installation.

[itsjeyd]

@sarina @nedbat OK, I'll fix that. Thanks!

[itsjeyd]

@sarina OK, done -- added at the end of the file.

[itsjeyd]

@sarina Following up on the question above about github.txt vs edx-private.txt, what are the criteria for including an XBlock in Open edX? :)

[sarina]

XBlocks we think are so core to the edX experience we want everyone to have
them. For example if Capa moved to an XBlock, it would be a default.

On Thu, Dec 10, 2015 at 12:32 PM, Tim Krones [email protected]
wrote:

@sarina https://github.com/sarina Following up on the question above
about github.txt vs edx-private.txt, what are the criteria for
including an XBlock in Open edX? :)

—
Reply to this email directly or view it on GitHub
https://github.com/edx/edx-platform/pull/10932#issuecomment-163696695.

[antoviaque]

@sarina Thanks for letting this being merged now btw - we'll definitely keep both XBlocks in our next sprint scope next week, to ensure we keep time to address any additional comments from Mark.

CC @bradenmacdonald

[openedx-webhooks]

Thanks for the pull request, @itsjeyd! I've created OSPR-1052 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams.

Feel free to add as much of the following information to the ticket:

• supporting documentation
• edx-code email threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will still be done via the GitHub pull request interface. As a reminder, our process documentation is here.