[CentOS-docs] How GSoC project can fit in to CentOS Docs

> 在 2015年8月4日，上午12:23，kunaal jain <kunaalus at gmail.com> 写道：
> 
> 
> Would start with the note that the basic project is complete. I would be releasing the prototype on a separate thread. But for the discussion sake the workflow will look like this :
> Authors contribute content in markdown format, on github.
> The pull request created gets mirrored to pagure thus saving dependency on github.
> Also the PR content is built using CI to preview how it looks.
> The PR is two way synced between the platforms, so that individual can use pagure or github.
> Once staff approves the post, website is built and deployed.
> 
> On Thu, Jul 30, 2015 at 8:55 PM, Karsten Wade <kwade at redhat.com <mailto:kwade at redhat.com>> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> There have been some questions about how the GSoC project interacts
> with the existing documentation work that happens around the wiki.
> 
> Let's get all the open questions in to this thread and discuss them.
> 
> Lei, Kunaal -- What other open questions do we have?
> 
> From my experience till now, CentOS community is little doubtful about the project. We continued project still, now that we have done the basics, would be great if CentOS tests it, and gives us suggestions. 

Yes, we are looking for suggestions to improve it.

>  
> Where things are published is still an open question for this group
> (centos-docs) to decide.
> 
> Agreed. Maybe a new site containing user curated how to do contents. CentOS doesnt have to officially endorse the content in this way.

Agreed.

> 
> For where to publish from the toolchain, if we want to keep all docs
> in the wiki, we should plan to have the tool output to MoinMoin wiki
> syntax so that one of the existing editors can copy/paste in to an
> existing or new wiki article. This wiki publishing would work for
> shorter form content.
> 
> Not sure about this. It adds a human effort in the toolchain. 

I agree with Kunaal. One of our goals is to provide an automated workflow. Maybe we can remove the “copy and paste” step and write a little tool to replace it ;)


Best regards,
Lei
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-docs/attachments/20150804/3a12202d/attachment-0002.html>