search for: contributors

The time has come to review the current Contributor and Core contributor grants for ZFS. Since all of the ZFS core contributors grants are set to expire on 02-24-2009 we need to renew the members that are still contributing at core contributor levels. We should also add some new members to both Contributor and Core contributor levels. First the current list of Core contributors: Bill Moore (billm) Cindy Swearingen (c...

I have habtm relationship between articles and contributors. Everything''s working fine, except when I create a new article Rails doesn''t seem to save the contributors that belong to it into articles_contributors. This is the controller (that I pilfered from typo): def new @article = Article.new(params[:article]) [...] if r...

...#39;cross.png'', :alt => ''Cancel''), :url => cancel_edit_project_path, :method => :get %> </p> <% end %> <% form_remote_for(:project, :url => add_contributor_project_path(@project), :html => { :method => :put }) do |f| %> <h4>Contributors</h4> Add contributor <%= text_field_tag ''contributor'' %> <%= image_submit_tag(''add.png'', :class => ''icon'') %> <% end %> <%= render :partial => ''contributors'', :object => @project %> And t...

...llvm.git >> $ git cherry-pick 4823be3be1d87632fbd51ce8e51a58ee5e44b115 >> $ git push > > Most development is not "some contributor's fork". Well, in the git model every developer has a fork. > What you suggest works great for the occasional drive-by > contributors, but most development is not from drive-by's. Not sure what you mean by "drive-by" but in git this is really irrelevant, I think. -David

Guys, OK, now that we have the new core contributors squared away, we can go back to finishing the contributors list. There were some people who got added and then there is existing contributors list. I think Darren''s suggestion to wait to add new core contributors is fine (let the new constitution settle down and we can in the meanwhile ha...

...t.column :year, :integer, :limit => 4 t.column :type, :string t.column :container_id, :integer t.column :collection_id, :integer t.column :original_id, :integer t.column :event_id, :integer end create_table :contributors do |t| t.column :type, :string, :default => "Person" t.column :sort_name, :string, :limit => 255, :null => false end create_table :contributions do |t| t.column :reference_item_id, :integer t.column :agent_id, :intege...

>> Most development is not "some contributor's fork". > > Well, in the git model every developer has a fork. > >> What you suggest works great for the occasional drive-by >> contributors, but most development is not from drive-by's. > > Not sure what you mean by "drive-by" but in git this is really > irrelevant, I think. Sorry for the lack of clarity. I was trying to contrast with the status quo. By "drive-by" I *roughly* mean "people without...

Hi all, Some discussions the night before prompted me to do a short lightning talk on 'improving the experience of first-time contributors' at the LLVM Cauldron back in September. I intended to write it up as an RFC, but have only just got round to doing so. I've tried to make this email self-contained, but you may still want to look at the slides or recording of the lightning talk. Slides: https://speakerdeck.com/asb/can-we-...

...19, 2015, at 9:27 AM, Joerg Sonnenberger via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Mon, Oct 19, 2015 at 08:25:16AM -0700, Chris Lattner via llvm-dev wrote: >> 1) We could introduce a novel legal solution. > > Please, no. > >> 2) We could require new contributors to sign the Apache CLA. > > To me, this is the most acceptable option of the listed terms. Please explain: why? >> 3) We could relicense all of LLVM under the Apache 2.0 license and add a runtime exception. > > This one I would consider a regression over the status quo. Your l...

Dear Prof.Vikram. Really appreciate the hard work and determination in bringing LLVM concept. I had been a GCC contributor for almost 3-4 years, specially in backend with Renesas(SH) targets. Gone through http://llvm.org and found very challenging, seems to be better in many areas w.r.t GCC. Seeing the work of LLVM, am motivated to contribute to LLVM with reference to HPC needs. I maybe slow to

> > #4 is interesting, but a *ton* of work. The Object library, most of Support > and System, all would have to sink into this core module, all would have to > get dual-licensed (ow!!! how? some of the contributors are around to agree > to new license, but not all... likely a fair amount of rewrite required to > produce new versions of libraries under the correct license). You actually don't have that many contributors. I've seen this done for projects with 200+ contributors. Even better, most...

...ated to switching license in general. > > Because LLVM has not had a policy of including copyright holders in files (something else that we should change), it’s difficult to identify copyright holders. When we relicensed libcompiler_rt and libc++ under the MIT license, there were only a few contributors and it was easy to identify us all. Over LLVM, it’s not clear that the people who have committed code on behalf of others have been good at ensuring that it’s correctly attributed. I’d be interested to hear what the Foundation’s strategy for dealing with this is (and what will happen if a contrib...

...istical Computing Version 2.0.1 (2004-11-15), ISBN 3-900051-07-0 R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type 'license()' or 'licence()' for distribution details. R is a collaborative project with many contributors. Type 'contributors()' for more information and 'citation()' on how to cite R or R packages in publications. Type 'demo()' for some demos, 'help()' for on-line help, or 'help.start()' for a HTML browser interface to help. Type 'q()' to quit R. >...

If I understand correctly, for contributors without commit rights, the new patches "path" is 1) local work 2) local git 3) contributor github fork 4) official github fork 2016-02-25 0:01 GMT+02:00 Joachim Durchholz via llvm-dev < llvm-dev at lists.llvm.org>: > #3) Contributors without commit rights need to set up a fo...

Hello, after executing an action, I add an <li> element to an existing list using a RJS template: page.insert_html :bottom, :contributors, "<li id=''contributor.#{@contributor.id}''>#{@contributor.user.name}</li>" but I need to add an image with a link_to_remote as I have in a partial page: <li id="contributor.<%= contributor.id %>"> <%= link_to_remote i...

...M, Daniel Berlin <dberlin at dberlin.org> wrote: > > > > #4 is interesting, but a *ton* of work. The Object library, most of > Support > > and System, all would have to sink into this core module, all would have > to > > get dual-licensed (ow!!! how? some of the contributors are around to > agree > > to new license, but not all... likely a fair amount of rewrite required > to > > produce new versions of libraries under the correct license). > > You actually don't have that many contributors. I've seen this done > for projects with 200...

...the following disclaimer. +# +# * Redistributions in binary form must reproduce the above copyright +# notice, this list of conditions and the following disclaimer in the +# documentation and/or other materials provided with the distribution. +# +# * Neither the name of Red Hat nor the names of its contributors may be +# used to endorse or promote products derived from this software without +# specific prior written permission. +# +# THIS SOFTWARE IS PROVIDED BY RED HAT AND CONTRIBUTORS ''AS IS'' AND +# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, +# THE IMPLIED WARRAN...

..., 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 switching to pull-requests immediately. The community should evaluate after a few months what would the next steps be. GitHub pull-requests is the natural way to contribute to project hosted on GitHub: this feature is so...

...when patch is looking good: > $ git fetch https://github.com/llvm-mirror/llvm.git > $ git cherry-pick 4823be3be1d87632fbd51ce8e51a58ee5e44b115 > $ git push Most development is not "some contributor's fork". What you suggest works great for the occasional drive-by contributors, but most development is not from drive-by's. -- Sean Silva On Thu, Nov 15, 2012 at 3:01 PM, Greg Fitzgerald <garious at gmail.com> wrote: > Hi Michael, > >> As for actually switching to git. I see no benefit to justify the cost >> of switching unless we actually take...

...the following disclaimer. +# +# * Redistributions in binary form must reproduce the above copyright +# notice, this list of conditions and the following disclaimer in the +# documentation and/or other materials provided with the distribution. +# +# * Neither the name of Red Hat nor the names of its contributors may be +# used to endorse or promote products derived from this software without +# specific prior written permission. +# +# THIS SOFTWARE IS PROVIDED BY RED HAT AND CONTRIBUTORS ''AS IS'' AND +# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, +# THE IMPLIED WARRAN...