[edx-code] Deprecation/Removal: outdated class_dashboard app in LMS

[Nimisha Asthagiri]

Hi there,

We plan to deprecate and remove the outdated class_dashboard app

in
the LMS.  We are targeting removal on 2019-06-14.

Please read https://openedx.atlassian.net/browse/DEPR-39 for more
information and to post any questions/comments. The proposed deadline for
comments before acceptance is  2019-06-12.

Thanks,

Nimisha

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to edx-code+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjcD4ffDz%3Dp9f-4TuR0b0iN0PSN%3DGJA_i5yj5jG0ByXoKw%40mail.gmail.com.

[edx-code] Deprecation/Removal: outdated instructor-analytics app in LMS

[Nimisha Asthagiri]

Hi there,

We plan to deprecate and remove the outdated instructor-analytics app

in the LMS.  We are targeting removal on 2019-06-14.

Please read https://openedx.atlassian.net/browse/DEPR-38 for more
information and to post any questions/comments. The proposed deadline for
comments before acceptance is  2019-06-12.

Thanks,

Nimisha

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to edx-code+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLje-a_5mC_vj5NpaYtd2SJjcDicv%2B-OuYpf0fQTeeYo_sQ%40mail.gmail.com.

[edx-code] Deprecation/Removal: django-openid-auth DEPR-20

[Nimisha Asthagiri]

Hi there,

We plan to deprecate and remove the edX fork of the django-openid-auth
repository. We are targeting removal on 2019-06-14.

Please read https://openedx.atlassian.net/browse/DEPR-20 for more
information and to post any questions/comments. The proposed deadline for
comments before acceptance is  2019-06-12.

Thanks,

Nimisha

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to edx-code+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjcXy308p2Cf59Gq_xrYYDy-xUHSHdNnRDT-hQ1NymdnMQ%40mail.gmail.com.

[edx-code] Re: Deprecation/Removal: Mobile Video Outlines API (DEPR-4)

[Nimisha Asthagiri]

*DEPR-4: Removal of Mobile Video Outlines REST API in favor of the Course
Blocks v1 REST API**(Last announced here in October)*

*Update on DEPR-4:*
We have begun the removal process of the old Video Outlines endpoint.  Once
the mobile team updates the iOS app to no longer call this old endpoint (we
found a few additional places), we will merge the removal of the endpoint.
For more information, please see the ticket:
https://openedx.atlassian.net/browse/DEPR-4

Thanks,
Nimisha

On Mon, Oct 22, 2018 at 3:15 PM Nimisha Asthagiri 
wrote:

> Hello all,
>
> We plan to deprecate and remove the Mobile v0.5 Video Outline REST API
> <https://github.com/edx/edx-platform/blob/master/lms/djangoapps/mobile_api/video_outlines/urls.py>
> in favor of the Course Blocks v1 REST API
> <https://github.com/edx/edx-platform/blob/master/lms/djangoapps/course_api/blocks/views.py>,
> targeting removal by *2019-01-15*.
>
> Please read https://openedx.atlassian.net/browse/DEPR-4 for more
> information and to post any questions/comments.
>
> Thanks,
> Nimisha
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjc86Sh_K-3DQX1v8rUXk9mgpmKc0shZyJhQdiQOthAVZg%40mail.gmail.com.

[edx-code] Re: TOMORROW: Open edX Architecture Hangout: Tues Feb 19th

[Nimisha Asthagiri]

For those of you who missed attending the hangout, you can find the
recording at
https://openedx.atlassian.net/wiki/spaces/AC/pages/936902681/Open+edX+Arch+Hangout+2019-02-19+Studio+Login+Authz+Comms+Dev+Summit

Feel free to post questions/comments on the wiki or in #architecture
<https://openedx.slack.com/messages/C0RU5BTCP> on slack.

Cheers,
Nimisha


On Mon, Feb 18, 2019 at 2:16 PM Nimisha Asthagiri 
wrote:

> Hi everyone!
>
> Our monthly Open edX Architecture hangout (3rd Tues of each month) is
> scheduled for tomorrow (Feb19th) at 11am EST.  Join us at
> https://zoom.us/j/8539474506
>
> We plan to cover latest thoughts on Authorization, among other things.
> Please see the proposed agenda at Open edX Arch Hangout 2019-02-19
> <https://openedx.atlassian.net/wiki/spaces/AC/pages/936902681/Open+edX+Arch+Hangout+2019-02-19>,
> and feel free to update with your own agenda items.
>
> Any questions, contact us at #architecture
> <https://openedx.slack.com/messages/C0RU5BTCP>.
>
> Cheers,
> Nimisha
> edX, Chief Architect
>
> On Tues, Feb 5, 2019 at 8:08 AM Nimisha Asthagiri 
> wrote:
>
> All,
>
> A reminder that we will present and discuss Open edX Authentication today
> at 11AM EST:
>
>
> https://openedx.atlassian.net/wiki/spaces/AC/pages/936902674/Open+edX+Arch+Hangout+2019-02-05+Authentication
>
> See ya there!
>
> Best,
> Nimisha
>
> On Mon, Jan 14, 2019 at 12:14 PM Nimisha Asthagiri 
> wrote:
>
>> Hi everyone!
>>
>> Our monthly Open edX Architecture hangout (3rd Tues of each month) is
>> scheduled for tomorrow (Jan 14th) at 11am EST.  Join us at
>> https://zoom.us/j/8539474506
>>
>> I have proposed a few agenda items at Open edX Arch Hangout 2019-01-15
>> <https://openedx.atlassian.net/wiki/spaces/AC/pages/935559288/Open+edX+Arch+Hangout+2019-01-15>,
>> but feel free to update with your own thoughts and needs.
>>
>> Cheers,
>> Nimisha
>> edX, Chief Architect
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjeHwvWUcLq-bqBViXJVbuOH2n-_%2B%3DX%2B8%2B8TCH6A97Lg_g%40mail.gmail.com.

Re: [edx-code] Next Architecture Hangout (on Authentication): Tues Feb 5th

[Nimisha Asthagiri]

Better late than never - the recording of this hangout is now available at Open
edX Arch Hangout 2019-02-05, Authentication
<https://openedx.atlassian.net/wiki/spaces/AC/pages/936902674/Open+edX+Arch+Hangout+2019-02-05+Authentication>
.

Thanks to Peter Pinch for stepping in last minute to record for us since
Zoom's servers were down.

Best,
Nimisha

On Tue, Feb 5, 2019 at 8:08 AM Nimisha Asthagiri  wrote:

> All,
>
> A reminder that we will present and discuss Open edX Authentication today
> at 11AM EST:
>
>
> https://openedx.atlassian.net/wiki/spaces/AC/pages/936902674/Open+edX+Arch+Hangout+2019-02-05+Authentication
>
> See ya there!
>
> Best,
> Nimisha
>
> -- Forwarded message -
> From: Lupus Furyo 
> Date: Fri, Jan 18, 2019 at 1:24 PM
> Subject: Re: [edx-code] Next Architecture Hangout (on Authentication):
> Tues Feb 5th
> To: 
> Cc: Peter Pinch 
>
>
> Hi Nimisha,
> Thank you very much for sharing the information about the upcoming hangout
> on recent changes, current status, and future vision of Open edX auth.
> Best, L.
>
> On Fri, Jan 18, 2019 at 5:39 PM Nimisha Asthagiri 
> wrote:
>
>> Hi everyone!
>>
>> Given the community's interest in learning about our platform's
>> Authentication vision, recent changes and status, we are holding another
>> hangout in 2 weeks.
>>
>> As before, join us at https://zoom.us/j/8539474506.
>> Past agenda and recordings are kept on the wiki at Open edX Arch Hangouts
>> <https://openedx.atlassian.net/wiki/spaces/AC/pages/858619933/Open%2BedX%2BArch%2BHangouts>
>> .
>>
>> Cheers,
>> Nimisha
>>
>> On Mon, Jan 14, 2019 at 12:14 PM Nimisha Asthagiri 
>> wrote:
>>
>>> Hi everyone!
>>>
>>> Our monthly Open edX Architecture hangout (3rd Tues of each month) is
>>> scheduled for tomorrow (Jan 14th) at 11am EST.  Join us at
>>> https://zoom.us/j/8539474506
>>>
>>> I have proposed a few agenda items at Open edX Arch Hangout 2019-01-15
>>> <https://openedx.atlassian.net/wiki/spaces/AC/pages/935559288/Open+edX+Arch+Hangout+2019-01-15>,
>>> but feel free to update with your own thoughts and needs.
>>>
>>> Cheers,
>>> Nimisha
>>> edX, Chief Architect
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "General Open edX discussion" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/edx-code/CACSOLjcj%3DdsYscpb%3Dz%2B%3DwVLfBp1Cpxb4xH1VETbp6A9a95nPGg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/edx-code/CACSOLjcj%3DdsYscpb%3Dz%2B%3DwVLfBp1Cpxb4xH1VETbp6A9a95nPGg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "General Open edX discussion" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/edx-code/CA%2BaB0d8T5Y9pxbYEpF7-M_oj_h79LcZQN3EJ%2BzQ8FUxidHiDgQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/edx-code/CA%2BaB0d8T5Y9pxbYEpF7-M_oj_h79LcZQN3EJ%2BzQ8FUxidHiDgQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjfasb5nJ5o43ayqKcXxOzgkp-j1MUBezW5Bb3khy%2BcjWg%40mail.gmail.com.

[edx-code] TOMORROW: Open edX Architecture Hangout: Tues Feb 19th

[Nimisha Asthagiri]

Hi everyone!

Our monthly Open edX Architecture hangout (3rd Tues of each month) is
scheduled for tomorrow (Feb19th) at 11am EST.  Join us at
https://zoom.us/j/8539474506

We plan to cover latest thoughts on Authorization, among other things.
Please see the proposed agenda at Open edX Arch Hangout 2019-02-19
<https://openedx.atlassian.net/wiki/spaces/AC/pages/936902681/Open+edX+Arch+Hangout+2019-02-19>,
and feel free to update with your own agenda items.

Any questions, contact us at #architecture
<https://openedx.slack.com/messages/C0RU5BTCP>.

Cheers,
Nimisha
edX, Chief Architect

On Tues, Feb 5, 2019 at 8:08 AM Nimisha Asthagiri 
wrote:

All,

A reminder that we will present and discuss Open edX Authentication today
at 11AM EST:

https://openedx.atlassian.net/wiki/spaces/AC/pages/936902674/Open+edX+Arch+Hangout+2019-02-05+Authentication

See ya there!

Best,
Nimisha

On Mon, Jan 14, 2019 at 12:14 PM Nimisha Asthagiri 
wrote:

> Hi everyone!
>
> Our monthly Open edX Architecture hangout (3rd Tues of each month) is
> scheduled for tomorrow (Jan 14th) at 11am EST.  Join us at
> https://zoom.us/j/8539474506
>
> I have proposed a few agenda items at Open edX Arch Hangout 2019-01-15
> <https://openedx.atlassian.net/wiki/spaces/AC/pages/935559288/Open+edX+Arch+Hangout+2019-01-15>,
> but feel free to update with your own thoughts and needs.
>
> Cheers,
> Nimisha
> edX, Chief Architect
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjfYBNk3YN--RnJcgSfJ5pLQ1a2_Weg9_%2BEUS%2BhW8dE-%3DQ%40mail.gmail.com.

Re: [edx-code] Next Architecture Hangout (on Authentication): Tues Feb 5th

[Nimisha Asthagiri]

All,

A reminder that we will present and discuss Open edX Authentication today
at 11AM EST:

https://openedx.atlassian.net/wiki/spaces/AC/pages/936902674/Open+edX+Arch+Hangout+2019-02-05+Authentication

See ya there!

Best,
Nimisha

-- Forwarded message -
From: Lupus Furyo 
Date: Fri, Jan 18, 2019 at 1:24 PM
Subject: Re: [edx-code] Next Architecture Hangout (on Authentication): Tues
Feb 5th
To: 
Cc: Peter Pinch 


Hi Nimisha,
Thank you very much for sharing the information about the upcoming hangout
on recent changes, current status, and future vision of Open edX auth.
Best, L.

On Fri, Jan 18, 2019 at 5:39 PM Nimisha Asthagiri 
wrote:

> Hi everyone!
>
> Given the community's interest in learning about our platform's
> Authentication vision, recent changes and status, we are holding another
> hangout in 2 weeks.
>
> As before, join us at https://zoom.us/j/8539474506.
> Past agenda and recordings are kept on the wiki at Open edX Arch Hangouts
> <https://openedx.atlassian.net/wiki/spaces/AC/pages/858619933/Open%2BedX%2BArch%2BHangouts>
> .
>
> Cheers,
> Nimisha
>
> On Mon, Jan 14, 2019 at 12:14 PM Nimisha Asthagiri 
> wrote:
>
>> Hi everyone!
>>
>> Our monthly Open edX Architecture hangout (3rd Tues of each month) is
>> scheduled for tomorrow (Jan 14th) at 11am EST.  Join us at
>> https://zoom.us/j/8539474506
>>
>> I have proposed a few agenda items at Open edX Arch Hangout 2019-01-15
>> <https://openedx.atlassian.net/wiki/spaces/AC/pages/935559288/Open+edX+Arch+Hangout+2019-01-15>,
>> but feel free to update with your own thoughts and needs.
>>
>> Cheers,
>> Nimisha
>> edX, Chief Architect
>>
> --
> You received this message because you are subscribed to the Google Groups
> "General Open edX discussion" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/edx-code/CACSOLjcj%3DdsYscpb%3Dz%2B%3DwVLfBp1Cpxb4xH1VETbp6A9a95nPGg%40mail.gmail.com
> <https://groups.google.com/d/msgid/edx-code/CACSOLjcj%3DdsYscpb%3Dz%2B%3DwVLfBp1Cpxb4xH1VETbp6A9a95nPGg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
-- 
You received this message because you are subscribed to the Google Groups
"General Open edX discussion" group.
To view this discussion on the web visit
https://groups.google.com/d/msgid/edx-code/CA%2BaB0d8T5Y9pxbYEpF7-M_oj_h79LcZQN3EJ%2BzQ8FUxidHiDgQ%40mail.gmail.com
<https://groups.google.com/d/msgid/edx-code/CA%2BaB0d8T5Y9pxbYEpF7-M_oj_h79LcZQN3EJ%2BzQ8FUxidHiDgQ%40mail.gmail.com?utm_medium=email_source=footer>
.

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjea9f4LbkaUm50PQ%3D5KAmijzR4dT4vpzG8xCHwJmmqiqQ%40mail.gmail.com.

[edx-code] Next Architecture Hangout (on Authentication): Tues Feb 5th

[Nimisha Asthagiri]

Hi everyone!

Given the community's interest in learning about our platform's
Authentication vision, recent changes and status, we are holding another
hangout in 2 weeks.

As before, join us at https://zoom.us/j/8539474506.
Past agenda and recordings are kept on the wiki at Open edX Arch Hangouts
<https://openedx.atlassian.net/wiki/spaces/AC/pages/858619933/Open%2BedX%2BArch%2BHangouts>
.

Cheers,
Nimisha

On Mon, Jan 14, 2019 at 12:14 PM Nimisha Asthagiri 
wrote:

> Hi everyone!
>
> Our monthly Open edX Architecture hangout (3rd Tues of each month) is
> scheduled for tomorrow (Jan 14th) at 11am EST.  Join us at
> https://zoom.us/j/8539474506
>
> I have proposed a few agenda items at Open edX Arch Hangout 2019-01-15
> <https://openedx.atlassian.net/wiki/spaces/AC/pages/935559288/Open+edX+Arch+Hangout+2019-01-15>,
> but feel free to update with your own thoughts and needs.
>
> Cheers,
> Nimisha
> edX, Chief Architect
>

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjcj%3DdsYscpb%3Dz%2B%3DwVLfBp1Cpxb4xH1VETbp6A9a95nPGg%40mail.gmail.com.

[edx-code] TOMORROW: Open edX Architecture Hangout: Tues Jan 14th

[Nimisha Asthagiri]

Hi everyone!

Our monthly Open edX Architecture hangout (3rd Tues of each month) is
scheduled for tomorrow (Jan 14th) at 11am EST.  Join us at
https://zoom.us/j/8539474506

I have proposed a few agenda items at Open edX Arch Hangout 2019-01-15
,
but feel free to update with your own thoughts and needs.

Cheers,
Nimisha
edX, Chief Architect

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjfDwCQ%3DdS9aV5MTaUZi%2B%2Bk3gqWkPObrfDnn%2BO_BBVOeFw%40mail.gmail.com.

[edx-code] OEP-19: Sustainable Developer Documentation

[Nimisha Asthagiri]

Hi All,

There's a draft of *OEP-0019: Developer Documentation* available for review.

   - *Pull Request:* https://github.com/edx/open-edx-proposals/pull/74
   - *Rendered Version*: oep-0019-bp-developer-documentation.rst
   

   - *Review Period*: 2018-12-06 - 2018-12-20
   - *Summary:* Developers who work on the Open edX platform, both inside
   and outside of edX, need accurate and current documentation about platform
   architecture, APIs, and development best practices. Currently, the
   documentation is duplicated, inconsistent and poorly maintained.

Please provide any feedback you might have on the pull request.

Thank you!

Grant, Robert, Nimisha (authors)
Cali (arbiter)

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjeKaMBfh4TwfysuJaRoppRjdLSo%2BoidBiGbq40-ZrOHDA%40mail.gmail.com.

[edx-code] OEP-26: Real-time Events

[Nimisha Asthagiri]

Hi All,

There's a draft of *OEP-0026: Real-time Events* available for review.

   - *Pull Request: **https://github.com/edx/open-edx-proposals/pull/73
   *
   - *Rendered Version*: oep-0026-arch-realtime-events.rst
   

   - *Review Period*: 2018-11-29 - 2018-12-20
   - *Summary:* To satisfy emerging use cases that require notifying
   external systems of LMS events (in standardized formats), supporting
   real-time events is a natural evolution of Open edX's eventing and API
   capabilities and its impact on connecting users, organizations, and
   learning services.

Please provide any feedback you might have on the pull request.

Thank you!

Nimisha (Author) & Brian (Arbiter)

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjeCUN-6Q%3DGi%3D6LrRhvYVmDweE5-JgThkJ4RLcHRgFCPCQ%40mail.gmail.com.

Re: [edx-code] Deprecation/Removal: External Auth Django App (DEPR-6)

[Nimisha Asthagiri]

Peter,

We had some issues with JIRA permissions.  It should be fixed now.
Regarding Ironwood, I'll respond on the ticket after gathering information
on the anticipated Ironwood from our Open edX team.

Thanks,
Nimisha

On Wed, Oct 24, 2018 at 12:44 PM Peter Pinch  wrote:

> The JIRA ticket isn’t open. I was hoping to get a better idea of the scope
> of the deprecation.
>
> Also, is a 2019-02-15 removal expected to be a change in Ironwood, or in
> Ironwood's successor?
>
>
> Thanks,
> Peter
>
> Peter Pinch
> Associate Director of Engineering
> MIT Open Learning
> pdpi...@mit.edu
> http://engineering.odl.mit.edu/
>
> On Oct 24, 2018, at 12:29 PM, Nimisha Asthagiri 
> wrote:
>
> Hi there,
>
> We plan to deprecate and remove from edx-platform the external_auth
> Django app
> <https://github.com/edx/edx-platform/tree/master/openedx/core/djangoapps/external_auth>
>  in
> favor of the third_party_auth Django app
> <https://github.com/edx/edx-platform/tree/master/common/djangoapps/third_party_auth>
>  (an
> extension of python-social-auth
> <https://python-social-auth.readthedocs.io/en/latest/>).  We are
> targeting removal by *2019-02-15*.
>
> Please read https://openedx.atlassian.net/browse/DEPR-6 for more
> information and to post any questions/comments. The proposed deadline for
> comments before acceptance is *2018-11-25*.
>
> Thanks,
> Nimisha
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "General Open edX discussion" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/edx-code/CACSOLjdsxLwLAfbcHbi1dNnwQ83iHaY4Q3u6A%3DqUdhCvcPCYTw%40mail.gmail.com
> <https://groups.google.com/d/msgid/edx-code/CACSOLjdsxLwLAfbcHbi1dNnwQ83iHaY4Q3u6A%3DqUdhCvcPCYTw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "General Open edX discussion" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/edx-code/6E2B9D7F-16EC-4AE8-A870-4086C48ED653%40gmail.com
> <https://groups.google.com/d/msgid/edx-code/6E2B9D7F-16EC-4AE8-A870-4086C48ED653%40gmail.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjfQZBBb1znM5KdGmFK5gy0zLaTQ4-k88hvw7LNkkKu3Tw%40mail.gmail.com.

[edx-code] Deprecation/Removal: Mobile Video Outlines API (DEPR-4)

[Nimisha Asthagiri]

Hello all,

We plan to deprecate and remove the Mobile v0.5 Video Outline REST API

in favor of the Course Blocks v1 REST API
,
targeting removal by *2019-01-15*.

Please read https://openedx.atlassian.net/browse/DEPR-4 for more
information and to post any questions/comments.

Thanks,
Nimisha

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjfJRpQzQ7-HtR3sVy9cOHZ74SPgCSS0suVXboiDBdCsmQ%40mail.gmail.com.

[edx-code] Deprecation/Removal: Grades v0 REST API (DEPR-3)

[Nimisha Asthagiri]

Hello all,

We plan to deprecate and remove the old Grades v0 REST API

in favor of the newer Grades v1 REST API
,
targeting removal by *2018-12-15*.

Please read https://openedx.atlassian.net/browse/DEPR-3 for more
information and to post any questions/comments.

Thanks,
Nimisha

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjctD34-RVnEGMYGHpkdsPbSH69YGCkcHqdTF%3DLPHk%3Dg8Q%40mail.gmail.com.

[edx-code] Open edX Architecture Hangout: Tues Oct 16th

[Nimisha Asthagiri]

Hi everyone,

We would like to invite you to an online community hangout to discuss Open
edX Architecture initiatives, strategy, and other architecture-related
topics.  At our 1st meeting
,
we plan to share the edX Architecture roadmap and present the design of
Blockstore (our future storage framework of learning content).

What types of topics/discussions would you like to see going forward?
Please post your ideas in the Arch Hangouts Backlog

.

For our first hangout, let's meet up on Tuesday, October 16th at 11am EST
at https://zoom.us/j/8539474506.  Hope you can make it!

Cheers,
edX Architecture Team

Dave, Doug, Robert, Greg, Marco, Ed, Nimisha

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLje3uzfGKzaV_iZbOpyxPS7%3DXqURaeNp0HgpdQ6_q88C0Q%40mail.gmail.com.

[edx-code] Re: Proposal for review: simplifying and updating the OEP process

[Nimisha Asthagiri]

Hi all.

Here's another attempt at further simplifying the OEP process, including
the submission process and the OEP template:

https://github.com/edx/open-edx-proposals/pull/60


Please review and provide any feedback.

*Review Period: *May 02, 2018 -> May 11, 2018

*Motivation*

Going forward, we want to encourage teams to write down and propose their
architectural and system-wide decisions so we can align with best
practices, processes, and system architectures.

Our hypothesis is that the rigid structure required by the PEP-based OEP
template deters and confuses authors. Also, we find that some authors
continue to prefer other documentation and discussion tools. So this PR
introduces 2 other OEP templates to accommodate those needs:

   - ADR-based template (much simpler format than PEP)
   - External-link catered template (requiring distilled decisions to still
   be captured in the OEP, but discussions and other details can be captured
   elsewhere)

Thanks,
Nimisha

On Tue, Feb 6, 2018 at 3:45 PM, Nimisha Asthagiri <nasthag...@edx.org>
wrote:

> Hello edx-code,
>
> *Proposal for Review*
>
> We would like to simplify the process for creating/maintaining Open edX
> Proposals <https://github.com/edx/open-edx-proposals>. Going forward, we
> want to lower the barrier for proposing architectural and system-wide
> decisions so we can align with edX best practices, processes, and
> architectures.
>
> Additionally, we are updating the process given recent changes in the org
> (i.e., the formation of an Architecture team
> <https://openedx.atlassian.net/wiki/spaces/AC/pages/439353453/Architecture+Team>
> in lieu of a chief architect).
>
> Please refer to the PR for updating and simplifying OEP-1
> <https://github.com/edx/open-edx-proposals/pull/53>.
>
> *Note*
>
> In particular, please notice that a proposed change is that future OEPs
> would be announced on slack
> <https://github.com/edx/open-edx-proposals/pull/53/files#diff-fe2e3cd15d875e19d9059cb402bb62d6R191>
> and may not always be announced on edx-code. So folks who are interested in
> architecture proposals can be informed through a more focused channel.
>
> *Review Feedback*
>
> You may share your comments/feedback by:
>
>- posting on the PR <https://github.com/edx/open-edx-proposals/pull/53>
>.
>- starting a thread on #architecture on slack
><https://openedx.slack.com/messages/C0RU5BTCP/details/>, which we
>would eventually record in the OEP PR.
>- contacting me or Cale <c...@edx.org> (the Arbiter of this edit),
>with the intent of capturing a summary of the conversation on the PR.
>
> *Timeline*
>
> As specified in the PR, the target review end date is Feb 15th
> <https://github.com/edx/open-edx-proposals/pull/53/files#diff-fe2e3cd15d875e19d9059cb402bb62d6R26>.
> If needed, we will extend the deadline.
>
> Thanks,
> Nimisha (and Cale as "Arbiter")
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjcDNUw3sRuHMLFa_QqFWKyi9YETy%2BwL1Kr%2BzAfCFap5iw%40mail.gmail.com.

Re: [edx-code] Re: course structure api removal from master (replaced by courses API)

[Nimisha Asthagiri]

If we really really need to, we can reinstate the User API and Enrollments
API links.  However, there's no reason to put back the "deprecated Platform
API" information.  That was causing another stream of confusion, which came
in from external partners through the Enterprise team.

On Thu, Apr 26, 2018 at 3:17 PM, Ned Batchelder <n...@edx.org> wrote:

> The API docs were getting out of date because the complexity of building
> them from the edx-platform repo meant that they wouldn't build successfully
> any more.  Perhaps too aggressively, we removed the ReadTheDocs projects
> rather than serve incorrect information.   We're looking for a way to
> restore them.
>
> --Ned.
>
> On Mon, Apr 23, 2018 at 5:17 AM, Jill Vogel <j...@opencraft.com> wrote:
>
>> Thank you for this information about the Course Structure API!
>>
>> But it looks like the API documentation has been removed from readthedocs
>> -- is this intentional?  E.g. the  Courses API V1
>> <http://edx.readthedocs.io/projects/edx-platform-api/en/latest/courses/index.html>
>>  link
>> that Dennis shared above 404s, as do the Enrollment API
>> <http://edx.readthedocs.io/projects/edx-platform-api/en/latest/enrollment/index.html>
>> and User API
>> <http://edx.readthedocs.io/projects/edx-platform-api/en/latest/user/index.html>
>> links from this old post Open edX ReST APIs
>> <https://open.edx.org/open-edx-rest-apis>.
>>
>> --
>> Jill
>> @OpenCraft
>> <http://opencraft.com/>
>>
>> On Sat, Apr 21, 2018 at 10:47 PM, Nimisha Asthagiri <nasthag...@edx.org>
>> wrote:
>>
>>> Hi all,
>>>
>>> It's been a while, but we have now finally removed the Course Structure
>>> API from the platform in this PR
>>> <https://github.com/edx/edx-platform/pull/17983>.
>>>
>>> As a reminder, the Course Blocks API
>>> <https://github.com/edx/edx-platform/blob/master/lms/djangoapps/course_api/blocks/views.py>
>>>  should
>>> be used for retrieving Course structure data and the Grades API
>>> <https://github.com/edx/edx-platform/blob/master/lms/djangoapps/grades/api/urls.py>
>>>  provides
>>> grades and grading policy information.  There is also an upcoming PR
>>> <https://github.com/edx/edx-platform/pull/17602> that will create a v1
>>> of the Grades API.
>>>
>>> Thanks,
>>> Nimisha
>>>
>>> On Tuesday, September 13, 2016 at 5:38:13 PM UTC+4, Dennis Jen wrote:
>>>>>
>>>>> Hi Open edXers:
>>>>>
>>>>> The Course Structure API Version 0
>>>>> <http://edx.readthedocs.io/projects/edx-platform-api/en/latest/course_structure/index.html>
>>>>> has been deprecated for some time now and will be removed from the
>>>>> edx-platform <https://github.com/edx/edx-platform> codebase on the
>>>>> master branch and will not affect any Eucalyptus release, even future
>>>>> ones.  Ficus will be the first Open edX release without the Course
>>>>> Structure API.  The grading policy endpoint will remain for the time being
>>>>> and the tentative plan is for it to be incorporated into the grades
>>>>> api
>>>>> <https://github.com/edx/edx-platform/tree/master/lms/djangoapps/grades/api>
>>>>> (V0 and still under development).
>>>>>
>>>>> Specifically, the following endpoints will be removed:
>>>>>
>>>>>
>>>>>-
>>>>>
>>>>>api/course_structure/v0/course_structures/{course_id}/
>>>>>-
>>>>>
>>>>>api/course_structure/v0/courses/{course_id}
>>>>>-
>>>>>
>>>>>api/course_structure/v0/courses/
>>>>>
>>>>>
>>>>> The grading policy endpoint will remain for the time being, although
>>>>> still deprecated:
>>>>>
>>>>>
>>>>>-
>>>>>
>>>>>/api/course_structure/v0//grading_policies/
>>>>>
>>>>>
>>>>> They can be replaced with similar endpoints on the Courses API V1
>>>>> <http://edx.readthedocs.io/projects/edx-platform-api/en/latest/courses/index.html>.
>>>>> As far as we know, edX Insights
>>>>> <https://github.com/edx/edx-analytics-dashboard> was the only
>>>>> consumer of the deprecated endpoints and ha

Re: [edx-code] Re: course structure api removal from master (replaced by courses API)

[Nimisha Asthagiri]

Hi all,

It's been a while, but we have now finally removed the Course Structure API
from the platform in this PR
.

As a reminder, the Course Blocks API

should
be used for retrieving Course structure data and the Grades API

provides
grades and grading policy information.  There is also an upcoming PR
 that will create a v1 of
the Grades API.

Thanks,
Nimisha

On Tuesday, September 13, 2016 at 5:38:13 PM UTC+4, Dennis Jen wrote:
>>
>> Hi Open edXers:
>>
>> The Course Structure API Version 0
>> 
>> has been deprecated for some time now and will be removed from the
>> edx-platform  codebase on the
>> master branch and will not affect any Eucalyptus release, even future
>> ones.  Ficus will be the first Open edX release without the Course
>> Structure API.  The grading policy endpoint will remain for the time being
>> and the tentative plan is for it to be incorporated into the grades api
>> 
>> (V0 and still under development).
>>
>> Specifically, the following endpoints will be removed:
>>
>>
>>-
>>
>>api/course_structure/v0/course_structures/{course_id}/
>>-
>>
>>api/course_structure/v0/courses/{course_id}
>>-
>>
>>api/course_structure/v0/courses/
>>
>>
>> The grading policy endpoint will remain for the time being, although
>> still deprecated:
>>
>>
>>-
>>
>>/api/course_structure/v0//grading_policies/
>>
>>
>> They can be replaced with similar endpoints on the Courses API V1
>> .
>> As far as we know, edX Insights
>>  was the only consumer
>> of the deprecated endpoints and has been cut over to the courses API
>> .
>>
>> We expect to have the course structure API removed the week of October
>> 4th, 2016.  If you’re impacted by this or need any help with the courses
>> API, please let us know!
>>
>> Thanks,
>>
>> Dennis
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "General Open edX discussion" group.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/edx-code/4a624a57-878d-4a4f-b7aa-cbbb4d85605e%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjfWC2fQO-KBJEjfwjE%3DqjboU%3DJ%2Bcm%3D9%2BgC07Kgk35FgRw%40mail.gmail.com.

[edx-code] Deadline for comments is today: OEP on Feature Toggle Best Practices

[Nimisha Asthagiri]

Hi all,

Please provide any final comments/feedback/etc on this OEP by EOD today.
Unless there are any blocking issues, we plan to merge it as "Accepted"
tomorrow.

Thanks,
Nimisha (and Eric as "Arbiter")


On Wed, Feb 28, 2018 at 2:32 PM, Nimisha Asthagiri <nasthag...@edx.org>
wrote:

> Hello edx-code,
>
> *Feature Toggle Best Practices*
>
> We use feature toggles extensively in our system to selectively enable a
> feature for certain users or certain deployments and more generally to
> decouple deployment of code from release (enablement) of the code. When
> used with care, feature toggles can be a powerful tool that enable many use
> cases.
>
> However, feature toggles inherently add complexity to the code since they
> introduce multiple paths and configuration operations. Let's align on a
> common best practice for feature toggling as it is critical for both the
> short-term and long-term health of the open edX system.
>
> Please refer to the PR for feature toggle best practices
> <https://github.com/edx/open-edx-proposals/pull/54>.
>
> *Review Feedback*
>
> You may share your comments/feedback by (in order of preference):
>
>- posting on the PR <https://github.com/edx/open-edx-proposals/pull/54>
>.
>- starting a thread on #architecture on slack
><https://openedx.slack.com/messages/C0RU5BTCP/details/>, which we
>would eventually record in the OEP PR.
>- contacting me or Eric <efisc...@edx.org> (the Arbiter of this OEP),
>with the intent of capturing a summary of the conversation on the PR.
>
> *Timeline*
>
> As specified in the PR, the target review end date is *March 19th **(extended
> from March 7th).*
>
> Thanks,
> Nimisha (and Eric as "Arbiter")
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjdm%2BUp2peuzepv%3DWXGKaFTOejgnna8rW%2Bgi_ohEect0-Q%40mail.gmail.com.

Re: [edx-code] Re: Upcoming xBlock and course APIs from mobile team

[Nimisha Asthagiri]

You need to declare that the xBlock's student_view has multi-device
support, as described in BlockRendering: Web, Responsive, and Native
<https://openedx.atlassian.net/wiki/spaces/EDUCATOR/pages/29688043/Course+Blocks+API#CourseBlocksAPI-BlockRendering:Web,Responsive,andNative>
.

As an example, see the drag-n-drop xBlock's student view
<https://github.com/edx-solutions/xblock-drag-and-drop-v2/blob/8c6ba95b5eccb7a6c9a7e860ddd1e19cef82ab10/drag_and_drop_v2/drag_and_drop_v2.py#L256-L257>
.

On Thu, Mar 1, 2018 at 6:40 PM, Samuel Marks <samuelma...@gmail.com> wrote:

> Hi Nimisha,
>
> I'm developing a basic XBlock that I would also like to work on mobile.
>
> What's the trick here?
>
> On Fri, 2 Mar 2018 at 5:35 am, Nimisha Asthagiri <nasthag...@edx.org>
> wrote:
>
>> Hi Samuel,
>>
>> Do you have a question regarding the Course Blocks API?  The API is
>> available for use on the platform.
>>
>> Thanks,
>> Nimisha
>>
>> On Thu, Mar 1, 2018 at 9:32 AM, Samuel Marks <samuelma...@gmail.com>
>> wrote:
>>
>>> FYI: Not Yet Implemented
>>> https://openedx.atlassian.net/wiki/spaces/EDUCATOR/pages/
>>> 29688043/Course+Blocks+API
>>>
>>> On Friday, July 15, 2016 at 2:59:29 AM UTC+10, Nimisha Asthagiri wrote:
>>>>
>>>> Hi Ishan,
>>>>
>>>> This project was completed last fall and is available in the Dogwood
>>>> release of open edX.
>>>>
>>>> There are essentially 2 options right now for supporting your SCORM
>>>> xBlock on mobile:
>>>>
>>>> 1. *Webview:* Render it in a webview after ensuring that the xBlock
>>>> has responsive web layouts and support for touch-based inputs.  This is
>>>> done by marking the xBlock's student view with the @XBlock.supports(
>>>> "multi_device") python decorator.
>>>>
>>>> 2. *Native:* Implement a student_view_data method on the xBlock and
>>>> return JSON data that could be interpreted and executed natively by the
>>>> mobile app.  This currently requires forking the edX app code in order to
>>>> add your native implementation.  In the future, we may be able to architect
>>>> the app code so it can include custom xBlock app libraries without a full
>>>> fork of our repo.
>>>>
>>>> The following section in the Course Blocks API wiki has more
>>>> information on this:
>>>> https://openedx.atlassian.net/wiki/display/MA/Course+Blocks+
>>>> API#CourseBlocksAPI-BlockRendering:Web,Responsive,andNative
>>>>
>>>> Thanks,
>>>> Nimisha
>>>>
>>>>
>>>> On Mon, Jul 11, 2016 at 1:39 AM, <ishan...@theteacherapp.org> wrote:
>>>>
>>>>> Hi Nimisha,
>>>>>
>>>>> Any update on this project? We are trying to extend the scope of a
>>>>> SCORM xBlock that plays SCORM content on web, but is not able to do on the
>>>>> edX mobile app.
>>>>>
>>>>> -Ishan
>>>>>
>>>>> On Friday, May 29, 2015 at 4:34:12 AM UTC+5:30, Nimisha Asthagiri
>>>>> wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> The Mobile team at edX is planning to extend the mobile apps with
>>>>>> generic support for accessing and navigating xBlocks in a course.  (The
>>>>>> currently deployed mobile apps have support for only video data.)  In our
>>>>>> initial support for xBlocks on mobile, we plan to render them through
>>>>>> webviews as long as they have responsive UI.
>>>>>>
>>>>>> In the spirit of giving you an opportunity to chime in during the
>>>>>> design phase of this work, we are sending out this note as a
>>>>>> pre-announcement to an upcoming design spec of this feature and an
>>>>>> invitation to send us any initial thoughts you may have.
>>>>>>
>>>>>> In the upcoming design, you can expect (based on a preliminary
>>>>>> prototype by our team):
>>>>>>
>>>>>>- A mechanism to *tag an xBlock* when its HTML/CSS is responsive.
>>>>>>- A REST API for *rendering a single xBlock*, without the extra
>>>>>>chrome of the containing courseware.
>>>>>>- A REST API for *listing all the xBlocks* in a course from the
>>>>>>perspective of the requ

Re: [edx-code] Re: Upcoming xBlock and course APIs from mobile team

[Nimisha Asthagiri]

Hi Samuel,

Do you have a question regarding the Course Blocks API?  The API is
available for use on the platform.

Thanks,
Nimisha

On Thu, Mar 1, 2018 at 9:32 AM, Samuel Marks <samuelma...@gmail.com> wrote:

> FYI: Not Yet Implemented
> https://openedx.atlassian.net/wiki/spaces/EDUCATOR/pages/
> 29688043/Course+Blocks+API
>
> On Friday, July 15, 2016 at 2:59:29 AM UTC+10, Nimisha Asthagiri wrote:
>>
>> Hi Ishan,
>>
>> This project was completed last fall and is available in the Dogwood
>> release of open edX.
>>
>> There are essentially 2 options right now for supporting your SCORM
>> xBlock on mobile:
>>
>> 1. *Webview:* Render it in a webview after ensuring that the xBlock has
>> responsive web layouts and support for touch-based inputs.  This is done by
>> marking the xBlock's student view with the @XBlock.supports("multi_de
>> vice") python decorator.
>>
>> 2. *Native:* Implement a student_view_data method on the xBlock and
>> return JSON data that could be interpreted and executed natively by the
>> mobile app.  This currently requires forking the edX app code in order to
>> add your native implementation.  In the future, we may be able to architect
>> the app code so it can include custom xBlock app libraries without a full
>> fork of our repo.
>>
>> The following section in the Course Blocks API wiki has more information
>> on this:
>> https://openedx.atlassian.net/wiki/display/MA/Course+Blocks+
>> API#CourseBlocksAPI-BlockRendering:Web,Responsive,andNative
>>
>> Thanks,
>> Nimisha
>>
>>
>> On Mon, Jul 11, 2016 at 1:39 AM, <ishan...@theteacherapp.org> wrote:
>>
>>> Hi Nimisha,
>>>
>>> Any update on this project? We are trying to extend the scope of a SCORM
>>> xBlock that plays SCORM content on web, but is not able to do on the edX
>>> mobile app.
>>>
>>> -Ishan
>>>
>>> On Friday, May 29, 2015 at 4:34:12 AM UTC+5:30, Nimisha Asthagiri wrote:
>>>>
>>>> Hi all,
>>>>
>>>> The Mobile team at edX is planning to extend the mobile apps with
>>>> generic support for accessing and navigating xBlocks in a course.  (The
>>>> currently deployed mobile apps have support for only video data.)  In our
>>>> initial support for xBlocks on mobile, we plan to render them through
>>>> webviews as long as they have responsive UI.
>>>>
>>>> In the spirit of giving you an opportunity to chime in during the
>>>> design phase of this work, we are sending out this note as a
>>>> pre-announcement to an upcoming design spec of this feature and an
>>>> invitation to send us any initial thoughts you may have.
>>>>
>>>> In the upcoming design, you can expect (based on a preliminary
>>>> prototype by our team):
>>>>
>>>>- A mechanism to *tag an xBlock* when its HTML/CSS is responsive.
>>>>- A REST API for *rendering a single xBlock*, without the extra
>>>>chrome of the containing courseware.
>>>>- A REST API for *listing all the xBlocks* in a course from the
>>>>perspective of the requesting user (e.g., a student).
>>>>   - Design consideration for making this a generic API that can be
>>>>   used by non-mobile clients as well.
>>>>   - Preliminary support for a participating xBlock to embed a
>>>>   student view in JSON form.  For example, with a native video player 
>>>> on
>>>>   mobile, the video module can send JSON data that is needed for a 
>>>> student
>>>>   view of the video.
>>>>- A REST API for delivering *navigation information of a course*.
>>>>For usability reasons, some LMS views (such as a mobile app) may have
>>>>maximum limits on how deep to show a course hierarchy.  In such cases, 
>>>> it
>>>>is useful to have a centralized API that returns a navigation view of 
>>>> the
>>>>course, while handling all types of course hierarchical structures.
>>>>
>>>> Our expected timeframe is as follows:
>>>>
>>>> June 12th: Preliminary design spec for review
>>>> June 13th - June 26th: Design review process
>>>> June 26th: Final and agreed upon design complete
>>>>
>>>>
>>>> Thanks,
>>>> Nimisha
>>>>
>>>> --
>>>>
>>>> *Mobile, Technical Lead*
>>>>
>>>> edX <http://www.edx.org> | nim...@edx.org
>>>>
>>>>
>>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "General Open edX discussion" group.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/edx-code/fbbec968-6589-4b8b-bd6d-8d6323ca6af6%40googlegroups.com
> <https://groups.google.com/d/msgid/edx-code/fbbec968-6589-4b8b-bd6d-8d6323ca6af6%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjdcoSpn75n-AzuOKUTfMX%3DfkgB5Xz621KbzLNUrm9P_iQ%40mail.gmail.com.

[edx-code] OEP for review: Feature Toggle Best Practices

[Nimisha Asthagiri]

Hello edx-code,

*Feature Toggle Best Practices*

We use feature toggles extensively in our system to selectively enable a
feature for certain users or certain deployments and more generally to
decouple deployment of code from release (enablement) of the code. When
used with care, feature toggles can be a powerful tool that enable many use
cases.

However, feature toggles inherently add complexity to the code since they
introduce multiple paths and configuration operations. Let's align on a
common best practice for feature toggling as it is critical for both the
short-term and long-term health of the open edX system.

Please refer to the PR for feature toggle best practices
.

*Review Feedback*

You may share your comments/feedback by (in order of preference):

   - posting on the PR .
   - starting a thread on #architecture on slack
   , which we would
   eventually record in the OEP PR.
   - contacting me or Eric  (the Arbiter of this OEP),
   with the intent of capturing a summary of the conversation on the PR.

*Timeline*

As specified in the PR, the target review end date is *March 7th*.  If
needed, we will extend the deadline.

Thanks,
Nimisha (and Eric as "Arbiter")

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjc_A0P2p%3DTcNJ7vAu2kGCjYVM9Bm5kStudeAU6Sys3ODA%40mail.gmail.com.

[edx-code] Deadline for comments is tomorrow Feb 15: simplifying and updating the OEP process

[Nimisha Asthagiri]

A friendly reminder that the deadline for review comments is tomorrow, Feb
15th. Thanks.

On Tue, Feb 6, 2018 at 3:45 PM, Nimisha Asthagiri <nasthag...@edx.org>
wrote:

> Hello edx-code,
>
> *Proposal for Review*
>
> We would like to simplify the process for creating/maintaining Open edX
> Proposals <https://github.com/edx/open-edx-proposals>. Going forward, we
> want to lower the barrier for proposing architectural and system-wide
> decisions so we can align with edX best practices, processes, and
> architectures.
>
> Additionally, we are updating the process given recent changes in the org
> (i.e., the formation of an Architecture team
> <https://openedx.atlassian.net/wiki/spaces/AC/pages/439353453/Architecture+Team>
> in lieu of a chief architect).
>
> Please refer to the PR for updating and simplifying OEP-1
> <https://github.com/edx/open-edx-proposals/pull/53>.
>
> *Note*
>
> In particular, please notice that a proposed change is that future OEPs
> would be announced on slack
> <https://github.com/edx/open-edx-proposals/pull/53/files#diff-fe2e3cd15d875e19d9059cb402bb62d6R191>
> and may not always be announced on edx-code. So folks who are interested in
> architecture proposals can be informed through a more focused channel.
>
> *Review Feedback*
>
> You may share your comments/feedback by:
>
>- posting on the PR <https://github.com/edx/open-edx-proposals/pull/53>
>.
>- starting a thread on #architecture on slack
><https://openedx.slack.com/messages/C0RU5BTCP/details/>, which we
>would eventually record in the OEP PR.
>- contacting me or Cale <c...@edx.org> (the Arbiter of this edit),
>with the intent of capturing a summary of the conversation on the PR.
>
> *Timeline*
>
> As specified in the PR, the target review end date is Feb 15th
> <https://github.com/edx/open-edx-proposals/pull/53/files#diff-fe2e3cd15d875e19d9059cb402bb62d6R26>.
> If needed, we will extend the deadline.
>
> Thanks,
> Nimisha (and Cale as "Arbiter")
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjemhFuGMk_y1F_ACWY7YSKX5asMusex69A36aYK8u6bbw%40mail.gmail.com.

[edx-code] Proposal for review: simplifying and updating the OEP process

[Nimisha Asthagiri]

Hello edx-code,

*Proposal for Review*

We would like to simplify the process for creating/maintaining Open edX
Proposals . Going forward, we
want to lower the barrier for proposing architectural and system-wide
decisions so we can align with edX best practices, processes, and
architectures.

Additionally, we are updating the process given recent changes in the org
(i.e., the formation of an Architecture team

in lieu of a chief architect).

Please refer to the PR for updating and simplifying OEP-1
.

*Note*

In particular, please notice that a proposed change is that future OEPs
would be announced on slack

and may not always be announced on edx-code. So folks who are interested in
architecture proposals can be informed through a more focused channel.

*Review Feedback*

You may share your comments/feedback by:

   - posting on the PR .
   - starting a thread on #architecture on slack
   , which we would
   eventually record in the OEP PR.
   - contacting me or Cale  (the Arbiter of this edit), with
   the intent of capturing a summary of the conversation on the PR.

*Timeline*

As specified in the PR, the target review end date is Feb 15th
.
If needed, we will extend the deadline.

Thanks,
Nimisha (and Cale as "Arbiter")

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CACSOLjd4UzoBymW3_Dk-ePND7jPsEsJ5r6RNf%2BoVHo3TcmKXCA%40mail.gmail.com.

[edx-code] Re: Exposing the Course Version number

[Nimisha Asthagiri]

Hi Jill et al,

Thanks for starting this thread.  (I had been away on vacation and am
catching up.)

For the mobile app, we've been considering using ETags to eliminate extra
work in updating its local cache.  However, the use case there is a bit
more complicated since we need to check for user-access state-changes in
addition to course-state changes.

For your use case, however, since you only care about course-state changes,
it is very plausible *now* for us to build what's required with minimal
effort.  With the following recent PR, we were able to update the
SplitModulestore and enable a BlockTransformer to store the course_version
(guid) and subtree_edited_on (timestamp) fields with the cached course
structure:


https://github.com/edx/edx-platform/pull/13082

So now, this data is available to the Course Blocks API.  The
subtree_edited_on timestamp may be all that you need to embed in the ETag
when non-user-specific blocks are requested (i.e., when all_blocks=true URL
param is specified).

Nimisha

On Fri, Jul 22, 2016 at 10:14 AM, Adam Palay  wrote:

> Hi Jill!
>
> You mention wanting to add a table "which stores the tree of blocks used
> in a course". Can you say a little more about this? I'm wondering because
> we've been working on a feature to visualize and query course structures in
> a graph-like-context by putting modulestore data into a graph database. The
> thing we're building is only an internal tool (not meant to be instructor
> facing), but I wonder if the work could overlap at all.
>
> Adam
>
>
> On Friday, July 22, 2016 at 1:40:08 AM UTC-4, ji...@opencraft.com wrote:
>>
>> Hi,
>>
>> This post is partly to record discussions going on in a planning
>> document, and partly to spark more discussion on the topic.
>>
>> Nimisha, do you have a list of pending API improvements where this
>> feature request could be captured?
>>
>> *Feature Idea*
>>
>> Update the Courses API
>> 
>>  to
>> add the current published version ID, which is available from the
>> modulestore.
>>
>> Example: course-v1:mit.eecs+6002x+branch@published+version@5
>> 19665f6223ebd6980884f2b
>>
>> *Impetus*
>>
>> We're working on adding a table to the analytics data which stores the
>> tree of blocks used in a course, as retrieved from the Course Blocks API
>> 
>> .
>>
>> Since this table may be relatively expensive to maintain, we'd like to be
>> able to update it only when a course has changed, i.e. when a course or any
>> of its sections is Published.
>>
>> If we knew the current published version ID, then we could update the
>> table only if the current published version has changed.
>>
>> *Discussions*:
>>
>> Captured for posterity.
>>
>> From Braden MacDonald :
>>
>> Every course in split modulestore has a version (internally), and any
>>> change to the structure of the course (or any content, too, I suppose) will
>>> change the version (which is just a mongoDB ObjectId). So "all you need to
>>> do" is store the result of the Course Blocks API query for each course
>>> along with the "version of the published branch" of that course. Then, you
>>> only need to re-fetch the block structure if the current version doesn't
>>> match the cached result version.
>>
>>
>>> A course's ID string/key can actually include this version information,
>>> though this form is rarely seen: "course-v1:mit.eecs+6002x+bran
>>> ch@published+version@519665f6223ebd6980884f2b"
>>
>>
>>> From what I recall about split's "versions" table, a MongoDB query to
>>> fetch a list of all courses and the version of each would be trivial and
>>> fast, though I don't know if there is currently any API which exposes it.
>>
>>
>>> FWIW I implemented content libraries using that approach - the
>>> randomized content block checks the version of the library to know when to
>>> prompt the course author to update. If we used that approach it should be
>>> non through some API that's not directly related to the modulestore.
>>
>>
>> From Gabe Mulley :
>>
>> Yeah, I thought about leveraging that data. I'm not aware of any API that
>>> exposes it, however, and am very wary of reaching in behind the modulestore
>>> API (given how complex it is).
>>
>>
>>> I like the idea of using the version, though, to determine which courses
>>> need to be pulled again instead of time. Maybe we could leverage entity
>>> tags? Basically set the etag to the version identifier? Maybe it already
>>> does this?
>>
>>
>>> I'm not very familiar with conditional get semantics, but I think we
>>> could then use "If-None-Match" to short-circuit and return a 304 if the
>>> course hasn't changed.
>>
>>
>>
>> Thank you!
>> --
>> Jill
>> @OpenCraft 
>>
>>
>>

-- 
You received this message because you are subscribed to the Google