similar to: GSOC proposal for Implement and create new documentation toolchain

Hi guys, I am Kunal Jain from India doing my undergraduate studies in Computer Science from Indian Institute of Technology Guwahati (IITG). I and Lei will be creating a new toolchain that will lower the barrier for contributing new content under the mentor-ship of Karsten this summer. I look forward working with you guys. More details :

Hi guys, I have submitted my proposal on google-melange. I have been active in discussion regarding this on centos-docs as well with Karsten. I have created a small demo tool chain, to have a clarity on how process will flow and how site can be generated on git commits and deploying to hosting platform. You can find the code as well as the live version at :

Hi Kartsen, you'll have my proposal by the end of the day. I am not good at writing content. :( I have sorted out all the technicalities though. Regards, Kunal Jain On Tue, Mar 24, 2015 at 5:48 AM, Karsten Wade <kwade at redhat.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Kunaal: > > I know you are still researching, but I think you may have

On Jun 4, 2015 12:17 PM, "Karsten Wade" <kwade at redhat.com> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 06/01/2015 10:30 PM, Lei Yang wrote: > > Hi, > > > > As discussed earlier about the workflow, I and Kunaal will need a > > server space to host Bugzilla, a test repository at Github + a git > > repository at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to welcome the two Summer of Code students who will be building different parts of the new CentOS documentation toolchain. * Kunal Jain * Lei Yang Students -- welcome again, and thank you for your work this far in helping define the project. Now we have the pleasure of working on the two new scopes that will work interdependently and

Hi, Lei and I have been working on the project, based on community input. We have implemented two way sync between github and pagure as suggest by many. Now we want build the site and display it to user. There are number of options mkdocs, hugo(docker uses it now) etc. There are pros and cons to each site generator. To use hugo, we need the user to have hugo installed too, and than he needs to

On Fri, Jun 5, 2015 at 1:33 PM, kunaal jain <kunaalus at gmail.com> wrote: > Can you tell us about Fedora Docs toolchain? We can surely help each other > if our interests align. > <https://fedorahosted.org/documentation-guide/> -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay>

> ? 2015?6?5????6:10?Karsten Wade <kwade at redhat.com> ??? > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 06/04/2015 12:58 PM, Pete Travis wrote: > >> >> I'm tentatively planning on working pagure[0] into the Fedora Docs >> toolchain. It handles issue tracking, process >> documentation/contribution guidelines, and of course

Hi, The basic toolchain is up and running. I encourage community to test this workflow once. It is an addition to the existing contributing mediums. Site: http://clown-olga-13325.bitballoon.com/ Contributing Docs repo : https://github.com/kunaaljain/test-centos-docs ==AIM== Initial Idea : http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain The CentOS Project needs more short-form

On 4 August 2015 at 14:21, kunaal jain <kunaalus at gmail.com> wrote: > Hi, > > The basic toolchain is up and running. I encourage community to test > this workflow once. It is an addition to the existing contributing > mediums. > > Site: http://clown-olga-13325.bitballoon.com/ > Contributing Docs repo : https://github.com/kunaaljain/test-centos-docs > > ==AIM==

On Tue, Jul 28, 2015 at 8:47 AM, kunaal jain <kunaalus at gmail.com> wrote: > Lei and I have been working on the project, based on community input. We > have implemented two way sync between github and pagure as suggest by many. > > Now we want build the site and display it to user. There are number of > options mkdocs, hugo(docker uses it now) etc. > > There are pros

On 08/20/2015 02:57 AM, Karsten Wade wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 08/03/2015 12:52 PM, Fabian Arrotin wrote: >> On 03/08/15 18:23, kunaal jain wrote: >> Is that possible to have an overview of the infra and goals (aka >> the architecture) of this GSoC doc project ? that would help >> understanding, as I agree that I'm

Hi, I just wanted to mail community first and get the discussion started, but I should have written details first. The main aim behind this project is to facilitate contributors, so the site generator should be such that, it doesn't complicate the workflow. Another constraint is that the site generator should require minimal human effort, as we plan to build the site continuously through CI,

-----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? Anyone else with open questions? The GSoC project is supposed to be additive to what we

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

Hi, Kunaal and I have completed a prototype of the first part of our GSoC project (implement a new doc toolchain). Our goal is to implement a doc toolchain for short how-to docs and lower the barrier for new comers to contribute. This is the workflow of the prototype: 1. Contributor creates a new pull request on GitHub 2. A corresponding issue is automatically created on Pagure 3. Staff and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/03/2015 12:52 PM, Fabian Arrotin wrote: > On 03/08/15 18:23, kunaal jain wrote: > >> 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

On 29 May 2015 at 20:33, kunaal jain <kunaalus at gmail.com> wrote: > > Hi, > > Over the last week, Lei and I have been researching about the review > platform where the content submitted can be reviewed, commented, tagged and > pushed. This will be an alternative to github pull requests interface, which > will thus reduce our dependency on Github in case Github changes

On Thu, Jul 9, 2015 at 1:19 AM, Brian (bex) Exelbierd <bex at pobox.com> wrote: > Hi Lei, > > Hi, I am Kunaal the other GSoC student working on this toolchain. > On Jun 20, 2015, at 11:21 AM, Lei Yang <yltt1234512 at gmail.com> wrote: > > > I am sorry it has taken me so long to test this workflow. > Thanks a lot! We need testers and input from community.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/01/2015 10:30 PM, Lei Yang wrote: > Hi, > > As discussed earlier about the workflow, I and Kunaal will need a > server space to host Bugzilla, a test repository at Github + a git > repository at git.centos.org <http://git.centos.org/>. This is > temporary, required for development and testing. > > Please let us