The Forgotten Pull Requests (PR) of a New Breed of Sherpas in the Himalayas

Pull Requests (PR) are a huge topic on Github and here is a whole “BOOK” about it on github: https://help.github.com/categories/collaborating-with-issues-and-pull-requests/ Here is a short summary from me. 1. a developer is forced to create a fork (separate copy) of a public repository (called upstream repo) on github because the repo does not belong to the … Read moreThe Forgotten Pull Requests (PR) of a New Breed of Sherpas in the Himalayas

How NOT to write (OOP PHP) code

My comment on one of the files of SuiteCRM: https://github.com/salesagility/SuiteCRM/issues/3561 which was closed and kindly “put” aside (IGNORED basically!): https://trello.com/b/Ht7LbMqw/suitecrm-suggestion-box So… Expected Behaviour It has to extend/implement only SugarBean and some relevant functions. Many functions must be implemented by separate classes esp. email management functions related to POP3 and IMAP so that we can maintain … Read moreHow NOT to write (OOP PHP) code

How NOT to write (PHP) code

My comment on one of the files of SuiteCRM: https://github.com/salesagility/SuiteCRM/issues/3687 So… * todo: encapsulate logically related code into separate classes — e.g. use (API) controller class(es) — contact management API — folder management API (create, rename, delete, etc.) — email management API (read, compose drafts, send, relate to other entities etc.) — signature management API … Read moreHow NOT to write (PHP) code