I've been thinking about moving some #WriteFreely development resources to their own dedicated space, instead of keeping everything so closely tied to Write.as.
Any thoughts? Interested in helping with this? https://discuss.write.as/t/separating-writefreely-from-write-as/1846
Interesting. Doesn't it create more time maintenance wise, and if so do you have the resources to spend that time?
Moving the GitHub repos wouldn't add any ongoing maintenance work, just the initial work reorganizing things. So we could handle that.
But separate API docs, developer resources, etc. would require extra ongoing work. Probably a little too early for that, resource-wise.
@write_as What kind of help do you need?
@aris We could definitely use help forking an API library like https://github.com/writeas/go-writeas, renaming it for WriteFreely, and ensuring it doesn't have any Write.as-specific functionality left in it.
We could also use help splitting up the writeas-cli repo into writefreely-cli, putting the bulk of the shared code there while maintaining the writeas-cli repo.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!