1>  I see most of us are already putting prefixes on our Mod files. Let's continue that trend. 

2>  I also put prefixes on the internal names of my mods to make sure there is no conflict with Core or other mods. Some of you are already doing that as well.

3> Most of our mods will have dependencies with other mods.  For example, new items might have new tech items required for them.  There needs to be a way to show dependencies between separate files.  For example, Gnilbert has lots of cool stuff, but some of his stuff I don't want to use because either it is too close to something I'm already doing or would conflict with mine.  It would be nice to be able to easily spot dependencies.  (i.e. I want his focus staffs, but what other files do I need for them to work?)  Should we perhaps use a suffix on the file names?  Group together all items with dependencies in the same files?  Or just put comments in the files?  I'm open to suggestions.  I suspect that none of these solutions will always be the best.  It might need to be on a individual basis as to which is best.

4> I know in some cases we like stuff broken out into individual files.  In other cases, where lots of files are involved, it might be better to combine more.  Especially when we're building huge mods  or pulling lots of individual mods.  Might be a good idea to keep this in mind as we go forward.

I'm sure others will thing of some things I haven't so pipe in.