User Tools

Site Tools


dev:new_developer_wishlist

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
dev:new_developer_wishlist [2018/03/23 10:52] sandbergjadev:new_developer_wishlist [2022/02/10 13:34] (current) – external edit 127.0.0.1
Line 32: Line 32:
   * **API Reference**   * **API Reference**
   * **Useful resources**   * **Useful resources**
-  * See Dan Scott's information on developing the TPAC at [[http://bzr.coffeecode.net/2011/tpac_tutorial/]] - it does not yet dive +  * See Dan Scott's information on developing the TPAC at [[http://bzr.coffeecode.net/2011/tpac_tutorial/]] - it does not yet dive into how we're loading up the context objects from Perl but is a suitably licensed starting point at least.
-into how we're loading up the context objects from Perl but is a suitably licensed starting point at least.+
  
   * **Areas Claimed to Document**   * **Areas Claimed to Document**
Line 57: Line 56:
   * **Additional desiderata, from Scott Prater**   * **Additional desiderata, from Scott Prater**
     * It would be nice if a list of required **libraries** and software and their versions were made available, not just packages.  It would be much easier to port Evergreen to a different OS, or a different release of a supported OS, if developers knew what software within a package was necessary.  Once you know the library or utility that's required, discovering which package contains it and installing it for a given OS is trivial.     * It would be nice if a list of required **libraries** and software and their versions were made available, not just packages.  It would be much easier to port Evergreen to a different OS, or a different release of a supported OS, if developers knew what software within a package was necessary.  Once you know the library or utility that's required, discovering which package contains it and installing it for a given OS is trivial.
-    * Change the formatting, fonts, etc. of the wiki.  Reading some of the wiki pages, especially the "Contributing" page, is a bit like reading the fine print of an insurance contract.  More white space, smaller chunks of text would help tremendously.  See http://guides.rubyonrails.org/getting_started.html[[http://guides.rubyonrails.org/getting_started.html|Rails Guides]] for an example of documentation that's easy-to-read.+    * Change the formatting, fonts, etc. of the wiki.  Reading some of the wiki pages, especially the "Contributing" page, is a bit like reading the fine print of an insurance contract.  More white space, smaller chunks of text would help tremendously.  See [[http://guides.rubyonrails.org/getting_started.html|Rails Guides]] for an example of documentation that's easy-to-read.
     * Code formatting style guide.  Some formal rules on how code should be formatted would be great.  Configuration files for popular editors (vi, emacs, nano, bbedit, etc.) that developers could copy and use to automatically format the code for you according to the formal conventions would be even better (a second pass).     * Code formatting style guide.  Some formal rules on how code should be formatted would be great.  Configuration files for popular editors (vi, emacs, nano, bbedit, etc.) that developers could copy and use to automatically format the code for you according to the formal conventions would be even better (a second pass).
dev/new_developer_wishlist.1521816779.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.