Re: Handling policy commitment disputes [was: Berlin Consensus document posted]
[email protected] (David Golden)
| Newsgroups | perl.cpan.workers |
|---|---|
| Message-ID | <CAOeq1c-0GmfkLwBgyHw7Kwja0KV141ghgab2WRaD4LRX6ZkkWA@mail.gmail.com> |
On Sat, May 9, 2015 at 8:28 PM, Aristotle Pagaltzis <[email protected]> wrote: > It was also brought up that if you are way upstream yourself with one of > your modules, you shouldn’t take dependencies on things willy nilly – as > that puts maintainers in an upstream position they may not want to be > in. Rather before you take a new dependency you ought to ask the author > whether he or she is willing to take on such responsibility; some just > want to release some code, in which case pointing your horde of users at > them would not be a very considerate move to either them or the users. > That's a great point that I'll try to remember to include in my annotated version. -- David Golden <[email protected]> Twitter/IRC: @xdg