> By your logic, anything run by a BDFL would be abandoned.
The "B" in "BDFL" stands for benevolent. Neither Sawyer, nor you Todd, exhibit this quality.
]]>* Create a separate github user ( the same type various Moose factions use for sync of non-github repos and gh mirrors )
* Make them a watcher of the repo(s) in question
* Subscribe them to the p5p mailing list
* Profit by having each conversation in github reflected in the usual interface, and moreover allowing other subscribers to the list to reply to github issues WITHOUT A GITHUB account
Proof: http://lists.scsys.co.uk/pipermail/dbix-class-devel/2019-November/thread.html
Downsides:
- Someone attempting to password-recover on the sync-account will spam the mailing list
- Technically violates GitHub TOS
]]>I don't want to publicize it too much, but https://travis-ci.org/Perl5/DBIx-Class/jobs/390708515#L441-L462 ( DBIC is not the only user afaik )
]]>Minor nit: your choice of lower-than-latest-dev release version is somewhat suboptimal. A surprisingly large amount of pre-smokers operate over the moral equivalent of:
`cpanm --look --dev DBD::Oracle`
As you can see your version is not being picked up as it is lower than @mjevans' older 1.75_2.
Cheers!
]]>P.S. Currently this works for reads only - there is no equivalent reifier for write operations.
]]>Yuki, the above part of Sawyer's comment is so (deliberately?) misleading, that in practice constitutes a lie. The fallout of the change in question is neither limited to Coro[1], nor is the original motivation[2] considered worth the trouble by a large contingent of perl-folk[3].
Sawyer, I believe that your current position as Pumpking compels you to clarify/revise your earlier statement.
Thank you in advance.
[1] As stated in AP's event recap the fallout includes (but is by no means limited to) older versions of mod_perl, and an unknown number of darkpan code relying on the SWIG bindings.
[2] See last paragraph of the commit message, which was further defended by its author as recently as 2 months ago.
[3] The author and 3 reviewers of the original recap (Aristotle Pagaltzis, Andreas König, Graham Knop, Peter Rabbitson), and additionally Aaron Crane, Dave Mitchell, Paul Evans,
]]>I continue to maintain that Chad Granum had no direct fault in this, as he can not be blamed for the "exploratory personality" which is an integral part of who he is.
I also recognize that this train has inexorably left the station. For posterity the ones responsible for the impending largely invisible wave of breakage are:
Dark times lie ahead :/
]]>Several hours ago my unorthodox campaign came to an unsuccessful end. There has been a lot of feedback to my previous post, some of it so surprisingly off the mark that I still have not wrapped my head around it enough for a proper response. I plan to publish a much more in-depth analysis and "lessons learned", but I need to gain much more distance from the current hot mess of CPAN, to better express the crux of what went right and what went wrong (spoiler - while the campaign itself failed, I consider the chain of events an incredible, way-beyond-what-I-expected success)
Couple weeks before the "I give up" announcement I compiled and started working in parallel on the following list, in order to shape up a "final ribasushi-approved" DBIC release:
]]>Unfortunately around the same time I got sucked into a (sorely needed) paying contract, helping deliver tens of thousands of fire-hazards to the homes of unsuspecting hipsters. This burned a huge amount of my physically available time, resulting in massive slippage of my OSS schedule.
The worst thing that can happen to a project with a previously established "ready when it is ready" release dynamic, is to force it into an artificial timeframe at any and all costs. Being bound by the mantra of "no work at all is decidedly better than half-assed work", I am left with two practical choices:
I won't deny that I was really looking forward to the first option. A number of events and comments that took place after I announced I am stepping away from CPAN, have only confirmed that I made the right call, and strengthened my resolve to reevaluate the entirety of my relationship with Perl. But in the end my "moral side" wins out for a bit longer. It would be downright criminally irresponsible to not donate these extra 50-odd hours to the existing DBIC userbase, especially in light of the sheer amount of stumbling blocks for anyone else without the (sadly non-transferable) overview of the larger system.
Thus, for the sake of continuity, and in light of the holiday spirit, I am postponing my long-deserved exit until the second half of January. After all... a delayed Christmas present is still a present. Stay tuned, it shouldn't be long now.
Still search()ing
Your outgoing janitor
Arriving at this sort of clarity took me several years, left alone being able to put it into words. I feel in the end it's for the best, less tension on all sides is not to be underestimated.
perhaps this would have worked better with a truly long fundraiser time.
Hmmm... longer than 3 months? That's... an interesting thought for whoever attempts to do this next.
You really only have 35kUSD in debt?
Hehe. Well, I didn't get a chance at higher ed. so that probably helped ;P
]]>Thank you so much for your contribution. The campaign triggered due to an internal problem in the tilt system. The resolution is ongoing. Please read more here
Sorry once again about this :(
Cheers!
I was indeed really sad to see you pushed out of #catalyst some weeks ago. Can only echo your words re "hopefully things will continue" ;)
Cheers!
]]>