On Tue, Dec 12, 2017 at 05:01:41PM +0100, Matthieu Huin wrote: > Hello, > > If the getting-started documentation effort is also aimed at end > users, I'd be happy to help Leif with this: we've written a quick > start guide for Software Factory explaining how to set up pipelines > and jobs with Zuul3, and this would probably be better hosted upstream > with minimal adaptations. Let me know if there's interest for this > (the storyboard item at > https://storyboard.openstack.org/#!/story/2001332 doesn't specify > which kind of doc is expected) and I can submit some patches to the > documentatoin. > I was just talking with leifmadsen about it this morning and we're going to organize a working group on docs in the coming days. With holidays coming up quick, it might be difficult to wrap things up before Christmas.
I know there already has been some discussion between Jim and Leif, plus myself and Leif documented in the etherpad[1]. Using Fedora and github, I believe the etherpad notes are correct. So the next steps are reformatting into RST and tuning the docs. TL;DR we have some docs, and jobs ran, now to make that a little more user friendly. [1] https://etherpad.openstack.org/p/zuulv3-quickstart > Best regards, > > MHU > > On Fri, Dec 8, 2017 at 9:25 PM, David Shrewsbury > <shrewsbury.d...@gmail.com> wrote: > > Hi! > > > > On Wed, Dec 6, 2017 at 10:34 AM, James E. Blair <cor...@inaugust.com> wrote: > > > > <snip> > > > >> > >> * Add finger gateway > >> > >> The fact that the executor must be started as root in order to listen on > >> port 79 is awkward for new users. It can be avoided by configuring it > >> to listen on a different port, but that's also awkward. In either case, > >> it's a significant hurdle, and it's one of the most frequently asked > >> questions in IRC. The plan to deal with this is to create a new service > >> solely to multiplex the finger streams. This is very similar to the > >> zuul-web service for multiplexing the console streams, so all the > >> infrastructure is in place. And of course, running this service will be > >> optional, so it means that new users don't even have to deal with it to > >> get up and running, like they do now. Adding a new service to the 3.0 > >> list should not be done lightly, but the improvement in experience for > >> new users will be significant. > >> > >> David Shrewsbury has started on this. I don't think it is out of reach. > > > > > > > > Indeed, it is not out of reach: > > > > https://review.openstack.org/525276 > > > > > > > > -- > > David Shrewsbury (Shrews) > > > > _______________________________________________ > > OpenStack-Infra mailing list > > OpenStack-Infra@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra _______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra