Whether you have a question, an issue, a feature request, or desire to help out
with the software engineering, go-fed welcomes you!
- Help, I have a question!
- Help, I found a bug!
- Whoa, I have a great idea!
- Beep boop, I want to contribute code!
- FAQ
- Contributors
The issues section of the repositories is generally not the place to ask questions. However, it is worth checking the existing issues to see if an existing bug or feature request provides enough context to answer the question.
For direct support, the best way to engage is to reach out on the Fediverse
(such as on Mastodon) to @cj@mastodon.technology.
That will be a direct communication to myself and will provide visibility to
others who are invested in the ActivityPub Fediverse.
In the future, there will be a website hosting better documentation and a tutorial for this library. My apologies that it is not available at this time.
The issues section is made just for you! Please check the
existing issues to see
if it has already been filed. If not, please file a new one with the
bug issue label.
The issues section is made just for you! Please check the
existing issues to see
if the idea has already been proposed. If not, please file a new one with the
feature request issue label.
Great! Please start participating in discussions on various bugs and feature
requests. For more casual discussions, reach out on the Fediverse at
@cj@mastodon.technology.
Here's a list of common or known issues.
Yes!
The vocab and streams packages are code generated on order of hundreds of
thousands to a million lines long. If using Go 1.9 or before, use go install
or go build -i to cache the build artifacts and do incremental builds.
Additionally, see #42.
Donations are strictly viewed as tips and not work-for-hire:
In order of first commit contribution.
- cjslep
- 21stio