Update TEAM_COLLABORATION_GUIDE.md
Browse files- TEAM_COLLABORATION_GUIDE.md +12 -4
TEAM_COLLABORATION_GUIDE.md
CHANGED
|
@@ -18,7 +18,7 @@ For hackathon submission purposes, you MUST document your team in the Space's RE
|
|
| 18 |
|
| 19 |
### Steps:
|
| 20 |
|
| 21 |
-
1. **Edit the Team Section in README.md**
|
| 22 |
|
| 23 |
The Team section is already added to your README. Update it with your actual team information:
|
| 24 |
|
|
@@ -61,13 +61,16 @@ Since your Space is owned by the **MCP-1st-Birthday organization**, team members
|
|
| 61 |
1. **Join the Organization:**
|
| 62 |
- Go to https://huggingface.co/MCP-1st-Birthday
|
| 63 |
- Click **"Request to join this org"** (top right)
|
| 64 |
-
- Fill out the registration form
|
| 65 |
-
|
| 66 |
|
| 67 |
2. **Verify Access:**
|
| 68 |
-
- Once
|
| 69 |
- Organization members with "write" or "contributor" roles can collaborate
|
| 70 |
|
|
|
|
|
|
|
|
|
|
| 71 |
### Option B: Direct Collaborator Access
|
| 72 |
|
| 73 |
If you have admin rights to your Space:
|
|
@@ -81,6 +84,9 @@ If you have admin rights to your Space:
|
|
| 81 |
- Set their permission level (read/write/admin)
|
| 82 |
- Send invitation
|
| 83 |
|
|
|
|
|
|
|
|
|
|
| 84 |
---
|
| 85 |
|
| 86 |
## Method 3: Collaborate via Pull Requests (SAFEST)
|
|
@@ -102,6 +108,8 @@ Team members can contribute without direct write access using Pull Requests.
|
|
| 102 |
- Go to Space Settings
|
| 103 |
- Ensure "Pull Requests" are enabled
|
| 104 |
|
|
|
|
|
|
|
| 105 |
---
|
| 106 |
|
| 107 |
## Method 4: Share Git Credentials (NOT RECOMMENDED)
|
|
|
|
| 18 |
|
| 19 |
### Steps:
|
| 20 |
|
| 21 |
+
1. **Edit the Team Section in README.md** (This is the most simple and preferred way)
|
| 22 |
|
| 23 |
The Team section is already added to your README. Update it with your actual team information:
|
| 24 |
|
|
|
|
| 61 |
1. **Join the Organization:**
|
| 62 |
- Go to https://huggingface.co/MCP-1st-Birthday
|
| 63 |
- Click **"Request to join this org"** (top right)
|
| 64 |
+
- Fill out the registration form provided to get eligible for free credits.
|
| 65 |
+
|
| 66 |
|
| 67 |
2. **Verify Access:**
|
| 68 |
+
- Once your team members have joined the HF Org, they'll automatically have access based on organization permissions
|
| 69 |
- Organization members with "write" or "contributor" roles can collaborate
|
| 70 |
|
| 71 |
+
3. **Add team member usernames to app's readme**:
|
| 72 |
+
- same as [above](#method-1-add-team-members-via-readme-documentation-easiest)
|
| 73 |
+
|
| 74 |
### Option B: Direct Collaborator Access
|
| 75 |
|
| 76 |
If you have admin rights to your Space:
|
|
|
|
| 84 |
- Set their permission level (read/write/admin)
|
| 85 |
- Send invitation
|
| 86 |
|
| 87 |
+
3. **Add team member usernames to app's readme**:
|
| 88 |
+
- same as [above](#method-1-add-team-members-via-readme-documentation-easiest)
|
| 89 |
+
|
| 90 |
---
|
| 91 |
|
| 92 |
## Method 3: Collaborate via Pull Requests (SAFEST)
|
|
|
|
| 108 |
- Go to Space Settings
|
| 109 |
- Ensure "Pull Requests" are enabled
|
| 110 |
|
| 111 |
+
4. **Add team member usernames to app's readme**:
|
| 112 |
+
- same as [above](#method-1-add-team-members-via-readme-documentation-easiest)
|
| 113 |
---
|
| 114 |
|
| 115 |
## Method 4: Share Git Credentials (NOT RECOMMENDED)
|