[Dbix-class] GOVERNANCE: Aggregation and conclusion

[David Precious]

From me, it's a +1 to Matt's proposal (new project team) and -1 to
forking - I don't want to see the current DBIx::Class languishing, and
I think it's something far more valuable to be managed by a team.

As much as I respect riba for all the work he's put in, his recent
behaviour concerns me greatly, and doesn't leave me filled with
confidence of him being sole gatekeeper of the DBIx::Class namespace
and everything that relies upon it - and even if I still had full faith
in him being the man for the job, the bus factor is too low for
something so important.

Whilst, yes, people could change to "use DBIx::Class2" or whatever a new
fork was called if they want the new stuff, that's a lot of
already-out-there code relying on something with a single maintainer,
and a lot of CPAN dists which depend on DBIx::Class which would need to
decide which version to target, etc.



On Wed, 2 Nov 2016 10:11:25 +0100
"Stefan Hornburg (Racke)" <racke at linuxia.de> wrote:
> I think we should at least give interested developers a chance to play
> with DBIx::Class and test out new features.
> 
> It can just live on Github and not on CPAN until something useful
> emerges out of it. In case that doesn't happen, the repo can
> be closed.

Being on GitHub, people can arbitrarily fork with one click to their own
repository, play with it as they wish, and if they end up with
something they think is good and useful, offer to contribute it back.

Isn't that what GitHub is /for/? :)