No dia 26 de Abril de 2012 20:52, Paul Wouters <pwouters(a)redhat.com> escreveu:
On Thu, 26 Apr 2012, Toshio Kuratomi wrote:
> So the big question is -- where did this break down? How can we update
> our
> documentation to guide people in this direction?
I find bugzilla as the core around which to navigate where things are
in a process difficult and inconvenient. Its emails don't really help
me as I get so many, and at the wrong times. The "my bugs" or
"frontpage" does not really help me to see which bugs have been updated
recently for me to look at. I end up opening 20+ tabs and scrolling down
in each item.
Is there some kind of RSS plugin for bugzilla?
Similarly, I find tracking all my packages and branches and repositories
not always that easy too, especially in the case of problems. Like I
modify git, push and build and it fails, and I ran out of time to look
at it. Perhaps people are using tools I'm not aware of?
On my $dayjob I was sent to investigate build platforms since we're
doing a lot of builds. I've investigated OBS and the main blocker was
the fact that we didn't had SUSE Linux experts on our infra-structure
teams. I've taken a very close look to Koji and it severely lacks a
lot of 'project management' tools.
Our decision was pretty much:
- enhance mock scm plugin;
- adopt mock as build tool;
- make our own web appliance (Ruby) to include our needs for project
management;
- Build our own RPC based on mock XMLRPC (once more Ruby/Rails)
My suggestion is that Koji does require a lot of work to add some
project management. We're currently inspired on this part on Open
Build Service , but we're adding our own stuff which goes with:
- Integration with JIRA
- Integration with Confluence Wiki
- Integration with SCM and FishEye
- Integration with some of our tools...
I don't believe there's much that can be done without a lot of
enhancements on Koji itself... By the way we don't have much expertise
with Python on my $dayjob, so we've adopted Ruby because we have very
good people with Ruby and a few specialists in other fields of
interest.
It would also be nice if fedora could detect two day old
'testing'
packages, and popup with a +1/-1 karma vote box. It would result in me
giving much more karma then I do now and speed up the process, though it
would not handle karma for specific bugs that a specific update is
supposed to fix.
Paul
--
devel mailing list
devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
--
Nelson Marques
// I've stopped trying to understand sandwiches with a third piece of
bread in the middle...