similar to: Update for FAQ - q.15 & q.31 update & merge

Displaying 20 results from an estimated 7000 matches similar to: "Update for FAQ - q.15 & q.31 update & merge"

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 Jun 05
0
Update for FAQ - q.15 & q.31 update & merge
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 > for any changes that have been going on in the last 18 months as the > project has expanded to include SIG releases,
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 09
0
Update for FAQ - q.15 & q.31 update & merge
On 06/09/2015 01:27 AM, Karsten Wade wrote: > [...] > http://wiki.centos.org/KarstenWade/GeneralFAQUpdateq31q15 > > Thanks - Karsten >> I'd say that at least the following paragraphs from q15 are worth >> preserving: - Any point release is just a "snapshot" with previous >> updates, plus the latest batch of new upstream updates, rolled into >> a
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
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 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
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
2014 Feb 04
0
Wiki submissions
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to start making formal submissions to the wiki. I'm back-filling this request as Jim Perrin already added me to the wiki edit group. I'm relearning how Moin Moin access works (it's been a while but Fedora used to use Moin) and I've been using the MediaWiki style of edit/contributions so I'll need to re-adjust to how
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
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 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 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
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 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
2018 Sep 18
4
[CentOS-devel] Authorization to use CentOS logo in GNOME Boxes
On 09/18/2018 11:03 AM, Fabiano Fid?ncio wrote: > My understanding is that we can use all the CentOS marks provided here[0]. > However, those unfortunately are not looking good enough on Boxes and > we'd like to use, if possible, just the logo as in here[1] > > Would that be possible? As far as I could understand that would be a > violation of the trademark. > > [0]:
2019 Mar 05
2
request to have edit access to wiki
Hi all, I did try to do this myself as I thought Tuomas had introduced himself and gotten wiki access for other pages ... but my skills with the #acl markup have atrophied and I couldn't make it work. :) I'd like Tuomas to have access so there is a clear commit record of him having down the work, and in the future to collaborate on any adjustments to that page. best regards, - Karsten
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