On Friday 21 June 2013 14:50:54 Robin H. Johnson wrote: > From what I've read on the list recently, there's a lot of demand for > non-maintainer updates to ebuilds. Esp. with the upcoming Git migration, > I predict there will be a much larger influx of changes from users.
seems like we're somewhat approaching it the wrong way around. our tooling sucks -- bugzilla is not the proper medium for gating ebuild contributions. something like gerrit would make things flow a lot more smoothly imo. i've been doing more workflow along the lines of: - dev/user posts patch to bugzilla - click "edit attachment as comment" - do patch review like a standard mailing list - dev/user posts updated patch - for a dev, i'll usually finish with "feel free to commit". for a user, i'll commit it at some point (same for devs if i happen to be digging around). if i do the commit, it's a pita: - ssh to a system that has commit access (assuming i'm in a location where this is possible, otherwise it'll have to wait) - open up the bug in a browser - find & download the attached patch - apply it and sort out any conflicts - run `repoman commit` - update the bug with gerrit and git, this process could be turned into me clicking "submit" in the web interface (gerrit also has a ssh command line interface for doing things). would be easy to add a `repoman upload` that'd take care of making the commit, regenerating things (Manifest/etc...), and then uploading it to gerrit. -mike
signature.asc
Description: This is a digitally signed message part.
