August 2015 - Acme-se - mailman3.cels.anl.gov

Re: [ACME-SE] Force push on master on purpose
by Taylor, Mark A 27 Aug '15

27 Aug '15

Rob, Since you rewrote history, I think you need to send an email to acme-all, letting everyone know that if they made a branch between that period, they need to do something (probably reset --hard?), otherwise they will have a lot of trouble when they eventually try to merge there branch that started from a point that no longer exists on github. The message below is too cryptic for non git experts and only went to acme-se. It mentions a "force push", and the correct time period, but leaves out the important detail that branches made off of master during that period need to be redone. Related to this, Did this case warrant rewriting history? In such a large project like ACME, it would seem much safer to do a second commit that undoes these changes. Mark -----Original Message----- From: <acme-se-bounces(a)lists.mcs.anl.gov> on behalf of Robert Jacob <jacob(a)mcs.anl.gov> Reply-To: Robert Jacob <jacob(a)mcs.anl.gov> Date: Wednesday, August 26, 2015 at 9:08 PM To: "acme-se(a)lists.mcs.anl.gov" <acme-se(a)lists.mcs.anl.gov> Subject: [EXTERNAL] [ACME-SE] Force push on master on purpose > >FYI. > >Master was in a bad state after an inadvertent commit and this was fixed >with a force push to master (by me). > >The state was bad between 5:40pm CT and 9:52pm CT, Aug 26th. > >See the Git Help page on Confluence if you have questions. > >Rob > > > >_______________________________________________ >ACME-SE mailing list >ACME-SE(a)lists.mcs.anl.gov >https://lists.mcs.anl.gov/mailman/listinfo/acme-se

3 2

Re: [ACME-SE] Force push on master on purpose
by Taylor, Mark A 27 Aug '15

27 Aug '15

Hi Jeff, Thanks for the explanation - that makes sense. But folks (if any) that happen to have made a branch during that time will have to do more than just 'git pull'. Shouldn't we tell acme-all that? Mark -----Original Message----- From: jnjohnson <jnjohnson(a)lbl.gov> Date: Thursday, August 27, 2015 at 1:57 PM To: "Taylor, Mark A" <mataylo(a)sandia.gov> Cc: Robert Jacob <jacob(a)mcs.anl.gov>, "acme-se(a)lists.mcs.anl.gov" <acme-se(a)lists.mcs.anl.gov> Subject: [EXTERNAL] Re: [ACME-SE] Force push on master on purpose >Mark, > >We evaluated the possibility of doing a revert, but reverting merge >commits (which the bad commit was) was not practical in this case. >Rewinding the history of the master branch was the next least intrusive >thing we could do. And considering that anyone who branched from master >during the Bad Period would be in bad shape anyway (and noticeably so, >since the merge included new atmospheric code changes that probably >hadn’t been tested), we are willing to work with those who we determine >to have incorporated it. > >All folks have to do to realize the new history is what they should be >doing anyway, which is ‘git pull’ on their master branch before branching >from it. > >Jeff > >> On Aug 27, 2015, at 12:44 PM, Taylor, Mark A <mataylo(a)sandia.gov> wrote: >> >> Rob, >> >> Since you rewrote history, I think you need to send an email to >>acme-all, >> letting everyone know that if they made a branch between that period, >>they >> need to do something (probably reset --hard?), otherwise they will have >>a >> lot of trouble when they eventually try to merge there branch that >>started >> from a point that no longer exists on github. The message below is too >> cryptic for non git experts and only went to acme-se. It mentions a >> "force push", and the correct time period, but leaves out the important >> detail that branches made off of master during that period need to be >> redone. >> >> Related to this, Did this case warrant rewriting history? In such a >>large >> project like ACME, it would seem much safer to do a second commit that >> undoes these changes. >> >> Mark >> >> >> >> >> >> -----Original Message----- >> From: <acme-se-bounces(a)lists.mcs.anl.gov> on behalf of Robert Jacob >> <jacob(a)mcs.anl.gov> >> Reply-To: Robert Jacob <jacob(a)mcs.anl.gov> >> Date: Wednesday, August 26, 2015 at 9:08 PM >> To: "acme-se(a)lists.mcs.anl.gov" <acme-se(a)lists.mcs.anl.gov> >> Subject: [EXTERNAL] [ACME-SE] Force push on master on purpose >> >>> >>> FYI. >>> >>> Master was in a bad state after an inadvertent commit and this was >>>fixed >>> with a force push to master (by me). >>> >>> The state was bad between 5:40pm CT and 9:52pm CT, Aug 26th. >>> >>> See the Git Help page on Confluence if you have questions. >>> >>> Rob >>> >>> >>> >>> _______________________________________________ >>> ACME-SE mailing list >>> ACME-SE(a)lists.mcs.anl.gov >>> https://lists.mcs.anl.gov/mailman/listinfo/acme-se >> >> _______________________________________________ >> ACME-SE mailing list >> ACME-SE(a)lists.mcs.anl.gov >> https://lists.mcs.anl.gov/mailman/listinfo/acme-se >

2 1

Force push on master on purpose
by Robert Jacob 26 Aug '15

26 Aug '15

FYI. Master was in a bad state after an inadvertent commit and this was fixed with a force push to master (by me). The state was bad between 5:40pm CT and 9:52pm CT, Aug 26th. See the Git Help page on Confluence if you have questions. Rob

1 0

We have Homme!
by Foucar, James G 19 Aug '15

19 Aug '15

https://github.com/ACME-Climate/homme Steps: 1) I had to use bleeding-edge version of git and svn for the git-svn clone of Homme to work: % git svn --version git-svn version 2.5.0 (svn 1.8.13) 2) Do the clone % git svn clone https://svn-homme-model.cgd.ucar.edu/trunk 3) Purge large files 3.a) Install repo cleaner (https://rtyley.github.io/bfg-repo-cleaner/) 3.b) Purge large files: % java -jar /Users/jgfouca/Downloads/bfg-1.12.4.jar --strip-blobs-bigger-than 40M homme 4) Push to GitHub -Jim

1 0

New sprint
by Robert Jacob 19 Aug '15

19 Aug '15

Its time again to update/close JIRA tasks. New sprint starts later today. Rob

1 0

[Confluence] James Foucar mentioned you in "Re: Help: Testing"
by James Foucar (Confluence) 13 Aug '15

13 Aug '15

1 0

Fwd: [SIAM-CSE] Second Call for Participation: 3rd Workshop on Sustainable Software for Science Practice and Experiences (WSSSPE3)
by Robert Jacob 12 Aug '15

12 Aug '15

SIAM workshop of interest. -------- Forwarded Message -------- Subject: [SIAM-CSE] Second Call for Participation: 3rd Workshop on Sustainable Software for Science Practice and Experiences (WSSSPE3) Date: Thu, 6 Aug 2015 14:33:45 -0500 From: Sou-Cheng (Terrya) Choi <sctchoi(a)uchicago.edu> To: siam-cse(a)siam.org 3rd Workshop on Sustainable Software for Science Practice and Experiences (WSSSPE3) September 28-29, 2015, Boulder, CO http://wssspe.researchcomputing.org.uk/wssspe3/ (Co-located with 10th Gateway Community Environments (GCE15) Workshop <http://sciencegateways.org/upcoming-events/gce15/>) Progress in scientific research is dependent on the quality and accessibility of software at all levels and it is now critical to address many new challenges related to the development, deployment, and maintenance of reusable software. In addition, it is essential that scientists, researchers, and students are able to learn and adopt a new set of software-related skills and methodologies. Established researchers are already acquiring some of these skills, and in particular a specialized class of software developers is emerging in academic environments who are an integral and embedded part of successful research teams. WSSSPE provides a forum for discussing these challenges, including presenting both positions and experiences, as well as a forum for the community to assemble and act. The WSSSPE1 workshop (<http://wssspe.researchcomputing.org.uk/wssspe1>http://wssspe.researchcomputing.org.uk/wssspe1) engaged the broad scientific community to identify challenges and best practices in areas relevant to sustainable scientific software. WSSSPE2 (http://wssspe.researchcomputing.org.uk/wssspe2) invited the community to propose and discuss specific mechanisms to move towards an imagined future practice of software development and usage in science and engineering. WSSSPE3 will organize self-directed teams that will collaborate prior to and during the workshop to create vision documents, proposals, papers, and action plans that will help the scientific software community produce software that is more sustainable, including developing sustainable career paths for community members. These teams are intended to lead into working groups that will be active after the workshop, if appropriate, working collaboratively to achieve their goals, and seeking funding to do so if needed. Potential WSSSPE3 team activities, based on the breakout groups in WSSSPE2 and additional community suggestions, are: * Development and Community o Writing a white paper/review paper about best practices in developing sustainable software o Documenting successful models for funding specialist expertise in software collaborations o Creating and curating catalogs for software tools that aid sustainability (perhaps categorized by domain, programming languages, architectures, and/or functions, e.g., for code testing, documentation) o Documenting case studies for academia/industry interaction o Determining effective strategies for refactoring/improving legacy scientific software o Determining principles for engineering design for sustainable software o Create a set of guidance giving examples of specific metrics for the success of scientific software in use, why they were chosen, what they are useful to measure, and any challenges/pitfalls; then publish this as a white paper * Training o Writing a white paper on training for developing sustainable software, and coordinating multiple ongoing training-oriented projects o Developing curriculum for software sustainability, and ideas about where such curriculum would be presented, such as a summer training institute * Credit o Hacking the credit and citation ecosystem (making it work, or work better, for software) o Developing a taxonomy of contributorship/guidelines for including software contributions in tenure review o Documenting case studies of receiving credit for software contributions o Developing a system of awards and recognitions to encourage sustainable software * Publishing o Developing a categorization of journals that publish software papers (building on existing work), and case studies of alternative publishing mechanisms that have been shown to improve software discoverability/reuse e.g., popular blogs/websites o Determining what journals that publish software paper should provide to their reviewers (e.g., guidelines, mechanisms, metadata standards, etc.) * Reproducibility and testing o Building a toolkit that could allow conference organizers to easily add a reproducibility track o Documenting best practices for code testing and code review * Documentation o Develop landing pages on the WSSSPE website (or elsewhere) that enable the community to easily find up-to-date information on a WSSSPE topic (e.g., software credit, scientific software metrics, testing scientific software) *Workshop Format: * * Opening keynote TBA * Lightning talks Ã¢ï¿½ï¿½ *submissions welcome* (via EasyChair, see below) * Team sessions Ã¢ï¿½ï¿½ list of possible sessions above * Team progress report-back to plenary group * At the end of the workshop, teams will Ã¢ï¿½ï¿½pitchÃ¢ï¿½ï¿½ their ideas to the audience, possibly including some funders (who would not committed to funding anything, just providing feedback), including e.g., Moore, Sloan, Digital Science, NSF, NIH. *Call for Participation / Actions:* 1. Save the dates for WSSSPE3: 28-29 September, 2015, Boulder, CO 2. Submit lightning talks Ã¢ï¿½ï¿½ submit a 1-page PDF containing the talk title, author names, affiliations, and a short abstract via Easychair, http://bit.ly/wsssep3-submit, by 7 August, 2015 3. Get started on discussing and planning for team sessions by commenting on them at https://github.com/danielskatz/WSSSPE/issues (note: they are listed as GitHub issues, so you will need to signup for a GitHub account <https://github.com/join> if you donÃ¢ï¿½ï¿½t have one) 4. Join the WSSSPE mailing list to be sure to get further information on WSSSPE3 Ã¢ï¿½ï¿½ via http://bit.ly/wssspe-list *Travel Support:* Some limited travel support is likely to be available; please check the workshop web page <http://wssspe.researchcomputing.org.uk/wssspe3/travel-support/>. *Important Dates:* * Lightning talk submissions: 7 August 2015 (any time of day, no further extensions) * Workshop: 28-29 September 2015 * Post-workshop report writing (participation is open to all): 30 September 2015 *Organizers:* * Daniel S. Katz, d.katz(a)ieee.org <mailto:[email protected]>, University of Chicago & Argonne National Laboratory, USA * Gabrielle Allen, gdallen(a)illinois.edu <mailto:[email protected]>, University of Illinois Urbana-Champaign, USA * Sou-Cheng (Terrya) Choi, sctchoi(a)uchicago.edu <mailto:[email protected]>, NORC at the University of Chicago and Illinois Institute of Technology, USA * Neil Chue Hong, N.ChueHong(a)software.ac.uk <mailto:[email protected]>, Software Sustainability Institute, University of Edinburgh, UK * Sandra Gesing, sandra.gesing(a)nd.edu <mailto:[email protected]>, University of Notre Dame, USA * Lorraine J. Hwang, ljhwang(a)ucdavis.edu <mailto:[email protected]>, University of California, Davis, USA * Manish Parashar, parashar(a)rutgers.edu <mailto:[email protected]>, Rutgers University, USA * Erin Robinson, erinrobinson(a)esipfed.org <mailto:[email protected]>, Foundation for Earth Science, USA (local organizer) * Matthew Turk, matthewturk(a)gmail.com <mailto:[email protected]>, University of Illinois Urbana-Champaign, USA * Colin C. Venters, colin.venters(a)googlemail.com <mailto:[email protected]>, University of Huddersfield, UK

2 1

[Confluence] James Foucar mentioned you in "Re: Help: Testing"
by James Foucar (Confluence) 06 Aug '15

06 Aug '15

1 0

Sprint ending
by Robert Jacob 04 Aug '15

04 Aug '15

The current sprint is coming to an end and a new sprint will start tomorrow. Please update any JIRA tasks that you can: -Log any effort in the support tasks. -Close tasks that are completed. -Stop progress on tasks you are no longer working on. Rob

1 0