similar to: Website Request, add link to release notes on download page

Displaying 20 results from an estimated 800 matches similar to: "Website Request, add link to release notes on download page"

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
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 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 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 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 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
2014 Dec 23
3
A Question of Style
Please read this in the spirit of my understanding what the CentOS community norms are. I fault neither of those mentioned for doing what they have done. I just want to understand how we all are documenting the CentOS distribution. In http://wiki.centos.org/Contribute#head-42b3d8e26400a106851a61aebe5c2cca54dd79e5 the standard for the wiki username is established as FirstnameLastname. In
2014 Nov 17
1
Reminder: Virt SIG meeting on #centos-devel tomorrow, 2pm GMT
Just a reminder everyone, we'll be having our biweekly Virt SIG meeting Tuesday at 2pm GMT, on IRC, channel #centos-devel on freenode. If you have any particular items you'd like to put on the agenda, please let me know. Lars will be on a plane to China at that point, so I'll be chairing the meeting. -George
2014 Feb 20
1
unsubscribing because...
I think it's a sad sign when the mailing list is more about how to manage access to the wiki than actually managing contributions and the content. I don't really have any confidence that centos wants a vibrant community. The recent change list at http://wiki.centos.org/RecentChanges isn't really a good sign. Sorry, but I felt if I simply unsubscribed and disappeared quietly, I'd
2014 Sep 30
2
Syntax for ACLs?
Hey all, Is there better documentation on setting up ACLs for the wiki than what's here? (http://wiki.centos.org/SyntaxReference?action=show&redirect=centoswiki%2FSyntaxReference) Thanks, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb at redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ -------------- next part -------------- A
2015 Jun 09
1
Update for FAQ - q.15 & q.31 update & merge
On 9 June 2015 at 07:55, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > <significant snippage> > > Call me picky but I'd rephrase > The CentOS Project ONLY provides updates or other changes for the > latest version of each major branch. > to > The CentOS Project provides updates or other changes ONLY for the > latest version of each major
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 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
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 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 Dec 15
2
Fwd: [CentOS Wiki] Update of "HowTos/Custom Kernel" by AkemiYagi
On Mon, Dec 15, 2014 at 3:12 PM, Alan Bartlett <ajb at elrepo.org> wrote: > On 15 December 2014 at 23:04, PatrickD Garvey <patrickdgarveyt at gmail.com> wrote: >>> The following page has been changed by AkemiYagi: >>> http://wiki.centos.org/HowTos/Custom_Kernel?action=diff&rev2=179&rev1=178 >> >> I know I'm new around here and this is
2015 May 29
5
Regarding GSoC project
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
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 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
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