Apache has a number of CI options available... For details, see: http://ci.apache.org/
I'd suggest Hudson. Regarding Mono support, I think providing a MonoDevelop compatible solution file, and testing builds in at least one standard Linux environment will be necessary. I'd suggest Ubuntu 10.4 or 10.10. Regarding NuGet for dependencies.. I'd say we should not do that at this time. Primarily because, AFAIK, NuGet is an add-on for Visual Studio which can only be used in a paid-for version of 2010. You can't use it with the Express versions. You can't use it in MonoDevelop. So, we'd be raising the barrier of entry to only those who have a licensed version of Visual Studio 2010. I think including .hgignore and/or .gitignore files are a smart move. Thanks, Troy On Wed, Jan 26, 2011 at 10:18 AM, Michael Herndon <mhern...@o19s.com> wrote: > That and the following probably needs to be branched into a new mail thread > and discussed. > > A couple of other topics or questions that might go along with that might > be: > > Another topic to cover is if there an actual CI (continuous integration) > Server setup? Do we wish to have one set up if there isn't one? If so, how > will that affect project structure, and what kind of setup would work well. > > > Should the project include build scripts for powershell, nant, albacore > scripts? (would this further entice developers to download the code and > build it)? These also could be available as a separate download. > > What would be the preferred way of working with the code base in mono ? > Should we ensure the project loads and compiles in mono develop, etc. > > would it be beneficial to add a .gitignore file for those avid git-svn > users? > > should we start looking at nuget for external dependencies? > > aside from documentation, how can we make the barrier to entry lower for > people? > > etc. etc. > > > > > On Wed, Jan 26, 2011 at 12:52 PM, Wyatt Barnett > <wyatt.barn...@gmail.com>wrote: > >> I'd be happy to continue my work with the Visual Studio versioning, >> building and dependency management bits (cf >> https://issues.apache.org/jira/browse/LUCENENET-377) ; I just need >> some direction from the committers as to what I should target and what >> the operational goals are. >> >> On Wed, Jan 26, 2011 at 12:36 PM, Michael Herndon <mhern...@o19s.com> >> wrote: >> > supposedly the wiki used to be:http://wiki.apache.org/lucene.net/ according >> > to http://incubator.apache.org/projects/lucene.net.html but thats >> currently >> > not resolving. >> > >> >
