search for: incentivize

Is Urguent any for the World and Messages of Expressivite,Communication at Hummanity,Society -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at

...embers of the community. You missed what is (IMO) the most important point: LLVM's development process and VCS optimize for active developers working in the open on mainline LLVM. They don't optimize for private forks or other development processes. This isn't an accident, and it helps incentivize members of the community to contribute early and in small, incremental patches. > Changing the ID creates > a serious problem, one which forces the private fork to make an early > decision about contributing back to the community. The fact that this (and all of the related and restated p...

...a pure DebugLoc variable or possibly an `Instruction *InheritLocationFromInst` one Some pros of this idea are: - Easier to create instructions with debug location. - It will make the code more readable by eliminating the many `NewInst->setDebugLoc(OldInst->getDebugLoc)` calls. - It will incentivize people to think about the DebugLoc of their newly created instruction and where it should come from. As the Create() functions are widely used, and sometimes location data could be out of scope when the Instruction is created, I think the best approach to this is to introduce the new field as opt...

LLVM Community, > http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-July/041738.html This was extraordinarily valuable in learning to understand the situation - thank you David Blaikie for pointing me to it. A few key snippets: "Because I optimize for the code reviewer, not the patch submitter," Chris Lattner "Forcing transitioning to git makes no sense for a lot of us - for

...merely a bump in the road, not a major mountain to climb over. In any case, I hope that we as a community don’t end up in a place where we are afraid of doing sweeping changes that make the codebase better. It is important to continually reinvest in the health of the codebase, and it isn’t bad to incentivize people to merge their changes upstream. Being overwhelmingly afraid of ‘breaking history’ is a path that leads stagnation and ultimate replacement by newer technologies. There are many other projects that have suffered this fate, usually for a combination of reasons including things like this. -...

Since the largest regional ILEC in Brazil completely stopped taking new BRI ISDN customers and started heavily incentiving their existing customers to migrate over to ADSL (regardless if what they need is voice or data), we have thousands of ISDN phones collecting dust. Is there any network side U cards that will work with Asterisk, so we can turn those phones into useful things ? I'm

...y is sufficiently capricious that 8 characters is frequently insufficient. I tried about a dozen times and failed, gave up, and went with an ill advised 10 character password that I forgot within 30 minutes after the installation was complete. The problem is the decision to stop innovating ways to incentivize irrational users into producing stronger passwords voluntarily, and instead bringing out boxing gloves to make everyone do it by force. It's inherently adversarial. Someone else made an analogy with the anti-immunization camp. The analogy has some fatal flaws, but one of the ways it works is t...

Hi, I am sending my application I submitted for the GSoC. There are still some hours left before the deadline, so if you have any remarks or a tip, I can still update it. thanks... i think there are some grammatical errors =(... == Name and Contact details == Andr? Luiz Nazareth da Costa Primary e-mail: andre.lnc@gmail.com Secondary e-mail: andre.lnc@lsc.ic.unicamp.br Gtalk:

...e should be able to make sweeping changes. I’m saying that I don’t think the direction I see us going in right now seems like it’ll work out well, and it seems easy to address my worries. > > >> It is important to continually reinvest in the health of the codebase, and it isn’t bad to incentivize people to merge their changes upstream. > > Agreed. However, as you know very well, merging upstream changes isn’t something that’s done over a weekend. First people have to know that a large change is coming and they probably should plan for upstreaming. Second we should give these folks en...

I am experiencing a curious event, and wondering if others have seen this... As well, I have a question related to it. Today, I noticed my puppet summary report from Foreman this morning, that 60 of my 160 hosts all stopped reporting at nearly the exact same time, and have not since restarted. Investigating, it appears that my puppetmaster temporarily ran out of disk space on the /var

On 6 Nov 2013, at 08:10, Renato Golin <renato.golin at linaro.org> wrote: > On 5 November 2013 10:12, <dag at cray.com> wrote: >> I'm fine with the general plan but I do want to see a longer notice >> period for toolchain changes on trunk. 1-2 months is too short. > > I may be wrong, but I think the final consensus was: for every new change, warn on (at

On 5 November 2013 10:12, <dag at cray.com> wrote: > I'm fine with the general plan but I do want to see a longer notice > period for toolchain changes on trunk. 1-2 months is too short. > I may be wrong, but I think the final consensus was: for every new change, warn on (at least) one previous release as when the changes go live. If I'm mistaken, this is still my

I see someone has noticed my lack of suggestions or recommendations for placement of virtual host source files... Since there are many places to put virtual host source files, I had intentionally avoided the discussion due to the complexities and to keep the document restricted to a single topic. I had planned to create a separate document devoted to the discussion. Specifically, there

As a very frequent explorer of history, I really don't think this is as big an issue as it may seem. Even absent refactorings, you often run into the "wrong" commit when looking at blame (e.g., someone just added a comma rather than actually changing the code you care about), and have to look past that, to another previous commit. Any interactive blame tool ought to have an easy way

[adding llvm-dev for wider audience] On Fri, May 19, 2017 at 12:28 PM, Daniel Berlin <dberlin at dberlin.org> wrote: > > > On Fri, May 19, 2017 at 11:00 AM, Davide Italiano <davide at freebsd.org> > wrote: > >> On Fri, May 19, 2017 at 10:00 AM, Sanjay Patel <spatel at rotateright.com> >> wrote: >> > Is "VRP" (value range

ANNOUNCING AGILE WEB DEVELOPMENT WITH RAILS, SECOND EDITION =========================================================== http://www.pragmaticprogrammer.com/titles/rails2/ Rails has changed a lot since we announced the first edition of the book a year ago. DHH says that the 1.1 release "boasts more than 500 fixes, tweaks, and features from more than 100 contributors." Who are we to

Hi all, Now that we're on GitHub, we can discuss about pull-requests. I'd like to propose to enable pull-request on GitHub, as a first step as an experimental channel alongside the existing methods for contributing to LLVM. This would allow to find workflow issues and address them, and also LLVM contributors in general to start getting familiar with pull-requests without committing to