Author: IRC
Category: Hyperbola Project
Date: 2021-04-20 10:34
Image: 2020/01/hyperbola-bsd.jpg
Slug: hyperbola-project-meetings
Tags: hyperbola, meeting
Title: Hyperbola Project Meetings
Meeting Files via IRC channel of HyperBola Project
_Click on me to see_
## Meet 9
~~~~{.irc}
~~~~
_Click on me to see_
## Meet 8 addendum - 2021-04-15
~~~~{.irc}
[19:28] dankon Emulatorman
[20:58] quiliro: ping
[21:02] quiliro: cuando puedas, fijate si puedes entrar con -> ssh -p 51100 quiliro@git.hyperbola.info
ok
he publicado el log
meeting – 8
ahi entrarias para poder agregar/quitar/listar repos de git en tu cuenta
[21:03] cuando es para repos compartidos por el equipo, es aqui -> ssh -p 51100 team@git.hyperbola.info
[21:04] aqui esta el codigo fuente del script -> https://git.hyperbola.info:50100/services/git-shell-commands.git/tree/
Ya ingrese…No entiendo bien las instrucciones que salen cuando entré
[21:05] To list a Git repositories use between:
‘list’, ‘lsgit’ or ‘gsc_lsgit.sh’
To make a Git repository use between:
‘make’, ‘mkgit’ or ‘gsc_mkgit.sh’
To remove a Git repository use between:
‘remove’, ‘rmgit’ or ‘gsc_rmgit.sh
ahi es solo para crear repos de git vacios
y despues puedes subir codigo ahi
[21:06] despues una vez creado la web generara la url para el grupo o para otros
creo que en lugar de “between” debe ser “any of the following”
es así?
[21:07] ok, puedes aprovechar y crear un repo con el mismo nombre de git-shell-commands
en team o en el tuyo
y luego haces pull del original y comenzas a hacer commits
[21:08] y a veces debe ser “a Git repository” y otras “Git repositories”
ok
yo no he probado y ni hice ese script
[21:09] no entiendo bien qué hacer
voy a intentar crear uno en el mio para entender como funciona
[21:12] ya lo entiendo!
[21:13] quiliro: copio en un paste lo que hice para evitar “flooding” aqui
[21:14] ok
quiliro: https://paste.debian.net/plain/1193930
pide address y name
ok
hice git-shell-commands dentro del directorio services
[21:15] para el team
y ahora tenemos disponible aqui -> https://git.hyperbola.info:50100/~team/services/git-shell-commands.git/
list please
[21:16] voy ahora clonar el directorio que hice
on the paste
after make
ya entiendo
voy ahora clonar -> git clone
ssh://git@git.hyperbola.info:51100/~git/~team/services/git-shell-commands.git
[21:17] ok
excelente
ahora voy intentar importar los commits del official -> https://git.hyperbola.info:50100/services/git-shell-commands.git/
[21:18] y pasarlos para el clon que hice en el team
voy a ver si me acuerdo del comando que estoy un poco olvidado
[21:19] estoy leyendo el man de git pull
porque hay que crear un origen para tomar cambios de otros repos con git pull
pero me olvidé del comando
origin/master
[21:20] git pull origin/master
creo
no es mejor hacerlo mañana?
con gente que hace esto a diario
[21:21] para que otros ayuden y tú puedas descansar un poco
[21:23] en realidad creo que es git pull https://git.hyperbola.info:50100/services/git-shell-commands.git
ya he creado documentation/libertad.git y documentation/freedom.git
[21:24] pero creo que está mal…esos debieran ser archivos, no repositorios
[21:26] creo que esta inestable
estoy con problemas para subir lo que importé
[21:27] oh
git push
[21:28] pude importar con git pull https://git.hyperbola.info:50100/services/git-shell-commands.git
ooh…bueno
ahora como es un repo nuevo tengo que configurar la rama de master
[21:29] segun dice el git
git push –set-upstream origin master
ok
[21:31] me di cuenta que esta mal lo que hace cgit
tira todo en el usuario git
por eso no pude
oh
[21:32] tuve que editar en .git/config de ssh://git@git.hyperbola.info:51100/~git/~team/services/git-shell-commands.git a ssh://team@git.hyperbola.info:51100/~git/~team/services/git-shell-commands.git
ami no me funciono clonar
cambiando el “git@” por “team@”
es un bug del cgit
oh…debo hacer eso mismo en el comando de clonar
fijate si te funciona
yo pude
[21:33] ahora -> https://git.hyperbola.info:50100/~team/services/git-shell-commands.git/
git clone https://git.hyperbola.info:50100/~team/services/git-shell-commands.git/
me funciona
[21:36] si pero debes de usar el ssh:// no el https:// para subir archivos
deberias de clonar como git clone ssh://team@git.hyperbola.info:51100/~git/~team/services/git-shell-commands.git
[21:37] cambiando el git@git.hyperbola.info por team@git.hyperbola.info
porque esta mal lo que dice el cgit
quizas falte algo por configurar en el cgit, o es un bug
despues el otro bug es que no aparece la previsualizacion de los archivos a no ser si haces click en (plain)
[21:38] digo en cgit en la web
git clone ssh://team@git.hyperbola.info:51100/~git/~team/services/git-shell-commands.git
me funciona
también
[21:39] si, es el modo para tener acceso a subir tus cambios ahi
ahora puedes subir tus commits ahi
Emulatorman: pardonu, I just cloned the kernel—can you suggest a program to view the formatted markdown?
Emulatorman: el problema de la visualización debe ser por highlighting
biovoid: emacs?
tal vez mirar la ruta adecuada de ::: source-filter=/usr/lib/cgit/filters/syntax-highlighting.py
[21:40] I don’t use emacs
as in I don’t know it
biovoid: for some strange reason, you should clone ssh://team@git.hyperbola.info:51100/ instead of ssh://git@git.hyperbola.info:51100/ for team git repos
[21:41] biovoid: for your own account it is -> ssh://biovoid@git.hyperbola.info:51100/ I had cloned ssh://biovoid@git.hyperbola.info:51100/~git/~team/hyperbolabsd/hyperbk.git
yes, that is the way
[21:42] okay good
you can push your own commits there
if you have plans to push commits in our team, just create a new origin inside .git/config by pointing to ssh://team@git.hyperbola.info:51100
[21:43] so you can pull/push commits between your git repo and team one
it is the way how to work in environments such as the Linux kernel
understood
[21:44] i will create package repos for the team to push new PKGBUILD’s commits
[21:49] Emulatorman: “HyperbolaBSD esta planeado para implementar nuevas caracteristicas heredadas del nucleo Linux” ¿Qué características en específico se tomará de Linux y de OpenBSD?
quiliro: estan explicadas en la entrevista
[21:50] ok
quiliro: en Linux y los *BSDs
no solo OpenBSD
adoro el sistema de archivos hammer y hammer2 de DragonflyBSD
estaria bueno implementarlo en el futuro para HyperbolaBSD
[21:51] rapido, compacto, seguro, simples
hablé de eso en la entrevista
[21:53] please, keep your own commits in your own branches, not master
[21:54] eg. https://git.hyperbola.info:50100/~team/packages/core.git/log/?h=emulatorman
[21:55] how to do: just run -> git branch yournickname
then: git checkout yournickname
Emulatorman: Actually I don’t understand why I would need to change user (`biovoid@git…` to `team@git…`) in the origin. Would that not remove our individual atributions for commits?
pull commits from master: git pull origin master
[21:56] biovoid: you can use custom origins
eg.
go to .git/config
then edit a custom origin
[21:57] Yes, I mean, must it be changed because `biovoid` does not have write permissions to ~team?
[21:58] i mean to create custom remote urls to push between the git repos
* Emulatorman is creating an sample
[21:59] Emulatorman: Linux kernel’s JFFS2
[22:00] Emulatorman: is that the only thing from linux?
from the interview
biovoid: it is a sample of remotes -> https://paste.debian.net/plain/1193932
[22:01] only stuff which is gplv3+
biovoid: so if you want to pull changes from the team’s repo, just run -> git pull team master
[22:02] I thnk I was getting confused on the authentication matching the ~user
biovoid: if you want to push for both (your own repo and team one): you should run -> git push origin master (for you as default remote origin) and git push team master
[22:03] since your repo is the “origin” remote repo the command “origin master” isn’t needed, but i added there to understand the syntax
biovoid: coadde fixed the syntax now in the cgit
[22:04] see here right now -> https://git.hyperbola.info:50100/~~biovoid/hyperbolabsd/hyperbk.git/
it says ssh://@git.hyperbola.info:51100/~git/~~biovoid/hyperbolabsd/hyperbk.git
where “” is your own user
or team for shared team account
[22:05] Emulatorman: my question was whether I could use my own user to push to ~team
or need team for both
[22:06] yes of course
check my sample in the paste.debian.net
https://paste.debian.net/plain/1193932
[22:07] you need create a custom remote path in .git/config
by default, git create a [remote “origin”] when you clone a repo
in that example they all match I mean would ssh://emulatorman@git.hyperbola.info:51100/~git/~team/packages/core.git work, or do you have to authenticate as team to push to ~team
[22:08] to pull commit, you don’t need use the ssh://, you can use the https:// to avoid authentica everytime, because it just pulling commits
[22:09] makes sense
in that case you can use the default/official url -> url = https://git.hyperbola.info:50100/packages/core.git
to push changes you should use the url to push commits, eg -> pushurl = ssh://team@git.hyperbola.info:51100/~git/~team/packages/core.git
[22:10] if you need 2 push’s urls, then you need create 2 remote instances
right
one as default, called origin -> [remote “origin”]
[22:11] then another one -> [remote “foo”]
in that foo instance, put the custom url, it could be the team, your one, another mirror around internet such as github, etc
then you will push it as -> git push foo master
[22:12] so those commits will be read by git in the remote “foo” instance in the pushurl field eg. -> ssh://team@git.hyperbola.info:51100/~git/~team/packages/core.git
so those those commits will go to the team git repo instance
[22:13] and both individual user and team user permissions are determined by ssh keys?
yes biovoid
coadde did that in those days
so your instance biovoid only you have access
and team our team
[22:14] Okay, I think everything is clear for now. Thank you for the explanations, Emulatorman
we create a personal git instance for personal reasons, maybe someday you would push your own projects there, eg. a free software source from your university made by you, and you need a git instance for that, etc
[22:15] at least, you guys, don’t need go to libregit, github, etc for that
quiliro: you could save those latest logs for tomorrow
[22:16] i wouldn’t to explain it again :P
or at least to take note for future “HOWTO” or something else, etc
ok…I will add it to today’s logs
[22:17] or maybe create a new log
to make it easy to search
git log
lol
that would be much better, biovoid
ok ty :)
[22:27] typo in [remote “team”]
it is fetch = +refs/heads/*:refs/remotes/team/*
not fetch = +refs/heads/*:refs/remotes/libregit/*
[22:33] quiliro:biovoid: fixed sample -> https://paste.debian.net/plain/1193934
[22:45] heckyel: cuando puedas, despues fijate si ya tienes acceso
deberia de ya funcionar
[22:46] Emulatorman: sí funciona. Lo probé hace rato :-)
ok genial
ya subi los repos core.git y extra.git en el team
o sea que puedes subir commits ahi
en lo posible hacete una rama (ej. heckyel)
asi no nos pisamos en la rama maestra
[22:47] Emulatorman: bien. Aunque dudo que use mucho el git
quiliro: eso debemos de mencionar mañana en la reunión, para que el equipo se haga sus ramas propias en los repos de team
[22:48] heckyel: ok
usas mercurial?
o subversion?
Emulatorman: uso git. Me refería a subir archivos a git.hyperbola.info :)
[22:49] ah ok
igual de ultima tienes tu propio usuario de git para subir codigos personales
o mirrors
[23:00] Emulatorman: si han terminado, subiré este log
ok, si
ya terminé
~~~~
_Click on me to see_
## Meet 8 - 2021-04-15
~~~~{.irc}
[12:22] Minall: you can give everyone the link you gave me
[12:23] Minall: that is very much more begginer-friendly
the people that know could skip it
Which one, the 00×00 Programmer Wannabe course?
yes
https://0x00sec.org/t/programming-for-wannabes-part-i/1143
A volunteer is preparing a document with a summary of the chats
[12:24] Cool!
thanks Minall
yw
[12:25] and will translate that spanish document to english
Now, we talked about GIT, which is just the tool we use for developing, which let us do essential developing things: Manage changes we make (even changing one letter), rollback if we made wrong changes, and allowing us to be update with the code and publish our changes in a safe repository, away from the main project but with changes that can be added to the main project if they are good
[12:26] The simplest part is just, git are just simple commands, but you have to know what you want to do, for that, a course would do, or just ask for help, that way one can learn if git is capable of what we want to achieve
[12:27] the document with the summary will not be ready for a week more…but the draft is ready
I would like to publish it once coadde1 and Emulatorman_ have set up the git infrastructure
[12:28] so that everyone can collaborate
[12:29] In a git project, anyone can collaborate with their changes, without damaging the main project which is a lot to ask when developing
[12:30] And since this team cares about security, each one of us have given a key which identifies us, so the changes we are making is us and nothing else, and all communications are secured of course
[12:31] Lol
IRC is the farthest thing from security!
tech_exorcist: do you have a ssh key?
I find it ridiculous to discuss Hyperbola’s future plans here.
I have several
great, tech_exorcist
They should do it on a more secure channel. Like tox.
infinite_recursi is because of the topic, I mean, we’re just learning C here
[12:32] Today is ok.
infinite_recursi: isn’t this channel meant to be public?
Some development things to know like git
are you on the hyperbolaBSD development team, tech_exorcist
?
Yesterday and a couple days before, it wasn’t.
However, important stuff has to be talked through encrypted mail or tox
are you on the hyperbolaBSD development team, tech_exorcist | I’m not
Yesterday and a couple days before, it wasn’t. | uhh, I’m pretty sure that I always autojoined this channel just fine
However, important stuff has to be talked through encrypted mail or tox | of course
[12:33] Encrypted mail cannot reach a group
Encryption typically works for 1 person.
tech_exorcist: would you like to be in the development team? it will demand working 1 hour per day
volunteer
[12:34] What about tox?, but again, we’re forming the dev team, but right now the topic is C introduction
tech_exorcist: would you like to be in the development team? it will demand working 1 hour per day | no thanks, and it’s mainly *not* due the 1 hour per day requirement
but it is not strict, tech_exorcist
hmm
I can’t anyway
I think we’re getting a little off-topic, you can talk about it one to one or outside the meeting quilito tech_exorcist
[12:35] s/quilito/quiliro
Main topic> C Introduction
sorry Minall
[12:36] the point is that contributors need to send Emulatorman_ their ssh public key
[12:37] As I know, C is a low level language, so there’s no much abstraction and you have to make everything on every process right?
[12:38] but it is not mandatory to know how to program….what is needed is that the contributors to the kernel know what are the free licenses we use, what is the hyperbolabsd project and to have the desire to learn to program in C and assembler (a little9 )
yes, Minall
but it is very powerful
and you can have libraries
[12:39] And it is compiled, aside from other High Level Languages which run without compilation, this makes C testing to need a step to test the program, but makes single code of C quicker, used for drivers which talk directly to hardware, and it is the most flexible thing you can work with
with: include
A code we develop can be compiled to more architectures, not just a x86 but ARM or others
[12:40] everything is compiled…the difference is if they are compiled at runtime or pre-compiled
* Minall Has to go, but he will be connected for the log and watching from above
\o
Minall: nice to see you
[12:41] Minall: meeting will start in 20 minutes
hi quiliro
hey buddy!
So not over?, cool, 2pm is good for me but, I think I will join at the middle of the meeting
so you preponed it 1h today
[12:42] I have some minutes though so, let’s keep going
1pm Minall
ok
rachad: you asked it to make it earlier
[12:43] but I thought some people might miss it
I did not think it would catch you in the middle of a meal
sorry
Now, C is a low level language because of that you can talk to the HW with it, for that it is used for kernel development… Just to make an example, not just for computers, some device’s kernel is made on C
but it is as it is, rachad
[12:44] will ask next time, rachad
its okay quiliro
i will just miss the first minutes and join you
have you made C programs, Minall ? why don’t you make a test program?
For example, on a game device I had, I could install an app with custom C code, which will allow me to produce sounds connecting to the speakers through a C library and an algorithm
[12:45] So System Libraries are just that, C libraries we can use to
talk to a hardware device
you see fasting means i dont eat or drink anything all day so i cant miss this meal quiliro :)
Let me get you this exact example:
[12:46]* Minall is looking for this example
[12:47] quiliro This is sorta of a complicated example
Do you want me to put it
paste it
on a paste service
but it should be your work
[12:48] that would be good practice
https://pastebin.com/CMcBs5By
[12:49] Now, here I am using some main libraries, and I define frequencies for the speaker to play
Saying something like: If I push the X button on the device, play this frequency
but this is specific for this game device, but it is the same for the computer
Use a system library to connect to a HW, and do something according to what the HW does
[12:50] I have to head out now, I think you can explain the ifs and the math behind it, and the frequencies quiliro
* Minall Coming back after finishing a quick meeting
[12:53] Minall: the exercise is explaining your program to newbies….in 7 minutes
[12:54] Minall: did you write this program or modified someone else’s program?
[13:03] Hello, greetings from the middle of the world.
[13:04] hello LightBearer :)
[13:05] welcome to the meeting everyone…including you, LightBearer
how are you rachad?
im doing great LightBearer
ty quiliro
[13:06] how is life arround you LightBearer
fine thanks a little cold and a small rain.
nice
and there? rachad
a bit cold here as well
see u later
* rachad is going to eat something tasty
[13:07] In this meeting we will discuss C language…feel free to comment what you want about your experience with C languaje just yet.
ok
The power of C be giveth to you my dear!
[13:08] and the spirits of it are to give everyone power.
[13:09] to be free, to code, to read…to make machines serve us
machines shall not have any power over us as users
[13:10] has anyone read https://0x00sec.org/t/programming-for-wannabes-part-i/1143 ?
I have this book “The C programming Language” by Dennis Ritchie
[13:11] It’s good for people who have learnt other languages before.
It’s quite concise, just 190 pages total
Without Appendices
https://www.tutorialspoint.com/cprogramming/index.htm
oh…nice infinite_recursi
[13:12] infinite_recursi: That’s the one recommended to me by a friend. I started it yesterday
any link?
[13:13] A quick DDG search returns a pdf of the current version (v2), but I am not sure if it is legally hosted, so I am hesitant to share that
v1 is outdated, but available on archive.org
on tutorialspoint, C programming video tutorials require javascript to be shown
biovoid: what is the license?
oof v2
[13:14] of v2
what can be outdated of C?
biovoid: Dennis Ritchie is the creator of C language. But it’s concise, it doesn’t explain what happens on hardware when someone writes "float c = 3.14;"
[13:15] I read this fantastic book “Teach yourself Ansi C++ in 24 days by Jesse Liberty.”
Best of the best books to learn programming!
It’s 1st 7 days are enough but it’s a long read.
what about for C?
quiliro: I don’t see an explicit license, but it is published by Prentice Hall, so I hesitate to think it is freely available
[13:16] I don’t know any for C. I’ve read just this 1 for C by Dennis Ritchie
weird it does not have a license
it is not illegal to give a link, biovoid
with that we can check the license
[13:17] even if it is illegal to publish copyrighted works, giving links to them is not illegal
https://hikage.freeshell.org/books/theCprogrammingLanguage.pdf
[13:18] on “outdated”: function calls have changed form since the initial release (much better now IMO), and there are updated notes on best practices
https://b-ok.asia
but not very much has changed
but my pdf link above is for v2
[13:19] infinite_recursi: Checking available domains.
Please wait…
Unfortunately, no available domains were found. But you can try to login using VPN, TOR browser or suggested domain below.
[13:20] try https://b-ok.cc
[13:21] Try with tor.
Anyways, I’ll leave now.
[13:23] infinite_recursi: you asked the early meeting
[13:24] Yes, in general. I’ll be here tomorrow. I don’t wanna learn C. I already know the syntax.
I need to practice it
the publishing will be communicated in 30 minutes
Also, throgh isn’t here
[13:25] when Emulatorman_ comes
so we can go back to the usual times
[13:26] since they could not come at these times, worse an hour earlier
[13:28] Unfortunately I don’t think it will be possible to cater to everyone’s schedule… I think leadership will have to enforce a stable time, and those with conflicts will be responsible for their own involvement
[13:29] hi guys
i’m available now
* rachad is back
:)
hi Emulatorman
[13:30] hey buddy
hi rachad
the people that called for an early meeting left
ok, seems so
and throgh did not come
it is common, because we have different time zones
[13:31] so I think the best is to keep the same time as before
since the one who preponed the meeting is not intrested we should get it back to the usual time
whoever can come, will come
yes i think so, i prefer the same time as before for workload reasons
for meal reasons here :D
[13:32] I agree with you, for me was very hard to be on time and people are not here with us
LightBearer revived
i was resting some time ago, because i’m working in the nights by developing code and studying
its so important though im fasting all day :)
[13:33] quiliro you think you are funny ;=)
haha
[13:34] haha or jaja are the same thing
we noticed yesterday, LightBearer
i would let you know guys coadde will complete the struture for tomorrow, currently he is developing new scripts to ease the options to create/delete/list git repos for each member in their personal git accounts inside our server
ok
[13:35] have you heard of throgh?
im sure he will join in a bit quiliro
[13:36] no, as i said some time ago, i was sleeping/resting until now
the draft concerning the summary of the chats we had before is ready
[13:37] but it needs to be heavily edited
it would be nice to publish it on a git repo
is somewhere temporary available?
i think i will start using some javascript from trusted sources
[13:38] like riseup pad or disroot cloud
quiliro: you can clone one of our git repos and create commits locally until our git will be available to push
* quiliro weeps for the kidnaping of rachad
ahha
quiliro: im following Emulatorman
[13:39] and throgh
* Minall Is back, with more weapons
nooooooo
HI all
https://git.hyperbola.info:50100/documentation/roadmap.git/
ok Emulatorman
they use some javascript sometimes
hi Minall
you can clone it
hello minall
will do now
[13:40] then you need create a git repo of that in your personal git account
and another one for team
git clone https://git.hyperbola.info:50100/documentation/roadmap.git/
to push your commits
on the command line
quiliro roadmap or algorithmg?
neither
[13:41] quiliro: the link you gave us says: repository seems to be empty
Emulatorman: if I clone it, why do I need to create a git repo
then you will need change the URL to ssh://git@git.hyperbola.info:51100/~git/~team/documentation/roadmap.git
quiliro ^
[13:42] that “user” git repo is focused for the team who will have entire access there all members
LightBearer: it is not a link…it is a command for the terminal
roadmap.git/info/refs not valid: could not determine hash algorithm; is this a git repository?
[13:43] I guess it is: git ssh://git@git.hyperbola.info:51100/~git/~team/documentation/roadmap.git
Was my C example of use on the meeting quiliro?
or not, Emulatorman
no Minall
quiliro: if you want create a copy for your personal git account, you can create a different “origin” in ssh://git@git.hyperbola.info:51100/~git/~~quiliro/documentation/roadmap.git by creating a git bare repo clone
it would have been, if you would have explained, Minall
[13:44] :c, I had to go, but I’m here now
quiliro: for that, coadde is creating a script to ease the life of us
Once we end this git topic I can explain a little
thanks Minall
quiliro: so you will can access to your personal git account and just respond the options to create git bare repos there
[13:45] but what can I do right now, Emulatorman ?
quiliro: even you could push your personal ones from different projects while those ones are free and follow the FSDG and Hyperbola Guidelines
quiliro: let me see the new coadde structure right now…
[13:46] “coadde structure” sounds so exclusive!
So right now we’re making the git repo for us to clone?
coadde1: ^
[13:47] coadde will push the source codes of those scripts soon
Minall: coadde1 is making it easier to work with several teams
they will be licensed under GPLv3
[13:48] nice!
quiliro: i saw the new structure, so i suggest you clone the repo in https://git.hyperbola.info:50100/~team/documentation/roadmap.git if it will be adapted for Roadmap
at least that repo will be adapted for the team
[13:49] and focused only for Roadmap
remember create an custom origin by pointing to your personal git repo
[13:50]