Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • James Willenbring
  • Trilinos
  • Issues
  • #372

Closed
Open
Created May 19, 2016 by James Willenbring@jmwilleMaintainer

Revise new developer checklist

Created by: jwillenbring

CC: @trilinos/framework

Description:

The new developer checklist needs to be revised. In particular, to be up-to-date with the move to GitHub. Mentors can now decide when new students should get push access.

https://software.sandia.gov/trilinos/developer/sqp/checklists/newTrilinosDeveloper201508.txt

Tasks:

  1. Initial update of checklist [Done]
  2. Have set out for review and collect updates ... IN PROGRESS ...
  3. Publish checklist to final location ...
Assignee
Assign to
Time tracking