Mon, Aug 19
Tue, Aug 6
Mon, Aug 5
Wed, Jul 31
Mon, Jul 29
Jul 19 2019
Jul 16 2019
Jul 11 2019
Jul 9 2019
@WDoranWMF, I do think this is a Code Health topic. I've added the Code-Health project tag to it so that it shows up on the Code Health Group's radar.
@WDoranWMF, I'll take ownership of this task for the time being.
Jun 28 2019
Jun 25 2019
Jun 18 2019
Jun 11 2019
I'll be moving this task to Done on the CS work board as RelEng is taking on CS responsabilities as it's being sunsetted.
Jun 6 2019
Do we have a sense of what is causing these rechecks? @zeljkofilipin, have any insight into this. I know we've discussed it a little in the past.
I am in favor of leaving them as voting, especially if the primary driver to changing that is their flaky nature. Although I do understand the issue at hand, I'd like to work to find a different solution to the problem of flaky tests. Monitoring and acting upon flaky tests hasn't been a priority in the past, but we are moving to bring more focus to that in the near future.
Jun 4 2019
Spoke with @Catrope and @MMiller_WMF re the ownership of this extension. We determined that this extension is outside the scope of the Growth team and would be better suited somewhere else. As such, this extension has returned to orphan status.
Hello @marcella, this extension came up as a Code Stewardship review request, but I've noticed that it is marked as being stewarded by the Editing team on developers/maintainers page. Just checking to see what the actual Code Stewardship status is before I dig any deeper.
Jun 3 2019
May 24 2019
May 23 2019
May 19 2019
Apr 16 2019
Mar 29 2019
I think this is good starting point for some knowledge building around this. I think some questions around how to improve the Code Review process might make sense. For example:
Mar 18 2019
Tech debt identification and management is being done as part of the PEP refactoring work.
Mar 12 2019
When done, the extension review instructions should probably be updated.
Feb 27 2019
Another thought to capture... This process should probably result in a workflow that is as automated as possible. For example - initiated by the creation of a phab task that then auto creates other tasks from template with appropriate folks subscribed/assigned. In the end, minimizing the room for error in a manual set of steps on a wiki.
Feb 26 2019
Although the goal is to have all code that deploys to production go through this process, it may be necessary to have two branches in this process. One that is for "permanent" deployment to production, and one that is "conditional". For example, team needs to get new capabilities into the production environment in order to obtain timely user feedback, but the code is not fully compliant to Code Health, security, performance, etc... criteria. They may have a time-based condition to address the gaps or be removed from production.
Feb 20 2019
@EvanProdromou, that sounds like a good thing to pursue. Definitely something worth investigating. Let me poke Tyler/Dan to see the feasibility for using K8s for that today. I know that there's some work in this space that could be leveraged.
@Aklapper, this was basically a request for assistance with Chromium profiling. If you know any particular person and/or team that might have expertise with this, please let me know. That being said, I'm not sure if Piotr still needs help with this.
@pmiazga, is this something that you still need help with? If not, are there any learnings/findings about this topic that you're able to share?