Skip to content
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.

Tools for easily editing the manifest #75

Open
EIA485 opened this issue Jun 15, 2022 · 6 comments
Open

Tools for easily editing the manifest #75

EIA485 opened this issue Jun 15, 2022 · 6 comments
Labels
conversation Further information is requested or it's a question enhancement New feature or request up for grabs Ready for implementation

Comments

@EIA485
Copy link
Member

EIA485 commented Jun 15, 2022

what are yalls general thoughts on adding a section to the website to easily edit the manifest?
maybe also an option to auto generate some fields from a github repo

thinking this would be implemented with github oauth

@XDelta
Copy link
Member

XDelta commented Jun 16, 2022

Yeah, it'd be pretty neat to have a part of the website that you can just paste your mod link in and have several fields filled out for you. At least providing most of the fields for your single manifest entry.

@XDelta XDelta added enhancement New feature or request conversation Further information is requested or it's a question labels Jun 16, 2022
@ljoonal ljoonal changed the title creating tools to easaly edit the manifest Tools for easily editing the manifest Jun 16, 2022
@ljoonal ljoonal added the up for grabs Ready for implementation label Jun 16, 2022
@rampa3
Copy link
Contributor

rampa3 commented Jul 9, 2022

Yeah, it'd be pretty neat to have a part of the website that you can just paste your mod link in and have several fields filled out for you. At least providing most of the fields for your single manifest entry.

Would be neat. Maybe the Neos OAuth as primitive as it is now would be useful here? Theoretically, I think having dev accounts with a mod release control panel gated behind a login would be a way to go here from my POV. And when such infrastructure would be implemented, we could technically leave git as the backbone, since everything user/dev/reviewer facing would be done on the website.

@ljoonal
Copy link
Member

ljoonal commented Jul 10, 2022

Maybe the Neos OAuth as primitive as it is now would be useful here?

I'd not mix Neos and Github accounts, just using Github's own Oauth2 should be fine.

@rampa3
Copy link
Contributor

rampa3 commented Jul 10, 2022

Maybe the Neos OAuth as primitive as it is now would be useful here?

I'd not mix Neos and Github accounts, just using Github's own Oauth2 should be fine.

But what if you develop GitHub less - everyone working on Neos stuff will have Neos account. And when I talked about control panel, the idea was to hide all the git stuff in the page (Having the page's program doing the pushes when authorized in page by reviewer.) and have user interact with the page, and that is it.

@XDelta
Copy link
Member

XDelta commented Jul 10, 2022

Using githubs Oauth system would work in that most people who've made mods have the source and releases hosted on github already. For Using Neos's Oauth stuff, it is less documented and going to be less featured. I say go with using Github's

@EIA485
Copy link
Member Author

EIA485 commented Jul 10, 2022

my reasoning for saying github oauth is so from there forks, branches and prs can be made. i see no reason to leave git.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
conversation Further information is requested or it's a question enhancement New feature or request up for grabs Ready for implementation
Projects
None yet
Development

No branches or pull requests

4 participants