On feature workflow

Like NethServer, other projects exist on GitHub and are splitted between multiple sub-repositories: they use a “master” repository for issue tracking and wiki. The other sub-repos have both wiki and issue tracker disabled.

I’m evaluating also a nice Kanban board for GitHub: waffle.io This is the Nethgui view.

By now the Redmine instance is a dedicated machine on DigitalOcean. Sometimes hangs, and requires updates and maintenance. I’m not very happy of it, and I’m looking around for other possible solutions…

I understand your worries about cloud services: like any other service, we must set up a backup strategy if the bad day will come. About the code, wiki, and web pages data: they are just git repositories, and the backup is a trivial git fetch. The PR, issues and comments are accessible through the API and require a specific client. A quick “github backup” search shows this is a common concern!

Please, let’s discuss further! I’d like to hear also other opinions on tools and workflow :wink: