ChanServ changed the topic of #kisslinux to: Unnofficial KISS Linux community channel | https://kisscommunity.org | post logs or else | "Seek simplicity but distrust it" -- Alfred North Whitehead
illiliti has quit [Quit: leaving]
jleightcap has joined #kisslinux
jleightcap has quit [Quit: WeeChat 3.0]
jleightcap has joined #kisslinux
n3o has joined #kisslinux
<n3o>
msg
n3o has quit [Remote host closed the connection]
n3o has joined #kisslinux
n3o has quit [Remote host closed the connection]
n3o has joined #kisslinux
<n3o>
Hello there!
n3o has quit [Remote host closed the connection]
jleightcap has quit [Quit: WeeChat 3.0]
jleightcap has joined #kisslinux
<testuser[m]>
Hi
an3223 has quit [Quit: WeeChat 3.2]
an3223 has joined #kisslinux
mahmutov has quit [Ping timeout: 245 seconds]
barpthewire has quit [Remote host closed the connection]
barpthewire has joined #kisslinux
mahmutov has joined #kisslinux
mobinmob has joined #kisslinux
sereg has joined #kisslinux
sereg has left #kisslinux [#kisslinux]
mobinmob has quit [Quit: Connection closed for inactivity]
Natris1979 has joined #kisslinux
<Natris1979>
Hi all, I want to make my own package for some software I use. What's the perferred workflow? Should I fork https://github.com/kiss-community/community or is it better to create my own git repo?
<dilyn>
if you plan on submitting the package to community, you should fork community
<dilyn>
you don't have to create a git repo if you don't intend on making use of something like vcs though. a repository can just be some folder on your machine
<Natris1979>
sure. I just like to have as much in vcs as is reasonable
<Natris1979>
I'm kind of bad at backups, so if I put all the things in vcs or otherwise in the clould I'm not so bad off
<Natris1979>
and if the community can benefit from my work, all the better