Yeah, I agree. I mean, we have different files for different chapters. So I guess a trunk based approach would work. Benefits from using a branch for each chapter variations might be needed, but only in specific cases. And to be honest, I think this does not really applies to us
semperpeppe
joined 2 years ago
Thank you for your reply! What are the "objects" possibly determining a branch? Features? Chapters? Writers? Releases?
Idk, she's black?
Thank you so much for your suggestions. I wasn't even thinking about something like notion or baserow, so this is definitely a good idea.
On mobile I have etar calendar and davx5. It generally works pretty well, even if the sync is not instantaneous. I have a few problems with inviting people to events and sending the associated email/invitation, but it's just a matter of how the SMTP servers are managed, just a minor thing
This is pretty much my setup. I use nextcloud as a calendar, but for to-do lists I am experimenting with Joplin, with a mermaid plugin for also mindmaps. I'd like to automate everything and have a all-in-one solution but it does not look like an easy thing so far
I've never played this game, but it's soundtrack helped me prepare for so many exams in uni that I can't even remember. I will have to try it once!
I always wonder to whom this gets reported to
Man, what sort of thing you made me just discover ahahaha
This is exactly what I am looking for. I am interested also in how other federated applications do it. I had a look at Pixelfed's documentation, but they don't seem to have an API for that... Do you know anything about other services?
This is great advice. I don't believe we need a "stable" version. I mean, at a certain point our work will be ready and that's it. We are not going to have different releases. We will have other formats (like a shorter version of this report), but in that case those would live as a different repository I guess