There have been 252.50 reported hours during this sprint. Gathering this data is only one way to help monitor the success of the Core Contributors project.
Is anyone looking for UX/UI design assistance on any projects?
Ali Hugo
Retrospective - What went well these last two weeks / sprint?
User
Tutor is freaking amazing. Most of the OARS work so far involves integrating 3rd party systems and building initialization scripts, and I haven’t found anything I’ve needed to do that Tutor can’t handle. Even just the file templating and variable expansion is so simple, and so powerful, and it just. plain. works.
Thank you so much Regis!
Jill Vogel
Attended the Product Working Group meeting and got a better idea of the PR product review process.
Ali Hugo
What did you accomplish in the last two weeks (aka “current sprint”)? (Optional)
User
- Created a list of instructions for Farhaan on how to host the monthly AMEA meet-up - Attended the Product Working Group meet-up - Went through the list of PR’s ready for product review to see if there were any I could review
Ali Hugo
participated in the helm/large instances group reviewed oep-18 PR
Attended meeting of Build-Test-Release Working Group. Attended meeting of Core Contributor Working Group. Attended meeting of Developer Experience Working Group. Attended meeting of the Harmony project. Attended meeting of the Translations Working Group. Attended meeting of the Translations Working Group with Transifex and LexiQA. Reviewed a few translations for fr_CA. Parse through Discourse and Slack to see if I could help answer some issues. Read minutes of Working Groups I cannot attend in order to mostly be kept informed on what is going on in the community.
Pierre Mailhot
Complete work on event routing backend issue 235 of event routing backends. Create two new concepts in openedx xAPI profile on adlnet.gov.
Zia Fazal
- I debguued the issue of not including German strings in some MFEs which was due incorrect usage of code in Makefile, where ‘de’ was/is used instead of ‘de_De’ ref slack thread Slack - also relating to the above point I create an issue in BTR to backport some PRs to be included in olive.3 ref issue Backport for Olive.3 · Issue #253 · openedx/wg-build-test-release · GitHub - I spend some time in the forum answering questions or give an opinion - Attended WGs meeting.
@arbrandes I see a request for your review at the end of that PR - is that your review which is necessary, or are you asking for broader input?
@ali_hugo That sounds like a great idea! Do you have any specific ideas in mind? CC @Dean
It would be great imho if there were more interactions about it - it’s async, but it doesn’t have to be passive. More coordination of efforts and intentional planning would be awesome.
Bumping this ^
Summary of work done
Dev:
Complete work on event routing backend (Zia)
Create two new concepts in openedx xAPI profile on adlnet.gov (Zia)
Fix for German strings in some MFEs (Ghassan)
OARS - progress on openedx-oars#30 – integrating Superset with Clickhouse is nearly done (Jill)
Events:
Monthly AMEA meet-up prep (Ali, Farhaan)
Reviews:
Tried to find a product PR to review (Ali)
reviewed oep-18 PR (Felipe)
Reviewed PRs from new contributors to the upstreaming course (Xavier)
Translations:
Reviewed a few translations for fr_CA (Pierre)
Documentation:
Upstreaming course - remote sprint (Xavier)
Create issue for backports (Ghassan)
DevOps:
Formalize DevOps subgroup (Xavier)
TOC:
Meeting, election iteration (Xavier)
Plus:
Answering on forums & Slack (Pierre, Ghassan, Xavier)
Review the Sprint Retrospective user-flow and identify areas where the UX could be improved. I’d love to get feedback from other Core Contributors too, perhaps by asking them to complete a mini remote usability test
Add commenting, tagging, and notifications to checklists
Overhaul reports (and make @Dean’s life easier in the process!)
Make the Lists page more intuitive and user-friendly
I love this idea! Do you think the commenting / tagging / notifications item in my list above would do the trick, or do you have something else in mind?
@ali_hugo Ah, I see, you mean updates to Listaflow right? That sounds like good improvements, +1! You might need to make sure with @Fox_Piacenti that there will be enough development time available to implement them shortly after though, to not end up with too much design backlog at a time?
It could likely help yes!
When I suggested it, I had more in mind changes to how we present the information on the forum - ie the presentation, structure and formatting of the information in the current thread. I was also thinking about linking it to the changes being made to the reporting done as part of the contributor meetup - see Open edX Contributors Meetup - #124 . Ie non-dev/technical changes, more process and presentation improvements to our communication.
Oh, I see. This would be a much more practical place to start, especially considering the limited development time available.
I’m sure we can come up with a no-code way to improve our async planning, reporting etc. I’ll take a look at what’s being done on the reporting for the Contributor Meetup too. Let me brainstorm some options next week and see what I come up with.
Open edX Conference Topics: In-person Working Group meeting ideas
Product Review of OSPRs
New process to:
All PRs that require Product Review will have a Feature Ticket created on the Open edX Roadmap. All product review will happen on these Feature Tickets, here.
Tickets currently “ready for product review” can be picked up for review
Is there anything you would like to add here, @jmakowski ?
TOC
From @antoviaque: “For now, I can mention that we are working with @abstract-technology and @sampaccoud on an iteration to the election rules. There are also preparations for a town hall discussion between the TOC members and the rest of the community during the upcoming conference. The next TOC meetings should be at the conference and then a formal one in April.”
I agree with @sarina. There is a lot of interesting info here (thanks @jalondonot ), so it would be nice if the async updates were placed somewhere where they’re easy to access.
Speaking of suggestions, I’ve started a new topic to brainstorm ideas like this one for improving our Core Contributor processes. Please join in on the discussion if you have any bright ideas.
:
), so it would be nice if the async updates were placed somewhere where they’re easy to access.