<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div dir="auto">Click on the footer link in each email and follow instru<span>ctions. Hope this helps.<span></span></span></div>
<div dir="auto"><span><br>
</span></div>
<div dir="auto"><span>Best,</span></div>
<div dir="auto"><span><br>
</span></div>
<div dir="auto"><span>Ico</span></div>
<div dir="auto"><br>
</div>
<div><br>
</div>
<div id="ms-outlook-mobile-signature" dir="auto">
<div>Best,</div>
<div dir="auto"><br>
</div>
<div dir="auto">Ico</div>
<div dir="auto">-- </div>
<div dir="auto">Ivica Ico Bukvic, D.M.A.</div>
<div dir="auto">Director, Creativity + Innovation</div>
<div dir="auto">Director, Human-Centered Design iPhD</div>
<div dir="auto">Institute for Creativity, Arts, and Technology</div>
<div dir="auto"><br>
</div>
<div dir="auto">Virginia Tech</div>
<div dir="auto">Creative Technologies in Music</div>
<div dir="auto">School of Performing Arts – 0141</div>
<div dir="auto">Blacksburg, VA 24061</div>
<div dir="auto">(540) 231-6139</div>
<div dir="auto">ico@vt.edu</div>
<div dir="auto"><br>
</div>
<div dir="auto">ci.icat.vt.edu</div>
<div dir="auto">l2ork.icat.vt.edu</div>
ico.bukvic.net<br>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> L2Ork-dev <l2ork-dev-bounces@disis.music.vt.edu> on behalf of vedant bande <vedantbande2002@gmail.com><br>
<b>Sent:</b> Sunday, March 3, 2024 7:30:37 AM<br>
<b>To:</b> l2ork-dev@disis.music.vt.edu <l2ork-dev@disis.music.vt.edu><br>
<b>Subject:</b> Re: [L2Ork-dev] L2Ork-dev Digest, Vol 115, Issue 2</font>
<div> </div>
</div>
<div>
<div dir="auto">How to Unsubscribe this. </div>
<br>
<div class="x_gmail_quote">
<div dir="ltr" class="x_gmail_attr">On Sat, 2 Mar, 2024, 10:30 pm , <<a href="mailto:l2ork-dev-request@disis.music.vt.edu">l2ork-dev-request@disis.music.vt.edu</a>> wrote:<br>
</div>
<blockquote class="x_gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
Send L2Ork-dev mailing list submissions to<br>
<a href="mailto:l2ork-dev@disis.music.vt.edu" target="_blank" rel="noreferrer">
l2ork-dev@disis.music.vt.edu</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" originalsrc="https://disis.music.vt.edu/listinfo/l2ork-dev" shash="U4ROYZ0muphBnzQZMA4wbEgiUExBLbdwAonfFk3bz1/1j6aHRloes7loyhvkoV0eqZa3l9N61DFq7xrQYelJlS9kUVPDj67CvWXTVS9iiUFK4v8qZfjhQpPssranbPzt3BsStqcnrb1riWZaC6erkC76S8tXWFBCJqai0pwo2+E=" rel="noreferrer noreferrer" target="_blank">
https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:l2ork-dev-request@disis.music.vt.edu" target="_blank" rel="noreferrer">
l2ork-dev-request@disis.music.vt.edu</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:l2ork-dev-owner@disis.music.vt.edu" target="_blank" rel="noreferrer">
l2ork-dev-owner@disis.music.vt.edu</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of L2Ork-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Inquiry Regarding Participation in Project for Gsoc'24<br>
(Jonathan Wilkes)<br>
2. Re: Inquiry Regarding Participation in Project for Gsoc'24<br>
(Jonathan Wilkes)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 1 Mar 2024 22:22:00 -0500<br>
From: Jonathan Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank" rel="noreferrer">jon.w.wilkes@gmail.com</a>><br>
To: <a href="mailto:l2ork-dev@disis.music.vt.edu" target="_blank" rel="noreferrer">
l2ork-dev@disis.music.vt.edu</a><br>
Subject: Re: [L2Ork-dev] Inquiry Regarding Participation in Project<br>
for Gsoc'24<br>
Message-ID:<br>
<<a href="mailto:CAOA7yC4yhXziNZ0wUwZdUZt9C8tDVGb9AwfBPwGtZZkx65Ja9A@mail.gmail.com" target="_blank" rel="noreferrer">CAOA7yC4yhXziNZ0wUwZdUZt9C8tDVGb9AwfBPwGtZZkx65Ja9A@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
On Fri, Mar 1, 2024 at 9:09?AM Chinnari Narashimha<br>
<<a href="mailto:chinnarinarashimha@gmail.com" target="_blank" rel="noreferrer">chinnarinarashimha@gmail.com</a>> wrote:<br>
><br>
> Dear Purr Data,<br>
> Myself Chinnari Narashimha and currently pursuing my Btech in NIT Rourkela. I came across your organization and went through the project lists for 2024. After carefully looking at the list of projects available, I am particularly interested in contributing
to "Incrementally Improve the Autocomplete Feature". I believe that my skills in javascript, ui/ux, css and pd language (which i will be learning) will make me suited to contribute in these projects. I really liked the project Ideas and I have some ideas which
we can use in this project.<br>
><br>
> WEEK 1: Research and Planning<br>
> - understand the project details and requirements.<br>
> -gather additional more information,if needed<br>
> -will spend time using autocomplete feature in Purr Data<br>
> -collect feedback from user on issues, bugs<br>
> -will research more on auto-complete feature in other applications for inspiration(not copying)<br>
><br>
> WEEK 2: Design and Analysis<br>
> -document and prioritize bugs, usability and design flaws during research.<br>
> -will ensure proposed improvements align with Purr Data GUI design principles<br>
> - will review and refine again based on proposed feedback and considerations.<br>
><br>
> WEEK 3:Implementation and Core Functionality<br>
> -will set up the development environment and will install necessary tools and packages required for development.<br>
> -will begin implementing the core functionality of auto-complete feature<br>
><br>
> WEEK 4 and WEEK 5:Testing, Bug Fixing and Optimization<br>
> -will focus on getting the core functionality working<br>
> - will gather feedback from initial testing.<br>
> - will expand the functionality more based on needs and project requirements<br>
> -conduct extensive testing on bug,edge cases and usability issues.<br>
><br>
> WEEK 6: Documentation<br>
> -document the implementation details and changes made during the development.<br>
> -will communicate with the team for enhancements.<br>
><br>
> WEEK 7:Pre-FInal Review<br>
> -will do final testing to identify any remaining issues.<br>
> - can make small changes based on feedback from the team<br>
><br>
> WEEK 8: Final Review and Submission<br>
> -will review the project to ensure all requirements have been met.<br>
> - will double check documentation.<br>
><br>
> It's a rough timeline on how we can complete this project. But we can make changes if required.<br>
><br>
> Additionally, If you could guide me on how to join the open community or forums where community members discuss this project ideas.<br>
> Please let me know how I can get involved and if there are any specific steps I should take to further explore more on this project.<br>
> Thank You for your time and consideration and I look forward to the opportunity to contribute to this project.<br>
<br>
Hello Chinnari,<br>
<br>
Welcome!<br>
<br>
If you check out our Gitlab repository you will see some guidelines in<br>
the readme for how to contribute. A good place to start is by<br>
downloading the source and seeing if you can successfully build Purr<br>
Data on your OS.<br>
<br>
There are also some issues on the tracker marked as "good-first-bug"<br>
that you can look into trying to fix to get a sense of the development<br>
process.<br>
<br>
As for your proposed schedule-- I think it stretches the development<br>
process over too long a time span. "Incremental improvement" means<br>
just that-- you want a collection small, easy-to-grasp improvements<br>
that you can work out over a short amount of time. Then build on that<br>
with another set of improvements.<br>
<br>
It would be better to start the first week actually implementing a<br>
small change so you can get familiar with the cycle of development.<br>
Similarly, you can use each week to iterate on the feature and<br>
continue implementing improvements.<br>
<br>
Best,<br>
Jonathan<br>
<br>
> Yours Sincerely<br>
> Chinnari Narashimha<br>
> Github link: <a href="https://github.com/narashimha05" originalsrc="https://github.com/narashimha05" shash="BuyFaK1WGSgBEZSHA//HtST9cJeTrGrRSo0pHYzdU0sZoetADhzcN2AV78cuzX9VYu9pFuLQQXmFHF9B97B6jfLUz0G1ztxzc1Zy8KElarFQK0PfGnSxAg7JX10ZUsTrF2aaSG5zY2uAX50zTD94nmOfejyZPSPC1fpvuXwViiY=" rel="noreferrer noreferrer" target="_blank">
https://github.com/narashimha05</a><br>
> _______________________________________________<br>
> L2Ork-dev mailing list<br>
> <a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank" rel="noreferrer">
L2Ork-dev@disis.music.vt.edu</a><br>
> <a href="https://disis.music.vt.edu/listinfo/l2ork-dev" originalsrc="https://disis.music.vt.edu/listinfo/l2ork-dev" shash="qdRkTx4QGlE+LSrVnG5OJVQpODsnocoUd3RBiVMmWRMrR9X0rvO0RcAHLLP1NfcC8iJ7z73nUWRhxCZQ1prCRuwZ7pH24jEqBjH7yMd0FsMdIpndiyYIAWVRwLIhVnYcydE60ybMaF/Zt4TQyCk3Aoi/HIzdP2ncB9/wtP9SjzY=" rel="noreferrer noreferrer" target="_blank">
https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 1 Mar 2024 22:24:39 -0500<br>
From: Jonathan Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank" rel="noreferrer">jon.w.wilkes@gmail.com</a>><br>
To: <a href="mailto:l2ork-dev@disis.music.vt.edu" target="_blank" rel="noreferrer">
l2ork-dev@disis.music.vt.edu</a><br>
Subject: Re: [L2Ork-dev] Inquiry Regarding Participation in Project<br>
for Gsoc'24<br>
Message-ID:<br>
<<a href="mailto:CAOA7yC4TknNw90x2a8Zrdz_X_7hupTeS_OGZmw97FZ-RjGA_VQ@mail.gmail.com" target="_blank" rel="noreferrer">CAOA7yC4TknNw90x2a8Zrdz_X_7hupTeS_OGZmw97FZ-RjGA_VQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
> Similarly, you can use each week to iterate on the feature and<br>
> continue implementing improvements.<br>
<br>
Well, *continue implementing more improvements* is what I meant. So<br>
have a small improvement the first week, then build on that success<br>
with more improvements that get more ambitious/challenging each week.<br>
<br>
-Jonathan<br>
<br>
><br>
> Best,<br>
> Jonathan<br>
><br>
> > Yours Sincerely<br>
> > Chinnari Narashimha<br>
> > Github link: <a href="https://github.com/narashimha05" originalsrc="https://github.com/narashimha05" shash="R6xQOBM0bTvjYGyepadi8TVUZdRX4ZQckMICuvlQD05Qqu6zcZvRMFqta7cZHKo38CGLFdZcNMyunVEVlhF2NLESjqp8JkJ5NVIBlKNw15oNgA9gxTq8nhRShNfuHq/EczGuO1LQYJQDi4XqqU/Qu2yivSaX6EHnSDo1XEXQwA4=" rel="noreferrer noreferrer" target="_blank">
https://github.com/narashimha05</a><br>
> > _______________________________________________<br>
> > L2Ork-dev mailing list<br>
> > <a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank" rel="noreferrer">
L2Ork-dev@disis.music.vt.edu</a><br>
> > <a href="https://disis.music.vt.edu/listinfo/l2ork-dev" originalsrc="https://disis.music.vt.edu/listinfo/l2ork-dev" shash="BG1IZJc7RiyJWVOYjwb8M3lJUM23iZOulUH3/xVQnB0qgS8JczBgkggBLnFuIkrnjyJJWvvV/VQA2bZhglE552PS8CNH7Ed0kVQdc24712NZXdJ0TYQCx14gKuEk0m7d1+nrQAdS4vbWZWfA2tao0dzpoD+HEMtzqnWNe++cpg8=" rel="noreferrer noreferrer" target="_blank">
https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
L2Ork-dev mailing list<br>
<a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank" rel="noreferrer">L2Ork-dev@disis.music.vt.edu</a><br>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" originalsrc="https://disis.music.vt.edu/listinfo/l2ork-dev" shash="Eg3ogbeoGv8L3ox2vIBKJmaHhAabDKNvM5Vk6ALyh3b6l1K2QFbpo/zBHb8PKB1rEwozPZqjMQujXCH9IaphqtRK4LX7QMLmpZGjqRl912LMhm5te7kCKwuCPsCC43Ra5cUPwnYRUPEBcWVnQaerNLuKhyvblpYX73xjXXx1oOY=" rel="noreferrer noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
<br>
<br>
------------------------------<br>
<br>
End of L2Ork-dev Digest, Vol 115, Issue 2<br>
*****************************************<br>
</blockquote>
</div>
</div>
</body>
</html>