Hi Chapel Developers - In order to better keep track of proposed improvements for the Chapel, I've created a concept of Chapel Improvement Proposals or CHIPs. This idea mimics Python Enhancement Proposals (PEPs) or D Improvement Proposals (DIPs) if you are familiar with those.
CHIPs are meant for in-depth proposals and design documentation. Small feature requests can continue to be filed as .future files in Chapel's testing system. Discussions on any of these topics can continue on the mailing lists. Sometimes it is useful to use a documentation format to arrive at consensus on a language or library design issue. Here are the key features and benefits to using CHIPs: * Each CHIP is stored in version control as part of the Chapel project, and so the history of the CHIP will be automatically maintained. * As a proposal is discussed, the CHIP will be updated to reflect any decisions made on the matter. * CHIPs can record design decisions that have been made. Otherwise, it is hard to track all of the proposals and which ones are moving forward. PR #2017 (just merged) adds the CHIPs, CHIP 1 describing the process, as well as two other CHIPs that I have been working on (constrained generics and ZeroMQ integration). I also included a script to render the CHIPs as HTML files using the same mechanisms as chpldoc (so the same RST formatting works). Cheers, -michael ------------------------------------------------------------------------------ _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
