if you do Gantt charts, please make sure you implement as many dependency types as possible - most of the power of gantt charts lies in how depencies allow for changing one thing and having automatic adjustment of the entire timeline, but almost all of the tools I've used have only implemented "this task starts when that task ends" which is infuriating
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Thank you so much for your feedback.
This is indeed a feature that would be interesting to implement—offering three types of links between two tasks:
- One would be a flexible link that allows the end date to be moved without affecting its downstream tasks
- The second would be a dynamic link that maintains the gap between upstream and downstream tasks regardless of any changes to the end date of the upstream task
- The last one would be a semi-dynamic link that simply shifts tasks backward to stay on the critical path of a set of tasks.
Of course, I need to consider all the constraints this might create in the current user interface. But it’s a very interesting idea that I hadn’t considered before.
You're very welcome! Just to be clear, these are the types of dependencies I was thinking:
- this task can only end a set time after that task ends (the cleaning of the job site can start during the job, but can't end until the job does)
- this task can start after that task has started (I can start processing lab data after the first experiments have come in - I don't have to wait to the end)
etc.!
I think it should be possible to define many dependencies / constraints and have the program simply freeze and flag when there are conflicts due to overdefining. I'm sure there's a way to calculate the degrees of freedom, though the math isn't something I can be bothered with rn haha
Wildly ambitious editing timeline in that chart there 😔
Could be a 20s clip! 😀
Hardly none is mostly all.
Testing, test plans, and QA is not "mostly all".
Let's also stay on topic please. Its tagged appropriately and the relevant disclosure is present.
Yes that's my point, they misphrased it
I read the original differently than you, but it seems its been edited in the meantime (and I'm on mobile at the moment)
Either way, I think all is well currently
Just a small point, double negatives can get pretty confusing. Even in English, you often have double negatives becoming a negative rather than a positive, e.g. "I didn't go nowhere" or "You don't know nothing". Changing which part of the phrase you emphasise can also change that, for instance, if you said "I didn't go nowhere" it implies that you did in fact go somewhere (double negative becomes a positive when stressing the second negative). This gets all the more confusing when you bring in other languages, since they all handle double negatives differently!
It's not my place to argue with your opinion.
Thank you for taking the time to share it anyway 😉
I mean when you say "hardly no AI" that means it was "mostly all" AI. I don't think that's what you meant to say.
English isn’t my first language, but no matter how many times I check my translation, it seems to make sense to me.
But anyway, I’m sure you understand the nuance in that sentence better than I do, so I’ll take it back just to be on the safe side
The original title was : [AIP] besstiolle/Timeline: my own tool for organizing my timeline diagrams with (hardly) no AI-generated content
I don't know why besstiolle is getting downvoted when they are correct.
When people say that there is very little of something the natural way is "hardly any rain" for example. So if you invert the meaning from "any" to "none"/"no" the whole sentence means the opposite.
I guess it could be explained as follows (but I am no ethymologist, just thinking aloud here, may be wrong):
"hardly any rain" means that there is so little of it, it is hard to even say that there is any rain.
If your friend says to you "There is no rain" and you go outside and it pouring, you could say 'Hardly "no rain!" ' As a kind of mocking comment highlighting that it's the complete opposite of no rain. It is very hard to call is "no rain" when it's raining so much.
Hope this helps!
If your friend says to you “There is no rain” and you go outside and it pouring, you could say 'Hardly “no rain!” ’ As a kind of mocking comment highlighting that it’s the complete opposite of no rain. It is very hard to call is “no rain” when it’s raining so much.
Hope this helps!
I also thought that was how it worked, but then again, as English isn’t my first language, I’d rather not dwell on that detail
ho ...
😱