Re: [Wikitech-l] [Engineering] Code Health Newsletter - Issue 2 Volume 1
I boldly wikified it. https://www.mediawiki.org/wiki/Code_Health/newsletters/Issue02Volume01 On Mon, Dec 17, 2018 at 4:18 PM Gergo Tisza wrote: > Will this also be published on-wiki? Reading it in plain text is kind of > painful. > > On Mon, Dec 17, 2018 at 8:26 AM Jean-Rene Branaa > wrote: > >> Code Health Newsletter - Issue 2 Volume 1 >> >> >> The Code Health[0a] newsletter is a publication provided by the Code >> Health Group[0b]. The Code Health Group serves as the hub for all >> Code Health topics and activities within the movement. If you are >> aware or engaged in Code Health activities, we'd love to hear about >> it. >> >> The Code Health Newsletter is a new and hopefully valuable activity. >> If you have feedback about this issue or any past issues[0c], please >> don’t hesitate to share. You can also submit content that you’d like >> to share through Phabricator (use the Code-Health-Newsletter project). >> >> # Code Health First Responders >> >> After last issue there was some concern voiced about calling this >> "First Responders" as the term is already used within the community. >> As a result, we've tweaked the name a bit to call it "Code Health >> First Responders". >> >> Please remember to share your experiences tackling your Code Health >> challenges. Become or nominate a First Responder by submitting a task >> in Phabricator in the Code-Health-First-Responder project. >> >> More information available here[1]. >> >> >> # Code Stewardship >> >> ## Quarterly Reviews >> >> This quarter's Code Stewardship review cycle is open and ending on >> January 16th. At the moment we've got three items being reviewed: >> CodeReview extension, UserMerge extension, and Graphoid service. >> >> Join the discussion in Phabricator[2a] or on Wiki[2b]. >> >> ## Latest Code Stewardship Coverage >> >> >> Core Components: 63% >> >> Extensions: 74% >> >> Services: 65% >> >> >> Note: these numbers are based on the Developers/Maintainers[2c] page. >> >> >> ## What it means to be a Code Steward >> >> >> Over the course of the last several months, the Foundation has been >> working to close the gap on the number of un/under-funded Components, >> Extensions, and Services deployed to the production environment. Many >> have already stepped up to become Code Stewards, but outside of some >> aspirational goals about bug resolution rates, and code review >> responsiveness, there hasn't been much guidance. Over the course of >> the next few weeks, we will be attempting to bring more clarity to >> that. >> >> >> >> # Code Health by the Numbers >> >> >> The following are some stats regarding Code Health. As we are early >> in defining/implementing our Code Health metrics, data is limited. >> >> See the Code Health Metrics project[3a] for more information. >> >> In future issues of the newsletter, we'll expand this section to >> include other metrics as well as trending information. >> >> >> ## Code Coverage >> >> >> 0-50% 51-90% 90-100% >> >> ___ >> >> Extensions 67 16 4 >> >> Code Components 511 18 >> >> Services Not Available Yet >> >> >> Note: As of 11/30/18[3b]. >> >> >> ### Did you know? >> >> >> Coverme[3c], a tool written by legoktm, is a great tool to help >> prioritize areas for additional test coverage. It helps by >> identifying the code that is most often executed in production and its >> current coverage level. Please note that currently these tools support >> PHP code bases. We are currently investigating what it would take to >> expand into other languages. >> >> Historical coverage charts can been seen here[3d]. These charts can >> be used to gauge the overall trend of test coverage for the 12 months. >> This is an important tool to use for measuring incremental progress >> over time. >> >> >> # Code Health Learning Circles >> >> If you have a topic that you'd like to share, but want a little help >> with organizing, please submit a Phabricator ticket to the >> Code-Health-Learning-Circles project. >> >> Are there some topics that you’d like to see some Learning Circles >> about? Submit a Phabricator ticket to the >> Code-Health-Learning-Circles project and we’ll do what we can to make >> it happen. >> >> More information about Code Health Learning Circles available here[4]. >> >> >> # Help Wanted >> >> ## Memory Profiling/Leak Troubleshooting >> >> Do you have experience/expertise in memory profiling? We’re trying to >> chase down some memory leaks using Chromium’s profiling tools, but >> we’re running into challenges. Join the conversation in phabricator[5] >> and/or in the wikimedia-codehealth irc channel. >> >> # Code Health Group Activities >> >> >> Although the Code Health Group looks to act as a hub for all code >> health topics, the group also sponsors various broader reaching >> initiatives. >> >> ##
Re: [Wikitech-l] [Engineering] Code Health Newsletter - Issue 2 Volume 1
Will this also be published on-wiki? Reading it in plain text is kind of painful. On Mon, Dec 17, 2018 at 8:26 AM Jean-Rene Branaa wrote: > Code Health Newsletter - Issue 2 Volume 1 > > > The Code Health[0a] newsletter is a publication provided by the Code > Health Group[0b]. The Code Health Group serves as the hub for all > Code Health topics and activities within the movement. If you are > aware or engaged in Code Health activities, we'd love to hear about > it. > > The Code Health Newsletter is a new and hopefully valuable activity. > If you have feedback about this issue or any past issues[0c], please > don’t hesitate to share. You can also submit content that you’d like > to share through Phabricator (use the Code-Health-Newsletter project). > > # Code Health First Responders > > After last issue there was some concern voiced about calling this > "First Responders" as the term is already used within the community. > As a result, we've tweaked the name a bit to call it "Code Health > First Responders". > > Please remember to share your experiences tackling your Code Health > challenges. Become or nominate a First Responder by submitting a task > in Phabricator in the Code-Health-First-Responder project. > > More information available here[1]. > > > # Code Stewardship > > ## Quarterly Reviews > > This quarter's Code Stewardship review cycle is open and ending on > January 16th. At the moment we've got three items being reviewed: > CodeReview extension, UserMerge extension, and Graphoid service. > > Join the discussion in Phabricator[2a] or on Wiki[2b]. > > ## Latest Code Stewardship Coverage > > > Core Components: 63% > > Extensions: 74% > > Services: 65% > > > Note: these numbers are based on the Developers/Maintainers[2c] page. > > > ## What it means to be a Code Steward > > > Over the course of the last several months, the Foundation has been > working to close the gap on the number of un/under-funded Components, > Extensions, and Services deployed to the production environment. Many > have already stepped up to become Code Stewards, but outside of some > aspirational goals about bug resolution rates, and code review > responsiveness, there hasn't been much guidance. Over the course of > the next few weeks, we will be attempting to bring more clarity to > that. > > > > # Code Health by the Numbers > > > The following are some stats regarding Code Health. As we are early > in defining/implementing our Code Health metrics, data is limited. > > See the Code Health Metrics project[3a] for more information. > > In future issues of the newsletter, we'll expand this section to > include other metrics as well as trending information. > > > ## Code Coverage > > > 0-50% 51-90% 90-100% > > ___ > > Extensions 67 16 4 > > Code Components 511 18 > > Services Not Available Yet > > > Note: As of 11/30/18[3b]. > > > ### Did you know? > > > Coverme[3c], a tool written by legoktm, is a great tool to help > prioritize areas for additional test coverage. It helps by > identifying the code that is most often executed in production and its > current coverage level. Please note that currently these tools support > PHP code bases. We are currently investigating what it would take to > expand into other languages. > > Historical coverage charts can been seen here[3d]. These charts can > be used to gauge the overall trend of test coverage for the 12 months. > This is an important tool to use for measuring incremental progress > over time. > > > # Code Health Learning Circles > > If you have a topic that you'd like to share, but want a little help > with organizing, please submit a Phabricator ticket to the > Code-Health-Learning-Circles project. > > Are there some topics that you’d like to see some Learning Circles > about? Submit a Phabricator ticket to the > Code-Health-Learning-Circles project and we’ll do what we can to make > it happen. > > More information about Code Health Learning Circles available here[4]. > > > # Help Wanted > > ## Memory Profiling/Leak Troubleshooting > > Do you have experience/expertise in memory profiling? We’re trying to > chase down some memory leaks using Chromium’s profiling tools, but > we’re running into challenges. Join the conversation in phabricator[5] > and/or in the wikimedia-codehealth irc channel. > > # Code Health Group Activities > > > Although the Code Health Group looks to act as a hub for all code > health topics, the group also sponsors various broader reaching > initiatives. > > ## Recent Activities > > ### Code Health Metrics > > The Code Health Metrics Working Group has been busy over the last > couple of months. The groups primary focus has been to evaluate some > of the code metrics frameworks. These tools provide us with code > analysis, reporting, and a framework to
Re: [Wikitech-l] Old tiles.wfmlabs.org maps services need maintainers to keep them alive after december 18th
Fair enough about the security issues. I wouldn't trust me either if I knew nothing about me, lol. That said, if there are some less critical things that you can get me access to that are also important to wikimedia let me know, so that I can still contribute in some technically significant way. alexan...@vassilevski.com ‐‐‐ Original Message ‐‐‐ On Monday, 17 December 2018 12:16, Derk-Jan Hartman wrote: > Hi Alexander, > > I haven't forgotten about your request... > Please don't take this the wrong way, but lately there has been quite a LOT > of malicious activity at several Wikimedia systems and your account is brand > new.. > I can't find any history of your activity with the projects or any other > projects in any public form... Especially in light of the recent event-stream > compromise for instance > (https://medium.com/intrinsic/compromised-npm-package-event-stream-d47d08605502), > I think it is wise of us to be extra careful and take some more time to make > sure your enthusiasm is exactly what it is pure enthousiasme to become part > of this. But at this time that makes me uncomfortable to give you access to > this set of servers as one of them is actually rather critical and could > allow a person to do a lot of potential harm to Wikimedians. > It is sad that we have to consider these kinds of things nowadays. I'm > considering how we should approach this and how I can gain enough confidence > to help you along. > > DJ > > On Fri, Dec 14, 2018 at 7:50 PM Alexander Vassilevski > wrote: > > > OK. Thanks for letting me know that. It looks like I've been declined but > > at least I'm getting some idea on how things work around here... > > > > alexan...@vassilevski.com > > > > ‐‐‐ Original Message ‐‐‐ > > On Friday, 14 December 2018 10:35, Brian Wolff wrote: > > > > > That is the process for getting shell access on production [e.g. servees > > > directly running Wikipedia]. Which is rather different (and much harder) > > > than getting access to an abandoned tool. > > > > > > -- > > > brian > > > > > > On Friday, December 14, 2018, Alexander Vassilevski > > > wrote: > > >> I created a task in phab to be added to NDA ldap, so I can sign the NDA > > >> and get shell access: > > >> https://phabricator.wikimedia.org/T211996 > > >> One of the subtasks (from > > >> https://wikitech.wikimedia.org/wiki/Volunteer_NDA#Privileged_LDAP_or_shell_access > > >> ) on this is to get > > >> > > >> [ ] At least one comment of support from a Wikimedia Foundation > > >> employee, explaining why it is a good idea to accept your request > > >> [ ] A comment of approval from one Wikimedia Foundation manager (usually > > >> the manager of an employee supporting you). > > >> [ ] (Have someone with access double-check which mediawiki.org account > > >> that the manager's Phabricator account is linked to, where the SUL > > >> account was created, and how it was created on that wiki.) > > >> > > >> Can someone do this? If you need to see some qualifications I can try to > > >> get some code of mine to you from some old puppet stuff I've done and I > > >> can show you my github, where you can see some of my code. > > >> If I'm making a rookie mistake here and this type of access is not > > >> needed, let me know. I'm also sasheto +i on IRC #wikimedia-tech, so you > > >> can message me there too, I check it from time to time. > > >> alexan...@vassilevski.com > > >> > > >> ‐‐‐ Original Message ‐‐‐ > > >> On Thursday, 13 December 2018 12:33, Alex Monk wrote: > > >> > > >>> You'll basically need to create a wikitech account (if you don't > > >>> already have one) and convince one of the existing project admins > > >>> (listed at https://tools.wmflabs.org/openstack-browser/project/maps) to > > >>> add you. > > >>> Please use Puppet instead of manually setting up servers by hand. > > >>> > > >>> On Thu, 13 Dec 2018 at 20:21, Alexander Vassilevski > > >>> wrote: > > >>> > > I have some free time this December and I could manually create the > > new vm's and replicate the configs/installs by hand on newly created > > Ubuntu 18 vm's ( after figuring out how the old ones are installed and > > configured and if given access, of course .. ). > > > > Keep in mind that I'm new to wikimedia and don't know much about the > > infrastructure or procedures, so what do I need to do to be given > > access and volunteer to do this? > > > > alexan...@vassilevski.com > > > > ‐‐‐ Original Message ‐‐‐ > > On Thursday, 13 December 2018 12:09, Johan Jönsson > > wrote: > > > > > On Thu, Dec 13, 2018 at 9:36 AM Johan Jönsson jjons...@wikimedia.org > > > wrote: > > > > > > > On Thu, Dec 13, 2018 at 9:24 AM Derk-Jan Hartman < > > > >
Re: [Wikitech-l] Old tiles.wfmlabs.org maps services need maintainers to keep them alive after december 18th
Hi Alexander, I haven't forgotten about your request... Please don't take this the wrong way, but lately there has been quite a LOT of malicious activity at several Wikimedia systems and your account is brand new.. I can't find any history of your activity with the projects or any other projects in any public form... Especially in light of the recent event-stream compromise for instance ( https://medium.com/intrinsic/compromised-npm-package-event-stream-d47d08605502), I think it is wise of us to be extra careful and take some more time to make sure your enthusiasm is exactly what it is pure enthousiasme to become part of this. But at this time that makes me uncomfortable to give you access to this set of servers as one of them is actually rather critical and could allow a person to do a lot of potential harm to Wikimedians. It is sad that we have to consider these kinds of things nowadays. I'm considering how we should approach this and how I can gain enough confidence to help you along. DJ On Fri, Dec 14, 2018 at 7:50 PM Alexander Vassilevski < alexan...@vassilevski.com> wrote: > OK. Thanks for letting me know that. It looks like I've been declined but > at least I'm getting some idea on how things work around here... > > alexan...@vassilevski.com > > ‐‐‐ Original Message ‐‐‐ > On Friday, 14 December 2018 10:35, Brian Wolff wrote: > > > That is the process for getting shell access on production [e.g. servees > directly running Wikipedia]. Which is rather different (and much harder) > than getting access to an abandoned tool. > > > > -- > > brian > > > > On Friday, December 14, 2018, Alexander Vassilevski < > alexan...@vassilevski.com> wrote: > >> I created a task in phab to be added to NDA ldap, so I can sign the NDA > and get shell access: > >> https://phabricator.wikimedia.org/T211996 > >> One of the subtasks (from > https://wikitech.wikimedia.org/wiki/Volunteer_NDA#Privileged_LDAP_or_shell_access > ) on this is to get > >> > >> [ ] At least one comment of support from a Wikimedia Foundation > employee, explaining why it is a good idea to accept your request > >> [ ] A comment of approval from one Wikimedia Foundation manager > (usually the manager of an employee supporting you). > >> [ ] (Have someone with access double-check which mediawiki.org account > that the manager's Phabricator account is linked to, where the SUL account > was created, and how it was created on that wiki.) > >> > >> Can someone do this? If you need to see some qualifications I can try > to get some code of mine to you from some old puppet stuff I've done and I > can show you my github, where you can see some of my code. > >> If I'm making a rookie mistake here and this type of access is not > needed, let me know. I'm also sasheto +i on IRC #wikimedia-tech, so you can > message me there too, I check it from time to time. > >> alexan...@vassilevski.com > >> > >> ‐‐‐ Original Message ‐‐‐ > >> On Thursday, 13 December 2018 12:33, Alex Monk > wrote: > >> > >>> You'll basically need to create a wikitech account (if you don't > already have one) and convince one of the existing project admins (listed > at https://tools.wmflabs.org/openstack-browser/project/maps) to add you. > >>> Please use Puppet instead of manually setting up servers by hand. > >>> > >>> On Thu, 13 Dec 2018 at 20:21, Alexander Vassilevski < > alexan...@vassilevski.com> wrote: > >>> > I have some free time this December and I could manually create the > new vm's and replicate the configs/installs by hand on newly created Ubuntu > 18 vm's ( after figuring out how the old ones are installed and configured > and if given access, of course .. ). > > Keep in mind that I'm new to wikimedia and don't know much about the > infrastructure or procedures, so what do I need to do to be given access > and volunteer to do this? > > alexan...@vassilevski.com > > ‐‐‐ Original Message ‐‐‐ > On Thursday, 13 December 2018 12:09, Johan Jönsson < > jjons...@wikimedia.org> wrote: > > > On Thu, Dec 13, 2018 at 9:36 AM Johan Jönsson jjons...@wikimedia.org > > wrote: > > > > > On Thu, Dec 13, 2018 at 9:24 AM Derk-Jan Hartman < > > > [[d.j.hartman+wmf...@gmail.com](mailto: > d.j.hartman%2bwmf...@gmail.com)](mailto:[d.j.hartman%2bwmf...@gmail.com > ](mailto:d.j.hartman%252bwmf...@gmail.com))> wrote: > > > > > > > Yeah might be wise to at least reach out to en.wp and de.wp. Or > maybe Tech > > > > News even ? > > > > > > "Hey folks, this might not work in the future" could be reason > enough to > > > include it in Tech News, yes. > > > > Included inhttps://meta.wikimedia.org/wiki/Tech/News/2018/51 which > is > > going out to the wikis on Monday. > > > > //Johan Jönsson > > > > > --- > > > > Wikitech-l mailing list > >
[Wikitech-l] Code Health Newsletter - Issue 2 Volume 1
Code Health Newsletter - Issue 2 Volume 1 The Code Health[0a] newsletter is a publication provided by the Code Health Group[0b]. The Code Health Group serves as the hub for all Code Health topics and activities within the movement. If you are aware or engaged in Code Health activities, we'd love to hear about it. The Code Health Newsletter is a new and hopefully valuable activity. If you have feedback about this issue or any past issues[0c], please don’t hesitate to share. You can also submit content that you’d like to share through Phabricator (use the Code-Health-Newsletter project). # Code Health First Responders After last issue there was some concern voiced about calling this "First Responders" as the term is already used within the community. As a result, we've tweaked the name a bit to call it "Code Health First Responders". Please remember to share your experiences tackling your Code Health challenges. Become or nominate a First Responder by submitting a task in Phabricator in the Code-Health-First-Responder project. More information available here[1]. # Code Stewardship ## Quarterly Reviews This quarter's Code Stewardship review cycle is open and ending on January 16th. At the moment we've got three items being reviewed: CodeReview extension, UserMerge extension, and Graphoid service. Join the discussion in Phabricator[2a] or on Wiki[2b]. ## Latest Code Stewardship Coverage Core Components: 63% Extensions: 74% Services: 65% Note: these numbers are based on the Developers/Maintainers[2c] page. ## What it means to be a Code Steward Over the course of the last several months, the Foundation has been working to close the gap on the number of un/under-funded Components, Extensions, and Services deployed to the production environment. Many have already stepped up to become Code Stewards, but outside of some aspirational goals about bug resolution rates, and code review responsiveness, there hasn't been much guidance. Over the course of the next few weeks, we will be attempting to bring more clarity to that. # Code Health by the Numbers The following are some stats regarding Code Health. As we are early in defining/implementing our Code Health metrics, data is limited. See the Code Health Metrics project[3a] for more information. In future issues of the newsletter, we'll expand this section to include other metrics as well as trending information. ## Code Coverage 0-50% 51-90% 90-100% ___ Extensions 67 16 4 Code Components 511 18 Services Not Available Yet Note: As of 11/30/18[3b]. ### Did you know? Coverme[3c], a tool written by legoktm, is a great tool to help prioritize areas for additional test coverage. It helps by identifying the code that is most often executed in production and its current coverage level. Please note that currently these tools support PHP code bases. We are currently investigating what it would take to expand into other languages. Historical coverage charts can been seen here[3d]. These charts can be used to gauge the overall trend of test coverage for the 12 months. This is an important tool to use for measuring incremental progress over time. # Code Health Learning Circles If you have a topic that you'd like to share, but want a little help with organizing, please submit a Phabricator ticket to the Code-Health-Learning-Circles project. Are there some topics that you’d like to see some Learning Circles about? Submit a Phabricator ticket to the Code-Health-Learning-Circles project and we’ll do what we can to make it happen. More information about Code Health Learning Circles available here[4]. # Help Wanted ## Memory Profiling/Leak Troubleshooting Do you have experience/expertise in memory profiling? We’re trying to chase down some memory leaks using Chromium’s profiling tools, but we’re running into challenges. Join the conversation in phabricator[5] and/or in the wikimedia-codehealth irc channel. # Code Health Group Activities Although the Code Health Group looks to act as a hub for all code health topics, the group also sponsors various broader reaching initiatives. ## Recent Activities ### Code Health Metrics The Code Health Metrics Working Group has been busy over the last couple of months. The groups primary focus has been to evaluate some of the code metrics frameworks. These tools provide us with code analysis, reporting, and a framework to plug in the results of other analysis tools. The two that are available for evaluation are: SonarQube [6a] PHPMetrics [6b] ## Upcoming Activities: ### Code Reviews Code reviews are a critical part of our development process. They are key to ensuring code changes are of the highest quality possible. That being said, getting timely code reviews can prove to be challenging
Re: [Wikitech-l] Deprecation of tag_summary table
Hey, Another update. Starting from deployment of wmf.9 tag_summary won't get updated and will be dropped soon. Please make sure your tool doesn't use table any more otherwise you might end up having out-dated data or errors. Best On Thu, 29 Nov 2018 at 15:45, Amir Sarabadani wrote: > Hello, > tag_summary table was introduced in 2009 as a roll up table for > change_tag. One of the reasons it was being used was that MySQL databases > that were using earlier versions of 4.1 (Released at 15 February 2005) > could not use GROUP_CONCAT feature. > > Around five years ago, developers started to replace usages of tag_summary > with change_tag primarily because GROUP_CONCAT became available then and it > most cases it was faster. For example [1] but it wasn't done fully which > led us to having discrepancies. For example, Special:RecentChanges uses > change_tag table but its API counterpart uses tag_summary table. > Maintaining two extremely large tables is a technical debt that have been > biting us since its deployment. Also, with normalization of change_tag > table in place [2], it's more performant than tag_summary. > > So we are replacing usages of this table with change_tag and in the next > couple of weeks, and then we will drop the whole table. If you're using it > in cloud replicas, please change it to change_tag. If you have any concerns > or notes, feel free to chime in at > https://phabricator.wikimedia.org/T209525 (Also, review of the patches > would be extremely appreciated) > > Thank you and sorry for any inconvenience. > > [1]: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/95584 > [2]: https://phabricator.wikimedia.org/T185355 > > Best > -- > Amir Sarabadani > Software Engineer > > Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin > Tel. (030) 219 158 26-0 > http://wikimedia.de > > Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen > Wissens frei teilhaben kann. Helfen Sie uns dabei! > http://spenden.wikimedia.de/ > > Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V. > Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter > der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für > Körperschaften I Berlin, Steuernummer 27/029/42207. > -- Amir Sarabadani Software Engineer Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Tel. (030) 219 158 26-0 http://wikimedia.de Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen Wissens frei teilhaben kann. Helfen Sie uns dabei! http://spenden.wikimedia.de/ Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Code Stewardship Reviews candidates open for comment
Many many thanks! On Mon, Dec 17, 2018 at 7:21 AM Jean-Rene Branaa wrote: > > Hello Alexandros, > > Makes sense. We'll extend the current review cycle until January 16th, > 2019 in order to allow more time due to the coming holidays. > > Cheers, > > JR > > > > On Sun, Dec 16, 2018 at 00:30 Alexandros Kosiaris > wrote: > > > Hi, > > > > Any chance the Dec 28th deadline be altered? It's end of the quarter and > > with the goal wrapping and PTOs, holidays etc I find it a bit difficult to > > collect all the necessary data to help make an informed decision. > > > > Στις Πέμ, 13 Δεκ 2018, 21:00 ο χρήστης Jean-Rene Branaa < > > jbra...@wikimedia.org> έγραψε: > > > > > Hello All, > > > > > > We've opened the feedback cycle for the current Code Stewardship > > > Review candidates. They include: > > > > > > CodeReview extension[0] > > > UserMerge extension[1] > > > Graphoid service[2] > > > > > > Feedback can be provided via the talk pages for each of the items > > > under review and/or their associated Phabricator tasks. > > > > > > The Code Stewardship review process[3] is intended to help address > > > code deployed to production that is un/under funded. The outcome of > > > this process is generally one of three: re-investment, no change, or > > > sunset (ramp down all investment and remove from production > > > environment). > > > > > > Please provide your feedback before December 28th. > > > > > > Cheers, > > > > > > JR > > > IRC: jrbranaa > > > Release Engineering/Code Health > > > > > > > > > [0] > > > > > https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitation/CodeReview > > > [1] > > > > > https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitation/UserMerge > > > [2] > > > > > https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitation/Graphoid > > > [3]https://www.mediawiki.org/wiki/Code_stewardship_reviews > > > > > > ___ > > > Wikitech-l mailing list > > > Wikitech-l@lists.wikimedia.org > > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > ___ > > Wikitech-l mailing list > > Wikitech-l@lists.wikimedia.org > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > ___ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Alexandros Kosiaris ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
