Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enrich the README #3

Open
ftomassetti opened this issue Jul 10, 2015 · 5 comments
Open

Enrich the README #3

ftomassetti opened this issue Jul 10, 2015 · 5 comments

Comments

@ftomassetti
Copy link
Member

  • we need screenshots
  • license
  • relations with WorldEngine
@psi29a
Copy link
Member

psi29a commented Jul 10, 2015

Honestly, I disagree here.... rather move most of the information to documentation via Sphinx. The README should be to the point and give directions to where you can find the rest, such as documentation.

@psi29a
Copy link
Member

psi29a commented Jul 10, 2015

The documentation can be (almost always) over at read-the-docs (RTD) which will generate HTML, Latex, PDF and more for us.

@ftomassetti
Copy link
Member Author

I think the README is the shop-window, so it must tell the user in 2 seconds why it should look into this project. Then all the details should stay in other places, I agree, but the README should explain what this project is (a GUI for WorldEngine, which is a world generator), under which license it is available (LGPL) and where to find the documentation. I think screenshots are extremely useful to describe what this project is in a blink.

@psi29a
Copy link
Member

psi29a commented Jul 10, 2015

With that, I totally agree. I just meant that it shouldn't turn out like the readme for worldengine itself, that is quite large. ;)

btw: PyQT is GPL so WorldEngine-GUI is also GPL. Hope that sits well with you.

@ftomassetti
Copy link
Member Author

yes, sorry my bad. I am fine with GPL for the gui

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants