Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I've been told that I should include PAD files with the freeware applications I distribute so hosting sites can list the information correctly and check for updates, etc.
Can you give me some info on using PAD files? Here are general questions which come to mind:
Is it worth the effort?
Do you use PADGen or an online tool like www.padbuilder.com?
Do you digitally sign yours?
I do use padgen, it does not take too long to make a pad file, but what takes time is submitting it... just copy+paste stuff from your marketing material into it.
keep storing all your pad files on your webserver and new version updates are listed in 1000+ small shareware/software sites automatically. however, download amounts from these sites are usually < 1000/mo.
not signed mine.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 months ago.
Improve this question
What are the open standard principles ?
I googled it but I am getting different answer from different website cant decide what to write
It's a pretty confusing concept because it is NOT the same as open source.
Open source means you can get the CODE and use it in whatever way you need (make your own changes etc).
Open standard means you can get the PROGRAM / TECHNOLOGY for free. To put it very roughly, open standard is that you can get a complied ".exe" executable (but no source code), and install the software at no cost, and open source means you can have the code, make your own changes, and then make your own ".exe" if you want.
HTML and XML are open standard technologies.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I'm building an application with the instant messaging functionality.
The application will allow the users to send files/images as well as normal text messages.
I decided to take the approach with storing the files on the filesystem and write only the file paths to the database. There will be no updates to the files (only insertions and deletions).
Which database would be the best for storing a large amount of file paths, that would be easy to query for a certain user files?
I would go with MongoDB. My experience is that a document based approach using a single Messages collection would be best. Each message document then contains all of the file paths. This eliminates joins and better supports potential future functional requirements changes.
MongoDB also provides great ways to deal with old messages such as TTL indexes.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am involved in a project which is meant to eventually become open-source and have a code contributor community. Is there any "right" way of doing this and what should/can I expect?
Thanks
There's a pretty good book on this topic, Producing Open Source Software by Karl Fogel, which is available for free online or in dead tree form if you prefer to read it that way. It would be hard to expand much on it in a single answer. Every project will, of course, be different, so I'd recommend reading that book, and then asking more specific questions about your particular project; answers will depend on the language and platform you use, how active an open source community there already is in your area, what your business model is, and many other factors.
I would recommand using Github or Google Project Hosting (subversion/mercurial), and of course use social media network to promote the project helps too.
You can start something like this - http://wxwidgets.org/develop/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I run a small startup and have developed some web applications. We use open source technologies heavily and I want to give proper attribution to everything that we use.
The only thing I am concern about is it safe to expose everything? Such as webserver, development language and framework etc. Are there any pitfalls of doing so?
e.g. One particular concern is if some vulnerability be discovered in framework, application can be easy target until gets a patch.
The more one knows the more one can leverage. Said that, it shouldn't be to much of a problem if you build your web application with security in mind.
Shouldn't be an issue - many companies make public the fact that they use particular open source solutions.
The main pitfalls are the obvious security related ones: have you changed all the default admin passwords etc.?
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am developing a database that organizes scientific data from my group and diverse experiments reported in the literature, (my background is in science rather than project management or programming).
I currently have three documentation documents for:
end users of data
data enter-ers
developers (e.g. myself and my successor)
Other than following the users guides and descriptions from other databases, are there any best-practices I should follow, perhaps a latex template, or a mysqldump option that will automatically do some of the documentation?
Doxygen supports SQL. I would export the DDL SQL statements, document them with Doxygen notation and export it to HTML / PDF / whatever.
I wish there were a standard solution, but industry practice is ad hoc at best.
In MySQL, be sure to fill in the comment fields when creating tables and fields. If you use MySQL administrator, it makes it easy to manage, but that's most useful for developers to directly use. It can be used as the basis for expansion for the other categories of readers.