Some details regarding github:
* Can use either a desktop client or the web client to access the repository
* Can have either a public repository (anyone can see it, but the owner
controls what commits are accepted; free), or a private repository (only
the owner and invited collaborators can see and commit to it; paid
subscription required) —
the document (i.e., “mvcr-spec).
text from the master copy creates a “fork" of the repository and after
editing, creates a pull request representing the proposed changes This
gives them their own space within which to makes changes. They might
call their copy “mvcr-spec-06"
github, where others may review the new file, add comments or issues, or
even create a branch from that to offer their own text.
forked copy will be “merged” back to the master file, and all changes
will be incorporated. We will have a history of what changed, and can
run a diff to highlight those changes at any point in time in the future.
requests back into the master, the WG chair or the WG editor should
create a copy on the Kantara wiki.
* This might be used to help keep track of suggestions that come out of
the call, and could serve as a way to make sure we have properly and
publicly responded to the issues and comments received, and indicate in
which version of the spec those comments were addressed
* We can decide upon a set of labels (e.g., diagram, use-case,
technical, editorial) to help structure the list of issues.
* Note that anyone can create and view issues on free public
repositories; only teammates and collaborators can create and view
issues on private repositories
|You may also want to use visual panels to communicate related information, tips or things users need to be aware of.|
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.