4.2 KiB
- decide on / create a tsr/nn base
- establish a standard directory structure for projex repos
- document an onboarding sequence for AP projex ppl
- notes
TODO decide on / create a tsr/nn base
this would basically be a single .org file that has all projex (including prok!) on it with a kind of overview of where it's at.
I am indifferent to where this is, for now thinking probably just /root/todo.org
Here's an example of hte kinds of projects I think should be in it:
projects https://irc.anarchyplanet.org/git/explore/repos
server backup
<link to the directory or something> <link to the todo file> etc.
projex
prok
proto
tech tuesdays
ircbang
etc.
TODO establish a standard directory structure for projex repos
I propose the folder structure we've started with org/ , /html , etc. And then the three following files:
README
- the context (e.g. audience, who has access to the project, whether the repo is public/private, etc)
- how to get new people involved in the project (we will need a overarching overview that explains the process which I will get to when I can)
TODOs
the todo contains things that actually need to be done (i.e. action items, these can be linked to pull requests or issues, and eventually we can probably even set up hooks etc.)
notes
I want to keep track of these but I don't necessarily want them cluttering up the repos. I use them for, e.g. walking kittens through tutorials, asking you questions and getting answers, etc. I have been putting a notes directory in gitignore… for now I'm going to probably leave this in TODOs because I'm not sure what the answer is yet.
TODO document an onboarding sequence for AP projex ppl
-
something like:
- SSH
- tmux/wemux
- git
- hidden services
- pandoc
notes
Another step is coming up with an admin/dev process (i.e. tsr and notnull) I thought that using README.org would be a good way to have the one intro document but I'd say the main function of README.md is to give outsiders an overview of the project, so it doesn't make sense for dev todos and notes.
One option might be to have a centralized org doc that links to the directories for our other projects, with TODOs.
Ideally, each directory will have a file (thinking todo.org) that has the todos. then the central document will link to each project directory's todos (also, I will show you about how to use agendamode).
and then each of these will have a repo and then a directory with the file struture outlined in projex (directories = org md html etc etc) and then the files README, todo, and notes can be in any or all of these.
that way when I'm like 'what is tsr working on that I need to know about?' It can all be in one place but also in all o fthe places (repo on gogs, personal directories, etc) I see, you want links to repos and files.
I am not opposed to autoamating the generation of that process by hitting an api that gogs has for that expore place, for example. (or building an API)
For me it's like figuring out prios atm. Need to restore my files and have to test cryptsetup more and procastinate very well.
what happened to your files? also, re: cryptsetup, that is something for serge backup or something you're doing independently? or both? The debian installer overwrote the partition table and i need to find the partition start or if it got overwritten bruteforce it which somehow seems unlikely to work.
:( sux! Still interesting to get familiar with. just need to start and write scripts or test hash..something - backup on serge is a good opportunity.
perfect! also I was thinking about maybe eventually setting up an encrypted partition here. but yeah, that is cool! let me try to create that loop device atached to a container.
sounds good to me! I will be working on this organizing I've mentioned here, and also if you work on cryptsetup on wemux I'll check in :) k
also re: gogs explore/repo thx for pointing that out… solike, if ircbang wants a list of todos that people could help with, I would want it to take the form of what we did with the irc-how-to for example, where now it is implemented in text, git, etherpad, etc.
The next step is establishing standards for the process. I propose a directory structure similar to the one we've been building that contains the following files: