Skip to content

Commit 56b5557

Browse files
authored
Merge pull request #4 from manwar/minor-tidy-up
Minor tidy up as below:
2 parents d611084 + 0d285fd commit 56b5557

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

README.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -87,14 +87,14 @@ A quick summary of Neil's post is:
8787

8888
### A New Camel for Perl
8989

90-
- Neil B suggests that Perl could adopt a new camel logo—separate from the one
90+
- Neil Bowers suggests that Perl could adopt a new camel logo—separate from the one
9191
used on O'Reilly's book cover—and use it as the official symbol for the Perl
9292
language.
9393

9494
- The goal is to create a logo that represents not just the language but also
9595
the community, one that feels friendly and welcoming.
9696

97-
- Neil B acknowledges that the "camel association" will always be tied to Perl,
97+
- Neil Bowers acknowledges that the "camel association" will always be tied to Perl,
9898
even if a new logo is chosen. He suggests this is a pragmatic approach,
9999
emphasizing that the restrictions around using camels on books are not a
100100
major issue.
@@ -108,12 +108,12 @@ onion logo with Allison Randal (who had just finished her tenure as president of
108108

109109
Here's a transcript:
110110

111-
> - Philippe
111+
> - Philippe
112112
> And what about the logo? Personally, I saw it as a way to become more
113113
> independent from the O'Reilly legalese and the fact that everywhere you use
114114
> the Camel you need to acknowledge the fact that the Camel is a trademark of
115115
> O'Reilly. But is there something else?
116-
> - Allison
116+
> - Allison
117117
> Well, that is a nice side effect. The main thing is that because of the
118118
> trademark relationship, there's a few places where we really *can't* use
119119
> the Camel at all. Say, if we published a collection of Perl documentation
@@ -122,19 +122,19 @@ Here's a transcript:
122122
> So we started the process just to give us another option in a few places.
123123
> But as we go on it seems to have kind of taken a life of its own. It's been
124124
> showing up on YAPC T-shirts and things like that.
125-
> - Philippe
125+
> - Philippe
126126
> It's a nice logo, because the onion has been part of Larry's talks for a
127127
> while, so it's already part of the culture.
128-
> - Allison
128+
> - Allison
129129
> Yeah. We spent a good deal of time looking for the right logo. We tried a
130130
> whole bunch of different things. At the very beginning we thought "Not an
131131
> onion, because it doesn't make a very good logo." We looked for something
132132
> else and just kept coming back to the onion because of that connection to
133133
> Perl history. Then we found an artist who did an onion that we liked so we
134134
> went with it.
135-
> - Philippe
135+
> - Philippe
136136
> Who's the author of the onion?
137-
> - Allison
137+
> - Allison
138138
> His name is Devin Shane Muldoon. He's an artist in the San Francisco area.
139139
> He's really talented.
140140
@@ -166,11 +166,11 @@ published in GNU/Linux Magazine France in 2006.
166166
enough stakeholders in the same room to come to an agreement in principle and
167167
then move ahead with the project.
168168

169-
- Can I Put This on a T-shirt, Mug or Candle?
169+
- Can I put this on a T-shirt, Mug or Candle?
170170

171171
Yes!
172172

173-
- Can I Put This on a Book About Perl?
173+
- Can I put this on a book about Perl?
174174

175175
No. Our understanding of O'Reilly's position is that we are free to use a
176176
camel in association with Perl, with the exception of books about Perl. See

0 commit comments

Comments
 (0)