Continuing/beginning

[Pete Letkeman]

Lets do a recap:

The general idea or two for a project has been settled upon as noted https://coderanch.com/t/696583/open-source/Project-ideas.

We looked a little at the legal end of things as seen here https://coderanch.com/t/696597/open-source/Legal-stuff.

Most likely GitHub will be used to host the code.

I suspect that unit testing will be part of this project.
To that end I recently came across free online CI systems which could be used see https://coderanch.com/t/697983/build-tools/free-online-continuous-integration-services.
Some free online CI services can connect to GitHub (and other systems).

I know that both Eclipse and IntelliJ support EditorConfig (https://editorconfig.org/).
I suggest that this be used so that anyone/everyone see code the same way.
I know that there are a few style variations for Java code including but not limited to:

https://javaranch.com/style.jsp

https://google.github.io/styleguide/javaguide.html

https://docs.oracle.com/javase/specs/ (hidden somewhere throughout the specs)

http://cr.openjdk.java.net/~alundblad/styleguide/index-v6.html

What do you suggest the next step(s) are/should be?

[Adrian Grabowski]

Pete Letkeman wrote:
What do you suggest the next step(s) are/should be?

Maybe a list of people who want to get involved in the project, their experience (or programming skills) and most importantly - number of hours per week they can spend on the project? Just a thought

[Stephan van Hulst]

Yes, establishing commitment is a good idea, and I think we need to make a final decision on a project we want to do.

After that, I think we need to start a thread on the business rules of the application. It's important for all the members of the project to have a good idea what we're working on, and that starts with a good problem description, or in the case of a game, the game rules.

We also need to discuss how we will deal with new members joining half-way through the project, because I imagine that it will be easier for people to want to hop on board once the project has gotten some traction.

[Adrian Grabowski]

Looking forward to hear more, in the meantime I started my own little project, it's a MUD (multi-user dungeon) where players can explore caves and mine tunnels (and possibly fight some monsters), it's a console based game, real time and multi-player. My knowledge of Java is limited so I have to do a lot of googling but it's moving forward, my code probably looks terrible and has a lot of bugs but I don't worry about this for now - debugging and refactoring is going to be fun on its own

[Islam Moheb]

Is there any news regarding the project ?

[Pete Letkeman]

I'll see if I can make a Wiki regarding this project by Monday Sept 10, 2018. If I do this correctly then any member could modify it.
The wiki would have the basic project goal and/or idea, as I see it at the moment but this may not be 100% correct.
I will also try to define a few basic concepts, but this may not be 100% correct either.

As far as signing up, I don't think that we need any sort of list.
We can probably stay clear of most of the big database systems and use something like SQLite and/or text files at least at first.

What version(s) of Java should be targeted?
Is this only for Java developers (I like to use Kotlin and Python as well)?

I suggest that Github be used, free for opensource projects.
Github supports automatic license creation given a few different templates and the license can always change later on.
I could easily create a email address (which could go to many different people) and attach a GitHub account to it.

We can figure out who and how code can be contributed in the next few weeks, I hope.
There is much to think about regarding how to handle this.

We will need some sort of business rules and/or game rules.
If we are doing a game then we may want some sort of story. Creative writing anyone?

First steps for anyone wanting to work on this would include:

Setup JDK in your system's PATH.

Compile the "Hello World" Java program using on the command line interface and an editor like Notepad or Notepad Plus Plus.

Compile a "Hello World" Java program which has two different classes which do not exists in the default package name space.

Create a GitHub account, free all you need is an email address.

Get an IDE e.g. Eclipse, IntelliJ and get that connected to your GitHub account so that you can publish code to it.

[Adrian Grabowski]

Pete Letkeman wrote:
What version(s) of Java should be targeted?
Is this only for Java developers (I like to use Kotlin and Python as well)?

I would vote for Java 8 as most of us are probably the most familiar with it

GitHub is a good idea I think as again, it's the most popular tool, we could set up Gitter channel  (unless people prefer Slack) for our project to make communication easier, what do you think?