[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fwd: Interested in GNU Lilypond Google Summer of Code Beaming Fixing Pro
Fwd: Interested in GNU Lilypond Google Summer of Code Beaming Fixing Project Idea
Mon, 20 Mar 2023 13:27:23 -0600
Forwarding to list, since I apparently didn't add the list to the email as
I intended to.
---------- Forwarded message ---------
From: Carl Sorensen <firstname.lastname@example.org>
Date: Mon, Mar 20, 2023 at 12:59 PM
Subject: Re: Interested in GNU Lilypond Google Summer of Code Beaming
Fixing Project Idea
To: Jason Yip <email@example.com>
Thanks for your interest!
On Sun, Mar 19, 2023 at 12:21 AM Jason Yip <firstname.lastname@example.org>
> Hello Carl,
> My name is Jason Yip, and I am interested in learning more about GNU
> Lilypond's "Fix Beaming Patterns/Beam Subdivisions and Tuplets" project
> idea for Google Summer of Code and participating in this project idea. I
> would like to ask, are you are still looking for prospective 2023 GSoC
> contributors for this project idea?
> I am currently a 2nd year student at University of Illinois at
> Urbana-Champaign, US and I am studying Computer Science + Music. I have
> some basic familiarity with LilyPond as I sometimes use it to create
> personal scores. I have about 4 years of experience in C++, which I hope
> will be of use. I am available to contribute full-time during the summer
> and would like to explore this issue, even if it means refactoring a lot
> of the Beam C++ classes.
The beaming project would be a great asset to LilyPond. I’d love to see
you tackle it, if you’re interested. Your background in C++ would be a
great asset here.
In preparation for submitting a proposal, it might be good to rename things
There is a discussion on the lists (wow, from 5 ½ years ago!) that mentions
the names used in the code don’t match the names used in the user
The bottom line on that discussion is that we could change “group” in
beaming-pattern.cc to “beat”, and “beat” in beaming-pattern.cc to “
base_moment” to match our user documentation. I would expect that making
this change would do two things:
1. Get you an introduction to beaming-pattern.cc, which is where the
major work needs to be done, and
2. Get you an introduction to our process for handling merge requests,
which would make you part of the team.
I've added email@example.com on the reply, in order to get you
introduced to the development group.
I'd also suggest that you look at the LilyPond Contributor's Guide, which
is where we keep all the available information about our development
If you'd like some help in getting started on the terminology change
project, please let me know.