3

We are receiving a lot of questions at Earth Sciences Exchange asking for identification of stones. I am trying to start a list of the identified minerals we have on our site's Meta.

As list point to identified minerals, I have started to fill a little sheet with some information about the piece and the best poster's picture.

My ask is if we could make a free app – without any ads or commercial purpose – for students, share it on GitHub with the information of the posts, using get petitions to generate a kind of mineral guide? It would contain the poster's question and pictures, the top answer and the sheet, that may be edited in wiki mode.

Should we write the site asking for permission? It would be nice if we could use Stack Exchange's and Earth Science's logos.

Improve this question
7
  • 2
    You can make an app that uses the content from the sites as long as you follow the attribution rules stated in the legal bits. I'm pretty sure you can't use their logo, even if you ask. Create your own derivative work
    – rene Mod
    Commented Oct 11, 2018 at 14:28
  • Thanks @rene. I wanted to mix the logo with my own svg. Ok understood. I think all would be ok -and would look kindly official wich is nice- saying at the splash activity or so "Application performed at Earth Sciences Exchange". I guess I can't use a webviewer to load the posts, but I want just to download the info to a local database and have an "upgrade database" option -so the app would work with not connection for students at the field.
    – user404146
    Commented Oct 11, 2018 at 14:37
  • 3
    I'm fine with the app, I do object to your adding partially duplicate answers to ID questions promoting this. It feels like 'hijacking' this site for your own project.
    – Jan Doggen
    Commented Oct 12, 2018 at 8:38
  • 1
    Looking "kind of official" is exactly what is not permitted. You need to be clear that you are using information from the SE site, but that your application is not under the control of SE. Anything that would suggest SE has responsibility for your bugs / policies / whatever is quite improper. That's the difference between "official" and not.
    – Ben Voigt
    Commented Oct 15, 2018 at 15:01
  • @Voigt the archi of the app is gonna be shared at github at public domain and if published with no adds. But the content is cc content from stack and authors. I just wanted to mean with my bad english is as the app should leave clear the content comes from stack's api it would have some kind of official perspective.
    – user404146
    Commented Oct 15, 2018 at 15:22
  • Thank you very much for the bounty. I'm glad my effort is appreciated, and hope to return the favor some day.
    – Glorfindel Mod
    Commented Oct 16, 2018 at 7:35
  • @Glorfindel You are welcome. I couldn't reach my programming level so quick without stackoverflow so it is me who is glad to return the favour
    – user404146
    Commented Oct 17, 2018 at 8:02

1 Answer 1

Reset to default
7
+100

Yes, this is allowed, and even encouraged:

All the content contributed to Stack Overflow or other Stack Exchange sites is cc-wiki (aka cc-by-sa) licensed, intended to be shared and remixed.

(I added some emphasis)

However, pay close attention to the attribution rules:

  1. Visually indicate that the content is from Stack Overflow or the Stack Exchange network in some way. It doesn’t have to be obnoxious; a discreet text blurb is fine.
  2. Hyperlink directly to the original question on the source site (e.g., http://stackoverflow.com/questions/12345)
  3. Show the author names for every question and answer
  4. Hyperlink each author name directly back to their user profile page on the source site (e.g., http://stackoverflow.com/users/12345/username)

That those hyperlinks won't work when your app is in offline mode is understandable and won't form a problem. There just needs to be an easy way to get there if your user does have an Internet connection.

Like @rene said in the comments, you can't use the Stack Exchange logo for your app.

Improve this answer
0

You must log in to answer this question.