similar to: Reg: Documentation Toolchain [GSOC]

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 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==

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kunaal: I know you are still researching, but I think you may have enough to write up your proposal in the Melange tool. The deadline for applications to be input is 27 March at 19:00 UTC. However, that is followed by a few more weeks for you to work with me and other mentors/helpers to refine the application. So your next step is to work on and

Hi, I have submitted my proposal for the above said idea. I have researched about this from past two weeks, put the proposed workflow in the proposal. I am in contact with Karsten from last two weeks. However I have not added exact implementation details about tools, which will be better if mentor discusses first. Please suggest changes. Regards, Kunal Jain

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

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

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 :

-----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

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.

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

Hi! Kunaal and I had an IRC chat last Wednesday at UTC 0600. We discussed about the new docs toolchain. The first part of the chat log is about the workflow, here is the summary: 1. user write on local text editor / on github or a web based editor 2. the PR is created on github, and the info is synced to a reviewing platform, where staff discussed about, tag and accept the file 3. if the PR is

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,

On Tue, Mar 17, 2015 at 3:30 AM, Shaun McCance <shaunm at redhat.com> wrote: > Just to throw another wrench in: I don't know what DigitalOcean's docs > are like, but Linode generally provides their guides for Ubuntu, Debian, > and CentOS. However, for whatever reason, they tend to do Ubuntu first. > So there are bunches of guides without CentOS versions. > > They do

-----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

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

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