Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • O org.eclipse.dash.handbook
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 154
    • Issues 154
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 3
    • Merge requests 3
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse Projects
  • Eclipse Dash
  • org.eclipse.dash.handbook
  • Issues
  • #16

Closed
Open
Created Jan 15, 2016 by Eclipse Webmaster@webmasterOwner

Document how projects can use GitHub, including issues, wiki, and releases

Submitted by Wayne Beaton @wbeaton

Link to original bug (#485964)

Description

We need to document how projects are expected to use GitHub. We have board approval for projects to use GitHub repositories and Issues with an understanding that the webmaster team is able to provide complete backups of the captured information thereby providing the necessary freedom of action.

Use of repositories is approved by the board of directors. This extends to the use of wiki which is effectively a Git repository that contains documentation.

The use of GitHub Issues is approved by the board of directors. The resolution indicates that PMC approval is required.

GitHub Releases can be used, but the PMI must be used as the canonical location for review documentation. Similarly, the EF-provided download server is the canonical location for distribution of project artifacts.

The handbook is probably the right home for this documentation, but I thought that I'd start the bug here to make sure that we've correctly captured the requirements.

Depends on

  • Bug 506836
  • Bug 517749
  • Bug 520706

Blocking

  • Bug 481771
Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent