It’s the last piece of the donation process and is pretty much stuck. You
can ask and keep asking about this, the answer will be the same. I propse
that we should simply be happy with what we have and move on. Python
support, I suggest, should be lightweight and done via LSP rather than the
old
I know this has been asked many times before but what is the current status
of the Python Donation?
Some work based on previous releases have been worked, and it's working
locally, (although the build fails due to some out of date API needing
updates) but in the end the work is waiting on the
I'd like to see a non apache.netbeans branch if it would result in some
modules that could be installed into regular NB. I'd contribute PRs once
and a while for bugfixes, maybe more as time permits.
If netbeans is ever interested in it, it could be merged.
-ernie
On 10/3/2020 7:37 AM, Eric
Okay so digging through other emails on the subject I find a lot of the old
code including python code in the Mercurial / hg repository as mentioned
previously here [1] as well as Tim's Maven-ized version here [2]
So the question is, to get "python" brought in is this as simple as
(1) make a
Is anyone working on python? If not, what needs to be done to start the
ball rolling? Is it still pending Oracle vetting for the donation?
Eric Bresie
ebre...@gmail.com
On Thu, Sep 17, 2020 at 8:00 AM Eric Bresie wrote:
>
>Hopefully there isn’t a newer thread on this but was looking
Hopefully there isn’t a newer thread on this but was looking through old
emails.
Assume this is related to
NETBEANS-4538 Please support Python.
Is the contribution in question the same as associated with the nbpython.org
project? On that site it seems to indicate it’s dual
What needs to be done by us individually?
I contributed a bit of build logic about 6 years ago.
Whichever commits are attributed to me, I'd obviously donate.
I had also signed the OCA before.
On 2020/04/13 05:13:17 Lou Dasaro wrote:
> Everyone on my team was required to sign the OCA before
Everyone on my team was required to sign the OCA before committing code was
allowed.
I'm sure we could sign something else if need be.
Most of the code was written by Sun employees who are long gone.
I am not able to work on the project, except for consults like this.
Regards,
On 2020/04/10
OK, thanks a lot, passed all this on, let's see.
Gj
On Fri, Apr 10, 2020 at 3:31 PM Matthias Bläsing
wrote:
> Hi,
>
> Am Donnerstag, den 09.04.2020, 11:39 +0200 schrieb Geertjan Wielenga:
> > The argument could be made that since the code was part of contrib under
> > the OCA (Oracle
Hi,
Am Donnerstag, den 09.04.2020, 11:39 +0200 schrieb Geertjan Wielenga:
> The argument could be made that since the code was part of contrib under
> the OCA (Oracle Contributor Agreement), it belongs to Oracle and Oracle can
> simply donate it.
yes - and assuming, that correct procedure was
Hello All,
I can vouch that nearly all of the code in the Python modules was written by
Sun or Oracle engineers.
Bug fixes were subsequently written by three or four volunteers, all of whom
signed the OCA. A couple of Oracle engineers helped out in their spare time
with some (bug fixes) code.
Hi all,
Ideally, Oracle would donate the Python modules as part of the 6th (and
hopefully final) donation.
However, unlike everything else donated so far, the code in the Python
modules was not written by Sun or Oracle engineers.
The argument could be made that since the code was part of
12 matches
Mail list logo
