Talk:Chapel (programming language)

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
???	This article has not yet received a rating on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.

Notability

Every product article needs reliable independent sources WP:RS to establish notability WP:N as required by WP:GNG and WP:CORPDEPTH.

The sources cited here are weak. I found the first one (Modular programming languages: 7th Joint Modular Languages Conference) on Amazon but according to the table of contents, the cited page 20 is in the middle of an article titled, "Event-Based Programming Without Inversion of Control", by Philipp Haller and Martin Odersky; David E. Lightfoot, named as the author is the volume editor. I wasn't able to find the article yet, but this sounds like a mention.

The second one (Future Information Technology, Part I: 6th International Conference) is better. It hasn't been released yet but after searching, I found it online; I'll update the reference in the article. And as a primary source, the sourceforge link is useless for establishing notability. I would prefer to see a second good source.

I'm also concerned that the article appears to largely paraphrase the Chapel Overview on the Cray site for the purpose of promoting WP:PROMOTION a future product (e.g., "It is being developed as part of the Cray Cascade project") WP:CRYSTAL. Msnicki (talk) 23:35, 16 August 2011 (UTC)[reply]

Some Proposed Changes

It is requested that an edit be made to the semi-protected article at Chapel (programming language). (edit · history · last · links · protection log)

This template must be followed by a complete and specific description of the request, that is, specify what text should be removed and a verbatim copy of the text that should replace it. "Please change X" is not acceptable and will be rejected; the request must be of the form "please change X to Y".

The edit may be made by any autoconfirmed user. Remember to change the |answered=no parameter to "yes" when the request has been accepted, rejected or on hold awaiting user input. This is so that inactive or completed requests don't needlessly fill up the edit requests category. You may also wish to use the {{ESp}} template in the response. To request that a page be protected or unprotected, make a protection request.

I have a conflict of interest with Chapel, so cannot make these changes myself, but propose the following improvements:

updating the external link to point to Chapel's GitHub repository (https://github.com/chapel-lang/chapel) rather than the SourceForge repository which ceased to be the primary project repository in 2014.
fixing the formatting of, or removing, the trademark (TM) symbols on the references to the Cray MTA / XMT extensions to C and Fortran in the "influenced by" section on the sidebar. In my Chrome browser on my laptop, they appear as "Cray MTATM /XMTTMextensions to..." rather than "Cray MTA (TM) / XMT (TM) extensions to..."
updating the "first appeared" date on the sidebar to an earlier year. 2003 is when the project started (http://chapel.cray.com/publications/PMfPC-Chapel.pdf) and was publicly announced. The earliest commits to the source repository were in 2004 (https://github.com/chapel-lang/chapel/graphs/contributors), the first by-request release was in 2006 (http://chapel.cray.com/publications/PMfPC-Chapel.pdf), and the first public release was in 2008 (https://github.com/chapel-lang/chapel/blob/master/CHANGES.md#version-08). I'm not sure what the current 2009 date refers to, but it seems misleadingly recent.
updating the introductory text to refer to the DARPA HPCS program (which wrapped up in 2012) as where Chapel originated from, but not what drives it today (http://chapel.cray.com/publications/PMfPC-Chapel.pdf, http://chapel.cray.com).
adding a reference to the Chapel Chapter from MIT Press' "Programming Models for Parallel Computing" (https://mitpress.mit.edu/programming-models-parallel-computing) to the "Further Reading" section (this is the PMfPC-Chapel.pdf document I referred to in the previous bullet).

Thanks for your consideration. 136.162.66.1 (talk) 04:07, 16 September 2016 (UTC)[reply]

@136.162.66.1: Partly done:

Replaced Template:SourceForge with Template:GitHub in external links. (Special:Diff/741739593)
Formatted infobox influenced by section, dropped trademark notations and wikilinked to articles. (Special:Diff/741740560)

As for the other three points I believe most of the statements are true. Programming Models for Parallel Computing is a primary source, as the book author Bradford L. Chamberlain seems to be a Principal Engineer at Cray Inc. I will hold this edit request for another review by another author. 80.221.159.67 (talk) 10:55, 29 September 2016 (UTC)[reply]