-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch from using fossil to git as the primary version control tool? #39
Comments
I strongly support, not surprisingly. I'm OK with fossil, but the current workflow can be improved with the use of git due to its ubiquity and, more importantly, integration with GitHub. For many, open source development is all about git/GitHub; most latest prominent OSS projects I can recall are centered around this platform. It's simply what people expect to work with; making our workflow more streamlined and transparent will undoubtedly make the project more attractive and easier to participate in. |
I expected you would like this proposal:). I think it is safe to assume we can expect the same from @dumblob. |
Yes, I support this idea with all my fingers! Still, I'm a little bit concerned about China users as I thought, that those people might have difficulties from time to time with the access to GitHub. Do you @daokoder plan to make these "China syncs" yourself and thus maintain the daovm.net site in a way, that even China users can contribute? |
This might be a problem, github had been blocked a few times and had been slow many times in China. But recently github seems to work quite well, some people said the previous blockages had rose too many protests in the software industry, so they (people in charge of GFW) switch to a more subtle approach by blocking specific projects. For the moment, github as a whole seems safe. On the other hand, many active github users in China are able to break through GFW, though it could get a bit annoying to have to use some techniques. So I think, for Chinese users who are capable of contributing to Dao, it may be just a minor problem, and an inconvenience problem at most. |
Great news, go on then with the switch. Can we use pull requests from now on? And issues tagging? A good example of a comprehensive yet easy GitHub usage (together with some other web services) can be demonstrated on Neovim. |
Given the current state of the Issues page on Dao core, it may be an apt time to start using labels... |
When we finally switch? Fossil doesn't cease to disappoint me: sometimes it doesn't update to the latest revision, sometimes reverting doesn't work. I don't care if it's lightweight or fast or anything, I want a tool which works. |
I also experienced issues with fossil, but just at rare times. Anyway, let's do the switch now:) . |
BTW, I could also make pull requests to the Dao core... Possibly fixing bugs gathering dust for months... |
As you may know, we have been using fossil as the primary version control tool, and git as the secondary one. Fossil is very convenient to use, and conversion/sync from fossil to git can be done seamlessly, but sync from git to fossil is not so much smooth. This was the main reason we have been keep using fossil as the primary tool.
But sync from fossil to git can be seamless, only if the sync is done by a single user (currently me). This may have been very inconvenient for contributors (especially @Night-walker) to work on the modules. I feel we really need to move to use git directly, as I realize the current way is not working well when I am not around to make the sync in time.
I also expect more people will be interested in contributing to Dao by helping with modules, as it would be a lot easy to start with modules than with the VM. It is hard to convincing every contributors to use fossil, sooner or later we may have to make such switch if we want the community to grow.
The text was updated successfully, but these errors were encountered: