User Tools

Site Tools


zzz_archive:opw

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
zzz_archive:opw [2018/04/24 16:35] – ↷ Page moved from archive:opw to zzz_archive:opw dbwellszzz_archive:opw [2022/02/10 13:34] (current) – external edit 127.0.0.1
Line 29: Line 29:
    * Applicants planning to work on a coding project are required to [[:contributing|submit a patch or point to a branch]] that addresses some problem or adds some small enhancement. [[http://bit.ly/Zsjz8F|Bite-size bugs]] are good candidates to tackle. Applicants will need to submit an SSH key to the git administrators and gain working access to the Evergreen git repository.  One can follow instructions on the [[dev:git#getting_commit_access_to_working_repositories|dev:git]] page, which contains other useful information on use of git for the project.    * Applicants planning to work on a coding project are required to [[:contributing|submit a patch or point to a branch]] that addresses some problem or adds some small enhancement. [[http://bit.ly/Zsjz8F|Bite-size bugs]] are good candidates to tackle. Applicants will need to submit an SSH key to the git administrators and gain working access to the Evergreen git repository.  One can follow instructions on the [[dev:git#getting_commit_access_to_working_repositories|dev:git]] page, which contains other useful information on use of git for the project.
    * Applicants planning to work on a documentation project should submit an improvement to the Evergreen documentation. [[http://bit.ly/WlmcXy|Bite-size documentation bugs]] are good candidates to tackle. Follow the intermediate-level instructions or the instructions for committing changes through the Evergreen working git repository.    * Applicants planning to work on a documentation project should submit an improvement to the Evergreen documentation. [[http://bit.ly/WlmcXy|Bite-size documentation bugs]] are good candidates to tackle. Follow the intermediate-level instructions or the instructions for committing changes through the Evergreen working git repository.
-   * Applicants planning to work on a User Interface should make a list of three ways a current interface in the Evergreen client could be improved, why each suggestion is beneficial, and documentation to solidify your position. These recommendations can be posted to the [[opw:ui_suggest|Evergreen wiki]].+   * Applicants planning to work on a User Interface should make a list of three ways a current interface in the Evergreen client could be improved, why each suggestion is beneficial, and documentation to solidify your position. These recommendations can be posted to the [[history:opw:ui_suggest|Evergreen wiki]].
  
 **Note:** Potential applicants are welcome to discuss alternate project contributions with their mentors. **Note:** Potential applicants are welcome to discuss alternate project contributions with their mentors.
zzz_archive/opw.1524602128.txt.gz · Last modified: 2022/02/10 13:34 (external edit)

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.