similar to: Wiki submissions

Displaying 20 results from an estimated 700 matches similar to: "Wiki submissions"

2015 Jun 08
3
Update for FAQ - q.15 & q.31 update & merge
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/05/2015 01:52 PM, Manuel Wolfshant wrote: > On 06/05/2015 08:30 PM, Karsten Wade wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> Folks: >> >> A few of us (KB, Johnny, myself) have begun work on updating the >> main FAQs on the CentOS wiki. Mainly that means looking over and >> updating
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 Jun 05
2
Update for FAQ - q.15 & q.31 update & merge
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks: A few of us (KB, Johnny, myself) have begun work on updating the main FAQs on the CentOS wiki. Mainly that means looking over and updating for any changes that have been going on in the last 18 months as the project has expanded to include SIG releases, monthly updates of many new types, new hardware architectures, and so forth. For this
2014 Dec 24
0
A Question of Style
On Tue, Dec 23, 2014 at 4:53 PM, Brian Stinson <bstinson at ksu.edu> wrote: > On Dec 23 16:29, PatrickD Garvey wrote: > > 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
2014 Dec 24
2
A Question of Style
On Dec 23 16:29, PatrickD Garvey wrote: > 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 > > >>
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
2015 Aug 20
0
How GSoC project can fit in to CentOS Docs
-----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
2014 Sep 29
1
possereg.teachingopensource.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is the app at http://possereg.teachingopensource.org still being used? If so, can we migrate that to the main TOS server? If not, I'd like to take it down as part of a server migration we're doing for theopensourceway.org host. Thanks - Karsten - -- Karsten 'quaid' Wade .^\ CentOS Doer of Stuff
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
2015 Jun 01
1
Regarding GSoC project
-----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
2015 Mar 23
0
[CentOS-devel] Congratulations for selection in GSOC-2015
Hi all, do you have a process in mind for selecting GSoC applicants? Regards Lars > On 10 Mar 2015, at 23:28, Karsten Wade <kwade at redhat.com> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 03/10/2015 05:32 AM, Karanbir Singh wrote: >> Hi, >> >> On 03/09/2015 10:22 PM, Karsten Wade wrote: >>> KB: >>> >>>
2015 Jan 04
0
http://www.centos.org/ Help menu anchor
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/02/2015 01:27 PM, PatrickD Garvey wrote: > 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 > >
2015 May 07
0
Welcome GSoC students, getting started
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to welcome the two Summer of Code students who will be building different parts of the new CentOS documentation toolchain. * Kunal Jain * Lei Yang Students -- welcome again, and thank you for your work this far in helping define the project. Now we have the pleasure of working on the two new scopes that will work interdependently and
2015 Jun 04
0
Resources Needed for Doc Toolchain Project [GSoC]
-----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 git.centos.org <http://git.centos.org/>. This is > temporary, required for development and testing. > > Please let us
2015 Jun 04
0
Resources Needed for Doc Toolchain Project [GSoC]
-----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]
2014 Sep 04
0
Dojo at Fossetcon (Orlando, FL) 11 Sep.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If any of you are attending Fossetcon next week in Orlando, FL, please join us for a CentOS Dojo on Thursday 11 Sep. http://wiki.centos.org/Events/Dojo/Orlando2014 * Garrett Honeycutt - Why Automation is Important * Dmitri Pal - Active Directory Integration * Greg Sheremeta - oVirt all-in-one tutorial Jim Perrin and Johnny Hughes will be running
2015 Mar 11
0
Students and GSoC
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You may have heard that the CentOS Project was accepted to this year's Google Summer of Code. - From now through to 27 March is the time when students work with CentOS mentors on their applications. Are you a student? Do you know any who might be interested? Students with some experience in software development work on interesting projects and
2015 Jun 05
1
Resources Needed for Doc Toolchain Project [GSoC]
> ? 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
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 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