Forked or not forked?

[nscala-time]

Forked or not forked?

[kmizu]

Hi, @skestle . I'm sorry to late reply.

It seems sad that this was a fork from scala-time but did not actually fork it (and then rename/move files).

Although I don't think that the decision was not so good, not using github's fork button is my intention. I wanted to avoid confusing since nscala-time is not just fork but separated project from scala-time. And If I didn't rename the project, I cannot publish nscala-time separately to maven central.

It seems that scala-time is active and it would be good to see the differences between the projects in a network graph.

Since when I forked from nscala-time, it seems that scala-time was not inactive actually for a long time, I forked from scala-time and started a new project nscala-time.

It would be really cool if:

1. the original copied scala-time revision was pulled into this repository
2. renamed (as in the second commiit)
3. merge the second commit into the new branch, and then merge the current head
   into the forked branch head.

Certainly, it would be really really cool if it was what you said.

It'd just be nice to see the differences easily - perhaps nscala-time could commit back -
scala-time seems to have a larger community (certainly a larger committer/fork base)

scala-time seems to have a little larger community. But I think the difference is not so big (cf. The number of Watch/Star/Fork). And I fear (slow update / stopping update) of scala-time. Then, (I / We) continue to maintain nscala-time separately.

For example, in spite of nscala-time being published against Scala 2.11 already, scala-time is not published against Scala 2.11. And its crossScalaVersion is still 2.10.2!: See https://github.com/jorgeortiz85/scala-time/blob/master/build.sbt#L9