similar to: Docs strategy and tactics [RFC]

Displaying 20 results from an estimated 20000 matches similar to: "Docs strategy and tactics [RFC]"

2015 Mar 17
2
Docs strategy and tactics [RFC]
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
2015 Mar 25
1
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
2015 Mar 16
0
Docs strategy and tactics [RFC]
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
2015 Mar 16
2
Docs strategy and tactics [RFC]
> 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
2015 Mar 16
0
Docs strategy and tactics [RFC]
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
2015 Mar 16
4
Docs strategy and tactics [RFC]
-----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
2015 Mar 16
1
Docs strategy and tactics [RFC]
----- 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
2016 Apr 11
6
discussions around upstream documentation
There is a Fedora Activity Day (https://fedoraproject.org/wiki/FAD_Documentation_2016 ) centered around documentation, where I'm going to see what can be done about the state of centos documentation from upstream sources. Most of the tooling for documentation for these two groups is centered around git. For the most part, our documentation currently lives in the wiki, and has a fairly high
2015 Mar 24
0
Docs strategy and tactics [RFC]
-----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
2015 Jun 04
4
Resources Needed for Doc Toolchain Project [GSoC]
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 Mar 17
2
Docs strategy and tactics [RFC]
-----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
2015 Jun 02
2
Resources Needed for Doc Toolchain Project [GSoC]
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
2014 Jan 23
2
Request for access to wiki
Hi folks, I'd like to request access to the CentOS wiki for the purpose of adding CloudStack-related CentOS documentation. username: DavidNalley Thanks, --David
2015 Aug 03
3
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
2014 Dec 24
3
A Question of Style
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
2015 Mar 16
0
Docs strategy and tactics [RFC]
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
2015 Jul 30
3
How GSoC project can fit in to CentOS Docs
-----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
2014 Dec 24
1
A Question of Style
On Tue, Dec 23, 2014 at 4:18 PM, Karsten Wade <kwade at redhat.com> wrote: > 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
2016 Apr 11
2
discussions around upstream documentation
On Mon, Apr 11, 2016 at 10:37 AM, Karsten Wade <kwade at redhat.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 04/11/2016 09:18 AM, Jim Perrin wrote: >> What are the thoughts or concerns about this sort of workflow >> change? > > Any chance Moin Moin can store wiki source in git and sync > automatically with a central git repository?
2015 May 13
1
Toolchain discussion 07:00 UTC 13 May in #centos-devel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a heads up that we're pulling together a last-hour discussion with the two GSoC students and myself in about 90 minutes in #centos-devel to discuss how the docs toolchain project will shape up - -- split the project, set timelines, and discuss resource needs. We'll post a log after the meeting is done, just wanted to send out a heads up