similar to: Docs strategy and tactics [RFC]

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

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

On Tue, 2015-03-17 at 01:54 +0530, kunaal jain wrote: > > 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

> 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

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

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

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 03/12/2015 03:59 PM, Karsten Wade wrote: > 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

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

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

On Thu, 2015-03-12 at 14:59 -0700, Karsten Wade wrote: > 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

----- Original Message ----- > From: "Dave Neary" <dneary at redhat.com> > To: "Mail list for wiki articles" <centos-docs at centos.org> > Sent: Monday, March 16, 2015 1:42:06 PM > Subject: Re: [CentOS-docs] Docs strategy and tactics [RFC] > > Hi, > > On 03/16/2015 03:44 PM, Karsten Wade wrote: > > On 03/16/2015 11:33 AM, Jim Perrin

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/16/2015 11:33 AM, Jim Perrin wrote: > My only question is, how do we determine what goes in the wiki vs > what goes in git? The flow/format between the two is a bit > different. Or is this development the first step in the transition > away from the wiki to another medium? That's a good question, and I don't have it

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/12/2015 04:59 PM, Karsten Wade wrote: <much snipping> > That would allow for us to mirror content to github.com/CentOS and > people could use Prose.io for editing and pull requests to submit > content. We would sync all that back to git.centos.org. > The last I looked at Prose.io, it wanted more privilege than I was

Hi, On 03/16/2015 03:44 PM, Karsten Wade wrote: > On 03/16/2015 11:33 AM, Jim Perrin wrote: >> My only question is, how do we determine what goes in the wiki vs >> what goes in git? The flow/format between the two is a bit >> different. Or is this development the first step in the transition >> away from the wiki to another medium? > > That's a good question,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/16/2015 07:50 PM, Karsten Wade wrote: > 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

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