FYI: On naming SCM implementation and extension plugins

[Stephen Connolly]

I have published my recommendations on naming SCM API implementation and extension plugins:

https://github.com/jenkinsci/scm-api-plugin/blob/master/docs/implementation.adoc#naming-your-plugin

Also my guidance on where functionality should land:

https://github.com/jenkinsci/scm-api-plugin/blob/master/CONTRIBUTING.md#add-to-core-or-create-extension-plugin

[Carles Capdevila Tejada]

Hi Stephen,

I have a (not yet hosted) plugin which does the same as Github Organization, but for Gitblit. Right now it's called gitblit-branch-source, following the naming of the respective Github and BitBucket plugins.

I'm thinking on requesting it to be hosted in the Jenkins community repositories; should I change it before into gitblit-scm? I hope it doesn't prevent users from finding it as its naming deviates from such big plugins as Github and BitBucket :'D

Thank you for your attention.

[Jesse Glick]

On Tue, Apr 17, 2018 at 11:10 AM, Carles Capdevila Tejada
<capde...@gmail.com> wrote:
> should I change it before into gitblit-scm?

According to the doc, since

https://plugins.jenkins.io/gitblit

does not exist, you should use that.

> I hope it doesn't
> prevent users from finding it as its naming deviates

Users will not typically find plugins by `shortName`; rather by
display name and tags.

[Stephen Connolly]

On Tue 17 Apr 2018 at 17:18, Jesse Glick <jgl...@cloudbees.com> wrote:

On Tue, Apr 17, 2018 at 11:10 AM, Carles Capdevila Tejada
<capde...@gmail.com> wrote:
> should I change it before into gitblit-scm?

According to the doc, since

https://plugins.jenkins.io/gitblit

does not exist, you should use that.

The doc Jesse is referring to is: 

https://github.com/jenkinsci/scm-api-plugin/blob/master/docs/implementation.adoc#naming-your-plugin

On the basis that there is no gitblit plugin currently, use gitblit

> I hope it doesn't
> prevent users from finding it as its naming deviates

Users will not typically find plugins by `shortName`; rather by
display name and tags.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0PQm_Gx9kahT_CSxf5BrAKkg36-JhE7%2BiayAgQ5J4S-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Sent from my phone

[Carles Capdevila Tejada]

gitblit will be the name then, thanks Jesse and Stephen!! :)

2018-04-21 14:59 GMT+02:00 Stephen Connolly <stephen.al...@gmail.com>:

On Tue 17 Apr 2018 at 17:18, Jesse Glick <jgl...@cloudbees.com> wrote:

On Tue, Apr 17, 2018 at 11:10 AM, Carles Capdevila Tejada
<capde...@gmail.com> wrote:
> should I change it before into gitblit-scm?

According to the doc, since

https://plugins.jenkins.io/gitblit

does not exist, you should use that.

The doc Jesse is referring to is: 

https://github.com/jenkinsci/scm-api-plugin/blob/master/docs/implementation.adoc#naming-your-plugin

On the basis that there is no gitblit plugin currently, use gitblit

> I hope it doesn't
> prevent users from finding it as its naming deviates

Users will not typically find plugins by `shortName`; rather by
display name and tags.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0PQm_Gx9kahT_CSxf5BrAKkg36-JhE7%2BiayAgQ5J4S-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Sent from my phone

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/CIL6VKkcNBk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxVKGYrJemu_xcdyqW%3DayZ8xDZtu7HoF_Yu8m-w23j4Xg%40mail.gmail.com.