# Core Contributor Sprint Retro - April 29th - May 13th

**URL:** <https://discuss.openedx.org/t/core-contributor-sprint-retro-april-29th-may-13th/7262>\
**Category:** Core Contributors\
**Tags:** core-sprints, retrospective\
**Created:** [May 16, 2022, 10:30am UTC](https://discuss.openedx.org/t/core-contributor-sprint-retro-april-29th-may-13th/7262 "2022-05-16T10:30:19Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![antoviaque](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/antoviaque/32/32_2.png) [@antoviaque](https://discuss.openedx.org/u/antoviaque)\
**Post date:** [May 18, 2022, 6:25am UTC](https://discuss.openedx.org/t/core-contributor-sprint-retro-april-29th-may-13th/7262/4 "2022-05-18T06:25:30Z")

</div>

Some additional notes from the discussions at the contributors meetup:

## Missing permission

> [@](#):
>
> |- Although I am part of the BTR working group, and I am working on testing the nutmeg release, I cannot assign (myself) BTR issues. Nor can I close them. (@pdpinch)

Since the tickets permissions are linked to the repository permissions, @pdpinch will request these permissions (potentially with other release group members also needing this).

## Tutor deployment at scale & Kubernetes - Collaboration

> [@](#):
>
> There is an ongoing discussion on this, on the following thread: [Tech talk/demo: Deploying multiple Open edX instances onto a Kubernetes Cluster with Tutor](https://discuss.openedx.org/t/tech-talk-demo-deploying-multiple-open-edx-instances-onto-a-kubernetes-cluster-with-tutor/4641) – if we pull together around a common architecture & project to handle this, we can share the maintenance and help each other?

@Felipe will post notes from the meeting in the thread, and schedule the next meeting there to discuss it.

## Frontend

> [@](#):
>
> |The learning MFE has a LOT of conditional views that use SCSS variables and it’s hard to always know how to configure a course properly so those can be seen. It would be nice to have a demo course configuration, or a guide to getting everything enabled. (@xitij2000)

@arbrandes and @djoy will discuss and @arbrandes will get back to @xitij2000 about this.

Also I have mentioned that @xitij2000 and @abstract-technology will reach out to @arbrandes to figure out a better time for the frontend working group meeting, to be able to join it and discuss topics like this.

# Improvements & blockers

## Nutmeg - Need contributors for Tutor plugins!

> [@](#):
>
> |Still waiting on some plugins for nutmeg (ecommerce in particular). (@sambapete)
> 
> > |There are still many Tutor plugins that need a Maintainer (highlighted in bold below):COOKIECUTTER, **ANDROID** , DISCOVERY, ECOMMERCE, FORUM, **INDIGO 1** , MFE, **MINIO** , NOTES, **WEBUI** , **XQUEUE**. Plus a number of these also need to be upgraded to Nutmeg, see this post to learn more: [Open edX Contributors Meetup - #93 by jalondonot](https://discuss.openedx.org/t/open-edx-contributors-meetup/1450/93) (@Dean)  
> > Since we have moved to Tutor, ideally we would have more developers joining the Tutor Maintainers program and adopting a plugin if possible. (@Dean)

@Felipe will take one, and the topic will be brought up during the next working group meeting.

> [@](#):
>
> |There were changes to openedx/configuraiton that broke regular branch builds, I needed this to showcase some demos but hopefully this will be fixed soon. (@xitij2000)

@xitij2000 Has this been fixed? The repository being non-supported, this will likely happen more and more. Do we have plans to deprecate the branch builds?

---

_[View the full topic](https://discuss.openedx.org/t/core-contributor-sprint-retro-april-29th-may-13th/7262)._