WIP/translation/codeofconductの添付ファイル:diff.html

添付ファイル 'diff.html'

ダウンロード

      '''Be considerate.''' Your Our work will be used by other people,people, and
      and you we in turn will depend on the work of others. Any decisiondecision we take
      you take will affect users and colleagues, and we expect you to
      should take those those
      consequences into account when making decisions. For Ubuntu has
      example, when we are in a feature freeze, please don't upload
      dramatically new versions millions of critical system software, as otherusers and thousands of contributors. Even if it's not
      people will be testing obvious at the frozen system time, our contributions to Ubuntu will impact the
      work of others.  For example, changes to code, infrastructure,
      policy, documentation, and not be expectingtranslations during a release may
      big changes.negatively impact others' work.

      '''Be respectful.''' The Ubuntu community and its members treat
      one another with respect. Everyone can make a valuable
      contribution to Ubuntu. We may not always agree, butbut disagreement
      disagreement it is no excuse for poor behaviour and poor
      poor manners. We might all all
      experience some frustration now and then,
      then, but we cannot allow that that
      frustration to turn into a personal
      personal attack. It's important to to
      remember that a community where people
      people feel uncomfortable or or
      threatened is not a productive one. We
      We expect members of the the
      Ubuntu community to be respectful when
      when dealing with other other
      contributors as well as with people outside
      outside the Ubuntu project, and project and
      with users of Ubuntu.

      '''Be collaborative.''' Collaboration is central to Ubuntu and Free Software are aboutto
      the larger free software community.  This collaboration involves
      individuals working with others in teams within Ubuntu, teams
      working with each other within Ubuntu, and individuals and teams
      within Ubuntu working together. Collaboration reduceswith other projects outside. This
      redundancy of work done in the Free Software world, collaboration reduces redundancy, and improves
      improves the quality of the software produced. You our
      work. Internally and externally, we should aim always be open to
      collaborate with other Ubuntu maintainers, as well as with thecollaboration. Wherever possible, we should work closely with
      upstream community that is interested projects and others in the work you do. Yourfree software community to
      coordinate our technical, advocacy, documentation, and other work.
      Our work should be done transparently and patches from Ubuntu shouldwe should involve as
      be given back to the community when they are made, not just when
      the distribution releases. many interested parties as early as possible.  If you wish to work on new code for
      existing upstream projects, at least keep those projects
      informed of your ideas and progress. It may not be possible we decide to
      get consensus from upstream or even from your colleagues abouttake a different approach than others, we will let them know early,
      the correct implementation of an idea, so don't feel obliged to
      have that agreement before you begin, but at least keep the
      outside world informed of your work, and publish your document our work in a
      way that allows outsiders to test, discuss and contribute to
      your efforts.inform others regularly of our progress.

      '''When you disagree,''' we disagree, we consult others. others.''' Disagreements, both
      political social and technical, happen all the time and the Ubuntu
      community is no exception. The It is important goal is not to avoidthat we resolve
      disagreements or and differing views but to resolve themconstructively and with the help
      constructively. You should turn to of the community and to the
      community process to seek advice and to resolve
      disagreements. processes. We have the Technical Board and Technical
      Board, the Community
      Community Council, both and a series of other governance
      bodies which will help to decide the right course for
      for Ubuntu. There are are
      also several Project Teams and Team Leaders,
      Leaders, who may be able to to
      help you us figure out which the best direction will befor Ubuntu. When our goals
      most acceptable. If you really want to go a different way, then
      differ dramatically, we encourage you to make a the creation of alternative sets of
      packages, or derivative distribution or
      alternative set of packages available distributions, using the Ubuntu Package
      Management framework, so that the community can try out yourtest new ideas and
      changes and ideas for itself and contribute to the discussion.

      '''When you we are unsure,''' unsure, we ask for help. help.''' Nobody knows
      everything, and nobody is expected to be perfect in the Ubuntu
      community (except of course the SABDFL). community. Asking questions avoids
      avoids many problems down the road, road,
      and so questions are
      are encouraged. Those who are asked should questions should
      be responsive and
      and helpful. However, when asking a question, care must must
      be taken to
      to do so in an appropriate forum. Off-topic questions, such as
      requests for help on a development mailing list, detract from
      productive discussion.forum.

      '''Step down considerately.''' Developers on Members of every project comecome and
      and go and Ubuntu is no different. When you leave somebody leaves or disengagedisengages
      from the project, in whole or in part, we ask that you they do so inin a
      a way that minimises disruption to the project. This means youthey
      should tell people you they are leaving and take the proper steps to
      ensure that others can pick up where you leave they left off.

添付ファイル

添付ファイルを参照するには、(下のファイル一覧にあるように)attachment:filenameと記述します。 [get]リンクのURLは変更される可能性が高いので、利用しないでください。
 All files | Selected Files: delete move to page copy to page

ファイルを添付する権限がありません。