I would assume since we (committers) can create a New Label in Github,
we would have the permission to do so via API...
On Wed, Aug 22, 2018 at 2:28 AM wrote:
>
> Labels that I would like to have:
>
> - something to show that you are open to suggestions or want to work out
> how something is
Nightly build #828 for cordova has failed.
Please check failure details on build details page at
https://builds.apache.org/job/cordova-nightly/828/
You can also take a look at build console:
https://builds.apache.org/job/cordova-nightly/828/consoleFull
-
Jenkins for Apache Cordova
I am raising this topic with some hope that we may find a good solution in
the near future.
As I said numerous times I still do not see a good way to track some
high-level topics of items that need to be addressed. I think this item is
an excellent example of itself.
I will admit that I have
>From some other discussions I started to wonder if we should consider
deprecating some more Cordova plugins that fall into either of these
categories:
* not critical to core need or functionality
* hard to support
My idea is that people in the user community can start to expand and
support the
I noticed that a lot of important dev chat discussions on private Slack PMC
channel does not really need to be kept private. I am not so happy that
some discussions leading to important decisions are kept on a private
channel. Can we make a public dev channel instead?
As I said in the PR I really do not see what this has to do with a project
or repo called "contribute".
On Wed, Aug 22, 2018 at 6:02 PM Jan Piotrowski wrote:
> And Part #2:
> Contributor documentation on the process "Deprecation and Archiving"
> of repositories:
>
Hi,
today I created a new repository https://github.com/apache/cordova-contribute
It is meant to contain all the contributor documentation like general
process, all the "How we do GitHub" documentation that will be written
based on the recent mailing list threads etc.
Content should be added
And Part #2:
Contributor documentation on the process "Deprecation and Archiving"
of repositories:
https://github.com/apache/cordova-contribute/pull/2
J
Am Mi., 22. Aug. 2018 um 21:07 Uhr schrieb Jan Piotrowski
:
>
> Part #1:
> A public deprecation policy on the Cordova website:
>
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
Part #1:
A public deprecation policy on the Cordova website:
https://github.com/apache/cordova-docs/pull/878
Please keep discussion on the PR and text in the GitHub Pull Request.
Part #2 will be the contributor documentation that will include the
steps and notice template required to deprecate a
janpio closed pull request #1: [WIP] Deprecation and Archiving Policy
URL: https://github.com/apache/cordova-contribute/pull/1
This is an automated message from the Apache Git Service.
To respond to the message, please log
janpio commented on issue #1: [WIP] Deprecation and Archiving Policy
URL: https://github.com/apache/cordova-contribute/pull/1#issuecomment-415116916
Thank you for hijacking this pull request, although I explicitly added
"[WIP]" to its title and mentioned that I will send an email when this
brodybits commented on issue #1: [WIP] Deprecation and Archiving Policy
URL: https://github.com/apache/cordova-contribute/pull/1#issuecomment-415113793
I gotta say that I cannot see what a deprecation policy has to do with a
project about "contributors". I would also favor putting this
Sorry for this email, I seem to have misconfigured the new repo. Will
get it changed by INFRA.
J
Am Mi., 22. Aug. 2018 um 19:18 Uhr schrieb GitBox :
>
> janpio opened a new pull request #1: [WIP] Deprecation and Archiving Policy
> URL: https://github.com/apache/cordova-contribute/pull/1
>
>
>
janpio opened a new pull request #1: [WIP] Deprecation and Archiving Policy
URL: https://github.com/apache/cordova-contribute/pull/1
Work in Progress PR - will send out email to dev mailing list when read to
review (and change title and this description)
Nope, the last few days convinced me that we do not want that ;)
But it gave a nice impression what we should add to the issues
templates so bug reports are actionable.
Am Mi., 22. Aug. 2018 um 01:21 Uhr schrieb julio cesar sanchez
:
>
> I just had a quick look and around 90% of new issues are
And it's gone. Thanks INFRA!
Am Mi., 22. Aug. 2018 um 15:33 Uhr schrieb Jan Piotrowski
:
>
> INFRA issue created: https://issues.apache.org/jira/browse/INFRA-16938
> Am Di., 7. Aug. 2018 um 00:03 Uhr schrieb :
> >
> > +1
> >
> > Chris Brody schrieb am Mo., 6. Aug. 2018, 16:38:
> >
> > > +1
> > >
INFRA issue created: https://issues.apache.org/jira/browse/INFRA-16938
Am Di., 7. Aug. 2018 um 00:03 Uhr schrieb :
>
> +1
>
> Chris Brody schrieb am Mo., 6. Aug. 2018, 16:38:
>
> > +1
> > On Mon, Aug 6, 2018 at 10:37 AM julio cesar sanchez
> > wrote:
> > >
> > > +1
> > >
> > > El lun., 6 ago.
Nice!
Seems the project is linked to https://github.com/apache/cordova as
https://github.com/apache/cordova/pull/1 is the only one thing that
shows up when one removes the `is:open` filter when "Only show results
from linked repositories" is checked.
Am Mi., 22. Aug. 2018 um 05:02 Uhr schrieb
19 matches
Mail list logo
