Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basics of setting up a new client #114

Open
10 tasks
iteles opened this issue Sep 10, 2018 · 3 comments
Open
10 tasks

Basics of setting up a new client #114

iteles opened this issue Sep 10, 2018 · 3 comments
Assignees
Labels

Comments

@iteles
Copy link
Member

iteles commented Sep 10, 2018

We need to have a checklist for what happens once we have agreed to partner with a client on a project.

This needs to be expanded into a comprehensive readme, but here is a start:

  • Create and sign contracts
  • Book initial workshop
  • Set up Google Drive
  • Set up Gitter channel
  • Create client org if one doesn't exist
  • Invite team members to org (client and dwyl team)
  • Create dwyl dev team
  • Create repo for the project, initialise with a description, readme and call it something intelligent
  • Copy over our labels
  • Ensure dwyl dev team has correct permissions in repo
@rub1e
Copy link
Member

rub1e commented Oct 31, 2018

Just finishing this - @iteles

  • what's "create dwyl dev team" involve?
  • is there a magic label copier or is that manual?

rub1e added a commit that referenced this issue Oct 31, 2018
First draft - WIP

Ref: #114
@iteles
Copy link
Member Author

iteles commented Nov 15, 2018

Oops sorry, only just saw this:

  1. Setting up a dwyl dev team is creating a team within the Collaborators & teams setting at the org level if we have access or at the repo access if that's all we have access to and adding all dwyl developers to it. This means that at the repo level you can just provide the whole team with the correct permissions rather than having to add people individually
  2. https://label-sync.herokuapp.com/ as per https://github.com/dwyl/labels

@iteles iteles removed their assignment Nov 15, 2018
@rub1e rub1e removed the in-progress label Jan 16, 2019
@rub1e rub1e added the T2h label Jan 30, 2019
rub1e added a commit that referenced this issue Mar 13, 2019
Clarify labels and team member permissions, per #114 (comment)
@rub1e
Copy link
Member

rub1e commented Mar 13, 2019

PR: #132

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants