Future of PubSweet
To do:
-
Create a gateway into the PubSweet ecosystem, https://gitlab.coko.foundation/pubsweet/pubsweet/: This will serve as the entry point for developers, with getting started instructions, descriptions of the building blocks of PubSweet, and as a central issue triage location (don't know which module is causing your issue or which module should be updated to add your feature - open an issue here). -
Check PouchDB project health (there seem to be no warning signs, project seems very actively developed, I misjudged it previously) -
Create a homepage for PubSweet -
Show examples of PubSweet (Editoria, Science Blogger). Use existing applications, don't develop new ones just for examples! (see Not to do section) -
Simple, single page, statically served
-
-
Rename modules for clarity -
pubsweet-backend ->
pubsweet-server -
pubsweet-frontend ->
pubsweet-client
-
-
Real-time collaboration support on PubSweet -
Maintain a read-only presence on GitHub for all of our repositories -
Organize a small PubSweet/INK hackathon (developing INK steps) for the PubSweet core team, Editoria team and INK team. Location is virtual and physical, sometime end of April. Suggestions? -
In the PubSweet core team, one of us will always be on support duty (supporting PubSweet apps development, writing documentation, answering support questions), so if you reach out on our Mattermost (https://mattermost.coko.foundation) #pubsweet channel, we can help out.
Not to do:
-
Don't develop features without demonstrable use cases
-
Don't develop and maintain demos (use apps that are already being developed with PubSweet)
-
Don't be afraid to ask