I'm working for a client on their new website.
It's my last mission, so another developer is going to continue my work after my final delivry.
In order to accelerate the process of "switching developer", my client asks me to give an access of the source code to the next developer.. but as my mission is not finished yet (98% of the website is OK) I risk that the new developer steals the code and the client refuses to pay me.
Is there any tool allowing me to securely give the new developer an access to view my code, ask questions, etc without allowing him to steal it (at least easily) ?
Thank you.
No, this seems more like a legal/contract issue. If the other developer can see the source, he could always duplicate it.
In short, no: If they see they source code, they can duplicate it.
However, if your client simply wants the new developer to have an idea of how your code is structured, you could send them UML diagrams of the Class Hierarchy and the flow of the site.
I hope this helps.
Related
My first Alexa skill is almost ready to go public, but I seem to have gotten myself a bit tangled... I'm sure I'm missing something obvious.
I asked Amazon to Certify But Not Publish this skill, to check that I wasn't missing anything obvious. They did so. Great, but...
Since then, I've uploaded some slightly modified models. Since I'm ready to go, I went to Validation and punched Certify again. It told me "You cannot submit this skill for review because it has a ‘Certified’ version. Publish or withdraw the previously ‘Certified’ version to submit this skill for review."
Submission shows a warning that the most recent validation failed (for the above reason).
OK, I understand. But I'm not sure how to do either of those.
When I look at Version History, I do see the previously Certified skill version. However, I can't see how to either publish or withdraw it!
A quick websearch hasn't found anything which clarifies this for me. I MUST be missing something obvious -- these operations are on a different page, or something like that. Could someone point me to where I can perform them?
(Yes, I looked at https://developer.amazon.com/en-US/docs/alexa/devconsole/test-and-submit-your-skill.html. That doesn't seem to address my situation of having a certified version, having a new version which couldn't yet be certified, and not being sure how to go either forward or backward.)
In the list of the skill, make sure you select the dev or in review version and go inside it
Go into the certification tab and in the submission menu
Click on withdraw from review
If you don't see that, contact the support
I have a client who would like me to publish his app on Google Play Store. He has given me the .apk, description, icons, and banners.
I am going to buy a developer account ($25) for him but before that I would like to ask you guys that as I didn't actually develop this app. I am only going to publish his app. Is it safe? What key points I should check?
Also, would I still need to have Android Studio JUST to publish an app to Google Play Store? Or the URL below would give me the opportunity to publish my app using website?
https://play.google.com/apps/publish
Please help!
Thank you!
Check the Google Play Store Developer Policy Center to see if it infringes any rules.
https://play.google.com/about/developer-content-policy
I would also consider asking to review the source code as well if your name or company is going to be associated with the product you publish.
So basically uploading an app that copyrights most of someone's legit coding and possibly licensing? Not a good approach.
If you are aware about the terms and conditions, you would be liable for cost and damages because technically it will be under your name if you go forward and if your profiting this commercially, that case would be serious should it be brought forward on complaint.
EDITED
If you doing this on his behalf, he should sign up for Developer account or allow you to put his information in. So that's the safe point. If you are saying it is his app.
We have a production app using the Instagram API - currently with only the basic permission scope approved. A couple of months down the line, we are now adding further functionality which requires the public_content permission. During development, I have used a new Sandbox Client ID, but now I'd like to have the current Live app submitted to request the public_content permission so that I can make the new functionality available to it. The Sandbox mode documentation states:
If you need access to more permissions, you can submit for review again and you will not lose access to the permissions that you have already been granted.
My question is: How can I submit a request for more permissions from Instagram when the Client is already out of Sandbox Mode?
The fact that it is already out of Sandbox Mode (with basic permissions), means that I cannot demonstrate the new functionality - after all, already being Live means I cannot authorise public_content from users. Instagram state We only review final and production version apps. Submissions with test and development version apps will not be approved. I don't see how this can be achieved?
I'm assuming that in this scenario, Instagram either does not expect you to have the functionality live (and perhaps a description/video will suffice for the extra permissions). Either that or they expect you to submit a new Sandbox app which demonstrates the functionality - but then this clearly won't be a production app. I'm clearly missing something, and the lack of documentation on this from Instagram isn't helping.
Would appreciate the help!
Just use the same process you used before. Click the "Manage" button for your client then, click "Start Submission" button under the "Permissions" tab. You'll need a new video demoing the permissions you want. This means, you need to set up the Sandbox so you actually can demo your use case for the permissions you want (fun stuff! lol).
Protip: Save your submission to a Word document so you can amend it. I made the mistake of not saving my original submission so when I went back, I had to work hard to make sure my language was in compliance with the use cases and stuff.
It's pretty simple to do what you want to do since you've already gotten through the approval process once - getting the sandbox set up can be tricky unless you have friend who will accept your sandbox invites (feel free to invite me #mikeghen, I'll accept).
If you're getting rejected, reread the use case you're applying for, make sure you actually can get the permissions you want using that use case, and then reread your document with the submission you submitted, you probably aren't being clear (Protip: don't say too much, be concise and let the video do the talking). I kind of feel silly for asking a similar question: Adding Features to Approve Instagram Client
Again, setting up a new Sandbox is probably where your struggling.
Protip: I suggest making another client (so you have a dev and production client) and then get the permissions you need using the dev client. Once you get the permissions you need, dev becomes production and production becomes dev.
Thank you for highlighting that line in the Sandbox docs, I didn't see that before. But I think that answers my question.
I understand this isn't a typically appropriate question for Stack Exchange but the Nest customer service has basically no information whatsoever on developer support, and the Works with Nest support contact form recommends using Stack Exchange tagged with nest-api. Anyway, I have created an application in the developer portal I need to submit for a user limit increase, and I have been unable to submit the form for the last 3 days. I receive a generic error that says:
We're sorry. Something went wrong. Please try again later. The backend responded with an error
As I said, I contacted every customer support outlet Nest offers and have yet to get any assistance. If anyone has encountered this error or has the proper avenue to reach out to Nest's developer support team, please let me know. Thank you in advance, again I apologize for the narrow scope of this question.
If anyone else runs into this issue, my final resolution was to re-create a second application on a different developer account, and then migrate my web service to use the new application's client secret, API tokens etc.. Albeit a huge hassle, the submission (using the exact same form data as before) worked on the new application.
I have been working with a Visual Studio project by myself for a while. and now we have a new coder with me. We are not sure yet how trustworty he is. so we need to block him to run or read the project source codes if he copied and take it to home or anywhere else except our environment with TFS. How could I do it, is it possible. Regards
EDIT: let me clear some points: I want a source code only available in office environment, in TFS, so developers can do anything with it but when they take it to the home, the solution wont run and display codes)
I am asking if this is possible. or is there any similar approach that I am unaware
There is no way to do this through TFS. You woul dneed to look at creating a secured desktop/remote session.
Even if you put him on a desktop that can't be taken home, you will have to disable USB ports etc. etc. so that he can't copy it over to his.her own device.
This isn't supported in TFS and I doubt it ever will. If you are worried about this then you need a tighter interview process. Have them sign non-disclosure agreements and such. Perhaps this is a case of paranoia, however there may be a slight alternative:
Get yourself a public/private key pair from a CA and sign your assemblies with the private key (which is known only to the 'trustworthy' developers or even just 1 of 2 senior members), have your builds compile using this private key (lock down your build server) and publish only these assemblies. Make your customers aware of this and give them your public key.
It will prevent people from stealing and publishing your source code under your name but it's a tremendous effort (and it won't stop them from outright theft and publishing as a competitor). If you are interested start looking up asymmetric encryption with assembly signing.