>From what I understood, 'netbeans' is reserved there. There's no hurry.
So 1st let's see if we are capable of producing snap packages on builds.apache.org and then, once we have the bits, we can open a relationship with Canonical via that site and have a script upload the bits. --emi ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On 5 July 2018 10:18 PM, Laszlo Kishalmi <[email protected]> wrote: > Changing list from private -> dev. > > > So this is what we are talking about? Do you want to "claim" the netbeans > > name on behalf of the PPMC on Snapcraft.io? > > > > --emi > > Yes, that's what I was talking about. > > On 07/02/2018 01:04 AM, Emilian Bold wrote: > > > I still don't understand what do you want and why are we talking on private@ > > > > So, I see we have https://issues.apache.org/jira/browse/NETBEANS-341 and > > the PR has been merged. > > > > The next steps seem to be: > > > > 2. actually building snap packages on builds.apache.org then > > 3. uploading the bits to snapcraft. > > > > So, what exactly do you want? Do you want to upload bits to snapcraft? We > > should have some script for that. > > > > If we generate some private key to talk with snapcraft we should save that > > private key in the private PPMC repo we have. > > > > Can't we put the script that uploads to snapcraft to builds.apache.org > > directly? > > > > It seems there is very little you need to do in person, so I'm not sure > > what kind of permission you need. > > > > I assume you might be talking about this > > https://issues.apache.org/jira/browse/NETBEANS-341?focusedCommentId=16367610&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16367610 > > : > > > > > someone with access to commit to the repository needs to login with their > > > github credentials [at the build service and add the repo]. Once that is > > > done they are able to select to register the name in the store by further > > > logging-into a launchpad account and then entering the name. They will > > > need to file a claim on the name as it is, which you pointed out, > > > reserved; they just need to explain that they’re acting on behalf of the > > > project and are therefore the legitimate owner of the name. > > > > > > So this is what we are talking about? Do you want to "claim" the netbeans > > > name on behalf of the PPMC on Snapcraft.io? > > > > --emi > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > > > On 2 July 2018 9:08 AM, Laszlo Kishalmi [email protected] wrote: > > > > > Thank you Emilian for asking questions! Giving further information never > > > > > > hurts. > > > > > > The netbeans name is a "reserved" name on Snapcraft.io, in order to no > > > > > > one shall create a package with the name "netbeans" coming just out of > > > > > > the blue. (So "netbeans" is a recognized brand by Snapcraft.io) > > > > > > Well, there can be separate channels set up for a package, like stable, > > > > > > beta or edge, but the naming of these channels are completely under the > > > > > > control of the package maintainer. > > > > > > What I think would be good is to have a channel track the release branch > > > > > > and have one to track the master. We could build our binaries in/after > > > > > > our Jenkins job produces a daily/whatrver build and push the result to > > > > > > the appropriate snap channel of the package. > > > > > > I hope I made this more clear. > > > > > > On 07/01/2018 10:45 PM, Emilian Bold wrote: > > > > > > > I don't really understand your question. > > > > > > > > Do you want to just 'reserve' the nebeans name or do you want to make > > > > snap releases on snapscraft.io? > > > > > > > > If you want to make releases, that doesn't seem to be the way to go see > > > > http://www.apache.org/legal/release-policy.html We could do snap > > > > convenience binaries as part of our normal release, but not separate > > > > out-of-band releases. > > > > > > > > If you just want to 'reserve' the name I have no problem you sending an > > > > email for that. NetBeans is an Oracle trademark and soon to be an > > > > Apache Software Foundation trademark so the Snapcraft guys really can't > > > > release anything under the netbeans name unless they want problems. > > > > > > > > Just note that reserving the netbeans name there doesn't mean we'll do > > > > releases there. > > > > > > > > --emi > > > > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > > > > > > > On 2 July 2018 4:37 AM, Laszlo Kishalmi [email protected] wrote: > > > > > > > > > Well, I have found Apache CouchDB does a Snap distribution, so we > > > > > have a > > > > > > > > > > precedence here. > > > > > > > > > > So I ask my question in reverse, is there anybody against this plan? > > > > > > > > > > On 06/18/2018 09:59 PM, Emilian Bold wrote: > > > > > > > > > > > I don't believe Apache does releases on 3rd party channels. > > > > > > > > > > > > Can we build a convenience binary snap package on our infra and > > > > > > just upload it there? > > > > > > > > > > > > --emi > > > > > > > > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > > > > > > > > > > > On 18 June 2018 11:31 PM, Laszlo Kishalmi [email protected] > > > > > > wrote: > > > > > > > > > > > > > Dear all, > > > > > > > > > > > > > > You may know that I'm trying to make Apache NetBeans available as > > > > > > > a Snap > > > > > > > > > > > > > > package. Right now they are keeping "netbeans" in their reserved > > > > > > > names. > > > > > > > > > > > > > > I do need to arrange that we could claim the name. I do not know > > > > > > > how > > > > > > > > > > > > > > such things shall be arranged, so I thought write here. If you > > > > > > > entitle > > > > > > > > > > > > > > me to have discussion with Snapcraft Team (Canonical), then I'd > > > > > > > gladly > > > > > > > > > > > > > > do that. If there are other ideas on this, or if there is someone > > > > > > > who > > > > > > > > > > > > > > does not support this movement, please speak up as well! > > > > > > > > > > > > > > Thank you in advance, > > > > > > > > > > > > > > Laszlo Kishalmi > > -- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
