Page 4 of 4

Re: [RFC] Aging Platforms

Posted: Sat Nov 10, 2012 9:24 pm
by Giovanni
Hi,

I already created a GIT repository in the chibios project on SF, you should have access to it, there was no need to create another project but we could use this too (I would remove the one on chibios).

My idea is to create a repository for contributions and have contributors handling it directly, my question is: is it possible to create a mirror of ChibiOS with other files on top? or we have to keep contributions separated from ChibiOS and have to merge the files locally?

I am writing a proposal for a new organization of the open source side of ChibiOS in order to allow contributions more easily, in this moment I am a bottleneck in the process :(

Giovanni

Re: [RFC] Aging Platforms

Posted: Sat Nov 10, 2012 9:49 pm
by barthess
Commonly the contributed code is drivers for some devices like EEPROM, accelerometer, LCD, etc. There is already present catalog (os/various) in source tree. External code can be added as git submodules (even if code hosted on different server) to that location and updated automatically. We just need to create convention about correct placement for different types of modules. Did I answer you question?

Re: [RFC] Aging Platforms

Posted: Sat Nov 10, 2012 11:47 pm
by Giovanni
Not just that, contributed code are also ports, support for platforms and demos.

The general idea is to put everything on this git repository and let the community handle it. When something is ready then it would be migrated into the distribution.

The repository must not contain files conflicting with the main repository, the only problem can be the .mk files, those will have a _ext suffix in the name in the git repository, for example platform_ext.mk.

Giovanni

Re: [RFC] Aging Platforms

Posted: Sun Nov 11, 2012 8:24 am
by barthess
Giovanni wrote:When something is ready then it would be migrated into the distribution.

Code: Select all

    The project maintainer pushes to their public repository.
    A contributor clones that repository and makes changes.
    The contributor pushes to their own public copy.
    The contributor sends the maintainer an e-mail asking them to pull changes.
    The maintainer adds the contributor’s repo as a remote and merges locally.
    The maintainer pushes merged changes to the main repository.

http://git-scm.com/book/en/Distributed- ... -Workflows
Is it?

Re: [RFC] Aging Platforms

Posted: Sun Nov 11, 2012 10:28 am
by Giovanni
Prof. Dr. YoMan wrote:Giovanni, you are on windows?

This is a nobrainer. :)
https://code.google.com/p/gitextensions/

Matureing well.


Thanks, this helped a lot.

Giovanni

Re: [RFC] Aging Platforms

Posted: Sun Nov 11, 2012 11:02 am
by mabl
Hmm since most new contributed ports are developed on github, could we not extend the chibios presence on github? As mentioned I already have allocated the chibios name as a team name there. Also we could move my git mirror to it. I'd be willing to help out as well.

Re: [RFC] Aging Platforms

Posted: Sun Nov 11, 2012 11:09 am
by Giovanni
Hi Mabl,

I already created a git repository on SF and loaded the first contributions there but if you (all of you) think that github would be a better place for it then I have no objections to move it there.

Mabl, are you also interested in co-organizing the contributions area? more applications welcome of course, more ideas also welcome, I really want this idea to work.

Giovanni

Re: [RFC] Aging Platforms

Posted: Sun Nov 11, 2012 3:45 pm
by mabl
Sure, I've talked to the guys on irc already. Tectu and barthess are now member of the github ChibiOS group. I'd very much like to help out - if somebody thinks it should be done differently - shout - I'm by no means a git and organization master :mrgreen: