Afaik there is no universal way to handle numbers in alphabetical lists. Sometimes numbers some before letters, sometimes after, etc.
A digit is not a part of the alphabet, right?
- If you could deploy a demo that doesn't require a signup/sign in, it'll make things a lot easier. You can reset it every x hours.
- The feature list is empty as I can't see what it offers or a comparison to other tools.
- After creating a task, I can't edit it.
Project management is very complicated and there's different groups of users, which one is yours? Those who need a full fledged jira with sso? they won't self host and won't care if it's open source. Small shops that need something cheap? Hobbyists or students?
I'm selfhosting vikunja https://vikunja.io/ at the moment. Opensource and supports my selfhosted sso.
You can find more here
https://github.com/awesome-selfhosted/awesome-selfhosted?tab...
https://github.com/awesome-selfhosted/awesome-selfhosted?tab...
Once again kudos on releasing and opensourcing it.
Not necessarily true. Id like to replace jira in an enterprise environment and we do need sso and prefer to self host.
We use the atlassian products at work and are planning to replace Bitbucket with Gitlab within short.
It worked well in ff on Android, except i did not see the final set of words in the end and share link got undefined in it:
I completed today's Fragment in 03:59. Think you can beat my time? Give it a try: https://playfragment.com/?=undefined
Some features, like clipboard history and window management (i.e "tabs") are better left to the desktop environment though. Every app shouldn't need to reimplement this logic.
The idea of the (guest) speaker was that when you hold a presentation, say the most important things first.
If anyone gets up and leaves, or the presentation is cut short, you should've gotten the most possible value out if the time.
Then dig into details as the presentation progresses and answer questions or concerns right away.
Answering right away does not mean side track the whole presentation, give the major response and take details later.
I.e "TL;DR" your presentations, oral or written alike.
A simple example is: you've been given the task of estimating the cost and work involved in developing a new feature.
When you present your result, don't start by listing all the things needed to be done and all the investments needed to be bought.
Start by giving the receiver what's on her mind: what is the price, when can we deliver, how many persons do need.
Then dig into the overall details of how you ended up in that, perhaps that the tools needed to be purchased are X, Y and Z.
Then dig into why we need those tools, and so on.
If you have to interupt early, or if you have a big trust from the receiver, the main point has been delivered and the the remaining 80% of the time can be invested in more important things.
I've applied this in my life, privately and professionally, and it's been working out well. I also hope this response was a good example of what I tried to pass on.