Can someone create a new jenkinsci repo please ("pipeline-rest-api-plugin")

[Tom Fennelly]

We created https://github.com/jenkinsci/pipeline-stage-view-plugin a week or so ago, but also need "pipeline-rest-api-plugin". Would someone with privs mind creating it please?

[Baptiste Mathus]

IIRC you've been voiced some weeks ago. So you could do it yourself if you want?

-- Baptiste

Le 2 févr. 2016 7:21 PM, "Tom Fennelly" <tom.fe...@gmail.com> a écrit :

We created https://github.com/jenkinsci/pipeline-stage-view-plugin a week or so ago, but also need "pipeline-rest-api-plugin". Would someone with privs mind creating it please?

--
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/dbfd776e-be7d-42d3-bd87-8de787899273%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tom Fennelly]

Ah ok ... thanks Baptiste. I'll look see what I need to do.

--
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/z5BG3Ol2IhI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS52ajM8J_QVyY-J7XwXTv4b9TC7%3Dpph%3Daf5TXVpu78UBA%40mail.gmail.com.

[Daniel Beck]

Due to the significant number of unused repositories (almost three weeks and not a single real commit in the one you mention) I'd prefer if you forked a repo that already has content.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPaoJH9UwrgunHatJ8Sy%2Bj8Pn45nNQPUsuWHX75Aq5kE46dA%40mail.gmail.com.

[Tom Fennelly]

Well, we were a bit premature about creating the other repo, but it is going to be used. What do you mean about forking a repo that already has content? Do you mean use a single repo for multiple things as a repo saving device? I don't mind doing that but I know others will get the underwear in a bundle :)

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/E3DC1DF0-A946-47BB-BBD8-16E49DC7E93D%40beckweb.net.

[Antonio Muñiz]

On Tue, Feb 2, 2016 at 9:19 PM, Daniel Beck <m...@beckweb.net> wrote:
> almost three weeks and not a single real commit in the one you mention

Daniel, there is currently an internal work-in-progress to make that
plugin OSS. We don't want to bother with internal stuff in a public
repository, that's why there were no commit in 3 weeks. Just FYI.

--
Antonio Muñiz
Software Engineer
CloudBees, Inc.

[Daniel Beck]

On 02.02.2016, at 21:24, Tom Fennelly <tom.fe...@gmail.com> wrote:

> What do you mean about forking a repo that already has content?

Only fork once you've actually pushed something.

The problem we sometimes have is that someone creates/asks for creation of a repo, and then does nothing to add content. The safer approach therefore is to fork another repo. Since forking an effectively empty repo would be pointless and have the same problem, forking should only be done once actual content has been pushed to that repo.

[Tom Fennelly]

On 2 February 2016 at 20:32, Daniel Beck <m...@beckweb.net> wrote:

The problem we sometimes have is that someone creates/asks for creation of a repo, and then does nothing to add content.

I get the objective.

 

The safer approach therefore is to fork another repo. Since forking an effectively empty repo would be pointless and have the same problem, forking should only be done once actual content has been pushed to that repo.

I don't get this part. I ultimately want to end up with a "jenkinsci/pipeline-rest-api-plugin" repo. What are you suggesting I fork to get to there? Are you suggesti ng that I create a repo in my own account and fork it into jenkinsci?

[Daniel Beck]

On 02.02.2016, at 21:42, Tom Fennelly <tom.fe...@gmail.com> wrote:

> What are you suggesting I fork to get to there? Are you suggesti ng that I create a repo in my own account and fork it into jenkinsci?

Yes, and only (request to) fork once there is actually something in your repo, as documented[1].

My favorite repos in the jenkinsci organization:
https://github.com/jenkinsci?utf8=%E2%9C%93&query=jenkinsmobi

If those began life in Luca's account and were only forked once the repos contained something (i.e. code), we'd either have a) no repos or b) repos with content. IMO either is better than what we have: empty repos that may or may not get filled (well, by now, the latter, so we should probably rm them).

Again, this is just my preference based on this possible problem when creating repos instead of forking. Additionally, if nothing ever gets added, it's difficult to determine why/for whom they were created.

1: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites

[Michael Neale]

I heretofore suggest calling empty repos "name squatters" as that seems to be what they end up doing. 

[Tom Fennelly]

Thanks Daniel. I agree with you. Creating the repo in my own account and then forking into jenkinsci just seemed like a sidestepping of the rules to me. It seemed strange that one cannot create a new repo in jenkinsci, but can fork an existing one into it.

--
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/z5BG3Ol2IhI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/90928C57-D6DF-474B-A38B-C73C0F106763%40beckweb.net.