Just having the conversation, and making it clear that you're considering people's concerns, is good. :)
You speak of having issues with managing multiple clones in deployment, but I don't do that. All of my clones are on my local disk, and I generate and upload patches to my dreamhack when I want to test them. Because I also have to generate and upload patches to Bugzilla for review, this is a natural workflow for me, but it does make testing less fluid.
What our setup really discourages (IMO) is collaborative development. You can't assign multiple people on a bug, and although it is possible for multiple people to upload patches on a bug, it's generally perceived as stepping on the bug owner's toes. I would be all for a more public and functional branched system of development if it helped to break down those walls. Otherwise, I'd rather spend my available time working on code than learning a new system.
no subject
You speak of having issues with managing multiple clones in deployment, but I don't do that. All of my clones are on my local disk, and I generate and upload patches to my dreamhack when I want to test them. Because I also have to generate and upload patches to Bugzilla for review, this is a natural workflow for me, but it does make testing less fluid.
What our setup really discourages (IMO) is collaborative development. You can't assign multiple people on a bug, and although it is possible for multiple people to upload patches on a bug, it's generally perceived as stepping on the bug owner's toes. I would be all for a more public and functional branched system of development if it helped to break down those walls. Otherwise, I'd rather spend my available time working on code than learning a new system.