1--- 2title: Contributing 3order: 2 4created_at: 2010-10-10 21:08:27.249191 -07:00 5filter: 6 - erb 7 - markdown 8--- 9## Mailing lists 10 11For questions, answers, feedback and other general discussion please 12join the [mailing list][mailing-list]. Changes to the DCE/RPC source 13code will also be posted to there. 14 15## Reporting Bugs 16 17If you find a bug or have an idea for an enhancement, please open 18a [Trac ticket][trac]. 19 20## Projects 21 22There a lots of interesting project to work on in DCE/RPC. Here 23are some ideas: 24 25* Clean up dce_error_inq_text to use error_status_t and 26 dce_error_string_t parameters. 27 28* Not all errors are in the message catalogue, eg. 29 rpc_s_protseq_not_supported is missing. Need to find and 30 catalogue all errors. 31 32* Fix the IDL compiler so that [in] reference parameters are 33 declared with the const qualifier. 34 35* Add support for [out,unique] parameters as used in the spoolss 36 protocol. 37 38* Add launchd (Mac OS X) and systemd (Linux) support to rpcd. 39 40### Projects specific to Mac OS X 41 42* Implement a ncacn_mach transport for local RPC on Mac OS X. 43 44* Add instant-off support to the RPC runtime. 45 46* Replace the DCEThreads runtime with [libdispatch][libdispatch]. 47 48## Contributing Code 49 50We do not require copyright assignment, however we ask that you 51assert your rights to the code you contribute by filing a [Trac 52ticket][trac] with your contribution. 53 54If you are sending in modifications to existing DCE/RPC code, you 55agree by submitting your modifications that the modifications are 56licensed under the existing license terms of the files you are 57modifying (i.e. BSD License). Please also add your copyright (name 58and year) to the relevant files for modifications that include more 59than 10 lines of code. 60 61If you are submitting new files for inclusion in the DCE/RPC project 62hosted here which are written by you (no code copied from another 63source), you agree by submitting the files that your contributions 64are licensed under the BSD License. Please include your copyright 65(name and year) and the BSD License in your submitted files. 66 67If you are not the author of the modifications, you agree to include 68the original copyright notices and licensing terms with your 69submission, to the extent that they exist. If there wasn't a copyright 70notice or license in the original sources, please make a note of 71it. 72 73Generally, we can only take in contributions that are licensed under 74the BSD License in order to maintain license compatibility within 75the project. Contact us if you believe an exception is warranted, 76prior to submitting the code. 77 78## Licensing 79 80DCE/RPC code and documentation contributions must be licensed under 81the 3-clause BSD license below. 82 83 Copyright (c) 2010 Apple Inc. All rights reserved. 84 85 Redistribution and use in source and binary forms, with or without 86 modification, are permitted provided that the following conditions 87 are met: 88 89 1. Redistributions of source code must retain the above copyright 90 notice, this list of conditions and the following disclaimer. 91 2. Redistributions in binary form must reproduce the above copyright 92 notice, this list of conditions and the following disclaimer in the 93 documentation and/or other materials provided with the distribution. 94 3. Neither the name of Apple Inc. ("Apple") nor the names of its 95 contributors may be used to endorse or promote products derived from 96 this software without specific prior written permission. 97 98 THIS SOFTWARE IS PROVIDED BY APPLE AND ITS CONTRIBUTORS "AS IS" AND ANY 99 EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 100 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 101 DISCLAIMED. IN NO EVENT SHALL APPLE OR ITS CONTRIBUTORS BE LIABLE FOR ANY 102 DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 103 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 104 LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND 105 ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 106 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 107 THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 108 109[mailing-list]: http://lists.dcerpc.org/mailman/listinfo/dcerpc-dev 110[trac]: https://www.dcerpc.org/trac/newticket 111[libdispatch]: http://libdispatch.macosforge.org/ 112