Tahia, It's great to hear that you're interested in working on Ceph and already configured a cluster on a machine. In terms of bugs to work on, I would suggest taking a look at the projects page (http://ceph.com/gsoc2017-ideas/) and finding a project(s) that you're interested in, and reaching out to the mentor about bugs to work on or learning more about the project. Ceph has a massive code base, and while fixing a bug is valuable to learning about the Ceph development workflow, the bug you might fix in one component of Ceph may not be relevant or teach you more about the component that you would be working on for you project. -Ali ----- Original Message ----- > From: "Tahia Khan" <tahia.khan@xxxxxxxxx> > To: ceph-devel@xxxxxxxxxxxxxxx, ceph-community@xxxxxxxx > Sent: Tuesday, March 7, 2017 3:11:50 PM > Subject: First contributions for Outreachy applicant > > Hi everyone, > > > I’m a prospective applicant for Outreachy Round 14. Part of the > application process for Outreachy is to submit non-trivial patches to > Ceph. So far I’ve submitted a handful of minor documentation patches > and have configured a 3-node storage cluster on my local machine, but > I’d like to move forward to code changes. I was wondering if I could > get some help identifying “low hanging” bugs/issues on the Redmine > tracker to get started. Any suggestions are much appreciated. > > Tahia > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
