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

Proposal: Corporation/Alliance SRP & Fittings #31

Closed
Hopobcn opened this issue Dec 30, 2015 · 7 comments
Closed

Proposal: Corporation/Alliance SRP & Fittings #31

Hopobcn opened this issue Dec 30, 2015 · 7 comments

Comments

@Hopobcn
Copy link

Hopobcn commented Dec 30, 2015

It would be great to manage the pvp part of a corp/alliance. Some ideas:

  • List of fittings (with requirements in skills) (Maybe the creation of fits its too much work, this task could be done in for example https://o.smium.org/ and then export it to seat)
  • List of members that can fly each doctrine (also this information visible in each person's page) (like fleet-up)
  • SRP: Forms for asking reimbursements of ships
  • etc..

For this I suppose the 'eve static data export' would be required.

If you consider this functionalities out of the scope of the application close it. The thing is that one of the big concerns of my corp right now are recruits & how many people are pvp-ready. This task could be handled by seat perfectly!

@leonjza
Copy link
Member

leonjza commented Dec 30, 2015

Howdie,

For now, I feel this is something that should be solved via a SeAT package/addon (and can be very easily done). SeAT has all the data you need too, so the package may be able to use the existing repositories along with the SDE.

I am happy to help anyone that wants to try this :)

@nizzan
Copy link

nizzan commented Dec 30, 2015

Could this be done in a way so that user's dont have to sign in?
As of right now i wouldn't want regular members to be able to log into seat, i use it as a director tool.

@leonjza
Copy link
Member

leonjza commented Dec 30, 2015

By design, nothing in SeAT is unauthenticated. If a new user registers an account, they cant see anything except for stuff they add. There is no need for this to be a 'director only' tool really.

@nizzan
Copy link

nizzan commented Dec 30, 2015

@leonjza biggest reason right now that i dont allow anyone except the directors to use it due to the load on the VPS it's on.
I dont want many users hitting the tool at the same time killing the machine.
But if they can only see what they add themselfs, then that sounds good imo.

@leonjza
Copy link
Member

leonjza commented Dec 30, 2015

Checkout whats hogging resources. Another user browsing the site is not really heavy.

@Netsuno Netsuno mentioned this issue Dec 31, 2015
@warlof
Copy link
Member

warlof commented Jan 9, 2016

Agree that should be an extension package.

@leonjza
Copy link
Member

leonjza commented Jan 26, 2016

Added to the wishlist

@leonjza leonjza closed this as completed Jan 26, 2016
@fackir fackir mentioned this issue Mar 2, 2017
This was referenced Dec 10, 2018
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

4 participants