> On Jun 20, 2017, at 12:37 PM, Halen Wooten via swift-dev > <swift-dev@swift.org> wrote: > > Hi, > > I would like to start a discussion about getting started with the > Swift Compiler. The end goal is to see if there are ways we can help > newcomers to the compiler get started and more quickly grow into a > more effective contributor. The motivation is that I've had a > surprising amount of trouble with my starter bug. Swift is amazing and > I would love to contribute more regularly, but I also don't want to > burden the core team. > > I know that documentation on a huge project like this is a > non-starter, but I wonder if we could have better information on the > contribution process, which likely wouldn't change frequently. For > example, I learned through a conference talk that Swift uses LLVM's > lit testing. I couldn't find that in any of Swift's documentation. The > docs explain how to run tests, but not how to write them. I would be > happy to help out with documentation if we can decide on changes that > would be useful. > > The learning curve for a compiler is always going to be high, but does > anyone have ideas on how we could assist newcomers with their first > starter bug and then transitioning into something larger?
Improving documentation for new developers is a great project. We have some information at swift.org/contributing <http://swift.org/contributing>, but it is unbalanced. (For example it has detailed specifications about the format of commit messages, but next to nothing about writing and running tests.) You might start by writing down the various topics that you yourself wished had been gathered in one place. As a recent new contributor you will have the best insight into what is currently lacking from that perspective. For example, we do have test documentation (as you found later), but your experience shows that the documentation is not sufficiently discoverable. > Also, after I'm able to get my starter bug merged, I have no idea > where to go from there. I don't want to take another starter bug and > deprive someone else of the opportunity to contribute (although maybe > that's an unnecessary restriction I'm placing on myself), but I'm also > not in a place where I could take on something much larger. Don't worry about that. Starter bugs are unlikely to be a scarce resource. If too many starter bugs get fixed then we will (1) celebrate, and then (2) find some more bugs that are good starter candidates. -- Greg Parker gpar...@apple.com <mailto:gpar...@apple.com> Runtime Wrangler
_______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
