similar to: Regarding GSoC project

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

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

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

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

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/16/2015 01:42 PM, Dave Neary wrote: > Prominent wiki-like controls are important to getting drive-by > edits, and I am personally a fan of the in-place editing experience > you get from a good wiki. I wonder if we can find a way to make the "Edit this page on GitHub" more obvious then? Because I agree, the [edit] link on

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 I've been thinking for a little while, and talking with people, about what would be a good documentation strategy for the CentOS Project. == tl;dnr aka Summary This is a proposal around creating new, short-format documentation about doing cool new things on top of CentOS Linux. These docs would support the work of the various SIGs (Cloud,

> 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

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

hey fletcher, thanks for your input here. :+) and -- quite obviously -- your program will be whatever it is that _you_ think that it should be. of course. the thing is, i am certain that i have been clear that the feature that i believe will be "killer" is on-the-fly formatted display. that's my stand. and i'd say my reasoning has been equally clear, namely that this

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