Hi,
There is quite bit of plugins that are not under Jenkins-ci org under github.
See the repository description [1] in section after $repoMap of $id = repo .
Each line that has slash means different github organization.
Jan
[1]
On Wed, Apr 2, 2014 at 2:15 PM, Jan Ruzicka
jan.ruzi...@comtechmobile.com wrote:
See the repository description [1] in section after $repoMap of $id = repo
.
Each line that has slash means different github organization.
A lot of those are in fact forked into jenkinsci. I suspect the map is
On 03/26/2014 03:06 AM, Nigel Magnay wrote:
+1.
I don't like the idea of having some plugins referenced under the
official update center that don't actually come from the jenkinsci
github organization.
The deal seems quite simple to me: either accept to host your plugin
On 03/25/2014 06:12 PM, Surya Gaddipati wrote:
You say it is for obvious reasons you'd want them listed under different
org, but I'd like to ask you why that is.
One of incentives for my employer is 'brand building' in terms of open
source presence which could help us attract more qualified
On Tuesday, 1 April 2014, Kohsuke Kawaguchi kkawagu...@cloudbees.com
wrote:
On 03/26/2014 03:06 AM, Nigel Magnay wrote:
+1.
I don't like the idea of having some plugins referenced under the
official update center that don't actually come from the jenkinsci
github
On Wednesday, March 26, 2014 2:12:36 AM UTC+1, Surya Gaddipati wrote:
You say it is for obvious reasons you'd want them listed under different
org, but I'd like to ask you why that is.
One of incentives for my employer is 'brand building' in terms of open
source presence which could help
Open source is also about making things together, not just making things
public.
Not necessarily.
There are plenty of projects that are open source, that are not interested
in contributions. Google Guava, for one.
Putting things in jenkinsci group probably *should* mean 'open to
+1.
I don't like the idea of having some plugins referenced under the official
update center that don't actually come from the jenkinsci github
organization.
The deal seems quite simple to me: either accept to host your plugin under
the jenkins github org, or accept it doesn't appear in the
I agree with Kohsuke. What would happen if the the original writer of a
non-hosted plugin stops supporting it? Somebody would probably end up
forking it (if it's on Github) and might even host it in the jenkins
organisation. It's kind of unclear what would happen in such scenario.
A pragmatic
+1.
I don't like the idea of having some plugins referenced under the official
update center that don't actually come from the jenkinsci github
organization.
The deal seems quite simple to me: either accept to host your plugin under
the jenkins github org, or accept it doesn't appear in the
My employer is interested in opensourcing a plugin that we developed in
house. But we would like our plugin to be under github org not jenkins-ci (
for obvious reasons) .
Is it possible to make plugin show up in the default jenkins update center?
--
You received this message because you are
24, 2014 3:04 PM
Subject: Opensourcing a plugin under a different github org
My employer is interested in opensourcing a plugin that we developed in house.
But we would like our plugin to be under github org not jenkins-ci ( for
obvious reasons) .
Is it possible to make plugin show up
yes, no problem, even it's easier for contributors to find its source code
when present in jenkinsci org.
2014-03-24 19:04 GMT+01:00 Surya Gaddipati suryapraka...@gmail.com:
My employer is interested in opensourcing a plugin that we developed in
house. But we would like our plugin to be under
We might not be enforcing it today, but it's at least my intention that
we want all the plugins in the community update center be hosted on our
GitHub org. To me, it's an important part of creating an incentive for
people to come to the community.
There's also the continuity problem --- if
+1 to trying to keep them in the same place.
On Tue, Mar 25, 2014 at 12:36 PM, Kohsuke Kawaguchi k...@kohsuke.org wrote:
We might not be enforcing it today, but it's at least my intention that we
want all the plugins in the community update center be hosted on our GitHub
org. To me, it's an
15 matches
Mail list logo
