Hi the CentOS Cloud images and other things are now built from end to end automated pipelines, but the wiki content corresponding to them isnt. Is there something that can be used to do this automation ? I have done some stuff many many years ago, via directly mangling content on the wiki objects, but that might not be the best way forward. thoughts ? Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc
On 21/02/18 22:58, Karanbir Singh wrote:> Hi > > the CentOS Cloud images and other things are now built from end to end > automated pipelines, but the wiki content corresponding to them isnt. Is > there something that can be used to do this automation ? > > I have done some stuff many many years ago, via directly mangling > content on the wiki objects, but that might not be the best way forward. > > thoughts ? > > > Regards >That's a good question, as we'll also have to migration for moinmoin if we can't find a support path to migrate to supported version anyway. So first question (already asked on the list) : is there a way to get in touch with moin people willing to help/assist us ? (as their upgrade tool wasn't working to test migration from 1.6 to 1.7) And then too : is there a way to consume a kind of API for moin that would then meet the "content management via automation" requirement. Or do we have to also investigate directly another solution (like mediawiki) and so migration ? -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos-docs/attachments/20180221/9a1688f3/attachment.sig>
On 21/02/18 22:30, Fabian Arrotin wrote:> That's a good question, as we'll also have to migration for moinmoin if > we can't find a support path to migrate to supported version anyway. > So first question (already asked on the list) : is there a way to get in > touch with moin people willing to help/assist us ? (as their upgrade > tool wasn't working to test migration from 1.6 to 1.7)it would be good if someone on the docs team ( or docs focused could take this up, I am far too removed from implementation at this point to drive that conversation productively ). Other than that, +1 to engage moin upstream> And then too : is there a way to consume a kind of API for moin that > would then meet the "content management via automation" requirement. Or > do we have to also investigate directly another solution (like > mediawiki) and so migration ?does media-wiki have an api ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc