Re: [Infotropique] template language braindump
|This message is part of the following thread:|
|the complete thread tree sorted by date|
> > > Interjection: > > > I've discussed and reflected sometimes monologues, more often dialogues with dvn > > > over 12 months now. Before 2017 I had my own key-experiences and 'aha' moments > > > that made me pick GuixSD over everything else I considered and worked on before. > > > There are still open parts in the design, ideas I'm exploring. Some difficult to > > > express until a certain point of talking "almost nonsense", braindumping conversations > > > with friends and people I meet regulary.
> > Extending this: The general _concept_ for the selftitled software is done, but I'm somewhere > > between analysis, design and implementation. In 2017 I made 270 commits to > > Guix (master), excluding the 300+(?) commits I've made in my branches (like > > 100+ rust crates for secushare). The marge majority of 2015,2016 and 2017 commits
> > was done because of 2 reasons: 1) I wanted multiple functional Guix desktops > > at home, so I needed the software I used on Gentoo and other systems. > > 2) it fits into the general frame of preference I want to be able to offer > > to people. For example: I would never use Thunderbird again, but I'm working > > on it (very slowly though). > > Guix has grown quiet large. > > I want to move the content of the old bugtracker to the new one > > (https://gitlab.secushare.org/infotropique/issues/) in the next > > 2 weeks. I'll review the content and see how much of these > > 4th(?) generation tasks are still applicable. Most of the time > > I'm not really working with a bugtracker, that's why the bugtracker > > might lack really way behind what I know, want and do. > > I want to get you involved, so this needs to change. At least I > > need to start using the bugtracker to include general tasks that > > can be picked up, ideally in sync with the website content.
> > > I know almost nothing about wisp. I've seen bits of the code, I remember bits of > > > the talk Arne gave. I see some potential problems, but it could be a future > > > goal. > > > Keep in mind that the code ideas include: > > > - to *extend* Guix, not to write duplicate code > > > - to make the code reusable for many generic applications of the code. > > > Think of a framework for OS creation giving you a sandbox and some > > > maintained instruction manuals, making use of the really free expression > > > you have in Guix to build and define systems. > > > - low effort maintenance for those who'll make use of the system.