> By my count, I think 6 including you? There is no current team > structure, build master, etc that I know of. There is Trac, at the > group's site at http://sharpos.sf.net , with some tickets and some
I've had experience running large open source projects for over 10 years. Some projects ran over 100 developers at times. Indy is probably the largest. You can check it out in Wikipedia, or just search for it. Its probably the most widely used socket library in existence, as well as the most comprehensive. Its Delphi based, but many companies actually use Delphi just for that specific purpose to get access to Indy. Its used by many of the government agencies of the world, the UN, ECB, Nasa, and the list goes on. Borland also integrated it directly into Delphi 5+ years ago and ditched their own socket libraries in favor of Indy. They even began to use it for Delphi itself and rewrote Delphi's web services to be based on it. You can Google it to verify my claims. My point is - that we should not run this project exactly the same. But I have a lot of insight into this and I suggest that its something we should think about before the project gets too big. Conflict resolution, team structure, procedures etc. it doesn't have to be super formal, but something as a base MUST be in place for a project to succeed. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
