Re: [RFC] Unify KVM kernel-space and user-space code into a single project

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



mingo wrote:

> [...]
>> No, the split-repository situation was the smallest problem after all. Its 
>> was a community thing. If the community doesn't work a single-repo project 
>> will also fail. [...]
>
> So, what do you think creates code communities and keeps them alive? 
> Developers and code. And the wellbeing of developers are primarily influenced 
> by the repository structure and by the development/maintenance process - i.e. 
> by the 'fun' aspect. (i'm simplifying things there but that's the crux of it.)
>
> So yes, i do claim that what stiffled and eventually killed off the Oprofile 
> community was the split repository.  [...]

In your very previous paragraphs, you enumerate two separate causes:
"repository structure" and "development/maintenance process" as being
sources of "fun".  Please simply accept that the former is considered
by many as absolutely trivial compared to the latter, and additional
verbose repetition of your thesis will not change this.

- FChE
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux