<html>
<head>
<meta http-equiv='Content-Type' content='text/html; charset=UTF-8'>
</head>
<body>
<style>
*{
margin: 0;
padding: 0;
}
font{
line-height: 1.6;
}
ul,ol{
padding-left: 20px;
list-style-position: inside;
}
</style>
<div style = 'font-family:"微软雅黑"; line-height:1.6;'>
<div>
<div><span>Dear Mr. </span><span style="line-height: 22.4px;">Bansod</span><span style="line-height: 1.6;">,</span></div><div><span><br></span></div><div><span>I have shared my proposal on GSoC website.</span></div><div><span>I also commit a demo to js-dev branch of my forked repository, which is also explained in my proposal.</span></div><div><span><br></span></div><div><span>Looking forward to your comments and guidance.</span></div><div><span><br></span></div><div><span>Regards,</span></div><div><span>Xinyu Liu</span></div>
<div><br></div>
<div id="ntes-pcmail-signature" style="font-family:'微软雅黑'">
<style type="text/css">
a#ntes-pcmail-signature-default:hover {
text-decoration: underline;
color: #199cff;
cursor: pointer;
}
a#ntes-pcmail-signature-default:active {
text-decoration: underline;
color: #246fce;
cursor: pointer;
}
</style>
</div></div><div class="J-reply" style="background-color:#f2f2f2;color:black;padding-top:6px;padding-bottom:6px;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;margin-top:45px;margin-bottom:20px;font-family:'微软雅黑';">
<div style="font-size:12px;line-height:1.5;word-break:break-all;margin-left:10px;margin-right:10px">On <span class="mail-date">2/27/2018 16:35</span>，<a class="mail-to" style="text-decoration:none;color:#2a83f2;" href="mailto:devenbansod.bits@gmail.com">Deven Bansod<devenbansod.bits@gmail.com></a> wrote： </div>
</div>
<blockquote id="ntes-pcmail-quote" style="margin: 0; padding: 0; font-size: 14px; font-family: '微软雅黑';">
Hi Xinyu,<br><br>On Sat, Feb 24, 2018 at 7:54 PM, meteorlxy <meteorlxy.cn@gmail.com> wrote:<br> <blockquote class="mmbqc1">Dear PMA Team,<br><br> My name is Xinyu Liu, a graduate student from Xi'an Jiao Tong<br> University(XJTU), China. I've been using phpmyadmin for a long time, and I<br> really want to catch the opportunity to be a contributor of phpmyadmin.<br><br></blockquote><br>Thanks for your interest in contributing to the project.<br><br> <blockquote class="mmbqc1">As for my skills, I'm familiar with Laravel (not CakePHP yet) and webpack.<br> (I have some small repos on my github [https://github.com/meteorlxy])<br><br></blockquote><br>That's great. CakePHP is not generally used inside phpMyAdmin per se,<br>but we do use it in our Error Reporting server. It'd be good to have<br>its knowledge if you are applying for a project related to Error<br>Reporting server.<br><br> <blockquote class="mmbqc1">I'm insterested in the topic 'Introduce modern JS features and tools to<br> phpMyAdmin codebase' in the idea list. I think modularization of js code is<br> necessary, but that needs lots of code refactor and may cause many issues.<br> As pma providing release version, we have to use something like webpack to<br> convert the modular source code to production files.<br><br> I'm not so clear about where should I begin, as it may need entirely code<br> refactor to the js codebase. Your guidance will help a lot.<br><br></blockquote><br>Thanks for your interest in the idea.<br><br>You are absolutely right in saying that this would involve a lot of<br>refactoring. You can look at various parts of our present JS code and<br>evaluate what features and modularization principles (and how best)<br>can be applied to the codebase, how can webpack be introduced to our<br>codebase.<br><br>For your proposal, you may want to come up with a plan/schedule on how<br>would you go around with handling different parts of the codebase.<br>Also, evaluating how can you let the untouched parts continue to work<br>as it is. This would be extremely important if you think, that it may<br>not be possible to cover the complete codebase in twelve coding weeks.<br><br>As mentioned on the ideas list, we would be targeting our development<br>efforts towards 5.0. This would be a major feature release and the<br>development would go around in the master branch, while the bug fix<br>versions for 4.8.x would be taken care of from a different branch. So,<br>this should not be a *big* problem. But your proposal plan should<br>involve the process for handling part-upgrades of the codebase, since<br>we would not want to leave the codebase in a broken state for too<br>long.<br><br>Hope that cleared some of your doubts. Feel free to write back to the<br>mailing list with any specific questions.<br><br>Regards,<br>Deven Bansod<br><br>_______________________________________________<br>Developers mailing list<br>Developers@phpmyadmin.net<br>https://lists.phpmyadmin.net/mailman/listinfo/developers<br></blockquote><!--😀-->
</div>
</body>
</html>