search for: kunaalus

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>

...te a PR on github. A corresponding issue will be created automatically on Pagure, so you may go to Pagure.io to check it. If you want to merge the PR, change the status of issue from Open to Fixed on Pagure (need admin access to the repo, if you want to test this part, please email me or Kunaal <kunaalus at gmail.com <mailto:kunaalus at gmail.com>> so we can add you as admin). Once the issue is marked as Fixed, the PR on github will be merged. GitHub repo link: https://github.com/yangl1996/doc-test <https://github.com/yangl1996/doc-test> Pagure repo link: https://pagure.io/docs-test...

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

...te a PR on github. A corresponding issue will be created automatically on Pagure, so you may go to Pagure.io to check it. If you want to merge the PR, change the status of issue from Open to Fixed on Pagure (need admin access to the repo, if you want to test this part, please email me or Kunaal <kunaalus at gmail.com <mailto:kunaalus at gmail.com>> so we can add you as admin). Once the issue is marked as Fixed, the PR on github will be merged. Feel free to merge or reject my PR as you see fit :) > Also, we are not very sure whether running a Pagure instance will add much workload to s...

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

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

...own, add the link in another file and done! Jekyll -- very blog specific, which we don't require. What do you think about it? On 28-Jul-2015 8:52 AM, "Sankarshan Mukhopadhyay" < sankarshan.mukhopadhyay at gmail.com> wrote: > 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 > >...

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

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

...corresponding issue will be > created automatically on Pagure, so you may go to Pagure.io to check it. If > you want to merge the PR, change the status of issue from Open to Fixed on > Pagure (need admin access to the repo, if you want to test this part, > please email me or Kunaal <kunaalus at gmail.com> so we can add you as > admin). Once the issue is marked as Fixed, the PR on github will be merged. > > > Feel free to merge or reject my PR as you see fit :) > > Also, we are not very sure whether running a Pagure instance will add much > workload to sys admin...

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 its API anytime in future. Even firefox is considering using Github as an alternative medium to receive

As I discussed earlier with you, I am very much excited about this idea, bringing a new user friendly standard of writing as well as accessing the documentation. A couple of queries, The author writes up in markup language -> possibly host the content on github -> discussion over the content on mailing list -> changes to be done -> changes done -- seems fine till here. We define a

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

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

On Fri, Jun 5, 2015 at 1:28 AM, Pete Travis <me at petetravis.com> wrote: > > 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

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

> On Mon, Mar 16, 2015 at 10:48 PM, Shaun McCance <shaunm at redhat.com> wrote: > I like putting focus on this. It provides people a resource for things > they actually want to do. Nobody wants just an operating system. I also > think it's a great avenue for getting community contributions. It's easy > to make a one-time contribution on a topic you know well without