Hi all, Well, yes, as Michaël explained we're going to be two maintainers for this plugin. (As we actually worked separately on our plugin version (without knowing the other had begun), so we ended up merging them before submitting.).
By the way, I've had a look at the plugin contributors wiki pages, but didn't find the information about plugin hosting under jenkinsci github organization: 1. Are we to work on our repo, and sometimes someone having commit rights onto the jenkinsci forked is going to git pull --rebase upstream? 2. Or are we to work directly on the jenkinsci forked version? 3. What else? Please note we are totally open to work the way you prefer. IMO, it'd be simpler and less work for everyone to just get commit rights on the forked version, and then even wipe out the upstream one (so that people don't potentially get confused). But if it's not the way it currently works, no problem. Just let us know. Cheers. 2012/9/18 Michaël Pailloncy <[email protected]> > Thank you Nicolas. > > Can you give me write rights to this repo ? (id : mpapo) > I can't push on it. > > Baptiste Mathus (id : Batmat) has also developed on this plugin. Can you > give him write rights too ? > > Thanks in advance, > Michaël > > > 2012/9/17 nicolas de loof <[email protected]> > >> project forked : https://github.com/jenkinsci/buildtriggerbadge-plugin >> >> >> 2012/9/15 mpapo - Michaël Pailloncy <[email protected]> >> >>> Hi, >>> >>> Here is a small plugin showing an icon representing the trigger cause of >>> a build (timer, scm changes or user action) directly in the build history : >>> https://github.com/mpapo/buildtriggerbadge-plugin.git >>> >>> Can you please fork it ? >>> >>> Thanks in advance, >>> Michaël >>> >>> -- >>> Baptiste <Batmat> MATHUS - http://batmat.net >>> Sauvez un arbre, >>> Mangez un castor ! >>> nbsp;! >>> >>
