-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should add Well-Understood paper to front page description #3360
Comments
@JacquesCarette Dr.Carette, can you provide more information? |
Reason it out. If you look around, you'll find that paper, and you'll also find how the old position paper is referenced on the front page. |
@smiths I am still confused about which paper it is, because there are lots of publications inside the folder. |
@daijingz you might not be looking in the right folder. You should be able to find the correct paper in the Papers folder. |
@JacquesCarette @smiths Dr.Carette and Dr.Smith, I guess this is what you designed to do: You want to add a link referring to the original Well Understood Paper. Additionally, If you mean adding some descriptions, then I feel it is unnecessary because there are existing words saying about it. Inside your requirements, the "old position paper" is the published essay "Generated Software for Well-Understood Domains". I just used the original way to add the link through the front page. |
@daijingz Yes, that's the desired outcome. You do not need to explain the contents of the paper in the front page description, as you note. The "old position paper" is not the "Generating Software for Well-Understood Domains" paper, it is the ICSE paper, and that is already linked in the README.md file. The "Generating Software for Well-Understood Domains" paper is the paper this issue refers to, which needs to be linked from the front page description. You can add a link to it to the README.md (perhaps hyperlinked at the first reference to |
|
Closed in #3860 |
Right now the main thing we link to is the old position paper.
The text was updated successfully, but these errors were encountered: