Hey all, I've put together a quick start guide to building packages on Ubuntu. It covers installing the build tools (and more importantly, which ones you need), installing build dependencies, and installing, configuring and using a tool called jhbuild, which is the standard tool for building packages (at least the Gnome ones) on Ubuntu.
The guide can be found here<https://wiki.ubuntu.com/OneHundredPaperCuts/PaperCutsNinja/Dojo/BuildingPackages> and I was wondering if anyone would be willing to take it for a test drive before we start publicising it. All of this info is easy for me, so I may not be noticing the gaps in the information that a less experienced contributor would have a problem with, so some feedback would be awesome. Chris On 21 June 2013 21:43, Darío Ruellan <[email protected]> wrote: > Hi Ninjas > I finally got some time to sit and read this. Sorry about the delay, but > life got complicated the last months. Just to point out some quick things, > Leonardo and Alberto brought some good points, that are not new for us: if > you are a newcomer, you can get lost very quickly, without knowing what to > do or how. > > I still believe that focusing on an app for one or two months is the way > to go, and PROMOTE it: on the wiki (big banner or calendar), IRC channels, > etc. This way, newcomers or just returning contributors (like me) know what > the project is doing right now. > > About motivation: I think that what devs and papercutters want to see is > their bugs released and working on their desktops, and for that I strongly > believe that working in conjunction to other Ubuntu teams is key, or at > least be aware of their calendars just to sneak in. Just as an example, a > new revision of Ubuntu 12.04 LTS is comming. This could be a wonderful > occasion to focus on Unity 5 and Compiz, and try to push some fixes. > > > On 09/05/2013 10:12 a.m., Chris Wilson wrote: > > Just realised that I didn't make any suggestions about what we're going to > work on in the coming cycle, so here are a few, but feel free to suggest > your own. > > - Rhythmbox, Nautilus, Shotwell, Firefox and Unity are all core to the > user experience on the desktop to I think they should get a generous amount > of attention. As we're working on them, we should make sure we're updating > the Dojo with information on how to work with them, particularly around > building them. > - Once I figure out what I'm doing with the build systems, I might > host a few developer hangouts where I'll show people how to do it > themselves. > - We should organise days throughout the development cycle where we > sit down with a particular app and test it for new paper cuts, similar to > the hug days the bug squad does. This can actually be done on their hug > days, so we can work with the members of their team. We should decide in > advance when we want to run these days, instead of deciding it throughout > the cycle. > > Those are just a few things I've been thinking about recently. Feel free > to suggest your own, and to disagree with mine. > > Chris > > > On 9 May 2013 12:06, Chris Wilson <[email protected]> wrote: > >> Hey all, >> >> 13.04 has just wrapped up and it's time to start thinking about what >> we're going to do in the next cycle. I don't think anyone would dispute the >> fact that we never came close to fixing 100 bugs over the over six months, >> and I think we should take some time to figure out why that happened, and >> what we could do better in this cycle. >> >> If anyone has anything they'd like to say about how we've been working, >> then please come out and say it, no matter how critical it is. The only way >> we're going to get better at this is by facing up to the truth, no matter >> how hard it is. >> >> A few points I'd like to make: >> >> - I dropped off the radar for the past few months as real life has >> gotten in the way. I fucked that one up and I'll look at managing my time >> better. One thing I'm thinking of doing is setting aside one evening each >> week for Ubuntu stuff, so no matter what else happens, I've always got the >> slot of time to give to the project. >> - We didn't target all 100 bugs at the very start, which made it >> harder for people to know what there was to do. >> - I went a little mad shortly after the start of the 13.04 cycle, and >> changed up a bunch of the milestones around the second month. That won't >> be >> happening again because we're going to talk together about what we want to >> do for the coming cycle and stick with it. I hope that by the end of next >> week (Sunday 19th) we can have our milestones and bug targets sorted out. >> - It's been mentioned before that it's not clear from our wiki pages >> how a new user should get involved with the project. I agree with that and >> we should have a look at our 'getting started' documentation to figure out >> how we can improve it. >> >> Those are my thoughts on what happened last cycle and what we can improve >> next cycle. what do other people have to say? >> >> Chris >> > > > > _______________________________________________ > Mailing list: https://launchpad.net/~papercuts-ninja > Post to : [email protected] > Unsubscribe : https://launchpad.net/~papercuts-ninja > More help : https://help.launchpad.net/ListHelp > > > _______________________________________________ > Mailing list: https://launchpad.net/~papercuts-ninja > Post to : [email protected] > Unsubscribe : https://launchpad.net/~papercuts-ninja > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~papercuts-ninja Post to : [email protected] Unsubscribe : https://launchpad.net/~papercuts-ninja More help : https://help.launchpad.net/ListHelp
