Add whitepaper source code to github
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- latex
- Domain
- documentation
Research direction
The issue names no repository files or tests and only speculates that the whitepaper may use LaTeX. First determine where the whitepaper source is maintained and what format should be added; done means the source is present in the repository alongside the existing whitepaper PDF.
Written by the indexing model from the issue text.
Description
I assume you are using some source code (LaTeX?) and don't edit the whitepaper pdf directly.
- Dominant language
- No language data
- Stars
- 10
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from daostack/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
Move all documentation to this repoMay be free again @tsuberim claimed this 3100 days ago, and no pull request is open. Openenhancement
Similar issues
-
CalendarEventAttendance/get returns eventAttendanceStatus while the doc says attendanceStatusPossibly taken @chibenwa claimed this today. Openbug claude
Difficulty 1/5 Under an hour Newbie friendliness 90/100
linagora/tmail-backend#2697 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PyPSA/PyPSA#1976 · 1 comment ·
Maintainers usually reply within 1 day
-
C-bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
midnightntwrk/servicedesk#234 ·
Maintainers usually reply within 1 day
-
[Docs][openrouter]: README JWT example mints a token without exp, which the proxy always rejectsOpengood first issue help wanted
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day