It sounds very annoying.moa wrote:Everytime you add new code it gets more and more difficult to rebase ... (I've said all this before). If you are wanting to create a new fork that is going to go off and doing its own thing then keep going in this direction, but you should be honest with yourselves that this is what you are doing ... by default.
All the other stuff about making better docs, install guides, tools and marketing is all good. Be careful your castle is not being built on sand ...
But is it really so ?
Namecoin is not a building but much more like a village built on a rock or whatever it is.(like the main developer also compared Bitcoin with this)
And the common fundament is not the client but the network. The client is just the main building and we already have some forks of it which is not necessary bad. (by Bitcoin is also not differently) The network itself is not forked and nobody intends to do it.
It is correct that rebasing getting more and more difficult but not because of the additional tools or wikis and manuals. (this would even help)
But because the Bitcoin client is more and more complex.
But it is easier to rebase the client on every Bitcoin client version step by step or it is easier to do it at once ?
We shouldn't do anything that change the network until the rebase is done because that would make it also more difficult. I agree.
But can everybody work on the rebase ? I don't think so.
So what should do the others ? Stay quietly or something which helps Namecoin but doesn't change the network and therefore don't make the rebase more difficult.
Wikis, manuals, tutorials, browser addons, marketing, collecting donations, identity based implementations (like Bitmessage or website login with id) would change the network ? I don't think so. And if cannot work all on the main building(rebased client) some can work on the others. Or not ?