Changes to our Git infrastructure
boud at valdyas.org
Mon Jan 5 21:22:19 GMT 2015
On Mon, 5 Jan 2015, Albert Astals Cid wrote:
> I think this is due to the fact that it's quite simple
> git clone kde:repo
* setting up gitconfig with the kde: alias. That requires finding the
right info on techbase, as well as the awareness that techbase exists.
* figuring out the reponame for a particular project (and that isn't as
easy as just downloading the entire trunk of kde's svn repo -- even if I
never did that myself)
> do coding
> git commit
* using the commit template
* with the relevant keywords
* having a grasp of what a git commit is, especially that a commit isn't
visbile to anyone else
> git push
But not before you have
* realized that you need to push, i.e. what local and remote is
* figured out what branches are for, and how different projects handle
* got your kde indenity
* posted it on the right reviewboard
* to the right reviewers
Of course it's doable, but even with cats just getting source and building
it poses hurdles that need articles like
help people jump them.
I am a very fortunate and happy person: there is hardly a week when I
don't have to guide someone through the process. Usually, half-way through
they ask me, why doesn't KDE use github (or, less often) phabricator. Then
I point them at the manifesto, and we usually spend another half hour
discussing that -- most often with good results! Our story about not using
github is not hard, but our contribution process often is.
> Obviously i think it is simple but you think it's not, i can't write a guide
> for dummies because i think it's simple and you can't write it because you
> don't know how to write it, it'd need to people to collaborate on it.
> If you can write somewhere your questions I'm sure we can find people to write
> the answers :)
>> Having said that, the mail flood I get from Qt gerrit also isn't fun. After
>> every comment a new review is requested... I don't have that time.
>> Having a system where every repository (project) automatically has its own
>> wiki and bug tracker is something I would really like to have. I think this
>> is especially useful with the frameworks effort. I'd really like to see a
>> "homepage" for each of the frameworks, and such a wiki page would be a
>> natural place to put it.
More information about the kde-core-devel