Private Repository

[rlguarino]

@zhuenink @rxl7906

Should we keep this repository as a private repo? If we want to keep the repo private I would need to create a new account to host the code and migrate it there, to freee up one of my private repo slots.

If we don't keep it private, we should choose a License, I doubt anyone will look at or use the code, but just in case.

[zhuenink]

Sure make it public, how about this license - http://choosealicense.com/licenses/mit/

[rlguarino]

I think this license is a good one. I'm not sure if @rxl7906 has seen it?

[rxl7906]

I also think the license is good.

So usually do people look for license samples online to put for their work?

Zack do you want to meet up today to work on this?

And Happy Birthday Ross, I hope that you don't have to work on this today

On Sat, Jul 5, 2014 at 9:05 AM, Ross Guarino notifications@github.com wrote:

I think this license is a good one. I'm not sure if @rxl7906 https://github.com/rxl7906 has seen it?

— Reply to this email directly or view it on GitHub https://github.com/rlguarino/lifeinvader/issues/31#issuecomment-48086032 .

Regards, Robin Li

Undergraduate 3rd Year Computer Science Major (Minor in Finance and Chinese) B. Thomas Golisano College of Computing and Information Sciences Rochester Institute of Technology, Rochester, New York

Email: rxl7906@rit.edu Phone: (646) 645 - 8885

[rlguarino]

@rxl7906 You can make up whatever license you want to but some of the most popular ones (MIT, BSD, Apache) are good enough. Personally I don’t like any of the copy-left (gnu) licenses.

Usually people just copy and paste one of those licenses into their project, and you usually don't need anything more than that.

[rlguarino]

Btw the project is already licensed under the apache license. If that is okay with everyone.

[zhuenink]

Yup, sounds good to me.