From: Michael Smith <smith@xml-doc.org>
To: cygwin@cygwin.com
Subject: Re: name: GNU/cygwin system
Date: Tue, 21 May 2002 08:40:00 -0000 [thread overview]
Message-ID: <20020521053722.PIZS18164.oe-ismta1.bizmailsrvcs.net@SMITH-MICHAEL.openwave.com> (raw)
In-Reply-To: <20020517164815.GK22415@redhat.com>
Christopher Faylor <cgf-cygwin@cygwin.com> writes:
> [...]
> It's never been a goal of Cygwin to adhere to something like the LSB
> and we already refer to the Single UNIX Specification for reference.
> This is another thing that you could have gleaned from inspection
> of the mailing list archives.
>
> Anyone who might be interested in participating in something like the
> LSB is undoubtedly already aware of it.
>
> Respectfully, you seem rather new to the project. I wouldn't feel
> comfortable with you representing it in any way.
You're right of course. I just intended the LSB and name suggestions
in part as suggestions to maybe help raise more awareness of Cygwin in
the free software community (though I can see now that these
particular suggestions weren't terrifically thoughtful ones).
In hindsight, I realize that the name suggestion was pretty
simple-minded (and I apologize once again for not having the courtesy
to first take the time to check the list archive to see if it had
already been discussed).
Anyway, though I think just about everybody who's got any familiarity
with the free software world at all knows that Linux packages (RPMs
and Debian packages) are available for all sorts of things, I'm not
sure how many are aware that:
* through Cygwin, many of the same tools available as packages for
Linux distributions are also available as packages for Windows
(and Cygwin provides an environment for compiling and installing
many others that aren't packaged yet)
* Cygwin provides a sophisticated package management system that
makes it easy to install and update packages
I don't what can be done to raise more awareness about Cygwin --
especially about the availability of packages; but in part, I guess
that more people should -- when, on mailing lists or websites, they're
pointing out that certain applications are available as Linux
packages -- take the time to check to see whether particular packages
are available for Cygwin, and acknowledge when they are.
That's what I've tried to do for the DocBook/XML/SGML packages that
Jon Foster and Markus Hoenicka put together -- by adding information
about them to the DocBook Wiki:
http://docbook.org/wiki/moin.cgi/DocBookPackages
http://docbook.org/wiki/moin.cgi/CygwinPackages
About the page at the second URL: I hope I'm not using the Cygwin logo
inappropriately. If I am, somebody please let me know (I couldn't find
any information at the Cygwin site about use of the logo).
Are there other promotional logos/buttons/banners I could/should use
instead? Maybe a version of the Cygwin banner (http://cygwin.com/cygwin.jpg)?
Cheers,
--Mike
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-05-21 5:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 2:06 name: GNU/Cygwin system Robert Collins
2002-05-17 2:26 ` Michael Smith
2002-05-17 10:44 ` name: GNU/cygwin system Christopher Faylor
2002-05-21 8:40 ` Michael Smith [this message]
2002-05-21 10:15 ` Christopher Faylor
2002-05-21 17:29 ` Charles Wilson
2002-05-21 17:57 ` Charles Wilson
2002-05-22 4:49 ` Gary R. Van Sickle
-- strict thread matches above, loose matches on Subject: below --
2002-05-22 14:27 Kilroy, David
[not found] <20020522065446.18919.qmail@sina.com>
2002-05-22 14:23 ` Charles Wilson
2002-05-21 20:22 Robb, Sam
2002-05-21 11:00 Robert Collins
2002-05-20 10:11 name: GNU/Cygwin system Peter Ring
2002-05-17 1:40 Michael Smith
2002-05-17 11:02 ` Charles Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020521053722.PIZS18164.oe-ismta1.bizmailsrvcs.net@SMITH-MICHAEL.openwave.com \
--to=smith@xml-doc.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).