Hi Carl and fellow developers!I'm excited to work with all of you on Lilypond and hope that we can complete the project!
I'll be quite busy with the end of my university semester and may have reduced communication until May 15th. But I'll be able to focus more on GSoC Bonding Period between the 16th and the start of the project.
On 2023-05-04 14:41, Carl Sorensen - carl.d.sorensen(a)gmail.com wrote:
As for now, I have already set up a Lilypond development environment. It's the LilyDev docker image (I actually use podman instead of docker). I was able to compile Lilypond on it, make a fix, then build that fix. I haven't tried running built executables within that image yet, but I believe this is my preferred way of having a Lilypond Development environment on my Linux desktop. Using it is quite clunky though--I have to constantly change permissions/UID/GID on the file data of the source files on my local file system so that the image can actually read those files and not report Permission Denied. I'll see if I have some time tweaking the LilyDev image and possibly making pull requests to the GitHub repository hosting LilyDev.Dear Jason,As you know by now, you've been selected to complete a GSOC project on improving LilyPond beaming. Congratulations! Your proposal was of very high quality, and we are anxious to have you starting to work with us.The next three weeks constitute the Community Bonding period. I hope you'll be able to get your development environment set up and explore the merge request submission process.
I have made one pull request to Lilypond merged by Jean. Jean taught me a lot about the pull request process, so I have some basic knowledge of how Lilypond developers like to handle them. But I'd probably need to get more familiar with it when it comes to committing a lot of changes across high-activity branches.
I'm excited to have the opportunity to serve as your primary mentor. How would you like to communicate? How often would you like to report to me? How much feedback do you want?
My proposal does answer some of those questions. I did say possible video conferences on a weekly basis, lilypond-devel mailing list. Video conferences can be done on Jitsi Meet so that we can share computer screens. Matrix/Element is the best way to message me. I am open to using IRC although I have never used it before. There's Discord, but I'd prefer not to use it since I cannot access or change the email address associated with my account, meaning I could permanently lose access to it any day.
I can report to you status updates of my code once every half week (Twice a week in total) through asynchronous messages. Of course there is always asking lilypond-devel for help/general questions. Types of feedback that would best help me are on how well my code is documented, how well my code works with other Lilypond components, how homogeneous my code style is with rest of Lilypond. Basically code review. I probably don't need a lot of feedback unless I raise such concerns about my code.
I expect that during the Bonding period our communication will be less formal than during the coding phase, as we won't have formal milestones during this time.Again, congratulations on being accepted to GSOC! And I hope we can bond well with you over the next three weeks!
Again, glad to meet you and the other developers too!
Carl Sorensen
-- - Jason Yip
OpenPGP_0xB69A3DD87D22F506.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
