search for: contributions

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 create a new Contribution, but does not associate it with the Donor (me). So, I tried this (using the build method): contribution = me.contrib...

...inal_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, :integer t.column :type, :string t.column :position, :integer end Drawing on this article ... <http://blog.hasmanythrough.com/articles/2006/02/28/association-goodness>...

> > > > 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? > > Agent, actual, or apparent authority. All valid. Let's start with: In just about every country in the world, anyone contributing on behalf of their company ar...

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

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

...nisms described above, add a line that states: Signed-off-by: Random J Developer <random at developer.example.org> using your real name and the email address you sent the original email you used to send the Samba Developer's Certificate of Origin to us (sorry, no pseudonyms or anonymous contributions.) That's it ! Such code can then quite happily contain changes that have copyright messages such as : (C) Example Corporation. and can be merged into the Samba codebase in the same way as patches from any other individual. You don't need to send in a copy of the Samba Developer...

...nisms described above, add a line that states: Signed-off-by: Random J Developer <random at developer.example.org> using your real name and the email address you sent the original email you used to send the Samba Developer's Certificate of Origin to us (sorry, no pseudonyms or anonymous contributions.) That's it ! Such code can then quite happily contain changes that have copyright messages such as : (C) Example Corporation. and can be merged into the Samba codebase in the same way as patches from any other individual. You don't need to send in a copy of the Samba Developer...

...on in [0], I'd also like to request for a member of the admin group to create my homepage[2]. [0]: http://goo.gl/dzq0yU (CentOS wiki contribution docs) [1]: http://goo.gl/7Oe9QO (Contribution location, CBS HOWTO#Quickstart) [2]: http://wiki.centos.org/DanielFarrell Thank you for your time and contributions, Daniel Farrell Software Engineer, Red Hat SDN Team https://twitter.com/dfarrell07

...w, and in this writeup I concluded that it cannot do that. str_offsets_base points to the element immediately after the header. You can have multiple units sharing the (entire) same contribution, but there's no slicing. I think there'd be some point/benefit to being able to have multiple contributions in a DWO file, but I don't think it's /buggy/ that it's not allowed - just a possible future enhancement. The trick with having multiple contributions in a DWO is that the .debug_line.dwo section has no way to specify which contribution to use. I mean, you could identify which CU poin...

> Sorry, but in the first mail I forgot to attach the Makefile and I > forgot also to mention that I already tried the password handling in win95 > via the registry. > > De Boe Bart wrote: > > > Hello, > > > > I need to install Samba on a HP J210 HPUX 10.20. > > I downloaded and compiled version 1.9.18p10. > > > > Following problems are

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 to overhaul. You can see mor...

Hi all, I'd like to propose the contribution of a Go frontend subproject to the LLVM project, based on the existing llgo project at https://github.com/go-llvm/llgo . As with the previous contribution of the Go bindings, I have obtained permission from all llgo contributors whose code is part of this contribution, to contribute their changes to the LLVM project and relicense their changes

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?

...vm-dev <llvm-dev at lists.llvm.org> writes: > >> Hi all, >> >> Now that we’ve settled on the license legalese to get to, we need to start the process of relicensing. We’re still sorting through all of the details of what this will take, but the first step is clear: new contributions to LLVM will need to be under both the old license structure and the new one (until the old structure is completely phased out). From a mechanical perspective, this is pretty simple, but I want to make sure that the community is aware of this and has time to digest and discuss any concerns. >&g...

...m.org> writes: >>> >>>> Hi all, >>>> >>>> Now that we’ve settled on the license legalese to get to, we need to start the process of relicensing. We’re still sorting through all of the details of what this will take, but the first step is clear: new contributions to LLVM will need to be under both the old license structure and the new one (until the old structure is completely phased out). From a mechanical perspective, this is pretty simple, but I want to make sure that the community is aware of this and has time to digest and discuss any concerns. >&g...