dev:new_developer_wishlist
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
dev:new_developer_wishlist [2012/02/05 07:28] – Warren's preliminary suggestions wlayton | dev:new_developer_wishlist [2012/05/18 13:10] – loriayre | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | Let's put our wish list items in here. We can discuss what is needed and who will work on developing them. | + | ====== Quicklinks to Contributions Pertinent to our Wish List Below ====== |
- | | + | |
+ | [[: | ||
+ | |||
+ | ====== Wish List Items/ | ||
+ | |||
+ | Let's put our wish list items in here. We can discuss what is needed and who will work on developing them. Anyone who would like to claim some items from this list can pull them out from the top and include them in a description of what they are going to document and list the "wish list" items that will be covered by their contribution below the description. | ||
+ | |||
+ | | ||
+ | * Building Evergreen | ||
+ | * Necessary prerequisites (packages, libraries) | ||
+ | * The build system (makefile structure, adding new make targets) | ||
+ | * Step-by-step troubleshooting: | ||
* Using git (the existing [[dev:git]] page is already very useful) | * Using git (the existing [[dev:git]] page is already very useful) | ||
* How to submit a patch | * How to submit a patch | ||
Line 8: | Line 19: | ||
* The bug tracking system | * The bug tracking system | ||
* Where to get help and find other developers | * Where to get help and find other developers | ||
- | * **The code itself** | + | * **Navigating the source |
- | * Description of languages toolkits used (expanding on [[dev: | + | |
- | * //Some developers will only want to work on the user interface, | + | |
- | * Overview of source tree structure | + | * Overview of source tree structure |
- | * Coding conventions | + | * Coding conventions |
- | * The database structure | + | * Style Guide |
- | * The build system | + | * Manual tests you can perform |
- | * Useful resources | + | * **API Reference** |
+ | * **Useful resources** | ||
+ | * See Dan Scott' | ||
+ | into how we're loading up the context objects from Perl but is a suitably licensed starting point at least. | ||
+ | |||
+ | * **Areas Claimed to Document** | ||
+ | * Overview of OpenSRF layer, Evergreen | ||
+ | * Working on the database | ||
+ | * Working on the middle layer | ||
+ | * Working on staff client | ||
+ | |||
+ | * **About funded projects** by Vicent Mas | ||
+ | I think the following points should be clarified in the "New Developer Starter Kit" document or be added to the Evergreen wiki or both: | ||
+ | |||
+ | * How to find out if there are available funded projects | ||
+ | * How to apply for a given funded project | ||
+ | * Once a developer has been assigned to a funded project what should she do before starting to work? | ||
+ | * to be in contract with the sponsor. How? | ||
+ | * to publish that she is working | ||
+ | * ... | ||
+ | * What to do if, during the development of the project, other developer (for instance a regular committer) implements a feature that covers the goal of the funded project? | ||
+ | * If, for some reason, a developer stops working on a funded project and the project becomes unassigned, how should the developer communicate this fact and make clear to other developers that the project status has changed to "not owned by anyone"? | ||
+ | |||
+ | It could be good to have this information | ||
+ | |||
+ | * **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. | ||
+ | * Change the formatting, fonts, etc. of the wiki. Reading some of the wiki pages, especially the " | ||
+ | * Code formatting style guide. |
dev/new_developer_wishlist.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1