Great, I'm up to assist with whatever needed - test cases, documentation and so on. I think we should have a branch or repo in the main project. Easier to track things in one place then easier to push PRs if needed.
On Tuesday, 25 October 2016 13:07:48 UTC+1, Greg Sutcliffe wrote: > > Hi all, > > Over the past few months we've seen increasing interest in HA deployments, > especially in the IRC channel. We've also seen quite a few anecdotal > success stories, so it seems like we have some good hands-on experience in > the community now. > > I'd like to see if we can collaborate on writing up something for the > community to use for HA setups. I know a few people are already interested > in contributing to this effort (hopefully they'll chime in :P). The goal > would be to distil the community experiences into something generic - > step-by-step notes for specific tasks, choices/considerations to make for > solving given questions (eg where to terminate SSL) and so on. > > The two main questions in my head are: > > 1) Where should this live? Should we add a new section to the manual? Or a > "white papers" sort of thing? It feels like it could be a bit long-winded > compared to some of the shorter scenarios in the manual, but a whole new > section doesn't feel quite right either.... > > 2) Slightly driven by (1), but how should those interested collaborate? If > we do it in the website repo, we could open a WIP PR and then allow > multiple contributors on the PR (thanks for that recent feature GitHub!). > Otherwise I guess an Etherpad or similar could work... > > Thoughts? > -- > Greg > IRC: gwmngilfen > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
