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

Put Steam requirements in doc #479

Closed
richelbilderbeek opened this issue Mar 15, 2019 · 14 comments
Closed

Put Steam requirements in doc #479

richelbilderbeek opened this issue Mar 15, 2019 · 14 comments
Labels
medium priority Do this after the high priority Issues
Milestone

Comments

@richelbilderbeek
Copy link
Owner

richelbilderbeek commented Mar 15, 2019

Is your feature request related to a problem? Please describe.

Currently, we have an idea of how to get our game on Steam. In the comments below, useful links are added.

Describe the solution you'd like

Put those links in a doc, e.g. doc/requirements.md.

Create an Issue for each Steam requirement.

Describe alternatives you've considered

None.

Additional context

None.

@richelbilderbeek richelbilderbeek added medium priority Do this after the high priority Issues Senior Richel's help is needed labels Mar 15, 2019
@richelbilderbeek richelbilderbeek self-assigned this Mar 15, 2019
@richelbilderbeek
Copy link
Owner Author

Note to self, from here:

  • A 30-day waiting period between when you paid the app fee and when you can release your game
  • You’ll need to prepare your store page and put up a publicly-visible ‘coming soon’ page for at least two weeks.

So, deadlines will be:

  • July 4th: final presentation
  • May 31st: having paid fee
  • June 14th: having prepared store page

@richelbilderbeek
Copy link
Owner Author

richelbilderbeek commented Mar 15, 2019

GPL license could be a problem, but acceptable, e.g. KeeperRL has a GPL-2 license.

[edit: Added Issue: all must agree on that we distribute on Steam: #482 ]

@richelbilderbeek
Copy link
Owner Author

richelbilderbeek commented Mar 15, 2019

Options:

  1. keep the license under my name and make me state it's fine to have it distributed on Steam
  2. put the license under Team Octane and make everyone state it's fine to have it distributed on Steam

[edit: Added Issue: all must agree on that we distribute on Steam: #482 ]

@richelbilderbeek
Copy link
Owner Author

We will need someone to setup the SteamPipe...

@richelbilderbeek
Copy link
Owner Author

There are many cool features our team members would love to explore!

@richelbilderbeek
Copy link
Owner Author

The review process appears easy!

@richelbilderbeek
Copy link
Owner Author

We need to think about an early access yes/no...

@richelbilderbeek richelbilderbeek changed the title Gather requirements how to get game on Steam Steam: gather requirements Mar 15, 2019
@richelbilderbeek
Copy link
Owner Author

We need to form or have a legal entity...

If you co-own the content with other individuals, you must form a legal entity to own and receive payments for your content.

@richelbilderbeek
Copy link
Owner Author

We want the Steam Error Reporting feature!

@richelbilderbeek
Copy link
Owner Author

Purchased a Steam right to publish, thanks to @antonhensen81:

we_zijn_op_steam

@DynCoder
Copy link
Collaborator

why is the account name blurred, is the right bought to an account named anton, can we change the name to team octane or create a steam group named team octane we can publish it under

@DynCoder
Copy link
Collaborator

@DynCoder
Copy link
Collaborator

found this to add devs (if that is how this is gonna work)

@richelbilderbeek richelbilderbeek changed the title Steam: gather requirements Put Steam requirements in doc Apr 4, 2019
@richelbilderbeek richelbilderbeek removed the Senior Richel's help is needed label Apr 4, 2019
@richelbilderbeek richelbilderbeek removed their assignment Apr 4, 2019
@richelbilderbeek
Copy link
Owner Author

I am happy enough as this is for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
medium priority Do this after the high priority Issues
Projects
None yet
Development

No branches or pull requests

2 participants