(no title)
njredar676 | 6 months ago
I apologize if the first impression was crude -- I was in an hurry to get the engine out at this time. I understand that the Discord server simply consisted of a few channels (since then, I've cleaned that up).
I had actually wanted to make a new GitHub account for the project, to separate concerns (GitHub ToS prohibits this, and I had to learn the hard way), so I eventually renamed my old account. I'll make sure to provide more resources under my account so it doesn't seem empty.
In regards to developer attribution, we will have a developer page as well as a resource hub so it seems more than an "account". I had not anticipated that people would look deeper into the account -- I had simply wanted to get the demo out, to show the concept.
On a separate note, I acknowledge some people found it suspicious that the initial commit was every file at once. This doesn't mean I don't know how version control works. It was because I had actually worked on the project alone on my computer and, subject to release, released the full source at once.
Once again, thanks for informing us about these issues. Perhaps, I will better prepare my future releases to avoid this issues, even if I was under time constraints. I think that there are great things that can be accomplished with this project.
jbaber|6 months ago
This is my standard operating procedure. My public repo's not going to start with the first hundred commits of the code in a different language, with API keys burned in, etc.
It did not occur to me this was rare enough to be suspicious. You shouldn't have to apologize for it :)
poly2it|6 months ago
Are you aware GitHub lets you create organisation accounts for collecting projects behind a common name? I think it might be what you were looking for. You can even turn your current account into an organisation.
https://github.com/settings/organizations
njredar676|6 months ago
I'll make sure to do that though as the next step.