SVN --> Github?
-
Switching to Github will greatly increase the productivity of KOS's development. This would allow easy editing for people on any computer. The SVN server should still be up for people to be able to look at past revisions. My computer recently broke. So, I have to borrow one until I get a new one (It's cheaper to get a new one). I want to work on KOS, but I am hindered by my current situation. My friend is not a programmer so does not have an SVN client. So, a switch to Github would be preferable to people in the same position as me. Please tell me your opinion.Last edited by crank123 on Sun Nov 23, 2014 1:21 am, edited 1 time in total.
I am fully aware of WebSVN. However, WebSVN can be confusing, unappealing, and lacking of functionality.
1. We are not going to switch to GitHub:3. I didn't see any single line of KolibriOS code from you (before your own computer broke).
- GitHub can shutdown our repository without any notification whenever they want in case someone reports it. Our repository doesn't contain any prohibited material, but this doesn't prevent people from reporting it
- We use our own auto-build script that triggers after every commit, which requires the sources to be present locally.
Code: Select all
git svn clone svn://kolibrios.org -r5000 && git svn rebase kolibrios.org
1.
a. True
b. True
2. True
3. I WANT to, but I can't. Just because I haven't posted any code yet doesn't mean I won't ever do it.
Why can't you add into the script a line that also pushes it to a Github repo?
a. True
b. True
2. True
3. I WANT to, but I can't. Just because I haven't posted any code yet doesn't mean I won't ever do it.
Why can't you add into the script a line that also pushes it to a Github repo?
It has no sense, because it would be one-way flow and would break at the first pull request. If you really want the one-way flow, you can just create your own git repository as mentioned above and clone it to GitHub, you could even commit to the project from the original repository, although not from GitHub. If you insist on the official Github repository, you basically require to switch development model from all active developers, without even showing one line of your code.crank123 wrote:Why can't you add into the script a line that also pushes it to a Github repo?
Сделаем мир лучше!
Mmmmm....Okay...So, I get that the general consensus is no. That means I can create a Github repo for myself to work on. However, merging it back in would be a little tricky. So, I'll just have to wait.
Wait for what?
"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." Albert Einstein
Who is online
Users browsing this forum: Google [Bot] and 2 guests