You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've had a chat with @erlend-sh, and a few topics came out.
First: does anybody has any interest in maintaining the project? The task should be to review incoming PR.
Second: should game library maintainers be collaborators (read permissions) on the project? The idea is that, along a repository maintainer, a second pair of eyes should be a game library maintainer.
That'd be it. I can take care of the technical maintenance of the repo (README updates, CI, etc.), which I'll start shortly.
The text was updated successfully, but these errors were encountered:
I have some bandwidth for PR reviews and such things. One thing we probably should do is keep up with engine releases so that's a bit more taxing.
Hi there! Thanks for joining 😄
So, I'm in the process of updating the repository for general release (I've completed the first step of three in plan; over the next couple of days I'll complete the other two).
Since there are a few principles to agree on (for example: the design requirements for ports to be accepted, since this project is also meant to be educational, or, if the library maintainers should be involved, etc.), I'll open an issue, then we can have a discussion before starting the procedure.
I've had a chat with @erlend-sh, and a few topics came out.
First: does anybody has any interest in maintaining the project? The task should be to review incoming PR.
Second: should game library maintainers be collaborators (read permissions) on the project? The idea is that, along a repository maintainer, a second pair of eyes should be a game library maintainer.
That'd be it. I can take care of the technical maintenance of the repo (README updates, CI, etc.), which I'll start shortly.
The text was updated successfully, but these errors were encountered: