-
Notifications
You must be signed in to change notification settings - Fork 9
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
RFC: Document Baseline #4
Comments
(for reference: the CowBiteSpec was allowed for use here #1 (comment)) |
I'd like to use CowBiteSpec as starting point, splitting in single files (per article/topic) and starting to improve and work on that baseline |
Since neither me or avivace are expecting to get an answer from Martin about GBATEK, and no other reference was brought up, I think we can considered this settled? |
Worst case we can add stuff fom gbatek later. I'd start importing CowBiteSpec here (but we first have to close #2) |
Yeah if we can agree on a tech stack then we can get writing. I would suggest that we do not just wholesale import from cowbite. i think we can do a little better on the organization of things that way. |
I'd start importing and reformatting the content splitting the document so we can have a separate file per chapter, after the initial import we can re-organize the structure, step by step |
Initial import is now covered by #17! |
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.
The text was updated successfully, but these errors were encountered: