Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
dev:new_developer_wishlist [2018/03/23 10:52] – sandbergja | dev:new_developer_wishlist [2018/04/25 14:05] – [Wish List Items/Discussion] rjs7 |
---|
* **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). |