This also ties into Mark’s question earlier on.
The OpenWhisk part of the proposal is currently being developed in GitHub and
the developers are used to the GitHub flow and features including but not
limited to GitHub Issues.
We have discussed this topic before proposing the project and we are all aware
on the caveats. But as we write in the proposal, we intend to work with infra
and other stakeholders to have repositories in GitHub accepted as primary work
repositories before graduation.
Hope that helps.
> Am 14.10.2016 um 12:50 schrieb John D. Ament <johndam...@apache.org>:
> Can your or someone representing the proposed podling explain why using
> github as master is preferable to the current mirror strategy in use?
> On Fri, Oct 14, 2016 at 6:29 AM Sam Ruby <ru...@intertwingly.net> wrote:
>> On Fri, Oct 14, 2016 at 1:31 AM, Greg Stein <gst...@gmail.com> wrote:
>>> On Thu, Oct 13, 2016 at 3:27 PM, Sam Ruby <ru...@intertwingly.net>
>>>> Hello everyone,
>>>> Attached to this message is a proposed new project - Apache OpenWhisk.
>>>> The text of the proposal is included below. Additionally, the proposal
>>>> in draft form on the Wiki, where we will make any required changes:
>>>> We look forward to your feedback and input.
>>> OpenWhisk has a first-time-unique request on its Git repository request.
>>> inserted a comment about OpenWhisk's use of a GitHub repository [from
>>> Infra's standpoint], and the relation to the Foundation and a possible
>>> block on graduation.
>> If I could get some help in the form of an infrastructure team review
>> of the following plan, I would appreciate it:
>> - Sam Ruby
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org