Feature Request: Team public folders
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I'm sorry if this has been suggested before elsewhere; I searched but didn't find anything.
I think it would be really nice if there was a way for teams to have a public folder in addition to the current private folder under /keybase/team/.
This would allow teams to have a homepage served at keybase.pub and would allow them to put out public documents as well. (I'm mostly thinking of larger open-source dev teams when I suggest this, but I'm sure other teams would have a use for this.)
With that said, I'm not sure where this public folder would go. The most straightforward way to structure it (I would think) would be to have:
/keybase/team/public/[teamName]
/keybase/team/private/[teamName]
But that wouldn't be easy to switch to since we've already got:
/keybase/team/[teamName]
for private folders right now.
Is this something that you would be interested in doing?
Edit: grammar
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the existing private team-folder handling and the keybase.pub serving path, then determine the design needed for public team folders. Done would require an agreed folder layout, implementation, and coverage for public access and homepage serving.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100