Money doesn't vote, people vote. Democracy is about people and not amount of money. Example, because one billionaire donates $5millions and 5000 Americans put each $200. Doesn't mean that Canadians care more because $5millions is more than $1million.
I'm impressed and I see potential on this one. I tried different ones over time but most fail at on-boarding. This was seamless and really easy. In about 2 minutes I successfully shared my project and followed known projects. This means this mvp works and it let me craving for more, I want to use this! I want issues and PR support to prove this can effectively work as a github replacement to me.
Now, the downside of this mvp is that there is no project discovery in the client itself. We need to go search for projects in a browser, in this page http://seedling.radicle.xyz/ which is a bit confusing. Considering the client itself is electron, it could at least, open this page for us somewhere. Or, we could at least have a less "noisy" seedling page focused on search and I would not even know it wasn't part of the client itself.
Overall, awesome project. I really hope it will grow and add the missing essential features. If I could vote, with priority these would be:
- project discovery integrated in the client
- issues support
- pr support
- multiple identities
Thanks for the feedback! The priorities you mention are very close to our own, and we have already started working on some of them. We will definitely be integrating discovery more closely into the app in the long run.
Recently I started a personal project to enable storing issues in the git repository itself. Then I discovered git-bug which, though lacking a good UI, has the data formats nailed almost perfectly in my opinion.
I highly recommend considering using git-bug natively for Radicle's issue tracking system. It seems perfect for the task.
I was very interested but unfortunately my experience was quite opposite. I launched the app image on Pop_OS but couldn't sign up no matter which user name i chose (even resorted to random strings) - finally just gave up.
At first I thought it was broken as I opened in mobile and it was very confusing. Otherwise, on desktop it looks funky, but fine - not awesome but not bad.
> I dont know why youre getting downvoted, the latin-rich terminology in medicine is pompous and unnecessary.
C'mon! This may seems true for english speakers and non-romance languages. But I as a non-english native speaker, can say exactly the same about CS terminology! It is just too pompous and unnecessary, as it will in almost any other non-germanic/anglic language.
These company make changes to Atlassian code? You're conflating internal or public use with derivative work or service offering. You clearly misunderstand licensing.
If they are the sole copyright owners (no external contribution) or have SLAs, they can for any future version of the software. It is not uncommon, it is just hard as most doesn't have SLA to do this.
I know who you're replying to. The premise that gary-kim laid out is still the relevant context. The hypothetical you're laying out, on the other hand, is not relevant, it's at odds with that premise (not in "agree[ment] with him"), and it's derailing the thread. (Which is the same reason your "future versions, not past versions" is downvoted, for that matter.)
Right. _they_ were not meant to be Wiki.js, but ANY open source project. And was a meant to indicate the same subject as _any_ in this reply:
> I don't think _any_ of the mainstream open-source licenses allow you to retroactively revoke or change the license.
My reply is in this context, not in the parent's parent which you mean as _relevant_ context. If I wanted to include the parent context the reply would be more specific. This was a direct reply to a specific message. This is a very normal way to reply on the internet, HN is not special.
Try rewriting history if you want, but the thread goes off-topic as soon as mekster suggests the project change the license, and your reply there only feeds into it. And it still doesn't explain how you can claim that your comment was meant to "agree" with gary-kim's.
> My reply is in this context, not in the parent's parent
The parent's parent at that point is... your comment, "For future versions, not past versions," which was off-topic.
> This is a very normal way to reply on the internet
Indeed, it's common for people to lose the plot in the comments section and then get defensive (and smug) while being wrong, e.g.:
Google plans to add ANGLE support for Metal backend. Once that backend is done (and even the Fuchsia support), ANGLE will continue to be an extremely viable option.
The delay of having a Metal backend may have been the reason they're deciding to ditch it, but is nonetheless sad.
Another future option will be WebGPU, once this is mainstream what Digia will do with Qt7? Drop everything again?
Since Digia put their hands on Qt, it is slowly going downhill.
