You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 16, 2023. It is now read-only.
As we all know paperless development is rather slow these days with may merge requests being stuck and no changes in the official repository for six months now.
I wonder if it's worth thinking about splitting paperless into multiple (sub)-repositories. At least for me the fact that everything is in one big repository is kind of intimidating to start submitting any patches or even think about maintaining my own forked repository.
I am thinking about at least seperate repositories for:
The Angular Frontend
The Django Backend
The glue code in between (ansible scripts and auxilary docker stuff)
Both the front- and backend repositories could then include the things needed to either "install manually" or "create a container" and everything else could be in the third repository.
I would also hope that moving away from the existing "multi technology stack monorepo" would help better automated testing of the individual parts.
What do you think? Would this lower your barrier to entry to contribute to paperless-ng?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
As we all know paperless development is rather slow these days with may merge requests being stuck and no changes in the official repository for six months now.
I wonder if it's worth thinking about splitting paperless into multiple (sub)-repositories. At least for me the fact that everything is in one big repository is kind of intimidating to start submitting any patches or even think about maintaining my own forked repository.
I am thinking about at least seperate repositories for:
Both the front- and backend repositories could then include the things needed to either "install manually" or "create a container" and everything else could be in the third repository.
I would also hope that moving away from the existing "multi technology stack monorepo" would help better automated testing of the individual parts.
What do you think? Would this lower your barrier to entry to contribute to paperless-ng?
--
sven
Beta Was this translation helpful? Give feedback.
All reactions