From: Jean Louis <bugs@gnu.support>
To: Thomas Ingram <taingram@mtu.edu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Conducting Research on FOSS communities
Date: Wed, 28 Nov 2018 03:41:29 +0100 [thread overview]
Message-ID: <20181128024129.GT22109@protected.rcdrun.com> (raw)
In-Reply-To: <153503a2-985d-034a-ddea-23110760bbe5@mtu.edu>
Dear Thomas,
FOSS is not same as free software.
Free Software is the original movement, so to
learn more about it, read:
http://www.gnu.org/philosophy/free-sw.html
Open Source is not free software, it is quite
different movement supporting more the vendors
rather than users. Open source software need not
be necessarily free software in terms of liberty.
You may see here a list of non-free software
licenses:
http://www.gnu.org/licenses/license-list.html#NonFreeSoftwareLicenses
and many of those non-free software licenses are
issued for "open source" which is very vague term.
For th eFOSS term, I don't know who invented that
but is also misleading because the context "free
and open source" may refer to "charge" and not
liberty as intended.
GNU Emacs is written by Richard Stallman initially
as free software.
In general free software supporters are working
together with "open source" community, both are
supporting each other in practice.
Let me answer questions from my side.
On Mon, Nov 12, 2018 at 04:03:44PM -0500, Thomas Ingram wrote:
>
> On 11/12/18 1:23 PM, Drew Adams wrote:
> > "Willing to answer some questions" can depend on the
> > questions. Maybe you can post the questions somewhere
> > and ask people to get in touch with you if they want
> > to participate?
>
> Yes, good point, I can provide you with the approved questions:
>
> Note: “community” refers to the FOSS community and the GNU Emacs community
> specifically.
GNU Emacs community is not FOSS community, it is
not the same.
The Free Software Foundation may have its members
list.
Mailing list may have its members. Yet it is open
for everybody to write to the list without being a
member.
There are in general no definite members lists and
nobody asks who is who, because we help each
other, but GNU Emacs lists on GNU.org is
definitely not an FOSS community, yet it does not
mean anybody supporting FOSS would be excluded
from participating ever. In fact it is not looked
upon.
Please read the article:
http://www.gnu.org/philosophy/open-source-misses-the-point.html.en
and also note that Emacs is hosted on GNU.org
website:
http://www.gnu.org/software/emacs/
> 1. Describe your role in this community.
Just an active GNU Emacs user supporting others to
use free software.
> 2. How long have you been a part of this
> community?
Since I know Emacs, since 1999.
> 3. Why are you involved in this community?
I am supporter of free software, help others solve
problems, and find solutions for myself.
> 4. What would you say are the shared goals of your community? (Why does this
> group exist? What does it do?)
It was formed by Free Software Foundation
https://www.fsf.org to gather and help users to
use free software, such as GNU Emacs. There are
many other mailing lists here:
http://lists.gnu.org/
> 5. What mechanisms do members use to communicate with each other? (examples:
> meetings, email, text messages, newsletters, reports, evaluation forms,
> handbook, etc)
That is email mailing list. There are also
newsletters with announcements, also sent to
mailing list. There are handbooks on GNU Emacs,
and there is IRC channel #emacs just as you can
see various support channels on GNU Emacs website.
> 6. What are the purposes of each of these
> mechanisms of communication?
To advance free software. Each member may have its
own individual purpose.
> 7. How do new members learn about the mechanisms of communication and how to
> use them?
In regards to GNU Emacs they learn it from the
website http://www.gnu.org/software/emacs/ and
http://www.gnu.org/software/emacs/documentation.html
and from the Help menu within the software and
www.gnu.org website, YouTube videos and many other
places.
> 8. Are there any shared texts or mechanisms for
> communication that you think are not working
> well? What do you see as the problem?
This mailing list is self-evidencing truth that it
works, if it works well or not is very subjective
opinion.
> 9. What are some examples of specialized language that the group members use
> in their conversation and written communication? (examples: acronyms, slang,
> specialized terms that “outsiders” might not
> understand)
You may start with GNU -- meaning GNU is Not Unix,
the name of operating system, and GNU Emacs is
part of it. https://www.gnu.org and there is
plethora of other terms.
> 10. How do you help new members learn the specialized language of the
> community?
Through the Help menu in GNU Emacs software and
websites.
Jean Louis
next prev parent reply other threads:[~2018-11-28 2:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <29ee14d8-d640-fec5-2ae7-f93b600bda65@mtu.edu>
2018-11-12 21:03 ` Conducting Research on FOSS communities Thomas Ingram
2018-11-14 1:04 ` David Arroyo Menendez
2018-11-28 2:41 ` Jean Louis [this message]
2018-11-12 17:05 Thomas Ingram
2018-11-12 18:23 ` Drew Adams
2018-11-14 13:21 ` Van L
2018-11-13 12:48 ` David Arroyo Menendez
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181128024129.GT22109@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=taingram@mtu.edu \
/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).