LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Pen-Yuan Hsing <penyuanhsing@gmail.com>
To: Ineiev <ineiev@gnu.org>
Cc: libreplanet-discuss@libreplanet.org
Subject: Re: ethical edtech edit-a-thon
Date: Mon, 18 Mar 2019 08:53:57 +0000	[thread overview]
Message-ID: <0d77a7b5-3f10-82fb-6d13-a8997df7ec25@gmail.com> (raw)
In-Reply-To: <20190318083011.GJ4713@gnu.org>

On 18/03/2019 08:30, Ineiev wrote:
> On Sat, Mar 16, 2019 at 05:32:35PM +0000, Pen-Yuan Hsing wrote:
>> (2) Outside of software, I think it is also crucial to consider
>> everything else (e.g., teaching material like artwork, multimedia,
>> text, etc.). Specifically, there should be discussion around free
>> culture and the use of the Creative Commons licenses. This is a
>> whole other big (but important) topic so I won't go into details in
>> this message. But I've been certified in Creative Commons licensing,
>> so let me know if you'd like more information.
> 
> Please don't say just "Creative Commons licenses". historically, CC
> provided (and still provides) an extremely wide range of different
> licenses.

Thank you for pointing this out, but that is why I said "licenses" 
(plural, not singular) which acknowledges that there are many, not just 
one, Creative Commons licenses. I also stated that this is a "whole 
other big topic" and didn't go into details unless there is a desire 
from the list to do so.

 > some of them are suitable for works of practical usage, other are not.

That's why I prefaced the point with "outside of software."

_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

  reply	other threads:[~2019-03-18  8:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 23:18 ethical edtech edit-a-thon Erin Glass
2019-03-12 18:08 ` Dmitry Alexandrov
2019-03-12 19:54   ` Erin Glass
2019-03-12 20:39     ` Nathan Schneider
2019-03-12 22:52       ` Dmitry Alexandrov
2019-03-13  3:45         ` Nathan Schneider
2019-03-13  4:40           ` Aaron Wolf
2019-03-13 14:05             ` overthefalls
2019-03-13 14:22               ` Michael McMahon
2019-03-13 14:30               ` Aaron Wolf
2019-03-16  2:25                 ` overthefalls
2019-03-16  3:12                   ` Aaron Wolf
2019-03-16  4:22                     ` bill-auger
2019-03-13 18:39             ` Dmitry Alexandrov
2019-03-13 21:11               ` Aaron Wolf
2019-03-14 22:57               ` no go for FLO, was " D. Joe
2019-03-13 16:25           ` Dmitry Alexandrov
2019-03-14 23:01           ` D. Joe
2019-03-13 20:20       ` Quiliro Ordonez
2019-03-16 17:32       ` Pen-Yuan Hsing
2019-03-18  8:30         ` Ineiev
2019-03-18  8:53           ` Pen-Yuan Hsing [this message]
2019-03-30 18:48         ` Adonay Felipe Nogueira
2019-03-30 20:04 ` Adonay Felipe Nogueira
2019-03-30 21:00   ` Aaron Wolf
2019-04-03  6:48   ` Leah Rowe
     [not found] <mailman.5.1552579202.16054.libreplanet-discuss@libreplanet.org>
2019-03-15  1:34 ` Prof Andrew A. Adams

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://lists.gnu.org/mailman/listinfo/libreplanet-discuss

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0d77a7b5-3f10-82fb-6d13-a8997df7ec25@gmail.com \
    --to=penyuanhsing@gmail.com \
    --cc=ineiev@gnu.org \
    --cc=libreplanet-discuss@libreplanet.org \
    /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).