Ask HN: What open source mailing list software do you use?
What do you use/recommend?
What do you use/recommend?
* Why did you decide to have a mobile app built?
* Where did you look for someone to build it?
* What made you choose a particular developer?
* What challenges did you encounter?
Any information you choose to share is helpful and appreciated!
How did you frame the argument that convinced the non-technical decision makers that technical debt should be taken care of? Was the metaphor of "technical debt" a good way to frame the argument, or was the notion too ethereal?
I find this to be very time consuming however I am reticent to have a subcontractor do this as I'm nervous about giving root access, if even for a short while.
Is there a reasonable way to delegate this such that I don't have to worry about nefarious activity? Or a way that I can detect that someone has been doing something they shouldn't?
Should I be requesting full rights and then agree to license it back to them to display in their portfolio?
I guess I'm not really seeing what is protecting me wrt my logo.
What have others done to protect their rights wrt to their logo?
Here are some thoughts I had:
1) A paid version and a free version in the market, where the free version only works in conjunction if the user has the windows app, using some sort of custom licensing code.
2) In case option 1 isn't allowed. A free app that has the abilities to install other apps (uses the PackageManager and has android.permission.INSTALL_PACKAGES set) in the GPM. This would download the free version and prompt the user to install it if they had the license, otherwise send them to the GPM app for the paid version. I'm thinking when they register the windows app, it sends a link in email to this installer app.
I'm not sure Google Play Market policies allows this. Does anyone have experience with anything like this?
What is a good way I can backup, keep personal revisions and share across all 4 systems? The thing that makes it tricky is some clients have their own git or subversion repositories.
Here are my thoughts:
On my main system, have two mostly mirror directory trees: one just containing source pulled from client repositories, and another that is my "working" source tree which contains everything including copies of client files (but excludes their source control system files.) The working tree would be checked into a local git repository.
So for the various tasks I need to do:
Update from client repositories:
After updating from client repositories into the client tree, I would merge all source files (no svn or git files) to the complimentary location in the working tree, then checkin any changes to my local git repository.
Committing to client repositories:
Merge source from the working tree (no svn or git files) to the client tree, then commit.
Sharing between other system:
The other systems would just update and commit to git on my main system.
Backups:
Backup the git repository, the client "tree" and the "working" tree to an external drive.
Any problems with this? Is there a better way to do it?
Thanks
Does anyone know of any good solutions (or apps) that can help with this?
How do you manage contacts, track where they are in the sales cycle, and gather statistics for later feedback and analysis?
Is there a particular methodology or software that is used?
Thanks, Curtis