U++ forum: Welcome to the forum

Re: Great (and funny) Linus' speach about GIT [message #13491 is a reply to message #13175]

Thu, 10 January 2008 21:04

mr_ped
Messages: 826
Registered: November 2005
Location: Czech Republic - Praha

Experienced Contributor

- what's wrong with whole svn writing rights, if the agreement will be to not commit any big change to official branch?
If anyone does commit something there, it can be rolled back, eventually he can lose svn access.
Should we be so hard even on obvious fixes of obvious defects? I would not like such policy. But if they will be allowed, who will be responsible for review of commit and accepting it as official fix? Also if Mirek will continue to work with uvs as main branch, who will merge those two "official" branches?
Also if Mirek will start to work directly on official svn branch, it may become easily unstable for couple of days ...

- stable upp core because of Mirek doing biz apps with it: that's obvious reason.

- good taste+forum politics = I was mostly pointing out the process is unofficial. Thus in similar situation it may easily lead to different results and it would be more encouraging if there would be official how-to for contributors (even if it would just describe this method).

- I think uvs2 is bad idea, because it is non-standard, and works only on limited bandwidth for limited number of people. So I think the migration to different development model would be a step forward.
But it's up to Mirek to decide which direction that forward should take. SVN? GIT? Mercurial? Bazaar (versioning system)?
Plenty of choices, each does promise a bit different future, and require quite different policies and rules.

Forking upp core doesn't look very promising to me. I can hardly imagine anyone else pushing so hard forward and so effectively as Mirek is. That means any fork would become quite obsolete within weeks, and exactly because of this evergoing big changes/refactoring to core it's difficult to maintain custom core changes if they are not merged back to official branch.

(and also core is quite complete for what it does, there's still plenty of room for improvements, but so far I didn't see people here moaning about wrong changes to core from Mirek. About missing features and fixing bugs.. those are common in forums... but the new version of core were so far very positively accepted and it looks Mirek's needs follow very good needs of others)

Forking TheIDE makes much more sense IMHO, as people may have quite different taste for what is important for IDE, and also experimenting a lot on such piece of SW makes more sense, than some crazy experiment changes to core itself.
But actually I think it's not worth of it. If there will be enough courage to do this, I would rather suggest to start TheIDE2 from scratch, as the original IDE is based on (IMHO obsolete) old concepts anyway and just "hacking it" would never move it that much away from current thing.

--- I see I'm writing lot of stuff, and quite offtopic.

So short summary what I don't like about current svn<->uvs and contributing.
I don't like the idea that if I find some obvious bug in upp (and I already did at least once IIRC), I can't simply fix and commit it. I have to write it in forum ... wait for Mirek to notice ... wait for next official release ... hope Mirek did not forgot to merge with my fix ... etc.
The current status is pretty much "Mirek is developing his UPP, and as he is very good person, he allows anyone else to download it and use it for free" (what is absolutely amazing of course).
As such the number of direct contributors to upp core will never grow too much.

I'm not saying we need to change this badly. I'm just summarizing how I see it is, and where it will lead in future. Smile

If it stays as it is, I'm not going to fork upp core just to allow me to fix little things immediately, I will rather post in forums and wait.

Report message to a moderator