[jboss-jira] [JBoss JIRA] (WFLY-10491) Fix wildfly-capabilities repository representation on GitHub

[Radoslav Husar (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-10491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar updated WFLY-10491:
----------------------------------
    Description: 
Currently, the https://github.com/wildfly/wildfly-capabilities repository says its "forked from bstansberry/wildfly-capabilities". The common practice and understanding in community is that the upstream repository is the one that is not forked from any other repository. Thus having the upstream repository not represented as upstream is confusing.

The repo should have been *moved* to wildfly organization and not *forked*. This as a result has messed up all the previous forks, like https://github.com/rhusar/wildfly-capabilities which makes a poor usability from the UI, because it opens PRs against wrong repo by default.

To remedy this, with a method we used in the past, is to delete the bstansberry/wildfly-capabilities repository (and then fork from wildfly of course).

  was:
Currently, the https://github.com/wildfly/wildfly-capabilities repository says its "forked from bstansberry/wildfly-capabilities". The common practice and understanding in community is that the upstream repository is the one that is not forked from any other repository. Thus having the upstream repository not represented as upstream is confusing.

The repo should have been *moved* to wildfly organization and not *forked*.

To remedy this, with a method we used in the past, is to delete the bstansberry/wildfly-capabilities repository (and then fork from wildfly of course).



> Fix wildfly-capabilities repository representation on GitHub
> ------------------------------------------------------------
>
>                 Key: WFLY-10491
>                 URL: https://issues.jboss.org/browse/WFLY-10491
>             Project: WildFly
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Radoslav Husar
>            Assignee: Brian Stansberry
>            Priority: Trivial
>
> Currently, the https://github.com/wildfly/wildfly-capabilities repository says its "forked from bstansberry/wildfly-capabilities". The common practice and understanding in community is that the upstream repository is the one that is not forked from any other repository. Thus having the upstream repository not represented as upstream is confusing.
> The repo should have been *moved* to wildfly organization and not *forked*. This as a result has messed up all the previous forks, like https://github.com/rhusar/wildfly-capabilities which makes a poor usability from the UI, because it opens PRs against wrong repo by default.
> To remedy this, with a method we used in the past, is to delete the bstansberry/wildfly-capabilities repository (and then fork from wildfly of course).



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)