Replies: 2 comments
-
Yes, that's the gist of it
Yes, I suggest Radicle only as an optional addon git exchange, not dropping Github nor demoting Github nor syncronizing issues. Obviously, if in some bright future Radicle becomes wildly popular, that position may change ;-) |
Beta Was this translation helpful? Give feedback.
-
I think that "require" is misleading: If only some developers have an interest in trying out Radicle, then they can occationally do That leaves two questions, as I see it:
Sounds like you, @labra, wants to play with Radicle which is adequate to answer 1). Do anyone at all see a problem in others toying with Radicle - e.g. a security risk? |
Beta Was this translation helpful? Give feedback.
-
@jonassmedegaard suggested in this issue the use of radicle to integrate contributions from people who don't want to use github.
In principle, it seems very nice, although it also seems quite new. I am not sure if we should directly abandon github to embark on radicle or if we should try to use both at the same time, which I think is what Jones is suggesting.
As Jonas says in the issue, using both at the same time would require to use:
instead of a simple
git push
, andwhen we want to integrate changes from
rad
.According to this discussion, it seems that it is not possible to synchronize the issues in radicle with the issues in github, so I think, radicle would be used just as another git remote.
Beta Was this translation helpful? Give feedback.
All reactions