[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Turkish makam (and beyond) contribution(s) to Lilypond

From: Karlin High
Subject: Re: Turkish makam (and beyond) contribution(s) to Lilypond
Date: Sat, 24 Nov 2018 12:40:02 -0600
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1

On 11/22/2018 3:25 PM, Adam Good wrote:
I need guidance from someone here to make it happen, like
a mentor as mentioned in the contributor guide. Would a developer be
willing to help me?

I think currently, your mentor will be the lilypond-devel list.


I'd say follow the Contributor Guide instructions for submitting a patch for code review, and your mentor for that particular patch will be whichever of the most-frequent contributors takes the most interest in it.

If someone plans to be a major, ongoing contributor to the project, I think having a single mentor would be the way to go.

For someone like me, contributing just one patch ever, it's worked out well to follow the Contributor Guide instructions and ask this list for help as needed.

Following the list has also been helpful; no way can I understand the discussions on the finer points of C++ or Scheme, but I'd like to think it does help me stay in touch with how to work with the community. It also gives me an idea of which of the main developers have what skills, and which ones are most likely to match my style of work and communication.

To contribute a patch, getting accounts for the SourceForge issue tracker and Rietveld code review isn't hard. I don't ever plan to get Git commit access unless not having that is causing someone else a big inconvenience. My skill with Git isn't enough to let me fully understand the effects of my actions. I'm quite happy to attach a review-complete patch to the issue tracker and let someone else apply it.
Karlin High
Missouri, USA

reply via email to

[Prev in Thread] Current Thread [Next in Thread]