7 Nov
2014
7 Nov
'14
12:13 p.m.
--Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 10/28, Brian Proffitt wrote: >=20 >=20 > ----- Original Message ----- > > From: "Karsten Wade" <kwade@redhat.com> > > To: infra@ovirt.org > > Sent: Wednesday, October 22, 2014 9:44:00 PM > > Subject: Re: Moving the wiki > >=20 > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > >=20 > > On 10/22/2014 11:19 AM, Michael Scherer wrote: > > > I still think the easiest way is to host our own setup. > >=20 > > Two notes: > >=20 > > * While there is definitely increased work for the Infra team in > > bringing it back from OpenShift, it also takes away some of the work > > being done to keep the OpenShift instance running well. > >=20 > > * We can always move back about as easily, such as when service > > features are at parity. > >=20 > > One of my concerns about OpenShift is that it now doesn't fit into the > > rest of the Infra scheme. If we're maintaining everything with > > Foreman/Puppet, for example, wouldn't it be a bit easier to bring the > > wiki server in to the same scheme? > >=20 > > It's like the problems we have with linode01.ovirt.org -- it's outside > > of the rest of the process Infra uses, so it's more likely problems > > will build up there until they get noticed. > >=20 > > - - Karsten > > - -- > > Karsten 'quaid' Wade .^\ CentOS Doer of Stuff > > http://TheOpenSourceWay.org \ http://community.redhat.com > > @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1 > >=20 > > iEYEARECAAYFAlRH+vAACgkQ2ZIOBq0ODEHEOwCgnGCFXO7tKVAoCM4YfkM0MYSs > > Er8AniDXc74R7QYk7s62s+nxZ1sTnn37 > > =3DIgIn > > -----END PGP SIGNATURE----- > > _______________________________________________ > > Infra mailing list > > Infra@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > >=20 >=20 > At Barak's request, I wanted to outline what should be the next phase for= oVirt.org, which may render this discussion moot. At least, the discussion= of shifting away from OpenShift, based on MediaWiki. We may want to migrat= e away for other reasons, but this will probably not be one of them. >=20 > oVirt.org is currently a MediaWiki site, and as such has a lot of (expect= ed) user collaboration. But that collaboration is not terribly organized, a= nd has no version control whatsoever. This makes it impossible for a group = like Content Services to scrape documentation content into their process, a= nd the end-user experience is also sub-optimal. >=20 > As an alternative, the OSAS design team wants oVirt.org to move over to M= iddleman-based when we revamp the site later this year. This would mean tha= t content would be stored on GitHub as markdown (MD) or HTML files, and the= n Middleman would be used to edit content locally as well as deploy onto th= e production site. This is currently how projectatomic.io handles=20 >=20 > Clearly, moving from a wiki to something static like a Middleman/GitHub s= olution is drastic, but Garrett LeSage and Tuomas Kuosmanen have come up wi= th an idea: prose.io is a third-party WYSIWYG editor that ties directly in = to GitHub repos. We will have links on the new oVirt.org site for each page= or section of a page that would open up the source content for that page/s= ection in prose.io, where a user could then edit the content and save it wi= th a simple GUI that would bypass the complexity of git commands. Depending= on the user's permissions, the edited content would be deployed immediatel= y on the site or held as a pull request for later approval. >=20 Feels strange to me having a project outside gerrit, that means having to setup and manage user acces also on github. Is there a way to use gerrit as base repo and only replicate to github as we currently do with other projects? Is the requirement of a web ui a strict one? Because I really like the idea of having the docs managed as code (reviews, git history and even ci) > An alternative to prose.io that Garrett has also proposed is bolting on a= n admin UI for editing blog posts using various existing components (mainly= for rich editing), so the entire thing could be done via a browser-based i= nterface (only available when running in development).=20 >=20 > From a user perspective, the experience is no different than using a wiki= =2E If we use prose.io, will have to have a GitHub account, but for our use= rs, that's not much or a hurdle, since they would have to have a MediaWiki = account on oVirt.org anyway.=20 >=20 > There are issues to narrow down with this plan (like how do oVirt.org use= rs add new pages?), but so far, it feels like a good solution and a positiv= e step away from MediaWiki. >=20 > Peace, > Brian >=20 > --=20 > Brian Proffitt >=20 > Community Liaison > oVirt > Open Source and Standards, Red Hat - http://community.redhat.com > Phone: +1 574 383 9BKP > IRC: bkp @ OFTC > _______________________________________________ > Infra mailing list > Infra@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra --=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUXKlsAAoJEEBxx+HSYmnD1lwIAItpTkWEH/R2yK3E+Cuq1YLc didExpJ5pDYP+OyuAxkZGjidVOS5EoFk4uoKYpgX5aBwSk1Y7OZ/kZ4rSJ7PoEly 3dP4xmXCyXIAvl3eS47PLvy4wNogGprNqzmUdfZ1V9wuuIpQLtUsatjd4ozFBY6c accpNB0/5n4cAxrP+W79zO7aHEL8gDSHJLMNQYaFJn2+Wk6fnIGJy0n06w4nw5H7 w6zN55XwMJQoR6Z8wGQULd3otVFXuDkHVso+N7MaAZUH/SaoaFo/Hn8stEpxbaCD uBU0SCwFVDOijydmVjmnaQiE8woQxeS2Pf6cUMH3t8Fu+CtzH7yPATmvMVqqMA8= =twIq -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi--