similar to: How GSoC project can fit in to CentOS Docs

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

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

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

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

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

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

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

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 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 http://www.centos.org/, the Help in the navbar is described by the anchor <a href="http://wiki.centos.org/Documentation?action=show&amp;redirect=GettingHelp <view-source:http://wiki.centos.org/Documentation?action=show&redirect=GettingHelp>">Help</a> Why does it contain ?action=show&amp;redirect=GettingHelp ? It seems to me Documentation would be

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/30/2015 09:19 AM, Dougal Matthews wrote: > An alternative approach would be to build the docs in CI and link > to the built version in a comment on both systems. This is an interesting idea. We'll end up wanting docs to build in the CI anyway, so this could be done using e.g. a -draft tag so an initial commit can be used to both build

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.

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

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

On 12/23/2014 03:56 PM, Yves Bellefeuille wrote: > On Tuesday 23 December 2014, PatrickD Garvey > <patrickdgarveyt at gmail.com> wrote: > >> In >> http://wiki.centos.org/Contribute#head-42b3d8e26400a106851a61aebe5c2c >> >> ca54dd79e5 the standard for the wiki username is established as >> FirstnameLastname. >> >> In