As Shazron said and as I pointed out once before, Apache can enable apps such
as Probot, which works nicely for more then just moving issues.
I pointed this feature link before.
https://probot.github.io/apps/move/
I think Probot will fit our needs better then the other as it provides more
Yes, I was talking about that. I only see a big "Authorize Github" button
there. Will try it when I find time. Thanks for testing.
Am Do., 23. Aug. 2018 um 11:13 Uhr schrieb Jan Piotrowski <
piotrow...@gmail.com>:
> > How do we get apps unlocked for organization access?
> > Just request access
> How do we get apps unlocked for organization access?
> Just request access using the GitHub dialog that pops up, or doe we have to
> file INFRA tickets?
I don't think anyone has tried that before.
If the question was directed at the
https://github-issue-mover.appspot.com/ I posted, it doesn't
How do we get apps unlocked for organization access?
Just request access using the GitHub dialog that pops up, or doe we have to
file INFRA tickets?
While I found it very nice to have some dedicated space for higher level
design discussions, cordova-discuss
is heavily unmaintained and feedback to
Issues can be moved e.g. with https://github-issue-mover.appspot.com/.
As the issues were a thing of keeping track of stuff, I think
@raphinesse and @brodybits who created most of those issue should take
care of moving their issues to the appropriate repo or close them
themselves, so they are
It's mainly about discoverability, now that we have `cordova` repo
itself (one stop shop for general issues?). `discuss` repo was there
as you mentioned for historical reasons. Now that we have the
`cordova` repo, and we can discuss in the Issues of that repo, another
repo for discussion is
Wasn't `cordova-discuss` for a totally different use case?
>From how I understood it, Cordova has/had a formal "proposal" process
that consisted of someone writing a proposal as a PR for higher level
topics. Then a discussion was triggered via an email to this list,
which was had in the comments
I think we should stick to one repo --
https://github.com/apache/cordova and archive the discuss repo.
We should point to that one repo for all things Cordova w.r.t to dev.
On Thu, Aug 23, 2018 at 4:13 AM Chris Brody wrote:
>
> While I personally think it would continue to fill an existing gap
While I personally think it would continue to fill an existing gap (track
discussion of some random and otherwise uncategorized Cordova topics) it
has proven to be unpopular.
Some alternatives I can think of:
* discuss such discussions in https://github.com/apache/cordova
* discuss elsewhere such
