On 3/5/19 1:13 PM, Alan Bartlett wrote:
> Please refresh my memory by specifying "that page" of which you mention,
> above.
Sorry, didn't notice that omission. This page:
https://wiki.centos.org/ArtWork/Brand/Logo
Best,
- Karsten
--
Karsten Wade | Community Architect | @qu
achine image
> catalogs etc)
>
> To do this, I need permissions to edit the wiki.
>
> My account is https://wiki.centos.org/TuomasKuosmanen
>
> Best wishes,
>
> Tuomas
>
--
Karsten Wade | Community Architect | @quaid
Red Hat Open Source and Standards (OSAS)
ines, there may be some ambiguity because there is no
corresponding logo without the wordmark and usage guidelines on the wiki
ArtWork page.
Best regards,
- Karsten
--
Karsten Wade | Community Architect | @quaid
Red Hat Open Source and Standards (OSAS) : @redhatopen
https://community.red
/2018 07:10 AM, Fabiano Fidêncio wrote:
> People,
>
> On Wed, 2018-09-19 at 09:28 -0700, Karsten Wade wrote:
>> On 09/19/2018 03:35 AM, Pablo Sebastián Greco wrote:
>>> From someone who doesn't know anything about design/legal, what is
>>> the
>>> differen
can resolve the question of
permission for GNOME so they can move on with their development, and ii)
fix any actual or perceived inconsistencies between the trademark
guidelines and the logo usage guidelines.
Best regards,
- Karsten
--
Karsten Wade | Community Architect | @quaid
Red Hat
he
GNOME Boxes application inside of a GNOME session? If yes, is there
also a corresponding use on the website? A mock-up from there would be
useful as well.
Knowing that this has been missed for a few months, I'll work through
the discussions on our side to expedite a decision for you.
Regards,
- Kar
that we could use
>> CentOS logo as well?
>>
>> [0]: https://wiki.gnome.org/Apps/Boxes
>> [1]: https://gitlab.gnome.org/GNOME/gnome-boxes/raw/master/README.logos
>>
>> Best Regards,
>>
>
--
Karsten Wade | Community Architect | @quaid
Red Hat Open Sour
input,
- Karsten
--
Karsten Wade | Community Architect | @quaid
Red Hat Open Source and Standards (OSAS) : @redhatopen
https://community.redhat.com | https://next.redhat.com | https://osci.io
gpg: AD0E0C41 | https://red.ht/sig
signature.asc
Description: OpenPGP digital signature
' to find information about the overall trademark usage.
Regards,
- Karsten
--
Karsten Wade | Community Architect | @quaid
Red Hat Open Source and Standards (OSAS) : @redhatopen
https://community.redhat.com | https://next.redhat.com | https://osci.io
gpg: AD0E0C41 | https://red.ht/sig
signature.asc
ps://docs.google.com/document/d/1WVgEJvgYfEMH1cmgteCnIDSizJKxDOBI7uyX4H34jac/edit?usp=sharing
* Updates to e.g. the wiki on getting help, channel topic on #centos, where
else?
* What changes do we need to make to centos.org/docs?
Anything else to do for release?
Best regards,
- Karsten
-
ed out until we decide if we want to
replace/rewrite them
* New content may be needed for e.g. Atomic Host and cloud images.
There are some other parts of the git repo that are placeholders such as
for AsciiDoc work that may happen within the CentOS Project.
Best regards,
- Karsten
--
Karsten Wa
can make
it an action to have it [[Include()]] the above content in to the SIG
Guide so that there is one location to reference, update, edit, and
translate.
- - Karsten
- --
Karsten Wade
Community Infra & Platform (Mgr)
Open Source and Standards, @redhatopen
@quaid gpg: AD0E0C41
-BEGIN PGP SIG
Eases merging upstream, etc. Last Summer's GSoC
students implemented such a workflow.
Best,
- - Karsten
- --
Karsten Wade
Community Infra & Platform (Mgr)
Open Source and Standards, @redhatopen
@quaid gpg: AD0E0C41
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/08/2015 11:55 PM, Manuel Wolfshant wrote:
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*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/09/2015 02:10 AM, Alan Bartlett wrote:
On 9 June 2015 at 07:55, Manuel Wolfshant
wo...@nobugconsulting.ro wrote:
significant snippage
Call me picky but I'd rephrase The CentOS Project ONLY provides
updates or other changes for the
-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
-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
-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.
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/29/2015 12:33 PM, kunaal jain wrote:
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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://www.centos.org/minutes/2015/may/centos-devel.2015-05-13-07.08.htm
l
Minutes summary from above:
==
#centos-devel: Docs toolchain planning
==
Meeting started by quaid at
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/28/2015 03:47 PM, William Nelson wrote:
Could a link to the release notes (
http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 ) be added to
http://www.centos.org/download/
I'm a Linux beginner, I was able to successfully download
on the proposal with you and other
interested mentors now that the initial deadline is here.
- - Karsten
On Tue, Mar 24, 2015 at 5:48 AM, Karsten Wade kw...@redhat.com
wrote: Kunaal:
I know you are still researching, but I think you may have enough
to write up your proposal in the Melange tool
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/16/2015 02:12 PM, Jason Brooks wrote:
Good info. Different strokes, etc., only way to judge is through
results. Wikis are certainly a well-known sort of tool, if ppl
don't realize they can make a change, they definitely won't.
I've wondered
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/16/2015 04:05 PM, Pete Travis wrote:
We've been having a very similar conversation in the Fedora Docs
group. I have a crude plan for the tooling part, to extend
buildbot to address this; the idea is that you feed it git repos
containing
-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
-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
-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
On 12/23/2014 05:02 PM, Akemi Yagi wrote:
On Tue, Dec 23, 2014 at 4:29 PM, PatrickD Garvey
patrickdgarv...@gmail.com wrote:
I'm not referring to the username used by a particular person
while using a CentOS community resource. I'm trying to understand
if the document example should use an
On 12/18/2014 02:59 AM, Sandro Bonazzola wrote:
Il 18/12/2014 11:29, Karanbir Singh ha scritto:
On 16/12/14 16:04, George Dunlap wrote:
On Wed, Dec 3, 2014 at 7:30 AM, Sandro Bonazzola
sbona...@redhat.com wrote:
Hi, I just joined the CentOS-virt call yesterday for the
first time and it was a
On 12/15/2014 03:52 PM, PatrickD Garvey wrote:
On Mon, Dec 15, 2014 at 3:38 PM, Akemi Yagi amy...@gmail.com
wrote:
On Mon, Dec 15, 2014 at 3:12 PM, Alan Bartlett a...@elrepo.org
wrote:
On 15 December 2014 at 23:04, PatrickD Garvey
patrickdgarv...@gmail.com
wrote:
The following page has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/17/2014 11:41 AM, George Dunlap wrote:
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
I'd like to help too, helps me keep busy. :)
--
Karsten 'quaid' Wade .:. CentOS doer of stuff
From: Jim Perrin jper...@centos.org
Sent: Oct 24, 2014 1:33 PM
To: Mail list for wiki articles
Subject: Re: [CentOS-docs] A request for help managing wiki permissions
On 10/24/2014 11:46 AM, Jim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/02/2014 03:45 PM, Theodor Sigurjon Andresson wrote:
In there you are almost telling people that security through
obscurity is a good way. That might sometimes be true but in this
case it could mean that you would be handing passwords and
.
- - Karsten
From:
centos-docs-boun...@centos.org [centos-docs-boun...@centos.org] on
behalf of Karsten Wade [kw...@redhat.com] Sent: Thursday, October
02, 2014 22:49 To: centos-docs@centos.org Subject: Re:
[CentOS-docs] Securing SSH -- Change ports
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/02/2014 09:11 PM, Manuel Wolfshant wrote:
Incidentally I am a fan of using iptables (recent match) to limit
the number of admissible attempts from any given IP to connect to
sshd ( yes, I know, it has nothing to do with the initial concern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/30/2014 09:45 AM, Joe Brockmeier wrote:
Hey all,
Is there better documentation on setting up ACLs for the wiki than
what's here?
(http://wiki.centos.org/SyntaxReference?action=showredirect=centoswiki%2FSyntaxReference)
FWIW,
I've been
-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
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, my mail client expanded 'tos' to centos@ instead the intended
recipient t...@teachingopensource.org. Never mind. :)
On 09/29/2014 02:01 PM, Karsten Wade wrote:
Is the app at http://possereg.teachingopensource.org still being
used?
If so
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Side-topic (and subject changed), but do we have centbot running in
this channel?
I'd love to get us in the habit of using Meetbot, it makes for such
nice meeting minutes and logs. Can I offer to join all meetings
happening for the next little while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/20/2014 02:31 AM, Paul Mansfield wrote:
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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/23/2014 10:35 AM, David Nalley wrote:
Hi folks,
I'd like to request access to the CentOS wiki for the purpose of
adding CloudStack-related CentOS documentation.
username: DavidNalley
Thanks,
This all fits in to the overall
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/23/2014 01:17 PM, Yves Bellefeuille wrote:
R P Herrold wrote:
Historically, to get rights on the CentOS wiki, one had to have
a: - have subscribed to the -docs ML - registered with CamelCase
wikiname - optionally set up a homepage (doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/23/2014 12:53 PM, R P Herrold wrote:
This is part of a piece I sent this to Karsten earlier today:
Karsten:
Speaking of which, do we have any writing standards for using the
wiki? Anything to point new contributors to?
Historically,
52 matches
Mail list logo
