Future_of_M2___Infrastructure

---

title: Future of M2 / Infrastructure permalink: wiki/Future_of_M2_/_Infrastructure/ layout: wiki

List of on-going Projects and interaction

• List of projects page on the M2 page is not regularly updated
• There is a project page on the wiki that should now be used for that (http://wiki.macaulay2.com/Macaulay2/index.php?title=Main\_Page)
• There is an M2 mailing lists
• A separate google group Macaulay 2 announcements
• Statistics on package use by volunteering M2 users (automatic feedback)

List of publications

• Dan has installed a frame on the M2 page that does that automatically
• Christian: The manual update didn't work at his institute -> automatic works better
  • Update your references on the arXive
  • A wiki on how to do that on the arxive
  • Dan should a button on the M2 page for updating on the arXive
• List of publications should be more often updated on the M2 page

• What should we do about updating these?

Place to post personal M2 functions

M2 Documentation Wiki

• How to document?

• It would be nice to have feedback on Macaulay 2 introduction! (http://www.math.uiuc.edu/Macaulay2/share/doc/Macaulay2/BeginningMacaulay2/html/)

• Correcting errors/unclear stuff in documentation
  • So far it is done by mailing to Mike and Dan
  • Someone should be in charge of that
  • There should be a button on the bottom of every documentation page -> clicking on it allows you to send your complaints/corrections/suggestions to the person in charge with a clear reference to that page
  • David E.: A ticketing system would be good to see the status
  • Could be combined with a bug tracker
  • Also for packages, i.e. for EVERY documentation page
  • Button that goes to the googlegroup for general questions
  • There should be a page to look at all the current tickets sorted by doc/bug/whatever
  • There should be "rules" for the maintainers of using the tickets
  • We need a M2 doc page or wiki page on using the bug tracker

Package authors/maintainers

• The people working on a package might change over time
• How to give credit to those who have been working or are working on a package
• When submitting to JSAG, the paper will have the name of the authors who wrote this paper, the package has different description of "author types"

• There might be a beginning version and end version
• There should be a distinction and new fields in newPackage:
  • current developers
  • past developers
  • contributors
  • acknowledgement
  • which all people involved have to decide on

• code going into the engine needs new credit and acknowledgement
• Set up a distinction betweem current and past...

JSAG (http://j-sag.org/)

• Set up adenda to journal articles
• Broken links on the journal
• email sign-up does not work

• State of the journal:
  • Very well
  • Next announcement will be soon, because the editors are waiting for current submitted papers which are refereed
  • Plan is to extend to other software
  • good thing that works for the journal is the package structure

• Goal of the journal
  • Referee packages and evaluate packages

• What is published?
  • Cutting-edge research
  • contains a lot of mathematics
  • should "low-level mathematics" package be considered or should there be a second class of packages that come without a paper but are refereed and certified?
  • Deep in the computer science view but low mathematics is good
  • Deep in the quality of exposition is also considered

• What about recertification after many changes?

Misc.

• Remind everybody to use the googlegroup

http://groups.google.com/group/macaulay2

Thank you Amelia for your work on this workshop!!!!