Bots United start a Sourceforge project?

[sPlOrYgOn]

Maybe bots united should get a source forge project and host all the open source bots..
they have a free cvs so you guys won't lose track of your changes..
Anyone else think bots united should start a sourceforge project?

[Pierre-Marie Baty]

I don't know... we have all the abilities needed to set up and maintain a CVS ourselves... and we'll soon need more than a CVS, if the United Bot project leaves the ground one day.

I reckon this is a good idea, but given the choice between CVS at SourceForge and CVS here, I'd prever CVS here

[Terran]

One advantage of using sourceforge would be a more reliable hosting with better worldwide internet links.

@memed:
Is there some kind of backup system in place for this server?

[@$3.1415rin]

I would prefer sourceforge, since we do not need to setup a cvs, we have nice hosting / mirrors for all files, a bugtracking system, task manager.

the only problem on sourceforge is the updating of download counters and counting cvs commits, but that's not a disadvantage at all I think. I'm pretty content with old joebot on sourceforge.

[Onno Kreuzinger]

ok, the backup here is n.p., Nova has ordered a 2nd hdd, and up to 2 GB of important data can be shadowed at my "spare" disk, which is raid1+5.

the uplink on this server is much better than a shared account at SF.net, no doubt about that.

from other developers i heard they where leaving SF.net to go to berlios.de, which runs the same software as SF, but with less restrictions, more speed and some advanced features, so sf.net is IMHO no option, it's either to go with this server or berlios.de.

the bugtracking is no question of software but of work, it soley depends on the will of the developers to spend time on bugzilla. there are other systems (e.g. mantis or QA director) but they do not lower the amount of time needed much.(atleast in my last company bugtracking broke down as the bug-hunter left the company)

so for bug tracking we should think about alternative organisation, if, and only if, all agree, some sort of open system like a wiki might be good. e.g. bugs _must_ be filed with a testcase so that even a non insider can find the bug, by using the code and replaying the testcase. this way a speedy development could be encouraged. i have that for some gpl vdr-plugin i maintain, we have had 3 main developer changes this year, always speeding up the development, i.e. i have to make a pre release every week)

just my 2cents

[Cpl. Shrike]

I tend to agree with memed.

Keep things in own house.
Gives the oportunity change what ever needed or desired.
Ofcoars source forge does a great job.
But doing it in house gives more "feeling" and "bonding" to the project.
Makes ppl more at home as the "cold looking" sourceforge environment.

[Terran]

@memed:
At least for some time I could provide some remote backup at one of my servers.

[Pierre-Marie Baty]

I agree with memed and Cpl. Shrike. Things look always better and more appealing, and people are more involved when the work and the means of the work are home-made and not relying on any external support.

[Onno Kreuzinger]

oh, well i should clarify, that using the kind service from berlios.de would be a "good way (tm)", for me it's just that SF is too big, too many non-uptodate mirrors and quite some hassle. the features at berlios would save some work, on the other hand making it on our own could tie people more to the project.

cheers

[botmeister]

About the only people who will contribute to a bot related open source project will already know about Bots United, so I don't expect much disadvantage on holding the source in house. I can see advantages however as was expressed by others above, so I agree with the option of "in house" open source development if that's the right term for it

*edit* copied related post from mEAn forum to here

I'd like to see BU build up a number of "in house" (but open to the public) bot related projects.

There's a ton of code that PMB has behind him that could go into a repository here (if he chooses of course).

There's the mEAn mod comming soon.

There's the old JoeBot code at sourceforge - would it do better if located here?

There's the POD bot 2.6 fix up project.

etc etc

We have a good number of very nice projects for a open source repository already!