project-management

I have a buildbot with some builders and two slave machines. Some of the builders can run on one slave, and some of them can run on both machines. What algorithm will buildbot use to schedule the builds? Will it notice that some builders can run on just one slave and that it should assign those that can run on both slaves to the less demanded one? (I know buildbot can be used to run the same build on multiple architectures, say Windows, Linux, etc. We are using it to distribute builds for performance, because a single build is enough for us). First it gets a list of all the slaves attached to

I have several projects that build reusable libraries. All these projects are under source control. When I use these libraries in a project I simply link to the same ONE version on my local drive. However as you can imagine, this can cause problems when I commit back, and a different developer tries to clone the repository. What is the best practice when using components also under source control? Should I include the "library projects" in the "main project" source control? Will this cause problems? NB: The libraries take quite a few compiler directives so its almost impossible to just compile

We're starting a new project in Python with a few proprietary algorithms and sensitive bits of logic that we'd like to keep private. We also will have a few outsiders (select members of the public) working on the code. We cannot grant the outsiders access to the small, private bits of code, but we'd like a public version to work well enough for them. Say that our project, Foo, has a module, bar , with one function, get_sauce() . What really happens in get_sauce() is secret, but we want a public version of get_sauce() to return an acceptable, albeit incorrect, result. We also run our own

I would like a "system" that monitors a process and would kill said process if: the process exceeds some memory requirements the process does not respond to a message from the "system" in some period of time I assume this "system" could be something as simple as a monitoring process? A code example of how this could be done would be useful. I am of course not averse to a completely different solution to this problem. For the first requirement, you might want to look into either using ulimit , or tweaking the kernel OOM-killer settings on your system. Monitoring daemons exist for this sort of

does anyone know of a Visual Studio (2008) Plug-in that attempts to track how long you've spent working on any given Solution or Project? I realize this would be difficult, like at work I might leave a Solution open all day, but only work on it for a couple of hours, on and off. However at home, I might only open a Solution when I'm working on it. Regardless, is there anything out there that at least attempts to track time spent? Do some/any Source Control reports achieve this? This would be a resource for me to get a rough idea of how long I've spent on a bunch of projects. cheers I don't

I am working on a userscript for Firefox, so I use GreaseMonkey . Moreover, to facilitate the development, I use git to update the different versions of my code. Now, let me try to explain the issue. When I add to GreaseMonkey the userscript from my local git directory, then new files are created in the gm_scripts folder of my Firefox profile. GreaseMonkey use these files as source and not my git directory, so if I want to modify my code and test some stuff, I have to change the files inside the gm_scripts. This means that I can not commit the modification, I first have to copy the files from

I have read on Stack Overflow some people that have converting to C#2.0 to C#3, but is it really worth it? I have a project that is done at 75% before going in maintenance phase. I am asking to myself if it is worth it to switch to C#3.0? Update: The project will have a web interface now so before entering the maintenance phase we have to develop the web part (all was done for internal purposes with Windows Forms). Most parts will be resused (back-end). Most people have said that it wasn't worth it in the past because it was already at 75%... but now do you still think it's not worth it? What

I'm looking for any tools that can give you code churn metrics (graphs and charts would be even better) for a Subversion repository. One tool I know of is statsvn - a Java tool that creates some HTML reports and some code churn metrics. Statsvn reports the number of lines modified (churned) by user over time, some descriptive stats on LOC per file and folder/subfolder, etc. I would like to know code churn in order to get a better idea of the state of the project. Idea behind this inspired by the MS research: Use of Relative Code Churn Measures to Predict System Defect Density In a nutshell,

What would be the general structure of a App/Project based in C Programming language. libs, includes, header files. etc etc. What would be the class structure. (in OOps) need to be scalable and other features. Something like main.cpp main.h does any one have any good links or images or pdf? Most of the projects follow a single hierarchy as follows: project \_ conf\ --> configuration files (Unix/Linux projects might prefer an 'etc' folder) \_ src\ --> main source (for C++ projects, headers and sources go along, but if your project is a library then separating include files for others is a

Perhaps the most obvious way of protecting a company's intellectual property from its own developers seems to be an NDA - Non Disclosure Agreement. Effectiveness of this approach may vary, depending on many factors, and sometimes or somewhere it may not work as expected. What other approaches, apart from this purely legal one, exist for protecting software code from the people who develop it? Do they exist at all? Does it make sense in practice? Maybe, for example, Team Edition of Visual Studio already contains some features related to this problem (for example, levels of access to parts of