Follow

I've been thinking about moving some development resources to their own dedicated space, instead of keeping everything so closely tied to Write.as.

Any thoughts? Interested in helping with this? discuss.write.as/t/separating-

· · Web · 2 · 5 · 5

@write_as
Interesting. Doesn't it create more time maintenance wise, and if so do you have the resources to spend that time?

@darius @sexybiggetje Definitely a good point.

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.

@aris We could definitely use help forking an API library like 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.

Sign in to participate in the conversation
Writing Exchange

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!