[HN Gopher] Plane - Open-source Jira alternative
___________________________________________________________________
Plane - Open-source Jira alternative
Author : prhrb
Score : 373 points
Date : 2023-07-22 08:21 UTC (14 hours ago)
(HTM) web link (plane.so)
(TXT) w3m dump (plane.so)
| TheNewsIsHere wrote:
| As someone who typically rejects/hard-passes on products with the
| SSO tax (sometimes even when there's budget/will to go with the
| SSO-included tier), I really appreciate the lack of the SSO tax
| here.
|
| The era for security and in particular identity and auth
| management to be pay-to-play is long over and I appreciate when
| projects and businesses are honest about that.
| viewtransform wrote:
| SSO = Single sign-on
|
| "SSO refers to a SaaS or similar vendor allowing a business
| client to manage user accounts via the client's own identity
| provider, without having to rely on the vendor to provide
| strong authentication with audit logs, and with the ability to
| create and delete user accounts centrally, for all users,
| across all software in use by that client."
| qwertox wrote:
| One of the things I like most about Jira is the ability to
| execute useful queries via REST on the data stored in there.
|
| Most of the times when I read some post about Jira alternatives
| is that they completely ignore this topic.
| dboreham wrote:
| It would be nice if someone implemented a clone of Bugzilla
| functionality using modern tech. Jira is the wrong thing to copy
| imho.
| fndex wrote:
| Bugzilla still exists. And if you think something is the wrong
| thing to copy, just copy the "right" thing yourself.
| shagie wrote:
| One of the problems of Jira is that it allows you to make
| _any_ workflow for its issues.
|
| Bugzilla had a "this is how it's done, and that it is"
| attitude to bug tracking workflow - it _wasn 't_
| configureable. As such, it couldn't be perverted into a dozen
| gates with different approvals needed for each gated step.
|
| It's really easy to copy Bugzilla's structure into Jira. It
| is very difficult to keep management from changing it into
| something else in Jira.
| dec0dedab0de wrote:
| It's also valid to make a comment where a bunch of developers
| might see it, and hope one of them agrees and has the time
| and skills to do it.
|
| Or maybe just to reach someone who never used bugzilla and
| doesn't realize it's light-years better than jira or rally.
| fndex wrote:
| That's valid, but saying that a product a few developers
| created for FREE, and made open source so anyone could copy
| and change is the "wrong thing to copy" is just
| disrespectful.
| dec0dedab0de wrote:
| It would be disrespectful if thats all they said, but
| including "it would be nice.." and "...imho" changes it
| to politely giving their opinion on a third party forum.
| If it were a show hn, or the projects own forum I might
| agree with you, but this is the appropriate place to give
| armchair opinions.
| ctas wrote:
| What are the unique features or approaches of Bugzilla compared
| to Jira? Before Jira was a thing, Redmine was (is?) very
| popular and often received better reviews than Bugzilla, so I
| was a bit surprised you mentioned Bugzilla.
| dubcanada wrote:
| Why do people call things Jira alternatives that contain about
| 1/500th of the features? It's just a simple project management
| tool with a kanban board...
| windmark wrote:
| Because that's that most people see Jira as. It's easy to only
| use Jiras surface level features, like a Trello with a little
| more functionality, and not the more advanced ones.
| davnicwil wrote:
| yeah, marketing is all about using the simplest language to
| communicate truth relevant to the group you want to reach,
| not about communicating absolute truth to all comers.
| nickserv wrote:
| Marketing is not about truth, period. I prefer the older
| term for the occupation: advertising and propaganda.
| esafak wrote:
| Marketing is not advertising. davnicwil had it right.
| Marketing is about positioning and explaining your
| product.
| gonzo41 wrote:
| Because jira's advanced features kinda suck. They have a market
| lock because they have been able to own the space with first
| mover advantage and buy their competitors.
| zelphirkalt wrote:
| Usually not much more than the basic features are needed. The
| rest is mostly management feel good goodies.
| bdcravens wrote:
| Pretty common. Everything I've seen presented as a "Notion
| alternative" is nothing more than a note taking app, "Airtable
| alternatives" only copy the data-in-rows UI, etc.
| tmikaeld wrote:
| Looks great, too bad there's no Gitlab importer or integration
| yet.
| greatgib wrote:
| My opinion based on feature and screenshots is that the UX is as
| shitty as Jira. The nightmare with Jira is this product manager
| obsession with kaban boards that become overwhelmed once your
| project become serious.
| uxcolumbo wrote:
| What's the solution to this? Which app would you recommend to
| deal with projects that become serious?
| bartels_media wrote:
| Why not using Kanban?
| lozenge wrote:
| Just because your project is serious doesn't mean you should be
| looking at 300 things at once. Hence a kanban board.
| ResearchCode wrote:
| Or as they call it outside of the agile industrial complex, a
| to-do list. Nobody is stopping you from keeping one.
| arketyp wrote:
| This totally expected level of unconstructive critique makes
| this comment a miniature art piece.
| gjvc wrote:
| Snark all you want, but that's this person's experience and
| it's worth considering why that is the case. I'd wager
| they've been a victim of productivity theatre, with
| management saying "we need to be agile! make it so everyone
| -- your job depends on it!". Then, they may even hire an
| experienced agile manager but (for whatever reason) give them
| no chance to spend time and effort properly training everyone
| involved in how to work differently and to use the tools
| effectively, and how to communicate the "burn-down rate" to
| the users every time-period so that their expectations may be
| set correctly. Combine this with the attitude of many "I'll
| raise it as a ticket, then I'll have something official with
| which to chase the developers", and it's perhaps easier to
| see how things can become chaotic.
|
| Perhaps you've been fortunate enough to be employed where
| these things are managed better than my hypothetical scenario
| above, but my experience that is the exception, not the rule,
| so it's not surprising that people can become fatigued.
| arketyp wrote:
| My comment actually came from a place of empathy. With this
| comment though, I will be openly snarky when I say that
| you've now contributed to the art piece.
| gjvc wrote:
| Thanks for not paying attention.
| wkat4242 wrote:
| For me the problem is more that 'agile' is now a buzzword and
| companies try to apply it to lots of things where it doesn't
| really work.
|
| In our company our CIO declared everything should be agile. So
| now we log our hours in Jira. That's it :P supposedly that
| makes us agile or something.
| quickthrower2 wrote:
| That makes you great at sending resumes to other companies
| ResearchCode wrote:
| That sounds like micromanagement. Are you a contractor?
| mrweasel wrote:
| You can use Jira just fine without Kanban boards. That's really
| the beauty and the curse of Jira, it can be pretty much
| anything you want it to. To truly compete with Jira you need a
| level of flexibility that almost guarantees that your product
| will suck to.
|
| If you run Jira, Confluence and Bitbucket, the level of
| integration you can achieve is pretty unmatched. The cost: You
| need to buy the data center edition, on-prem is required to get
| any sensible level of performance, and you need Atlassian
| experts on staff.
| high_priest wrote:
| Alright, I am not denying you might be right, but it sounds
| like an old man yelling at cloud. If not Kanban, what else
| would you propose as the 'better' solution
| gardenhedge wrote:
| So whenever anyone doesn't like something you like you think
| it sounds like an old man yelling at cloud?
|
| There's no obligation to propose a better solution when
| saying something sucks.
| bartels_media wrote:
| Can anyone read that? https://app.screencast.com/jzzS96PuNylg6
| movedx wrote:
| I've wondering if something like a Discourse instance could be
| used to replace Teams, Jira, and email.
| jillesvangurp wrote:
| > Simplify your transition to Waterfall, Agile, and other
| workflows to keep up team's momentum with Cycles and Modules.
|
| LOL, at least they are honest about companies doing waterfall
| style planning being their target audience.
| aiisjustanif wrote:
| I mean sometimes waterfall is required depending on the
| industry, especially industrial or space and some of government
| and medical.
| pydry wrote:
| The closer you are to agile the more basic your ticketing
| system needs and vice versa.
|
| You could probably do without one at all even.
| smohare wrote:
| [dead]
| gorgoiler wrote:
| Most of my "tasks" are buggy, poorly written, feature
| incomplete, draft requests for code review which come with an
| implied contract that early feedback is welcome, but that
| I'll let you know when it's actually ready, and I promise to
| either make good on that or cancel the request and say why
| before the end of the quarter.
|
| Planning schmanning!
| hnarn wrote:
| I used to work at a company where incoming support tickets
| were just another jira project (FOO-123), it worked great
| because you could then relate the tickets to actual work
| items (BAR-123) and while the support tickets weren't public
| for obvious reasons, the work items were, so customers could
| easily follow the progress of the work item without having to
| re-contact support.
|
| My impression was that this level of transparency was
| extremely appreciated by customers, even in cases where bug
| fixes were marked as "won't do", usually with a workaround of
| some kind. This in itself also becomes an invaluable
| knowledge base over time, not to mention all the other
| benefits you get from support and engineering tracking their
| work in the same application.
|
| But of course, like all good things it didn't last, because
| the company was bought by some other company that thought it
| was absolutely insane to publicly admit that your software
| had bugs.
| anthonyskipper wrote:
| ^ You nailed it. The only issue tracker you need today comes
| with your source code repo. Both github and gitlab are not
| only more than sufficient, they are arguably better because
| the stripped down natures keeps people from doing silly
| things like all the jira anti-patterns.
| Hamuko wrote:
| I kinda wish we could migrate completely off Jira and just
| start using GitLab issues instead. Unfortunately that's
| probably a fat chance when GitLab wants to charge us
| $99/month/user if we want to grant non-developers access to
| our GitLab. Jira is like $15/month/user.
| neilv wrote:
| I've had good luck with getting GitLab Issues to do an
| appropriate variation on Kanban, so long as I have their
| Scoped Labels (which seems to be in the $29/user/month
| Premium plan). I like the tight integration with the Git
| workflows, and I like not having to manage yet another
| SaaS.
|
| Do some of your users need the $99 Ultimate plan, and
| GitLab salespeople couldn't meet you at workable pricing
| for your users who mostly only need to use Issues?
| Hamuko wrote:
| I don't think you can pick and choose the plans per user?
| We're currently using the security features of GitLab
| Ultimate and as far as I've understood it, that's
| $99/month/user for every user you need on your GitLab
| license.
| neilv wrote:
| I think enterprise software agreements can often be
| negotiated.
|
| In the case of GitLab, their pricing page has the usual
| easy ordering buttons for each pricing tier, but the $99
| tier button also has a prominent "Contact Sales" link
| right below the button. https://about.gitlab.com/pricing/
|
| Once you're already paying sticker price, and have
| invested in using it (i.e., moving to a competitor is a
| lot of work), your negotiating position will be
| different, but the vendor can still lose the account, if
| customer is unhappy enough to eat the moving costs.
| sanitycheck wrote:
| I wish.
|
| A client of mine decided to ditch Jira last year. Now what
| they do is use a much simpler system but with a ton of
| manual wrangling going on constantly. Lots of duplication
| across boards, most tickets are in the wrong state, nobody
| knows who's supposed to be handling any given task. I'm
| mostly trying to stay away from it.
|
| Your theory works if there are only developers, and they
| are all competent. Throw the usual mix non-dev staff into
| the mix along with the and it's a mess.
| IshKebab wrote:
| I strongly disagree. You can't easily have conversations
| about issues in Git and even if you could do you really
| want to have a commit for each message?
|
| I'm aware of some systems that try to tack issue tracking
| onto Git in a similar way to Fossil, but they just aren't
| as good as a proper issue tracker.
|
| That said, Jira is a _terrible_ issue tracker. I do not
| understand how it is so bad given that it is literally its
| only job.
|
| I used Phabricator for issue tracking in my previous
| company and it was so far ahead of Jira... It makes no
| sense.
|
| Something as basic as parent/child issues is barely
| implemented in Jira. You can only have 2 levels of
| hierarchy.
|
| You can't put a task in your sprint unless it matches the
| task filter for that sprint, which means you can't easily
| track the work of people that work on multiple projects.
|
| You can't even put tasks from multiple projects into one
| sprint. Realistically you should have a single project for
| everything.
|
| They haven't even got basic stuff like "refresh the page
| when information on it changes" working.
|
| And that's before you even get to the core flaw of Jira
| which is that it encourages product managers to
| overcomplicate it.
|
| But just because Jira is awful doesn't mean issue trackers
| in general are. Phabricator's is great. GitHub and Gitlab
| are basic but decent. I haven't got experience with any
| others but I'm sure there are great ones.
| smohare wrote:
| [dead]
| sanitycheck wrote:
| As you touched on, the major problem with Jira is
| actually that it does so much nobody (roughly) knows how
| to use it.
|
| You get 3 levels if you include Epic (Epic > Task >
| Subtask).
|
| You can set up a sprint/kanban board filter to cover
| multiple projects, so this does actualy gives you
| multiple projects per sprint.
|
| I do agree that it's slow and doesn't update itself to
| reflect changes.
|
| The two groups of people who hate Jira the most are (1)
| those who can't get it to work how they want it to and
| (2) those who have to deal with someone else's mad/broken
| custom workflow.
| andrewaylett wrote:
| If you're Enterprise enough, you can have a lot more
| levels than that!
|
| We appear to have four levels of grouping above "Epic",
| albeit none of them are even visible in our sprints.
| noam_compsci wrote:
| The H1s are so badly worded. They all feel like they are missing
| a word.
| evrflx wrote:
| Looks very promising I will give it a try.
|
| Related: I would love to see an open source confluence
| alternative as well, as for issues there are many (more or less
| capable) options to choose from.
| SifJar wrote:
| Haven't used it extensively, but there is XWiki:
| https://www.xwiki.org/xwiki/bin/view/Main/WebHome
| macintux wrote:
| What I most want from a Confluence alternative, and I have a
| few poor ideas _how_ this can be solved, is a way to manage
| stale content. The Confluence spaces I work with are dumping
| grounds of old, often misleading, information.
|
| Deduplication guidance, reports on untouched content...I don't
| know how to fix this, but someone surely can solve it.
| tacone wrote:
| Thank you for posting this.
|
| Looks pretty basic but somehow complete. The first impression is
| good. Here's some criticism:
|
| The first thing I look for in a issue tracker is the screen
| estate to write the task. I understand that some people write a
| list of issues in the form of short blurbs and iterate on them
| afterwards, but it always feels frustrating to me to having to
| write the title in a modal window, save and then open the issue
| again to be able to see a larger textarea for the description. I
| also see it as discouraging for people to write better
| descriptions for the issues they open.
|
| The keyboard navigation is probably not complete (press P to
| create a project, you would still need the mouse to focus the
| textbox and to save the project)
|
| On my computer it started in Dark Mode, and the experience
| overall was quite a bit disorientating. Also no light/mode switch
| icon in the header.
|
| It is not clear to the user that you can/should use markdown.
| flappyeagle wrote:
| Which issue trackers fulfill your requirements?
| lelanthran wrote:
| > On my computer it started in Dark Mode, and the experience
| overall was quite a bit disorientating. Also no light/mode
| switch icon in the header.
|
| I don't really know that you _need_ a light /dark mode switch.
| It should follow your preferences. I see dark mode websites all
| the time, because my desktop is set to dark mode. On my Windows
| machine I see the same websites with the light-mode, because I
| did not bother to figure out how to set Windows to dark-mode.
|
| [EDIT: The Plane App ignores my preferences].
| oefnak wrote:
| No, some applications work better in light mode, some in dark
| mode.
| AntonCTO wrote:
| And sometimes it depends on the environment outside of the
| computer.
| kristofferg wrote:
| [flagged]
| kristofferg wrote:
| Lots of dovnvotes. I am curious to know the reasoning
| behind these. :)
| jitl wrote:
| You made a rude low quality joke comment that did not
| contribute to the discussion. So, downvote.
| kristofferg wrote:
| Interesting - thanks for sharing your perspective. It
| certainly was not meant rude or as a joke.
| lolinder wrote:
| I come to HN for high-quality discussion. If I were
| looking for snark and meme content I'd be on Reddit.
|
| In this particular case, your parent made a very
| reasonable case that a web app could simply choose to
| respect the system light/dark mode and that would be
| enough. I happen to disagree with them, but they were
| sincerely contributing to the discussion.
|
| You came along with a 4-word + emoticon + hashtag parody
| of what they said that was inaccurate and frankly rude. I
| came away from your comment not at all sure what point
| you were trying to make but 100% sure that your comment
| wasn't contributing to an interesting discussion.
|
| Here's a possible rewrite, assuming your objection was
| that some computers don't support system theming:
|
| > If you only support system themes, you're excluding a
| large number of older systems that don't have their own
| light and dark modes. A toggle wouldn't take up much
| space in the header and would help those users to use the
| mode they prefer.
| kristofferg wrote:
| I see your point - I suppose it was quite snarky. My take
| is (and I suspect the same as the people who upvoted my
| comment) that the comment was disregarding another
| persons feature request/preferences based because the did
| not match his/her own. It is an, in my experience,
| attitude not uncommon - and it (unfortunately) gets my
| blood boiling every time.
| aaryan610 wrote:
| Hi, I am Aaryan, one of the maintainers at Plane. We
| currently have the theming settings available under the
| profile section, where you can set themes like light, dark,
| custom themes, and more. Thank you for your suggestion; we
| will certainly work on implementing the system preference
| setting and find a better placement for the theme switcher.
| CharlesW wrote:
| Hey Aaryan, I just signed up and am taking the tour, and
| the body copy (#737373 on #070707) is effectively
| unreadable while sitting outside with my MacBook Air at max
| brightness. (Hacker News remains easy to read in the same
| scenario.)
|
| For accessibility's sake, it'd be nice if the site met WCAG
| Level AAA contrast ratio requirements.
| aaryan610 wrote:
| Thanks for your feedback. Rest assured that we will
| carefully consider it and work towards enhancing our
| color schemes accordingly.
| capitanazo77 wrote:
| Please make it multilingual (Spanish). Some people here
| don't speak good english
| ericls wrote:
| One piece of feedback: The screenshot on the landing page is
| sooooo slow to load.
| iFire wrote:
| License AGPL3
|
| https://github.com/makeplane/plane/blob/develop/LICENSE.txt
| skwashd wrote:
| Until last month they used the Apache license.
| https://github.com/makeplane/plane/commit/a3f6d61347ef98171f...
| goodpoint wrote:
| Excellent!
| kissgyorgy wrote:
| As a user, that's the best for a software like this, because it
| means it cannot be ever closed source!
| dspillett wrote:
| _> cannot be ever closed source_
|
| Cannot be closed source _unless the maintainer_ dual licenses
| and stops making OS (assuming a single maintainer or group
| that all agree, or that other contributors have signed a
| relevant copyright waiver).
|
| (though what has already been released can't be retracted)
| stavros wrote:
| > (though what has already been released can't be
| retracted)
|
| This is the only relevant bit. A license can't force people
| to do work for free in the future.
| jillesvangurp wrote:
| It has that in common with essentially all other open source
| license. And it only extends to the version given to you
| under the license. The copyright holder(s) retain the right
| to change their mind. Which is a reason AGPL v3 is popular
| with companies that are looking to sell commercial licenses
| for their software. There are quite a few startups out there
| that attempted to keep control whose primary business model
| is providing a way out from the many restrictions the AGPL v3
| imposes on users by offering a commercial license.
|
| In this case, it looks like Plane is not requiring copyright
| transfers. So that cuts off the practicality of them ever re-
| licensing their software (commercially or otherwise). That's
| a good thing as it means it is indeed not likely the license
| will ever change. The bad thing is that it would be hard to
| build a company around this project. The AGPLv3 is just very
| strict about having to open source any and all bundled
| features and imposes a lot of restrictions and requirements.
| rapnie wrote:
| What if a project has a plugin architecture and plugins are
| compiled files that can be dropped in at runtime? Those
| plugins can be any license then, is it not?
| maxloh wrote:
| No. Those plugins call functions from AGPL's codebase and
| they are designed only to be combined with AGPL's work
| into a larger work, so they are derivative works.
|
| But there is a chance that CSS and svg icons are not
| required to be GPL.
|
| See WordPress clarification on themes' licensing:
| https://wordpress.org/news/2009/07/themes-are-gpl-too/
| voakbasda wrote:
| Plug-ins are generally considered a derived work, if
| directly written to use a specific API. You would need to
| build a module that works for many different systems and
| only uses the Plane APIs as a shim.
|
| Even then, the shim might be argued to be infected, and
| thus the rest of the module too. In that case, you still
| could be facing an expensive and risky lawsuit, because I
| don't think there are any precedents to predict how those
| winds will blow.
| empty_banana wrote:
| Looks good
| alexnewman wrote:
| GitHub projects are wild good now
| madeofpalk wrote:
| The team at GH really have been knocking it out of the park
| with Issues and Projects, especially the new Task Lists.
| hiatus wrote:
| But then your PMs and all stakeholders need to have github
| accounts.
| thrown1212 wrote:
| This is the entire point
| stockhorn wrote:
| Not to confuse with https://plane.dev a container orchestrator
| for ambitious browser-based applications.
| trollied wrote:
| Interesting, the UI looks the same as Twenty (
| https://twenty.com/ ), that was shared on HN this week.
| vegarab wrote:
| Aside from being open-source, what's the main differences from
| https://linear.app/ ?
| dvngnt_ wrote:
| linear ui has better performance imo
| colordrops wrote:
| "aside from being open-source"... That's a huge difference and
| the main difference that many care about.
| no_wizard wrote:
| It's AGPL licensed which is interesting. Much like Redmine this
| means modifications or customizations are a license violation
| unless shared correct? I wonder if these licenses are hurting the
| adoption of OSS alternatives for enterprise software
| slifin wrote:
| Does this one allow you to assign more than one person to a
| ticket?
| quickthrower2 wrote:
| That is a bugbear for me in Jira. Who solos on all tasks?
|
| Subtasks kinda helps in Jira
| asyx wrote:
| We just use custom fields. So we have a backend, frontend and
| QA field. Assigned is always the one who needs to do
| something.
| berkes wrote:
| This bothers me on almost all project management software.
|
| What I'd love to see, is to be able to assign _one_ person as
| the one "responsible" and then assign others ad-hoc when/if
| they work on-, review-, discuss, or co-author it.
|
| Some software allows multiple assignees, but as the ancient
| management-saying goes: if everyone is responsible, no-one is.
| So i'd still love to have one person assigned with a special
| role or label.
| Mister_Snuggles wrote:
| At my work we have a couple of different roles that get
| involved in each ticket, so we created custom fields in Jira
| to assign those roles.
|
| So each ticket gets a Primary Developer, Primary SME, etc,
| but might get assigned to some one else to do one small bit
| of work (e.g., it'll get assigned to a different developer
| for code review, but whoever's listed as the Primary
| Developer is still responsible for it).
| IshKebab wrote:
| Yeah this is an issue with my current company's use of Jira.
| They're super worried about tickets being "lost" so they all
| have to be assigned to one person, but then that means you
| can't tell who is actually working on something.
|
| My previous company used Phabricator and you only assigned
| yourself a task when you actually started working on it. It
| meant anyone could work on anything - much more agile and
| much much better knowledge spreading and teamwork.
|
| But I understand where my current company is coming from. You
| want a "person who is responsible for making sure this
| eventually gets done" field _and_ a "person who is currently
| working on this" field.
| ptman wrote:
| Shared responsibility is no responsibility.
| noen wrote:
| Shared _accountability_ is no accountability.
|
| Shared responsibility is called collaboration.
| noirbot wrote:
| Sure, but you can have plenty of options where there's one
| responsible person, but you may still want to track another
| person who's involved. Maybe another engineer who's paired on
| the project, or the PM who's taking point on it, or the QA
| who's testing it, or the other engineer who's reviewing it.
|
| Having to rely on comments or assignment history to uncover
| that information is a bad experience.
| macintux wrote:
| Wouldn't child tickets address that problem?
| noirbot wrote:
| Perhaps? But I do plenty of projects where I'm just
| paired with another engineer. I'm maybe taking lead, but
| they're sitting in on all the meetings and helping make
| decisions when I want someone to check my work. That may
| be worth noting in a ticket in case I'm busy or out of
| office and someone needs an answer around the project,
| even if they don't have a specific task they're
| responsible for that they'd be assigned a child ticket
| for.
|
| It's also a level of precision question. At some point,
| having a lot of child tickets is just extra work if it's
| mostly just documenting something that could have been as
| easily documented by attaching another person's name to
| the parent ticket.
| macintux wrote:
| Perhaps the watchers attached to the ticket could be
| used.
| ptman wrote:
| Sure. Maybe there needs to be an owner/assignees
| distinction?
| MatekCopatek wrote:
| Is it me or does that look extremely similar to Linear, another
| competitor in that space?
|
| Not in the sense of the feature set, there's only so many things
| you can do with an issue tracker and a kanban board, but in the
| sense of actual visual design (fonts, text sizes, etc.)
| hotpotamus wrote:
| I don't know a thing about either, but the names plane and
| linear would seem to indicate that one is at least the
| spiritual successor to the other.
| delphi4711 wrote:
| Why .so? I understand payara.fish, because payara is based on
| glassfish.
|
| What is the story here? I'm just curious (and bored) :).
| quickthrower2 wrote:
| not a bad find of an extension for a common english word. More
| common than notion!
| senkora wrote:
| If wonder if it has something to do with shared libraries
| jitl wrote:
| I think Notion (my employer) https://notion.so/product made it
| popular. However .so gave us a lot of trouble over the years,
| so I wouldn't recommend.
| thejammahimself wrote:
| Out of interest: what sort of troubles has it given? (if
| you're able to say)
| jitl wrote:
| - Corporate firewalls don't like people visiting .so
| Somalia URLs. Wouldn't have this problem with .com. We had
| to fight hard for domain reputation.
|
| - Back in the day communication between us, our registrar,
| a middleman registrar in Germany, and SomaliNIC wasn't too
| good. We weren't notified of a takedown report and got DNS
| blocked by a bunch of ISPs offline for 8 hours. Even
| figuring out what happened on that one was baffling.
| RockRobotRock wrote:
| My domain uses an Afghanistan (.af) domain. They actually
| froze new registrations after the Kabul takeover.
| KnobbleMcKnees wrote:
| Short for software
| rapnie wrote:
| I find the name 'plane' itself curious. As an upcoming product
| you make yourself quite hard to find in search engines (though
| "plane issue tracker" gives plane.so as first result in DDG).
| notfried wrote:
| = "source open"? :-)
| stavros wrote:
| I'm guessing it's a combination of 1) it was available, and 2)
| why not?
| gadflyinyoureye wrote:
| Maybe because so is the 5th of a scale, and this has 5/8ths of
| the features of Jira?
| riffraff wrote:
| For potentially confused people out there: some
| countries/musical traditions use a do-re-mi-fa-so-la-ti(si)
| scale, rather than do-re-mi-fa-sol-la-si or a-b-c-d-e-f-g.
|
| This has the interesting side effect that the word solfege
| (sol-fa) makes little sense.
|
| https://en.m.wikipedia.org/wiki/Solf%C3%A8ge#Note_names
| foxbee wrote:
| Interesting tool. Happy to see it's Open Source. It would be nice
| to see better roadmap visualization.
| bbkane wrote:
| Does Plane offer an alternative for JQL (Jira Query Language)?
| That's what I appreciate most about Jira
| thrown1212 wrote:
| They meant "linear.app", not Jira, and "copy" instead of
| alternative.
|
| There's currency in this type of knock off. Find a well executed
| closed source app, clone as open source, pick an alternative
| pitch "the Jira killer", then raise YC because open core is the
| fashionable argument.
| Mountain_Skies wrote:
| Anyone tested it for speed? That it can be self hosted should on
| its own gain it some extra acceptance.
| tacone wrote:
| It's built on top of Next.js, it feels pretty fast compared to
| other solutions.
| phosfox wrote:
| Tabnavigation is completely broken on the landing page.
| gadflyinyoureye wrote:
| I couldn't easily fine an answer. Would self-host run on PI and
| still be useful?
___________________________________________________________________
(page generated 2023-07-22 23:01 UTC)