gbadev-org / gbadoc Goto Github PK
View Code? Open in Web Editor NEWCommunity initiated GBA Technical documentation effort
Home Page: http://gbadev-org.github.io/gbadoc/
License: Creative Commons Zero v1.0 Universal
Community initiated GBA Technical documentation effort
Home Page: http://gbadev-org.github.io/gbadoc/
License: Creative Commons Zero v1.0 Universal
We should disable the Wiki tab. Content shouldn't get into the repo wiki, it should be going into the repo files which are published to github pages. Having the wiki enabled can give people the wrong idea.
We should also consider enabling the Discussions tab. We have the discord, but that's only good for short term discussions. For longer term questions, it's nice to have a place to post about something and people potentially can see it days or weeks from now.
We should document the audio part from http://www.belogic.com/gba/ . Maybe ask the author about licensing that documents?
Related:
HTML -> PDF via pandoc
could be an alternative, too
Which license should we apply to the produced assets (figures and text)?
(insert inception noise here)
Should the RFC process itself be documented? I think most importantly an issue template would be good so all the important information gets included from the get-go (checklist of questions, related/blocking RFCs, time estimate for resolution, so on), but also how and when we decide to resolve
What should the editing, review and contribution process look like? I think Pull Requests are the way to go, since it lets us make use of GitHub's review features, and hopefully prevents merge disasters.
This RFC marks the start of a community initiated effort in researching and documenting the GBA architecture. Our goal is to produce something similar to Game Boy's Pan Docs.
Some basic points to decide on:
Any suggestion for the favicon?
Which document should we use as a baseline?
Keep in mind we'll also need a permission enabling us to reuse. Items marked with * are already released with a permissive license.
This was something discussed in the Discord yesterday, and there seemed to be a lot of differing opinions on it so I think it's good to decide on it ahead of time
There's a couple options that were discussed
Personally I don't have significant gripes with the official names, although there's a couple undescriptive names and misnomers.
Additionally, we would need to come up with new names for undocumented registers, although this can be decided on a case by case basis.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.