Comments (7)
Kernellib-doc is listed twice in the first section.
lpc-doc appears to be one of Dworkin's repositories, like kernellib. Do we want to add more to it, or do we consider the existing disclaimers adequate (as we do with kernellib)?
from eos.
We definitely want a /usr directory in eOS. It's necessary as a location for linking other modules (mini-libraries) once they're properly broken up into repositories.
My planned MVP for modules is to update the "modules" files used by SkotOS a bit to include information on where to git-clone them, not just the names of modules being depended on. Then an external script running outside DGD can clone the repositories and link them into appropriate places, normally inside the usr directory. The same thing can be done with submodules, either by the script or by a downstream user.
I don't think that having people effectively copy repos into place is a good idea. It can make for a really ugly update story later if they want to incorporate newer changes. The MVP modules system isn't perfect either, but it's better than that.
from eos.
Do we want to add more to it, or do we consider the existing disclaimers adequate (as we do with kernellib)?
If there are any good LPC specific resources that support or teach the language that are kernel and game indepedent, we should add them here as long as the are public domain and CC0 like these files from Dworkin are. If it do a good job he might accept a PR back to his root repo. If not, it will be useful for our people.
from eos.
We definitely want a /usr directory in eOS. It's necessary as a location for linking other modules (mini-libraries) once they're properly broken up into repositories.
I added ./usr
and an empty ./usr/.gitignore
in a5bb611 and changed ./usr/.gitignore
to ignore the default ./usr/admin
directory created with the first user logs in in de7a2f9.
from eos.
If the plan is that we want to get as much SkotOS functionality as possible and eOS is significantly in second place, I assume that means I should be moving most SkotOS-type documentation into SkotOS-Doc rather than eOS-Doc.
I'm thinking specifically of the item called "Edit/Merge to eOS-doc, name appropriately (eOS-architecture?) and delete originals (if not in SkotOS they may have been moved to SkotOS-Docs)".
Presumably we want those to be in SkotOS-Docs, while eOS will probably slowly add links to relatively low-level code like the Kernellib, etc.
from eos.
I agree that those items relevant to both SkotOS and eOS should be in SkotOS-Docs, with the exception of generic (not SkotOS specific) kernellib related items which should be in KernelLib-Docs.
from eos.
Sounds good. Agree.
from eos.
Related Issues (3)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from eos.