# SOME DESCRIPTIVE TITLE. # Copyright (C) 2017, OpenStack Developers # This file is distributed under the same license as the contributor-guide package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: contributor-guide \n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2021-06-20 08:22+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../source/organizations/index.rst:3 msgid "Contributing Organization Guide" msgstr "" #: ../../source/organizations/index.rst:6 msgid "What is the Contributing Organization Guide?" msgstr "" #: ../../source/organizations/index.rst:8 msgid "" "A guide outlining the base requirements and recommendations for employees " "looking to contribute to OpenStack." msgstr "" #: ../../source/organizations/index.rst:12 msgid "Recommendations" msgstr "" #: ../../source/organizations/index.rst:15 msgid "Developer Involvement" msgstr "" #: ../../source/organizations/index.rst:18 msgid "Why we need to send technical people into the community?" msgstr "" #: ../../source/organizations/index.rst:20 msgid "" "With technical people in the community, you will find it's easier to trigger " "development tasks or discussions in the community to get the best chance of " "integrating with your business/product plan." msgstr "" #: ../../source/organizations/index.rst:24 msgid "" "You need people to maintain your product, just as the community needs people " "to maintain projects in each release cycle to keep development going." msgstr "" #: ../../source/organizations/index.rst:27 msgid "" "There are multiple chances in each release cycle to trigger development " "tasks in the community. Bringing more technical decision to the community " "will help you get more feedback and guidelines from developers and operators " "globally. Also, help them to make better cycle goals which also be a benefit " "for you." msgstr "" #: ../../source/organizations/index.rst:33 msgid "How many people you should send?" msgstr "" #: ../../source/organizations/index.rst:35 msgid "" "Depends on your own plan, but try to cover the range of project services " "that you're using or plan to use for your services." msgstr "" #: ../../source/organizations/index.rst:38 msgid "Getting involved in these projects means you can:" msgstr "" #: ../../source/organizations/index.rst:40 msgid "Monitor the health of the project." msgstr "" #: ../../source/organizations/index.rst:41 msgid "Be involved in design and direction of the project." msgstr "" #: ../../source/organizations/index.rst:42 msgid "Being involved in and shape implementation discussions." msgstr "" #: ../../source/organizations/index.rst:43 msgid "Avoid carrying downstream patches." msgstr "" #: ../../source/organizations/index.rst:45 msgid "" "The more people you have working upstream, the better attention your feature " "will get. Providing more reviewers will definitely help merge your " "implementation to projects. Code review is a bottleneck for landing patches, " "more good reviews the faster code can land." msgstr "" #: ../../source/organizations/index.rst:51 msgid "How long they should be there?" msgstr "" #: ../../source/organizations/index.rst:53 msgid "" "The ideal answer is to give the technical people as much percentage of their " "time as you can give, and for as long as possible." msgstr "" #: ../../source/organizations/index.rst:56 msgid "" "If your company is large enough to have the choice, giving engineers more " "time to specialise and concentrate on specific areas tend to be more " "efficient than having engineers continually context switching as they have " "to wear multiple hats." msgstr "" #: ../../source/organizations/index.rst:61 msgid "" "Having engineers spending more time upstream helps everyone by providing " "continuous input and feedback to tasks that you set as high priority. But " "it's more then that, OpenStack relies on `peer review `_. From landing code to its governance, to function the project " "needs people in the community reviewing." msgstr "" #: ../../source/organizations/index.rst:68 msgid "" "Further, having engineers in the community long term will also keep the " "company ahead of the curve as they are embedded and engaged in the community " "rather then popping in and out." msgstr "" #: ../../source/organizations/index.rst:72 msgid "" "To put more simply, the more invested a company is in the community, the " "more likely they are to earn a place of influence." msgstr "" #: ../../source/organizations/index.rst:76 msgid "Why you need to sync with the technical community?" msgstr "" #: ../../source/organizations/index.rst:78 msgid "" "The community upstream is filled with passionate and intelligent people who " "all want what's best for the project. Being involved means you can help " "shape and improve the project." msgstr "" #: ../../source/organizations/index.rst:82 msgid "" "Better yet, instead of forking or adding downstream patches in your own " "products that you'd then need to carry, support and maintain, which can be " "very costly. You could push it upstream and get benefit from an entire " "community of developers improving and maintaining it with you. Effectively " "removing most, if not all of the additional cost and risk of maintaining it " "downstream." msgstr "" #: ../../source/organizations/index.rst:89 msgid "" "It will also be better tested than anything developed internally because it " "will be tested by the community and used more widely than just your " "customers." msgstr "" #: ../../source/organizations/index.rst:92 msgid "" "All these extra developers means more eyes on code finding, fixing, and " "improving the code. This means having a community of developers helping in " "the development and improvement of your own infrastructure." msgstr "" #: ../../source/organizations/index.rst:96 msgid "Remember many hands make light work." msgstr "" #: ../../source/organizations/index.rst:99 msgid "Technical" msgstr "" #: ../../source/organizations/index.rst:102 msgid "Code" msgstr "" #: ../../source/organizations/index.rst:104 msgid "Access to review.opendev.org for code review and code submission." msgstr "" #: ../../source/organizations/index.rst:106 msgid "Port 29428/tcp is the Gerrit SSH API." msgstr "" #: ../../source/organizations/index.rst:107 msgid "" "Port 443/tcp is also available to access gerrit but only recommended if " "opening port 29428 is not possible, as it requires generating a password in " "the gerrit interface rather than using ssh certificates, so is inherently " "less secure." msgstr "" #: ../../source/organizations/index.rst:112 msgid "" "https://docs.opendev.org/opendev/infra-manual/latest/developers." "html#accessing-gerrit-over-https" msgstr "" #: ../../source/organizations/index.rst:114 msgid "For more information on how we use gerrit see:" msgstr "" #: ../../source/organizations/index.rst:116 msgid ":ref:`what_is_gerrit`" msgstr "" #: ../../source/organizations/index.rst:117 msgid ":doc:`../code-and-documentation/using-gerrit`" msgstr "" #: ../../source/organizations/index.rst:120 msgid "Internet Relay Chat (IRC)" msgstr "" #: ../../source/organizations/index.rst:122 msgid "Access to chat.oftc.net port 6697/tcp (IRC communication)" msgstr "" #: ../../source/organizations/index.rst:124 msgid "If utilizing an IRC bouncer port 443, to the bouncer, may be used." msgstr "" #: ../../source/organizations/index.rst:125 msgid "See :ref:`setup-irc`." msgstr "" #: ../../source/organizations/index.rst:128 msgid "Suggestions" msgstr "" #: ../../source/organizations/index.rst:130 msgid "" "There are browser based IRC services, like irccloud, that will keep users " "connected and use the standard HTTPS (443/tcp)." msgstr "" #: ../../source/organizations/index.rst:133 msgid "" "If connectivity to certain ports are locked down or are a problem, a SOCKS " "server can be used to provide access." msgstr "" #: ../../source/organizations/index.rst:137 msgid "Email Consideration" msgstr "" #: ../../source/organizations/index.rst:139 msgid "" "Ability to receive E-mail from and send E-mail to addresses at lists." "openstack.org (mailing lists)" msgstr "" #: ../../source/organizations/index.rst:142 msgid "" "Mailing list can be high traffic, consider permitting use of external mail " "services to handle the intake from community mailing lists." msgstr "" #: ../../source/organizations/index.rst:145 msgid "" "Consider an exception for standard email footers on emails being sent to the " "community mailing lists" msgstr "" #: ../../source/organizations/index.rst:147 msgid "See :ref:`communication-mailing-lists`." msgstr "" #: ../../source/organizations/index.rst:150 msgid "Operating System (OS) Considerations" msgstr "" #: ../../source/organizations/index.rst:152 msgid "" "There are many components and projects related to running and developing " "OpenStack all of which run on top of Linux. So a developer will need:" msgstr "" #: ../../source/organizations/index.rst:155 msgid "" "Permission to run Linux and install other open source software on employer-" "supplied hardware." msgstr "" #: ../../source/organizations/index.rst:159 msgid "Technical Events" msgstr "" #: ../../source/organizations/index.rst:161 msgid "" "There are a number of technical events that are held where community, " "project, and cross-project planning and networking happen in person. " "Although this planning and networking does happen online outside these " "events you should consider sending developers along to be involved." msgstr "" #: ../../source/organizations/index.rst:166 msgid "Some technical events include:" msgstr "" #: ../../source/organizations/index.rst:168 msgid "Project Technical Gatherings (PTGs)" msgstr "" #: ../../source/organizations/index.rst:169 msgid "Summits and Forums" msgstr "" #: ../../source/organizations/index.rst:170 msgid "Operator meetups" msgstr "" #: ../../source/organizations/index.rst:172 msgid "" "For more information on such events see: https://www.openstack.org/community/" "events/" msgstr "" #: ../../source/organizations/index.rst:175 msgid "Non-Technical" msgstr "" #: ../../source/organizations/index.rst:177 msgid "" "OpenStack is a global community. Interaction with the community means " "working and interacting with people from different timezones and cultures, " "as such there are other non-technical recommendations that help facilitate " "engagement in the OpenStack community, these can be broken down into three " "areas: communication, culture and expectations." msgstr "" #: ../../source/organizations/index.rst:184 msgid "Communication" msgstr "" #: ../../source/organizations/index.rst:186 msgid "" "Being a global community, with members from across the globe being available " "to occasionally work, talk or meet outside of typical office hours is " "paramount." msgstr "" #: ../../source/organizations/index.rst:190 msgid "" "Some asynchronous communication mediums, such as email and gerrit, are " "heavily used, but at times these discussions can to be sped up by using more " "synchronous mediums such as:" msgstr "" #: ../../source/organizations/index.rst:194 msgid "IRC conversations" msgstr "" #: ../../source/organizations/index.rst:196 msgid "" "Working if developers from a different part of the globe may mean finding a " "time to chat on IRC when all parties are available." msgstr "" #: ../../source/organizations/index.rst:198 msgid "" "Likewise, when reviewing patches, talking with a patch author in channel can " "greatly speed up reviews especially for more complicated patches." msgstr "" #: ../../source/organizations/index.rst:201 msgid "IRC meetings" msgstr "" #: ../../source/organizations/index.rst:203 msgid "" "All projects have regular meetings on IRC. Most these meetings alternate " "between two different timezones. Sometimes however, it is advantageous to " "get all developers working on a certain feature or project to be in one " "place at the same time." msgstr "" #: ../../source/organizations/index.rst:208 msgid "Other" msgstr "" #: ../../source/organizations/index.rst:210 msgid "" "Other projects may choose other ways of communicating depending on the " "developers in question. But transparency is important. Anything discussed " "should be logged or minuted for the rest of the OpenStack project and world " "to see." msgstr "" #: ../../source/organizations/index.rst:217 msgid "Community Culture" msgstr "" #: ../../source/organizations/index.rst:219 msgid "Timezones" msgstr "" #: ../../source/organizations/index.rst:221 msgid "" "The OpenStack community is spread across the different timezones, so always " "try be transparent to the greater community and if using a synchronous " "communication system to make feature/project decisions, make sure you make " "it possible for asynchronous input from members in other timezones." msgstr "" #: ../../source/organizations/index.rst:225 msgid "" "Different timezones means different cultures, so be sensitive to these " "cultural differences. One example is to give non-native English speakers a " "chance to think and speak and if using a voice medium, please slow down." msgstr "" #: ../../source/organizations/index.rst:230 msgid "" "Titles held by community members are temporary and activities are not really " "linked to titles." msgstr "" #: ../../source/organizations/index.rst:233 msgid "Everyone is in this together and are working for a better OpenStack." msgstr "" #: ../../source/organizations/index.rst:234 msgid "" "Everyone who holds a title, such as PTL or a part of the technical committee " "are elected in. So titles are temporary." msgstr "" #: ../../source/organizations/index.rst:237 msgid "Forks are bad, contributing upstream is much better." msgstr "" #: ../../source/organizations/index.rst:239 msgid "" "citing articles about how maintaining forks is generally an expensive and " "painful process (via links to further reading on effective open source " "community involvement)" msgstr "" #: ../../source/organizations/index.rst:243 msgid "" "The community does not officially endorse Stackalytics, a contribution " "statistics gathering service hosted by Mirantis. The community does not " "encourage attempting to boost one's contribution statistics by proposing " "large quantities of low-value commits or voting on large numbers of change " "proposals without providing thoughtful reviews. Activities like this appear " "to other members of the community as an attempt to game the system and " "contributors who engage in this will often lose credibility for themselves " "and their employers in the community. Instead, contributors should try to " "engage deeply with a single project or a small number of projects to gain " "understanding of the software component and build relationships with the " "other contributors for that project." msgstr "" #: ../../source/organizations/index.rst:255 msgid "" "Focusing staff on particular project areas, or towards particular goals is " "more effective than asking them to track activity over many projects." msgstr "" #: ../../source/organizations/index.rst:259 msgid "Expectations" msgstr "" #: ../../source/organizations/index.rst:261 msgid "Permission to agree to the OpenStack ICLA (required)" msgstr "" #: ../../source/organizations/index.rst:262 msgid "Permission to occasionally work outside typical office hours" msgstr "" #: ../../source/organizations/index.rst:263 msgid "A process to clear contributions from IP point of view" msgstr "" #: ../../source/organizations/index.rst:264 msgid "Permission and budget to send contributors to events" msgstr "" #: ../../source/organizations/index.rst:265 msgid "Expectation of travel to at least some events - does not need to be all" msgstr "" #: ../../source/organizations/index.rst:267 msgid "" "Should be prepared to write permission letter/visa letters/necessary letters " "for getting visas" msgstr "" #: ../../source/organizations/index.rst:269 msgid "" "The letters/decisions made on travel should be given out, ideally weeks or " "more, in advance" msgstr "" #: ../../source/organizations/index.rst:271 msgid "" "Permission to agree with terms of becoming an Open Infrastructure Foundation " "Individual Member" msgstr "" #: ../../source/organizations/index.rst:274 msgid "Consider signing up as a contributing organization member" msgstr ""