NixOS Marketing | 262 Members | |
| NixOS website + marketing team: https://nixos.org/community/teams/marketing.html | 58 Servers |
| Sender | Message | Time |
|---|---|---|
| 25 Oct 2023 | ||
In reply to @garbas:matrix.orgThe workshop part will be literally a training session to help everyone align their thoughts. The hacking part serves the sprint purpose Domen highlighted, to get things done quickly that are already agreed upon. Yes, attendance is a privilege, but I feel the NixCon governance sessions we did were fruitful. Otherwise there would have been some sort of opposition online. | 15:06:06 | |
| From all I gathered in the in-person or synchronous meetings of the past two years, especially with people I thought I was in some more profound disagreement, it always turned out we all kind of want the same thing. But for various reasons we often fail to align either on somewhat superficial aspects or on priorities and order of execution. Which hints at that our mental models of the problem structure and its internal dependency relations may be out of sync. But once that’s settled, the next steps are often obvious and uncontroversial. As long as the people involved manage to write down that thought process clearly enough, most of the time there is nothing to add to that. It does happen that small groups of people overlook important parts, and that’s why there needs to be a healthy interval between these discussions and final decisions, but otherwise it seems to work quite well that way. | 15:16:43 | |
| Right now it doesn’t even look like you’re in actual disagreement on the principle. Seems to me like the endorsement part could easily be resolved by providing some context in marketing posts: who’s message is amplified? Why does it matter? Who is amplifying? Things like that. | 15:20:37 | |
| „The Nix Marketing team“ is misleading in many ways. You’re actual people, like 2 of them, with lots of bias and personal opinion. But the brand apparently makes it look like „all of NixOS, whatever that is“, because that’s the way people reply. NixOS says this, NixOS does that. I’ve seen it so often. | 15:23:27 | |
| Being a little bit more specific about context outsiders cannot possibly have would get us really far, in my opinion. | 15:24:32 | |
| Doing it that way should promote people and what they do rather than the artifacts they happen produce on the way. I think that’s what we may want. | 16:13:27 | |
| fricklerhandwerk: I disagree on few point with your statements:
| 19:29:56 | |
| Jonas Chevalier: I would really like to understand what goals would you like to achieve with a more focused branding strategy. Just so you understand current goals of the marketing team: (1) attract new nixers - OUTreach (2) engage community to collaborate - INreach, i know it is not a word but i think you will understand :) If you would ask me what is the most urgent task at hand that we are struggling to do I think I was laud at the NixCon about it. We need to rework the website. We already have a messaging plan and the vision/strategy after that, but it is hard to do the first step, since it is not small amount of effort. | 19:39:06 | |
| 26 Oct 2023 | ||
| 06:47:11 | ||
No doubt.
I know very well what it means not to be able to be present where the action is, and I appreciate just as much that it's a luxury most can't afford for a number of reasons. Fact is though, there will always be in-person meetings, and we'll have to figure out how to make the best of all kinds of interactions that happen. | 11:30:50 | |
| I think the most important element of an in-person meeting in a community context like this is documentation. If the people participating clearly communicate what was discussed and work to establish a subsequent discussion in online channels, that goes a long way. | 16:55:33 | |
| 27 Oct 2023 | ||
| 01:24:22 | ||
| 28 Oct 2023 | ||
| Hey team I'm looking at the nixos-homepage main branch and trying to figure out how people are starting the astro dev environment. The only thing I see in the flake is a package for building the site the old way. Am I missing something? | 18:42:47 | |
| Home page needs some help, perhaps with someone with permissions: https://github.com/NixOS/nixos-homepage/issues/1138 | 20:16:52 | |
| 29 Oct 2023 | ||
In reply to @djacu:matrix.orgthat's not happening on main, but on astro/* branches | 10:39:39 | |
| I'm not sure if Hacker News is still a thing, I never really followed it, but I must admit it's kinda satisfying to see https://discourse.nixos.org/t/nixos-reproducible-builds-minimal-installation-iso-successfully-independently-rebuilt/34756 take the #2 frontpage spot for a while :) . The comments aren't even all that terrible. | 17:00:00 | |
| 22:41:14 | ||
| 30 Oct 2023 | ||
In reply to @hexa:lossy.networkI took a look at the branches and the only active one I see is astro/landingpage which hasn't change the flake.nix file significantly. So I'm still confused as to how people are developing astro components and testing them without astro available. | 03:53:17 | |
| 13:22:50 | ||
In reply to @djacu:matrix.orgUhm, this is mine but I didn't touch the flake.nix actively. Maybe direnv did some magic? | 20:26:18 | |
| Astro is an npm dependency and is installed through `npm install`. It's not a thing you have to install globally like hugo or jekyll. | 20:27:23 | |
| * Astro is an npm module and is installed through `npm install`. It's not a thing you have to install globally like hugo or jekyll. | 20:27:39 | |
| * Astro is an npm module. It's not a thing you have to install globally like hugo or jekyll. | 20:27:52 | |
| But I wonder why your CI breaks when feature branches break. This seems counterintuitive. | 20:28:48 | |
In reply to @avocadoom:avocadoom.deYeah I got word back from garbas . npm install and npm run dev. I was looking for a devShell from npmlock2nix or something like it. | 21:29:58 | |
| Imo as long as you are not packaging a node app using npnlock2nix doesn't really make sense | 21:38:17 | |
| And since the output is static there is no nix related build process needed. I tried this for NixCon Website and with modern SSGs this just shoots you in the foot at every secound corner, since most fetch images and others things or external API data from a CMS for example. | 21:40:20 | |
| But the node Version is pinned, so we are all on the same runtime, which in combination with the npm lockfile should be enough | 21:44:40 | |
| I built my personal site using astro and npmlock2nix and had a similar experience. Using nix really limited the packages I could use because package authors would try to fetch random things at build time. I did get it running tho | 22:02:43 | |
| 31 Oct 2023 | ||
| Hello marketing team, I would like to work on the newsletter, who I should speak with that? | 11:45:27 | |