[DISCUSS] Transfer an iOS App to ASF's Apple account ?
Hi, community There is an iOS App called Weex Playground[1] built from the source code of incubator-weex-playground [2]. According to my knowledge, the App was uploaded before Weex donated to ASF under the bundle ID of `com.taobao.weexplayground`. Currently we are trying to solve the problems, and here are the solutions we have: - Delete the existing Weex Playground, then do a source code release for incubator-weex-playground, finally publish a new Weex Playground in ASF's Apple account with the bundleID of `org.apache.weexplayground`. - Transfer the existing Weex Playground to ASF, then do a source code release for incubator-weex-playground, finally publish a new Weex Playground in ASF's Apple account with the bundleID of `org.apache.weexplayground`. After the new one(org.apache.weexplayground) published, we would delete the old one(com.taobao.weexplayground). As suggested in dev@weex.apache, it would be easy to pass the App review of Apple if there are two Apps which only differs in bundleID. As Apple just doesn't allow rename bundleID, I don't know whether it's suitable to have an App whose bundleID is `com.taobao.weexplayground` in ASF's Apple account. I also contact the current owner of Weex Playground [1], they are willing to cooperate with ASF no matter we choose opinion 1 or 2. So, which way is better? [1] https://apps.apple.com/cn/app/weex-playground/id1130862662 [2] https://github.com/apache/incubator-weex-playground/ Best Regards, YorkShen 申远
Re: [DISCUSS] NuttX Proposal
Hi, > Github issues etc can be transferred not sure about bitbucket, I’ll ask. It’s not been done before at the ASF, and infra would need to look into tooling to do that, it may take some effort. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] NuttX Proposal
Hi, > And I think there is no technical problem for transferring the code base, > the infra team will help? Yes Infra will do this, I believe bitbucket is git under the hood so they can transfer it and you will retain all the history of commits. > Just mirror the code from bitbucket to ASFgitbox, and then mirror it to > GitHub, I’m not sure that is possible, but we can ask. > The problem maybe the stuff on BitBucket other than > code, for example, the issues and PRs? I do not think it is easy to > transfer these things... Are they important to the project Greg? Github issues etc can be transferred not sure about bitbucket, I’ll ask. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] NuttX Proposal
I think we can transfer the repos to ASF first. As it is possible to use the disclaimer when making a release in ASF, the transfer should not effect the old release schedule. And we can make a new branch to do the clean up work(which may mess the repo up when it is not fully done), and then merge it back to the development branch. So before the first nasty clean up works done, we could still make releases based on the old code base which has the old license, etc. And I think there is no technical problem for transferring the code base, the infra team will help? Just mirror the code from bitbucket to ASF gitbox, and then mirror it to GitHub, then we could start to use GitHub. And we could even just clone the code to local, and then push it to the ASF gitbox, no problem. The problem maybe the stuff on BitBucket other than code, for example, the issues and PRs? I do not think it is easy to transfer these things... Are they important to the project Greg? Thanks. Justin Mclean 于2019年11月29日周五 下午12:28写道： > Hi, > > > It is our intention to use the Apache GitHub. > > Just be aware that you can use git as well and modify the ASF mirror and > the changes will go to GitHub and vice versa. People don’t have to use > GitHub if they don’t want to. > > > I do have some question about the transition. NuttX is a very active > project with a large user base. We have to both (1) modify the code base > to conform to licensing and other requirements, but also (2) continue to > support the community with quality releases. > > I would suggest moving over repos quickly and continuing to make releases > at the ASF with the work in progress disclaimer. Alternatively you could > not transfer right away and continue to make a couple of non ASF releases > while things are put in order in your current bitbucket repos. Up to the > project to decide. > > > I imagine that it will take a month or two to get the GitHub > repositories ready for prime time. > > The physical transfer shouldn’t take that long, fixing up all the headers > and licenses may take longer but that’s OK when using the work in progress > disclaimer, you can makes incubating ASF release that don’t fully comply > with ASF policy when including that disclaimer. > > > with changes pulled into the Apache Github until such time that support > can transition seamlessly to GitHub. > > Im not sure how easy that’s going to be, generally infra have made a > single transfer and I’m not aware of any projects that tried this approach. > It would require some discussion with infra to see what’s possible here. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] NuttX Proposal
Hi, > It is our intention to use the Apache GitHub. Just be aware that you can use git as well and modify the ASF mirror and the changes will go to GitHub and vice versa. People don’t have to use GitHub if they don’t want to. > I do have some question about the transition. NuttX is a very active project > with a large user base. We have to both (1) modify the code base to conform > to licensing and other requirements, but also (2) continue to support the > community with quality releases. I would suggest moving over repos quickly and continuing to make releases at the ASF with the work in progress disclaimer. Alternatively you could not transfer right away and continue to make a couple of non ASF releases while things are put in order in your current bitbucket repos. Up to the project to decide. > I imagine that it will take a month or two to get the GitHub repositories > ready for prime time. The physical transfer shouldn’t take that long, fixing up all the headers and licenses may take longer but that’s OK when using the work in progress disclaimer, you can makes incubating ASF release that don’t fully comply with ASF policy when including that disclaimer. > with changes pulled into the Apache Github until such time that support can > transition seamlessly to GitHub. Im not sure how easy that’s going to be, generally infra have made a single transfer and I’m not aware of any projects that tried this approach. It would require some discussion with infra to see what’s possible here. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] NuttX Proposal
Hello, It is our intention to use the Apache GitHub. I have been using Bitbucket for a few years and have resisted moving to GitHub. I like Bitbucket only because I know how to use it (My favorite tools are always the ones I know how to use). But GitHub is the plan of record if NuttX is accepted as a podling. I do have some question about the transition. NuttX is a very active project with a large user base. We have to both (1) modify the code base to conform to licensing and other requirements, but also (2) continue to support the community with quality releases. I imagine that it will take a month or two to get the GitHub repositories ready for prime time. During that time, I think that the Bitbucket/BSD repositories should continue with business as usual with changes pulled into the Apache Github until such time that support can transition seamlessly to GitHub. Does that seem reasonable? We may be somewhat different from other podlings because of the state and maturity of the code. Greg On 11/28/2019 9:04 PM, Justin Mclean wrote: Hi, Over on the google groups I saw some comments about the use of GitHub. While most ASF projects have moved that way it not a requirement to use. You could use svn [1] or git at Apache and be hosted on the ASF servers. You can even be hosted at the ASF and on GitHub [1]. Committers are not forced to use GitHub if they don't want to. Staying at bitbucket is probably not an option, but you could talk to Infra to see if it was possible. Thanks, Justin 1. https://svn.apache.org/viewvc 2. https://gitbox.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] NuttX Proposal
Hi, Over on the google groups I saw some comments about the use of GitHub. While most ASF projects have moved that way it not a requirement to use. You could use svn [1] or git at Apache and be hosted on the ASF servers. You can even be hosted at the ASF and on GitHub [1]. Committers are not forced to use GitHub if they don't want to. Staying at bitbucket is probably not an option, but you could talk to Infra to see if it was possible. Thanks, Justin 1. https://svn.apache.org/viewvc 2. https://gitbox.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] NuttX Proposal
I have added two mentors (based on volunteer at email threads) and more initial committers (based on Gregory Nutt's update) into the proposal. Please comment if any other concerns. Thanks, Junping 张铎(Duo Zhang) 于2019年11月27日周三 下午4:13写道： > OK, good. > > So the remaining issues for joining the incubator are: > > 1. Get more initial committers. > 2. Besides you, get two more mentors. > > Will start working on resolve them. > > Thanks. > > Justin Mclean 于2019年11月27日周三 下午2:23写道： > > > Hi, > > > > > Hi, Justin, do these works need to be done before joining the > incubator, > > or > > > we could do this during the incubating time, before we make the first > > > official release under the governance of ASF? > > > > Neither. They need to be made before you graduate, so you have plenty of > > time to work on them once you join the incubator. > > > > If you use the work in progress DISCLAIMER [1] you can make releases that > > don’t comply with policy while in incubation. > > > > Thanks, > > Justin > > > > 1. https://incubator.apache.org/policy/incubation.html#disclaimers > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [VOTE] Release Apache DLab (incubating) 2.2
Hi, > - DISCLAIMER: Do we need to replace the current disclaimer with work in > progress disclaimer? You don’t have to but doing so may make it easier to pass an IPMC vote. If you use the WIP DISCLAIMER you don’t need to fully comply with ASF policy. >3) We will remove unnecessary dependency(directory-server) which > we do not use. I think you may of missed my point. You don’t lis dependancies at all, you only need to list what 3rd party code is included in your source release. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Font size on incubator site too small?
+1 On Thu, Nov 28, 2019, 5:25 AM Andy Seaborne wrote: > Or default to the user's choice of font family in the browser. > > On 28/11/2019 06:01, Dave Fisher wrote: > > Reading glasses will enlarge things for many of us. > > > > I’m certainly in favor a larger font, but please keep it serifed. > > > > Sent from my iPhone > > > >> On Nov 27, 2019, at 11:48 PM, Ted Dunning > wrote: > >> > >> The problem might just be that pixels are getting smaller. > >> > >> > >> > >>> On Thu, Nov 28, 2019 at 12:15 AM Justin Mclean < > jus...@classsoftware.com> > >>> wrote: > >>> > >>> Hi, > >>> > >>> Is it just my old eyes or do other people also find the font size too > >>> small on the incubator site? While it does scale well and easy for a > user > >>> to increase the size, have we set the default too small? This may of > course > >>> depend on platform and browser use and I’ve not done any exhaustive > >>> checking, as the measurement is in px that may be the issue. The body > text > >>> seem to be set to 14px, (which is 10.5pt and that should be in pt or > ems > >>> not px) and 12pt (16px) is generally recommended as a minimum size. > >>> > >>> Thanks, > >>> Justin > >>> - > >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >>> For additional commands, e-mail: general-h...@incubator.apache.org > >>> > >>> > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] NuttX Proposal
Thanks Mohammad for volunteering as mentor here. I have added you and Justin into the proposal. Thanks, Junping Mohammad Asif Siddiqui 于2019年11月28日周四 下午7:13写道： > Hi Guyz, > > Incase if you are looking for Mentors for this project then I would be > happy to help the NuttX community in any dimensions I can. Even if your > mentor list is full then still I can help the community with the release > activities. Do let me know if you need any help. > > Regards > Asif > https://github.com/asifdxtreme > https://asifdxr.netlify.com > > On 2019/11/27 08:13:36, 张铎(Duo Zhang) wrote: > > OK, good. > > > > So the remaining issues for joining the incubator are: > > > > 1. Get more initial committers. > > 2. Besides you, get two more mentors. > > > > Will start working on resolve them. > > > > Thanks. > > > > Justin Mclean 于2019年11月27日周三 下午2:23写道： > > > > > Hi, > > > > > > > Hi, Justin, do these works need to be done before joining the > incubator, > > > or > > > > we could do this during the incubating time, before we make the first > > > > official release under the governance of ASF? > > > > > > Neither. They need to be made before you graduate, so you have plenty > of > > > time to work on them once you join the incubator. > > > > > > If you use the work in progress DISCLAIMER [1] you can make releases > that > > > don’t comply with policy while in incubation. > > > > > > Thanks, > > > Justin > > > > > > 1. https://incubator.apache.org/policy/incubation.html#disclaimers > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] NuttX Proposal
Hi Guyz, Incase if you are looking for Mentors for this project then I would be happy to help the NuttX community in any dimensions I can. Even if your mentor list is full then still I can help the community with the release activities. Do let me know if you need any help. Regards Asif https://github.com/asifdxtreme https://asifdxr.netlify.com On 2019/11/27 08:13:36, 张铎(Duo Zhang) wrote: > OK, good. > > So the remaining issues for joining the incubator are: > > 1. Get more initial committers. > 2. Besides you, get two more mentors. > > Will start working on resolve them. > > Thanks. > > Justin Mclean 于2019年11月27日周三 下午2:23写道： > > > Hi, > > > > > Hi, Justin, do these works need to be done before joining the incubator, > > or > > > we could do this during the incubating time, before we make the first > > > official release under the governance of ASF? > > > > Neither. They need to be made before you graduate, so you have plenty of > > time to work on them once you join the incubator. > > > > If you use the work in progress DISCLAIMER [1] you can make releases that > > don’t comply with policy while in incubation. > > > > Thanks, > > Justin > > > > 1. https://incubator.apache.org/policy/incubation.html#disclaimers > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Font size on incubator site too small?
Or default to the user's choice of font family in the browser. On 28/11/2019 06:01, Dave Fisher wrote: Reading glasses will enlarge things for many of us. I’m certainly in favor a larger font, but please keep it serifed. Sent from my iPhone On Nov 27, 2019, at 11:48 PM, Ted Dunning wrote: The problem might just be that pixels are getting smaller. On Thu, Nov 28, 2019 at 12:15 AM Justin Mclean wrote: Hi, Is it just my old eyes or do other people also find the font size too small on the incubator site? While it does scale well and easy for a user to increase the size, have we set the default too small? This may of course depend on platform and browser use and I’ve not done any exhaustive checking, as the measurement is in px that may be the issue. The body text seem to be set to 14px, (which is 10.5pt and that should be in pt or ems not px) and 12pt (16px) is generally recommended as a minimum size. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache DLab (incubating) 2.2
Hello Justin Mclean, Thanks for your feedback. - DISCLAIMER: Do we need to replace the current disclaimer with work in progress disclaimer? - LICENSE: 1) We will add a license for Material Icons and Open Sans font to the list of licenses. 2) Mentioned files will be updated with license too. 3) We will remove unnecessary dependency(directory-server) which we do not use. Thanks, Oleg On 2019/11/26 23:28:06, Justin Mclean wrote: > Hi,’ > > -1 (binding) due possible IP issues with this cat photo [1] and missing > license information. > > These issues have been brought up before in past VOTES and there was a > discussion on that same image a while back on this list, believe it comes > from here [5]. > > I checked: > - Incubating in name > - signatures and hashes are fine > - DISCLAIMER exists (but not the work in progress one) > - LICENSE is missing some licenses (see below) > - NOTICE is fine > > LICENSE is missing: > - License for Material Icons > - License for Open Sans font > - This files [2][3][4] > > It also seem to me that you have list the licenses of dependancies rather > than what is actually bundled in the source release. If it not in the release > there's no need to mention it. Can yo confirm everything mentioned is > included and not just a dependancy? > > It would also be good to sign the release with an apache email address. > > Thanks, > Justin > > 1. ./integration-tests/examples/test_templates/deeplearning/cat_gray.jpg > 2. ./services/provisioning-service/provisioning.yml > 3. ./integration-tests/examples/test_templates/deeplearning/conv.prototxt > 4 ./services/self-service/src/main/resources/webapp/.editorconfig > 5. https://www.warrenphotographic.co.uk/galleries.php > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
