I think these are both good ideas. Jay
On Sat, Dec 19, 2015 at 4:56 PM, Stephen De Gabrielle <[email protected]> wrote: > Hi, > > Would it be appropriate for package maintainers to add (voluntarily) a > special collaborator (like 'racket-dep-fixer') that can be used if there is > a problem? > > Other package maintainers might be more comfortable with the _pull request > hack_ 'Whenever somebody sends you a pull request, give them commit access > to your project.' - http://felixge.de/2013/03/11/the-pull-request-hack.html > > Happy holidays! > > Stephen > On Sat, 19 Dec 2015 at 21:46, Matthias Felleisen <[email protected]> > wrote: >> >> >> Neil, >> >> I appreciate your comments very much. From where I sit, I think these >> “take overs” will be extremely rare but always to the benefit of the >> community and with ample communication with the creator of the original >> package. Nobody will take over anyone else’s package by force. >> >> What the community deserves, and what the Dunstable meeting has worked >> out, is an announcement of when we invoke this rule on a package so that >> everybody else — not only the previous owner and new maintainer — but >> everyone knows what’s happening. >> >> — Matthias >> >> >> >> >> >> >> >> >> > On Dec 19, 2015, at 3:03 PM, Neil Van Dyke <[email protected]> wrote: >> > >> > No comments on this particular package, but if the package system rules >> > are going to change in fundamental ways (imagine this were a programming >> > language), then those changes must be communicated to everyone. >> > >> > Also, maybe it's time to think ahead to what other package system rules >> > there will likely be a desire to change, and get all the rule changes over >> > with at once, so that we don't get into the habit of changing the rules on >> > people. >> > >> > When we're encouraging altruistic third-party contributions through the >> > package system, and presenting it as open and decentralized, then we have >> > to >> > be aware of centralized, proprietary behavior that might erode trust and >> > discourage participation. One thing third parties have to go on, in >> > absence >> > of formal business relationships and contracts, is the rules or >> > documentation of how these open-ish systems will work. >> > >> > Again, no comment on this particular package; just trying to help the >> > new package system find the mix of centralized and decentralized that it >> > seems to be looking for. >> > >> > Neil V. >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Racket Developers" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an email to [email protected]. >> > To post to this group, send email to [email protected]. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msgid/racket-dev/5675B7F9.3010509%40neilvandyke.org. >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Racket Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/racket-dev/744FAF31-CCDF-4FF4-8288-03A2A89B1313%40ccs.neu.edu. >> For more options, visit https://groups.google.com/d/optout. -- Jay McCarthy Associate Professor PLT @ CS @ UMass Lowell http://jeapostrophe.github.io "Wherefore, be not weary in well-doing, for ye are laying the foundation of a great work. And out of small things proceedeth that which is great." - D&C 64:33 -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAJYbDan7-FtH9EByEFW4ueybYd3vquVPFu4R%2Bx%2B10zKTHpDpJQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
