On Nov 26, 2009, at 6:51 AM, Jonathan Lange wrote: > Hello all, > > I'm going to be the Build Engineer for the month of December. Sadly, I > might not actually get that much time to actually do anything. At > least, not in the way of programming. > > What I might be able to do is figure out what would be best to work > on. Thus, at Rob's suggestion, I'd like to conduct a secret ballot. > > Please reply privately and tell me the top three pain points in > Launchpad development. These can be things that: > * cause pain > * slow you down > * are annoying > * you always get wrong the first time > * you keep having to look up > * you always have to ask Hacker X about > > Or they can be whatever you wish. > > Again, please reply just to me, not to the list. Surveys are closer to > being actual data when the answers are independent.
Hi Jono. I was thinking about what my replies should be. For any number of possible reasons, the first ones I thought of fell more in the category of Foundations-team work rather than build engineer work, at least as I see the distinction. To be clear, my perception of build engineer tasks is focused on the things *around* the Launchpad code itself: the build system, the way we test code, and the way we land code. Foundations team work encompasses those sorts of jobs, but adds in maintenance/upgrade/integration of libraries *in* the Launchpad code. Could you clarify the intent of your survey in that regard? Thanks Gary _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
