They should provide access as long as one might reasonably need it which is at least as long as the statute of limitations give one to take legal action.
1. Get formal approval for the project, stating which license(s) will be used for the code, libraries and documentation.
2. Establish your governance including project management framework etc (same as closed source, except all tools will need to be accessible to anyone involved in the project). Find a lawyer who understand FOSS licensing and ensure he/she reviews the contracts you will be using.
3. Define your requirements. Make the high level design as modular as possible. Decide on the development environment.
4. Search for similar projects to see if you can leverage them or entice the developers to work on your project.
5. Setup a project environment - either on your infrastructure or somewhere like sourceforge. As a minimum this needs a code repository, wiki for documentation, mailing lists and a bug/ feature request tracking application.
6. Ensure that you know who wrote every line of code and that you have the right to include it in your application. Where code is reused you need to ensure that the license is compatible and appropriate attribution is retained. (You do this with closed source applications anyway, don't you!).
There are two models for paying the programmers - by the hour (which means you may want them working in your office at least part of the time) and by delivery of an agreed output with suitable quality. For the former, simply follow your normal recruitment practices for a contractor but advertise through your local Linux or other FOSS groups as well as the normal channels. If you are paying by the completed module you can either follow the normal quotation process or simply offer bounties of a set amount for a module. Bounties are likely to appeal to a different group of programmers including folk in developing countries and are a low risk way of tapping this resource.
You will also need to decide whether to run the entire project openly or just open source it when you release version 1.0 - I recommend you start publishing code as soon as you can since that will maximise the benefits of open source flowing to your project.
Since you want to code on a free operating system and your professors are still tied to One Microsoft Way, why not pick a project which runs in both environments?
There are lots of cross platform development environments - anything from a plugin for Firefox to applications that run in mono and.Net!
That way you can develop under your OS of choice and your professors might learn something from you...
If there is only one effective supplier, this is an ideal opportunity for FLOSS to innovate.
The lack of good speech recognition applications on Linux and the BSDs is a major barrier to corporate and government organisations switching to FLOSS. Frequently the main users of speech recognition use it for occupational health and safety reasons. Failing to provide the software the OH&S specialist recommended may be enough to scuttle a migration project.
>> There is absolutely no need to encrypt the main hard drive. >> What? You afraid of someone stealing C:\WINNT?
Unfortunately many windows applications including IE and Office write loads of stuff to C drive including temp files and of course that is where the swap file is by default.
Many other badly written windows apps store data in their program files directories.
Therefore encrypting everything is the safest option.
So, how long is it before we start seeing hardware-based registration schemes? It might be expensive for a company like Adobe to have the keys made, but volume pricing and the amount of money they'd save versus privacy might be worth it. Microsoft certainly has the weight (and the volume) to get them made cheaply enough for it to benefit.
Microsoft already use hardware based schemes: X-Boxen.
The next hardware based scheme will be Palladium or whatever they call it this week, dressed up as the only way to combat spyware and trojans.
During your lectures use a number of environments, starting with a text editor (no syntax checking etc). By the end of the course the students should know that there is more than one way to write code and some of the pros and cons of each.
For most of the lab exercises use an IDE, but provide emacs if they want to use it.
The programmers probably implemented a spec (this sin't Microsoft) and will no doubt fix the issue as soon as they are told about it (i.e. now it is on slashdot they will spent the weekend doing that).
In this case it is th lawer who is clearly the major problem.
A realistic comparison is the organisation's inevitable migration to Vista with one to linux. Many of the costs are the same (e.g. training users to use a substantially different interface) and hardware costs will probably favour linux.
Getting up and wandering over to the TV to turn on/ off is exercise - something we need more of!
If forced I am sure manufacturers could easily change things so standby mode relied on a battery and non-volatile memory. The only issue would be with those 'legacy' CRTs (vacuum tube filaments need to stay warm) and stupid systems such as my TV set top box which reloads its operating system via the cable network whenever it is powered up.
If it will take while to move to the 6 monly release cycle they could move to a minor release every 6 months (primarily bug fixes and incremental improvements) plus a less frequent major change release ever 12 months.
Slashdot Mirror
Download caps are the norm for many ISPs in Australia.
Just move to Australia and let Senator Conroy do it for you as he tries to go one better than the Great Internet Wall of China!
Just wait - the other states and the Feds will all move to harmonise their laws with NSW.
They should provide access as long as one might reasonably need it which is at least as long as the statute of limitations give one to take legal action.
1. Get formal approval for the project, stating which license(s) will be used for the code, libraries and documentation.
2. Establish your governance including project management framework etc (same as closed source, except all tools will need to be accessible to anyone involved in the project). Find a lawyer who understand FOSS licensing and ensure he/she reviews the contracts you will be using.
3. Define your requirements. Make the high level design as modular as possible. Decide on the development environment.
4. Search for similar projects to see if you can leverage them or entice the developers to work on your project.
5. Setup a project environment - either on your infrastructure or somewhere like sourceforge. As a minimum this needs a code repository, wiki for documentation, mailing lists and a bug/ feature request tracking application.
6. Ensure that you know who wrote every line of code and that you have the right to include it in your application. Where code is reused you need to ensure that the license is compatible and appropriate attribution is retained. (You do this with closed source applications anyway, don't you!).
There are two models for paying the programmers - by the hour (which means you may want them working in your office at least part of the time) and by delivery of an agreed output with suitable quality. For the former, simply follow your normal recruitment practices for a contractor but advertise through your local Linux or other FOSS groups as well as the normal channels. If you are paying by the completed module you can either follow the normal quotation process or simply offer bounties of a set amount for a module. Bounties are likely to appeal to a different group of programmers including folk in developing countries and are a low risk way of tapping this resource.
You will also need to decide whether to run the entire project openly or just open source it when you release version 1.0 - I recommend you start publishing code as soon as you can since that will maximise the benefits of open source flowing to your project.
Good luck.
Just do what they want. First step in the process is to search for prior art - I am sure you will find some for any software development project!
Since you want to code on a free operating system and your professors are still tied to One Microsoft Way, why not pick a project which runs in both environments?
.Net!
There are lots of cross platform development environments - anything from a plugin for Firefox to applications that run in mono and
That way you can develop under your OS of choice and your professors might learn something from you...
If there is only one effective supplier, this is an ideal opportunity for FLOSS to innovate.
The lack of good speech recognition applications on Linux and the BSDs is a major barrier to corporate and government organisations switching to FLOSS. Frequently the main users of speech recognition use it for occupational health and safety reasons. Failing to provide the software the OH&S specialist recommended may be enough to scuttle a migration project.
Use a proven firewall such as OpenBSD which can both act as a firewall and provide NAT dhcp etc for the LAN.
Unlike windows OenBSD has suffered "Only one remote hole in the default install, in more than 10 years!".
Oh and version 4.0 is due out tomorrow - see http://openbsd.org/40.html
The Dapper release was delayed for extra testing, while Edgy started late but shiiped according to the original every 6 months schedule.
I upgraded two systems from Hoary to Dapper without an issue, but the one I did a dist-upgrade to Edgy is broken.
As with most IT projects testing is critical!
>> There is absolutely no need to encrypt the main hard drive.
>> What? You afraid of someone stealing C:\WINNT?
Unfortunately many windows applications including IE and Office write loads of stuff to C drive including temp files and of course that is where the swap file is by default.
Many other badly written windows apps store data in their program files directories.
Therefore encrypting everything is the safest option.
The key advantage of the high res screen will be that it is easily read for hours on end. The text/ xhtml or pdf file for this won't take much space.
Why don't you include the cost of re-validating as a separate line item on the bill?
Microsoft already use hardware based schemes: X-Boxen.
The next hardware based scheme will be Palladium or whatever they call it this week, dressed up as the only way to combat spyware and trojans.
As long as they run for a whole day (16 hours plus) when running Ubuntu or FreeBSD they will be fine.
Yes, OpenBSD still has a few security patches each version, but thier methodology is far better than many other software developers.
During your lectures use a number of environments, starting with a text editor (no syntax checking etc). By the end of the course the students should know that there is more than one way to write code and some of the pros and cons of each.
For most of the lab exercises use an IDE, but provide emacs if they want to use it.
The programmers probably implemented a spec (this sin't Microsoft) and will no doubt fix the issue as soon as they are told about it (i.e. now it is on slashdot they will spent the weekend doing that). In this case it is th lawer who is clearly the major problem.
Surely the safest way would be to only support debugging via optional code compiled into the kernel.
A realistic comparison is the organisation's inevitable migration to Vista with one to linux. Many of the costs are the same (e.g. training users to use a substantially different interface) and hardware costs will probably favour linux.
IBM are apparently going to do a linux version of Notes. Sadly we just moved to Outlook...
Both IBM and Novell are busy converting their own desktops so they will have the expertise to do these types of migration.
Getting up and wandering over to the TV to turn on/ off is exercise - something we need more of!
If forced I am sure manufacturers could easily change things so standby mode relied on a battery and non-volatile memory. The only issue would be with those 'legacy' CRTs (vacuum tube filaments need to stay warm) and stupid systems such as my TV set top box which reloads its operating system via the cable network whenever it is powered up.
>> Will it run on my NetBSD toaster? No - only on G-BSD!
If it will take while to move to the 6 monly release cycle they could move to a minor release every 6 months (primarily bug fixes and incremental improvements) plus a less frequent major change release ever 12 months.