NixOS Marketing | 273 Members | |
| NixOS website + marketing team: https://nixos.org/community/teams/marketing.html | 59 Servers |
| Sender | Message | Time |
|---|---|---|
| 26 Oct 2023 | ||
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 | |
| I have been wanting to run my own NixOS newsletter for a while | 11:45:34 | |
| I am mostly interested in a newsletter targeted for people working in NixOS/Nixpkgs/Nix/ecosystem of | 11:45:51 | |
| According to this post https://discourse.nixos.org/t/marketing-team-update-for-july-june-2023/31238 It's IdaBzo and garbas, though I remembered it being djacu at some point | 14:54:04 | |
| I worked on the what's new in nix videos for a bit but not the newsletter. | 17:30:16 | |
| 1 Nov 2023 | ||
In reply to @garbas:matrix.org I think this is a bit more upstream and complementary. What a good branding strategy does for you is to provide clarity. it helps establish things like what is our identity, tone, value proposition, what are our values, ... that helps create a tone, more consistent feel, and communicate more clearly. As developers, we tend to view the website in terms of functional changes only, and it's hard to get the website right without these other dimensions. Same with the social media posts. The branding strategy can act as a filter and give a more directed feeling to the posts. Does that make sense? | 09:22:17 | |
| As part of the work on the S3 cache GC, we discovered that the vast majority of our Fastly traffic is coming from North America. We are wondering if this could be mostly GitHub traffic. Would anybody like to work with the various upstream nix install actions to get them to add the "user-agent-suffix" to their Nix config? That would allow us to parse the logs and make that distinction more easily. Bonus point if the user-agent includes which github org is using the cache, and we can then approach them for sponsorship :) | 10:15:47 | |
| 2 Nov 2023 | ||
| * As part of the work on the S3 cache GC, we discovered that the vast majority of our Fastly traffic is coming from North America. We are wondering if this could be mostly GitHub traffic. Would anybody like to work with the various upstream nix install actions to get them to add the "user-agent-suffix" to their Nix config? That would allow us to parse the logs and make that distinction more easily. Bonus point if the user-agent includes which github org is using the cache, and we can then approach them for sponsorship :) => https://github.com/cachix/install-nix-action/issues/198 | 07:39:12 | |
| Jonas Chevalier: can we announce it more broadly on Discourse? | 14:18:07 | |
| So that people are not surprised | 14:18:13 | |