Where to put these?

[JacquesCarette]

I was googling around and found some potentially interesting papers. Not sure the best place to put them, so here we go:

• [correlation of software metrics, but also definitions, etc ] https://www.researchgate.net/profile/Md_Abdullah_Mamun4/publication/321091593_Correlations_of_software_code_metrics_an_empirical_study/links/5af19db2458515c283758860/Correlations-of-software-code-metrics-an-empirical-study.pdf
• An Empirical Study of the Relationships between Code Readability and Software
  Complexity
• The Correlation among Software Complexity Metrics with Case Study
• Software Metrics for Predicting Maintainability

[smiths]

Those look like good papers @JacquesCarette. I've been putting interesting papers in the se4sc repo (https://gitlab.cas.mcmaster.ca/SEforSC/se4sc/tree/git-svn/SciCompAndSoftEngPapers), and probably more importantly, I've been adding them to the References.bib file (https://gitlab.cas.mcmaster.ca/SEforSC/se4sc/blob/git-svn/SciCompAndSoftEngPapers/References.bib).

The good thing about this approach is that we can just add our students to the se4sc repo, and then they can see the papers and reuse the bibtex entries. I haven't really imposed much structure, but we could get in the habit of separate bib files for separate topics. The bad thing about this approach is that to get the references, you get all of the se4sc repo, which may not be relevant. Also, for those that actually want something from the se4sc repo, they may not want all of the references. (I ran into that problem recently with Alan when inadvertently cloned the entire se4sc repo.) I've also had a problem with sharing these resources with students outside of our research group, like the students in my cas741 class.

My proposal is that we create a new repo on GitLab, open to anyone in CAS (but not the public). In this new repo we put all of our papers of mutual interest. We can use different bib files to organize them, if we want. We could use subfolders too, but I think a flat model is fine, as long as the bib entries are made. For some papers, we probably just need the bib entry. If we are confident that the link will continue to work, we can just include a link to the resource in the bib file.

What do you think?

[smiths]

@Ao99, can you please add the references that @JacquesCarette to the following repo:

https://gitlab.cas.mcmaster.ca/smiths/pub/blob/master/README.md

These look like good references, and it would be nice to share them with our entire research group. The next time this comes up, we'll have to be sure to assign it to someone else, to spread the workload. 😄

Once you have done this, you can close this issue.

[Ao99]

@smiths
I updated the reference.bib and pushed it to the repo.

[smiths]

Thank you @Ao99. This is very helpful.

In the future, please use the natbib style (author year) for citation names. I had to correct all of the citation names. They should be in the form of AuthorYEAR. If there are two authors, the form is Author1Author2YEAR. If there are more than 2 authors, it should be in the form AuthorEtAlYEAR. (If this leads to duplicates, you can put something after the name to disambiguate them.

Also, when it is an external repo that is being changed, please include a link for traceability purposes, like this one:

https://gitlab.cas.mcmaster.ca/smiths/pub/commit/4567601ff0370fcc97a245f33965d8c17f862e86