Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] Tweaks to Paho projects on Github

The "signing" of the agreement you are referring to is actually what one is doing by providing the statement mentioned in step 4 of [1].

The easiest way to go for people that want to benefit from Github facilities is to fork the Eclipse mirror of the project on Github, work on whatever fixes/patches they want and then create Eclipse bugzillas when they want their modifications to be pulled back into the Eclipse repo.
If a commit is >250 lines, there will be the necessity of a CQ in addition of simply the bug w/ attached git-patch.


Benjamin Cab ::  Open Source Manager


SIERRA WIRELESS :: AirVantage Business Unit

Main  +33 5 61 00 52 90  ::  Direct  +33 5 61 00 06 41  ::  Fax  +33 5 61 00 51 46

Lake Park  ::  Zac de l'Hers - Alle du Lac - BP 87216 :: 31672 Labge Cedex, France


BCabe@xxxxxxxxxxxxxxxxxx ::


De : Nicolas DEVERGE <ndeverge@xxxxxxxx>
Rpondre  : General development discussions for paho project <paho-dev@xxxxxxxxxxx>
 : General development discussions for paho project <paho-dev@xxxxxxxxxxx>
Objet : Re: [paho-dev] Tweaks to Paho projects on Github


for the IP rules, I once saw a kind of signing an agreement with your GitHub account (see for an example).

I don't know if this is relevant in the scope of the Eclipse IP process ?

My two cents...

On Wed, May 30, 2012 at 1:35 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
They are just regular Git repositories. You can pull things into your GitHub mirror.

Keep in mind that the IP rules still apply. Well mostly.

The GitHub repositories--since they're not "eclipse" repositories--are not themselves subject to the rules. But anything that you bring into the repository is subject to the full IP Due Diligence process.

Note that GitHub provides us with no legal protections. Users are not required to agree to any terms or grant any rights.


On 05/30/2012 05:04 AM, andypiperuk@xxxxxxxxx wrote:
I'm new to Eclipse Git development myself, so I'm not certain.

I think these are essentially just read-only mirrors, and per and we'd need an organisation / team set up in order to use Github as a master for dev. I guess Chris or Wayne could clarify.

To be fair, the way the mirroring is set up via a period manual script, there's a chance that the commit hooks I've configured on the Github repos will not in fact work - but it's worth a shot and could be pretty cool :-)

On Wed, May 30, 2012 at 7:48 AM, Nicolas DEVERGE <ndeverge@xxxxxxxx> wrote:
That's great news !

Does it mean that we can fork and submit pull requests on GitHub and that it will reach the Eclipse Git repo ?

Also, that could be handy if someone could add a tag on the current head in order to fix a version (1.0 or something else), no ?

On Tue, May 29, 2012 at 5:45 PM, andypiperuk@xxxxxxxxx <andypiperuk@xxxxxxxxx> wrote:
The Eclipse Git repositories are mirrored on Github, and therefore the Paho C and Java clients exist on Github as well as at Eclipse.

I made a couple of minor changes to the Github repos, and an additional pretty cool one (well, I think so!)

- I changed them both to have a web link to
- I turned off Issues and Wikis on Github for both repos, and added a note in the description that issues should be reported via Eclipse Bugzilla
- I created a service hook for both repos. In the future, when changes are made to the repositories, a message will be published to the broker on the appropriate topic (github/paho/java or github/paho/c) containing the JSON object from the Github commit hook :-)

Andy Piper | Farnborough, Hampshire (UK)
blog:   |   skype: andypiperuk
twitter: @andypiper  |  images:

paho-dev mailing list

paho-dev mailing list

Andy Piper | Farnborough, Hampshire (UK)
blog:   |   skype: andypiperuk
twitter: @andypiper  |  images:
_______________________________________________ paho-dev mailing list paho-dev@xxxxxxxxxxx

Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects

paho-dev mailing list

Back to the top