"Jess Robinson" <casta...@desert-island.me.uk> writes: > Admittedly I haven't been following the DBIC ML / commits lately, for at > least a year.. This is mostly because its felt like > > a) Nothing is allowed to be added/tweaked until specifically approved by > Riba, or until some other piece of work is finished which can only be > done by Riba.
I concur with this sentiment. I have contributed code lately, but as pointed out by Riba upthread a lot of it is blocked: | Some of his work has already made it into mailnline, while other has | been delayed ( none of it rejected ), due to a combination of review | tuits and/or tuits necessary to fix sub-par sections of the | submissions. I know a bunch of the the pending changes are not ready to merge (or "sub-par" if you will); this is because I haven't had the motivation to put more work into them beyond the initial prototype/proof-of-concept, either because of vague review feedback or statements that the underlying code was being rewritten, but with no public work-in-progress branch for said rewrite. > b) I didn't want to add to all the more things that Riba had to do, thus > keeping quiet until some point became available that others could join > in, was reached. Ditto. [snip] > TL:DR - more community involvement, less micromanagement please Ditto. I realise that fostering community involvement requires that the people who are intimately familiar with the codebase spend more time giving constructive review feedback on contributions and mentoring new contributors. This can be frustrating in terms of short-term progress, but I strongly believe it's better for the long-term health of the project. - ilmari -- "The surreality of the universe tends towards a maximum" -- Skud's Law "Never formulate a law or axiom that you're not prepared to live with the consequences of." -- Skud's Meta-Law
