I would recommend to use jenkinsci org as a main repository. Regarding the issues, why don't you use the central Jenkins JIRA tracker? The most of users will create their issues on it in any case, so we commonly disable trackers in GitHub
2015-08-16 15:17 GMT+03:00 Damian Szczepanik <[email protected]>: > They are the same (fork). I can push commiets but not issues. In that case > I don't think this is confortable to keep jenkincci for release and fork > for issues/pull. That's why I wonder if I can have one repo with all > history, issues and incompleted pulls. > > Damian > > > > @Damian > Are these plugins different? They have the similar group/artifact IDs, so > I thought one of them forks another one. In such case you would be able to > just push the commits > > > > 2015-08-16 14:46 GMT+03:00 Damian Szczepanik <[email protected] > >: > Invitation accepted. > > https://github.com/jenkinsci/cucumber-reports-plugin is 3 years old > (without any > update) and does not have issues that haven't been fixed yet > https://github.com/damianszczepanik/cucumber-reporting-jenkins/issues so > how > about deleting first repo and transferring second one to jenkinsci (just > replace it)? In that > case no need to maintain both. Does it make sense? Will I have push access > to such > repo? > > Damian > > > There is an existing repo: > > https://github.com/jenkinsci/cucumber-reports-plugin . I've added > Damian to > > committers, ho he can push actual changes there after accepting the > invitation. > > > Damian also provided his JIRA id in another thread: dszczepanik , so > I've made him a default assignee. > > > > > воскресенье, 16 августа 2015 г., 12:40:30 UTC+3 пользователь Oleg > Nenashev написал: > > +1 for the default location. We cannot transfer the permissions on the > remote > > repository. BTW we can fork it if you agree. > > > > In order to complete the transfer, we also need your Jenkins JIRA ID. > > > > воскресенье, 16 августа 2015 г., 11:18:49 UTC+3 пользователь Richard > Bywater написал: > > Re the new location, shouldn't it be being developed at the standard > > location? ( https://github.com/jenkinsci/cucumber-reports-plugin ) > > > > Richard. > > > On Sun, 16 Aug 2015 at 19:07 Damian Szczepanik <[email protected]> > wrote: > > > Hi, > > > Recently I've taken over responsibility for Cucumber Reports Plugin[1] > which > > is now developed at new location [2]. I have already released dependent > > libraries over maven central repository after transferring privileges > [3] but now I need: > > > 1. Update [1] because there is outdated > > 2. Have access to upload new version of the plugin > > 3. Transfer all privileges belongs to old owner that might be helpful > for further maintenance of the plugin > > > Thanks, > > Damian > > > [1] https://wiki.jenkins-ci.org/display/JENKINS/Cucumber+Reports+Plugin > > [2] > https://github.com/damianszczepanik/jenkins-cucumber-reporting-plugin > > [3] https://issues.sonatype.org/browse/OSSRH-17110 > > > > -- > > 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 [email protected]. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/jenkinsci-dev/17eee173-83ad-4696-8270-ffd2d726dae7%40googlegroups.com > . > > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > 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/vqNh6_1-HCA/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/1609700586.20150816134647%40gmail.com > . > For more options, visit https://groups.google.com/d/optout > . > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCcL5aJ%2Bq2vi2JdsAiURkzH%3Di49u2RfmBCm3hr4CT1SpQ%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCcL5aJ%2Bq2vi2JdsAiURkzH%3Di49u2RfmBCm3hr4CT1SpQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- > 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/vqNh6_1-HCA/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/1926657430.20150816141727%40gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/1926657430.20150816141727%40gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBXu%3DfPT13a34Z%2Bu1M1DQHeR%3Dnm%2Behx440s%3Dbd4RapaZg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
