search for: contributed

Hi, With multiple proposals to improve the situation for newcomers in flight, let me add another brief proposal: Let’s add a CONTRIBUTING.md file to the top-level directory of llvm-project. I think this would make the information about how to contribute more visible and Github uses CONTRIBUTING.md to display ‘Contributing Guidelines’ at a few places, like when creating new issues or pull

I have two models, Donor and Contribution, and have has_many and belongs_to set respectively. My question is regarding creation of associated objects. I''ll let the code speak: me = Donor.find(1) contribution = me.contributions.create do |e| e.amount = 164.00 e.category = Category.find(1) end I thought this was valid, but it doesn''t work properly - it appears to

I posted something about this a week ago wihtout response, but have made some progress since. However, I''m still not getting exactly what I want. OK, three core tables: create_table :reference_items do |t| t.column :title, :string, :limit => 255 t.column :year, :integer, :limit => 4 t.column :type, :string t.column

> > > > Again, as stated before, both of these issues are covered by the apache > license. > > > > It has a built-in CLA that explicitly grants both copyright and patent > > rights from contributors when they make contributions to the work. > > Huh? How can employee X of company Y contributing a patch grant any > patent rights on behalf of Y? > >

I am working on a methodology for qualifying R, for GLP and GCP. If I quailfy only the base R install, with no contributed packages, it seems relatively simple to qualify R. However, from time to time I will want to use a contributed package. If I use a contributed package, does it leave anything behind that will be loaded with the next invocation of R? Suppose I run R and use a contributed package and then exit. Next...

As requested on http://wiki.centos.org/Contribute, here is my info: # your FirstnameLastname username [SteveBonds] # the proposed subject of your Wiki contribution(s) [Personal Page] # the proposed location of your Wiki contribution(s) [Personal Page] I'll branch out from here. Maybe. While I understand the problem with spammers, asking each user to send each proposed page to the list for

Hello Akemi, I want to give support to CentOs user with any kind of issue, hence please suggest me what should I do for that. And also one thing I am new here so can suggest me the workflow. Gajanan On Fri, Dec 19, 2014 at 12:43 AM, Akemi Yagi <amyagi at gmail.com> wrote: > > On Wed, Dec 17, 2014 at 3:49 AM, Gajanan Kankal <grkankal at gmail.com> > wrote: >> >>

Hi, i would like to contribute to the WiKi. Lots of the articles are outdated... *Username: LucianMaly* *Proposed subject of my contribution(s): for example https://wiki.centos.org/HowTos/Skype <https://wiki.centos.org/HowTos/Skype> and https://wiki.centos.org/HowTos/OS_Protection <https://wiki.centos.org/HowTos/OS_Protection> plus some others* *Proposed location of my

Here is a change we're instituting immediately to make it easier for corporations to contribute code changes to Samba whilst still retaining copyright ownership of the contributed code. Feel free to ask any questions on the samba-technical at samba.org list. We'd like to thank our lawyers at the Software Freedom Law Center for helping us to make this change. Regards, The Samba Team. ------------------------------------------------------------------- Samba is a proj...

Here is a change we're instituting immediately to make it easier for corporations to contribute code changes to Samba whilst still retaining copyright ownership of the contributed code. Feel free to ask any questions on the samba-technical at samba.org list. We'd like to thank our lawyers at the Software Freedom Law Center for helping us to make this change. Regards, The Samba Team. ------------------------------------------------------------------- Samba is a proj...

Hello all, I'd like to contribute to the CentOS wiki. Per these docs[0], I should email this list with the following information. Username: DanielFarrell Contribution subject: Update CBS Koji Poodle patch docs Contribution location: http://goo.gl/7Oe9QO (CBS HOWTO#Quickstart) I'd like to make the docs related to patching Koji for the Poodle exploit[1] generally more clear. For example,

Yep, Wolfgang picked up on the one thing I saw too. This is why I like having people review my stuff. I think it's a bit of a pity that str_offsets_base can point into the middle of a str_offsets contribution in some ways Actually I changed my mind after saying that in the review, and in this writeup I concluded that it cannot do that. str_offsets_base points to the element immediately

...ment this so that smbd can # operate as an authenticated user identity to operate on files that # live in the DCE Distributed Filesystem. # DCE_BASE = /opt/dcelocal # DCE_FLAGS = -DDFS_AUTH -I$(DCE_BASE)/include # DCE_LIBDIR = -L$(DCE_BASE)/lib # DCE_LIBS = # This is for Kerberos 5 authentication. Contributed by Nathan Neulinger # Univ. of Missouri - Rolla <nneul@umr.edu> # KRB5_BASE = /usr/local/krb5 # KRB5_FLAGS = -DKRB5_AUTH -I$(KRB5_BASE)/include # KRB5_LIBS = -L$(KRB5_BASE)/lib -ldes425 -lkrb5 -lcrypto -lcom_err # This is for Kerberos 4 authentication. Contributed by Johan Hedin # Royal Inst...

Hello Akemi, I have gone through your mail and provided link and this is my contribution details - the proposed subject of your Wiki contribution(s) :- Provide technical support to CentOS user - the proposed location of your Wiki contribution(s) :- Pune (India) Thanks & Regards, Gajanan Kankal On Sun, Dec 21, 2014 at 11:50 AM, Akemi Yagi <amyagi at gmail.com> wrote: >

Hi Guys, While updating es/ pages, noted that actually there are two Contribute pages. One in Contribute and other in HowToContribute. I wonder if we could reorganize that a bit. Maybe separate contribution needs by SIGs. Then create a Contribution index page where all those SIG's contribution pages be linked from ? It may be needed to create some SIGs in those areas where they don't

I wanted to make sure that everyone was aware of a slight change we''ve made to the process for open source contributions. For *trivial* contributions, we are no longer requiring a Contributor License Agreement (CLA). Note that for most contributions a CLA signature is still required. I''m also working on making the overall CLA process easier, but that will take a little more time

...d if checked out into tools/llgo would build as part of the regular LLVM build (with CMake only). We would be keeping llgo compatible with top-of-tree LLVM, although I imagine this would be less burdensome than the other subprojects as llgo is written in Go and depends on the Go bindings previously contributed to LLVM. llgo depends on certain third-party components, namely a copy of the Go standard library (libgo), a Go program analysis library (go.tools) and two library dependencies of the standard library (libbacktrace and libffi). These would be mirrored into the llgo repository under a third_party d...

Howdy, as you already know from my intro email, I'm working on CentOS Stream. I'd love to start publishing docs to wiki and therefore need edit access for the wiki.centos.org/contribute tree: could you grant it to me, please? My plan is to create a new document for it: wiki.centos.org/contribute/CentOSStream and then link to it from the contribute document - does that sound right?

...assignments, which means that the >> copyright for the code in the project is held by the respective contributors. >> Because you (or your company) >> retain ownership of the code you contribute, you know it may only be used under >> the terms of the open source license you contributed it under: the license for >> your contributions cannot be changed in the future without your approval. >> >> Because the LLVM project does not require copyright assignments, changing the >> LLVM license requires tracking down the >> contributors to LLVM and getting th...

...he >>>> copyright for the code in the project is held by the respective contributors. >>>> Because you (or your company) >>>> retain ownership of the code you contribute, you know it may only be used under >>>> the terms of the open source license you contributed it under: the license for >>>> your contributions cannot be changed in the future without your approval. >>>> >>>> Because the LLVM project does not require copyright assignments, changing the >>>> LLVM license requires tracking down the >>>...