similar to: Finished a prototype of GSoC project: Implement a new doc toolchain

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

> ? 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 09, 2015 at 02:11:26AM +0530, kunaal jain wrote: > On Thu, Jul 9, 2015 at 1:19 AM, Brian (bex) Exelbierd <bex at pobox.com> > They have both a private git (with gerrit) and a github repo.A If you > open a PR on github it is closed by a bot with instructions to submit > the PR via gerrit to their private repo.A When the PR is resolved and >

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 format, on github. The pull request > created gets mirrored to

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

-----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 repo > management and pull requests. It might fit for CentOS docs as > well. > > [0]

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, 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 know how do we obtain the same? We need it to get started on our project. Thanks! Regards, Lei -------------- next part

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 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 Kunal! Thanks for your reply! I think the official mirroring is a great method because of higher efficiency. Another thing I am trying to solve is how to retrieve and store all the discussion / issue / PR on GitHub? These functions are great for a doc toolchain. However we shouldn?t rely on GitHub as a part of our project. My plan now is to use bugs.cents.org as a place to discuss about docs

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>

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

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

On 11/12/17 10:22, Thibaut Perrin wrote: > Hello Fabien, > > First, thank you for even trying for what seems to be an impossible task :( > > Quick points :? > - if it was decided not to continue, what would happen to the current > wiki ? Dismantled or would it remain as read-only for documentation > purpose ? > - What about Sphinx