August 24 #10

Merged

cloudyy merged 16 commits from august24 into main 2024-08-13 11:05:47 +00:00

Conversation 13 Commits 16 Files changed 4 +70 -35

cloudyy commented 2024-07-22 12:29:40 +00:00

Collaborator

Copy link

If you have any suggestions, posts, commentary, feel free to comment on this pull request or push your changes. If you don't have write permissions, you can create a review.

Check zine-preview.exozy.me from time to time to preview what the final result would look like.

If you have any suggestions, posts, commentary, feel free to comment on this pull request or push your changes. If you don't have write permissions, you can create a [review](https://forgejo.org/docs/latest/user/pull-requests-and-git-flow/#reviews). Check [zine-preview.exozy.me](https://zine-preview.exozy.me) from time to time to preview what the final result would look like.

👍 1

cloudyy added 2 commits 2024-07-22 12:29:40 +00:00

Updating dependencies 4849fae970

to-do post c6ba6d1540

cloudyy added 1 commit 2024-07-22 12:32:52 +00:00

trigger CI 1e4b78ec99

a commented 2024-07-23 22:58:45 +00:00

Owner

Copy link

Nice, we're starting really early this time. @cloudyy you might also want to announce this PR on Matrix.

Nice, we're starting really early this time. @cloudyy you might also want to announce this PR on Matrix.

a added 1 commit 2024-07-24 00:29:17 +00:00

Commentary for Ubuntu and Janet as DB posts ffc7cb4126

dragongoose commented 2024-07-24 15:54:24 +00:00

First-time contributor

Copy link

Give me a couple days, I'll have an entry about DSP and radio signals done real soon!

Give me a couple days, I'll have an entry about DSP and radio signals done real soon!

🚀 1

cloudyy added 1 commit 2024-07-24 23:00:31 +00:00

trigger CI ebefcd9021

a commented 2024-07-24 23:49:54 +00:00

Owner

Copy link

@cloudyy Maybe you should stick to manually starting the CI in the Woodpecker UI to avoid littering the commit history with empty commits?

@cloudyy Maybe you should stick to manually starting the CI in the Woodpecker UI to avoid littering the commit history with empty commits?

👍 1

cloudyy added 1 commit 2024-07-25 03:22:23 +00:00

running the preview step manually instead of on the deployment event 4709aa97e5

iacore commented 2024-07-26 10:41:02 +00:00

Owner

Copy link

single branch name (next time) pls

june24 july24 august24 :(
draft draft draft :)

single branch name (next time) pls june24 july24 august24 :( draft draft draft :)

iacore commented 2024-07-26 10:43:58 +00:00

Owner

Copy link

the Janet article is old old. my articles are numbered by inception date of ideas.

the Janet article is old old. my articles are numbered by inception date of ideas.

iacore added 1 commit 2024-07-26 10:45:10 +00:00

correction ... 461c6c2204

is: janet in-memory data structure
is not: janet code file

cloudyy commented 2024-07-26 13:41:28 +00:00

Author

Collaborator

Copy link

single branch name (next time) pls

june24 july24 august24 :(
draft draft draft :)

Personally, I prefer to organize things this way to make it clearer to everyone what we're working on. But if more people think it would be better to just have one draft branch, we could do that instead.

> single branch name (next time) pls > > june24 july24 august24 :( > draft draft draft :) Personally, I prefer to organize things this way to make it clearer to everyone what we're working on. But if more people think it would be better to just have one draft branch, we could do that instead.

a added 1 commit 2024-07-26 14:45:32 +00:00

Simplify .woodpecker.yml, remove @iacore Janet post 6ddc76c5fe

a commented 2024-07-26 15:09:39 +00:00

Owner

Copy link

@iacore Sorry that I misrepresented your Janet post, since I read it and the code in a rush and didn't get the main idea. I guess it's actually more like writing a program using two general purpose languages in one file. Also, I just took the most recent posts from feeds.exozy.me and didn't notice your Janet post was so old.

Personally, I prefer to organize things this way to make it clearer to everyone what we're working on. But if more people think it would be better to just have one draft branch, we could do that instead.

It might be nice to just have an immortal draft branch instead of creating and deleting monthly branches, although I'm fine with either. For the monthly branches, I prefer abbreviating the months such as mar24 instead of march24, but @cloudyy feel free to do either. It's all just bikeshedding, really.

@iacore Sorry that I misrepresented your Janet post, since I read it and the code in a rush and didn't get the main idea. I guess it's actually more like writing a program using two general purpose languages in one file. Also, I just took the most recent posts from feeds.exozy.me and didn't notice your Janet post was so old. > Personally, I prefer to organize things this way to make it clearer to everyone what we're working on. But if more people think it would be better to just have one draft branch, we could do that instead. It might be nice to just have an immortal draft branch instead of creating and deleting monthly branches, although I'm fine with either. For the monthly branches, I prefer abbreviating the months such as mar24 instead of march24, but @cloudyy feel free to do either. It's all just bikeshedding, really.

a added 1 commit 2024-07-26 15:19:14 +00:00

Limit publish step to pushes to main 205265f268

iacore commented 2024-07-27 16:27:43 +00:00

Owner

Copy link

@iacore Sorry that I misrepresented your Janet post, since I read it and the code in a rush and didn't get the main idea. I guess it's actually more like writing a program using two general purpose languages in one file. Also, I just took the most recent posts from feeds.exozy.me and didn't notice your Janet post was so old.

np.

It's all just bikeshedding, really.

Nooo -- Since I use Arabic numerals, I had to remember how to spell months in English. With one branch, it would be git pull and done.

> @iacore Sorry that I misrepresented your Janet post, since I read it and the code in a rush and didn't get the main idea. I guess it's actually more like writing a program using two general purpose languages in one file. Also, I just took the most recent posts from feeds.exozy.me and didn't notice your Janet post was so old. np. > It's all just bikeshedding, really. Nooo -- Since I use Arabic numerals, I had to remember how to spell months in English. With one branch, it would be `git pull` and done.

iacore added 1 commit 2024-07-27 16:46:51 +00:00

add commentary 7e2b4ad305

a commented 2024-07-27 19:36:51 +00:00

Owner

Copy link

Nooo -- Since I use Arabic numerals, I had to remember how to spell months in English. With one branch, it would be git pull and done.

We could also use YYMM (like what arXiv does) for the branch names. @cloudyy any thoughts?

> Nooo -- Since I use Arabic numerals, I had to remember how to spell months in English. With one branch, it would be `git pull` and done. We could also use YYMM (like what arXiv does) for the branch names. @cloudyy any thoughts?

cloudyy commented 2024-07-27 21:05:07 +00:00

Author

Collaborator

Copy link

Nooo -- Since I use Arabic numerals, I had to remember how to spell months in English. With one branch, it would be git pull and done.

We could also use YYMM (like what arXiv does) for the branch names. @cloudyy any thoughts?

It would be easier to type but the problem would remain the same which is a branch for each month. Let's stick with just one 'draft' branch from now on, as that would solve both problems.

> > Nooo -- Since I use Arabic numerals, I had to remember how to spell months in English. With one branch, it would be `git pull` and done. > > We could also use YYMM (like what arXiv does) for the branch names. @cloudyy any thoughts? It would be easier to type but the problem would remain the same which is a branch for each month. Let's stick with just one 'draft' branch from now on, as that would solve both problems.

👍 1

dragongoose commented 2024-07-30 23:56:24 +00:00

First-time contributor

Copy link

Give me a couple days, I'll have an entry about DSP and radio signals done real soon!

All done!
https://drgns.space/posts/making-a-sdr-transciever-beginning

I need to add mobile support to the site and fix some rough edges and styling issues, but this should be good enough for now. Should I write a description for the zine?

> Give me a couple days, I'll have an entry about DSP and radio signals done real soon! All done! https://drgns.space/posts/making-a-sdr-transciever-beginning I need to add mobile support to the site and fix some rough edges and styling issues, but this should be good enough for now. Should I write a description for the zine?

🚀 1

a added 1 commit 2024-07-31 20:58:10 +00:00

SDR commentary 0625cab172

a added 1 commit 2024-08-05 00:53:05 +00:00

TODO: Epilepsend tweaks post af5a2414af

cloudyy added 1 commit 2024-08-06 12:51:16 +00:00

Adding a title to the gradience post, adding commentary about using a dumb phone, adding commentary about fast food content, adding commentary about the updates to epilepsend + prettier fix 0288726052

cloudyy added 1 commit 2024-08-06 12:57:59 +00:00

added missing link about the gradience post e2db53835c

cloudyy added 2 commits 2024-08-12 11:02:17 +00:00

updating packages 68c53626f7

added a description d7d17a1da4

cloudyy changed title from WIP: August 24 to August 24 2024-08-12 11:04:12 +00:00

cloudyy commented 2024-08-13 11:05:07 +00:00

Author

Collaborator

Copy link

I'll be merging this month's issue now. Also as @iacore suggested, from now on let's use only one "draft" branch.

I'll be merging this month's issue now. Also as @iacore suggested, from now on let's use only one "draft" branch.

👍 1 🎉 1

cloudyy merged commit c308823d4d into main 2024-08-13 11:05:47 +00:00

cloudyy deleted branch august24 2024-08-13 11:05:47 +00:00

cloudyy referenced this pull request from a commit 2024-08-13 11:05:48 +00:00

Merge pull request 'August 24' (#10) from august24 into main

a commented 2024-08-22 12:29:59 +00:00

Owner

Copy link

@cloudyy Thanks for completing and publishing this month's issue while I was on vacation! I think we've set a new record for the longest amount of time to write an issue 😆 (22 days) but that's fine.

@cloudyy Thanks for completing and publishing this month's issue while I was on vacation! I think we've set a new record for the longest amount of time to write an issue 😆 (22 days) but that's fine.

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

4 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: exozyme/zine#10

No description provided.