SLF4S moving to SLF4J

Ceki, I just made the first step in moving SLF4S to SLF4J: In my fork of the SLF4J repo I added the slf4j-scala-api module and contributed all SLF4S code (except for one stupid implicit conversion). The OSGi stuff is still missing, but that's not too much. How are we going to proceed? I think as the author of the Scala stuff I should be given "write access" to the SLF4J repo, because the Scala stuff must be maintained and developed further. Ceki, you already received the signed contributor agreement. What do you think? Heiko Company: weiglewilczek.com Blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net Akka - Simpler Scalability, Fault-Tolerance, Concurrency & Remoting through Actors: akkasource.org

On 14/09/2010 9:51 PM, Heiko Seeberger wrote:
Ceki,
I just made the first step in moving SLF4S to SLF4J: In my fork of the SLF4J repo I added the slf4j-scala-api module and contributed all SLF4S code (except for one stupid implicit conversion). The OSGi stuff is still missing, but that's not too much.
I just pulled from your repo and committed back to mine.
How are we going to proceed? I think as the author of the Scala stuff I should be given "write access" to the SLF4J repo, because the Scala stuff must be maintained and developed further. Ceki, you already received the signed contributor agreement. What do you think?
I think the distributed model allowed by git works nicely. It was quite easy to pull in your contributions from your repo into mine and vice versa. How about we go on with the set up and change if it proves to be unsatisfactory?
Heiko
-- Ceki

On 14/09/2010 10:25 PM, Ceki Gülcü wrote:
I think the distributed model allowed by git works nicely. It was quite easy to pull in your contributions from your repo into mine and vice versa. How about we go on with the set up and change if it proves to be unsatisfactory?
s/the set up/the current set up/

K On 14 September 2010 22:25, Ceki Gülcü <ceki@qos.ch> wrote:
On 14/09/2010 9:51 PM, Heiko Seeberger wrote:
Ceki,
I just made the first step in moving SLF4S to SLF4J: In my fork of the SLF4J repo I added the slf4j-scala-api module and contributed all SLF4S code (except for one stupid implicit conversion). The OSGi stuff is still missing, but that's not too much.
I just pulled from your repo and committed back to mine.
How are we going to proceed? I think as the author of the Scala stuff I
should be given "write access" to the SLF4J repo, because the Scala stuff must be maintained and developed further. Ceki, you already received the signed contributor agreement. What do you think?
I think the distributed model allowed by git works nicely. It was quite easy to pull in your contributions from your repo into mine and vice versa. How about we go on with the set up and change if it proves to be unsatisfactory?
Heiko
-- Ceki _______________________________________________ slf4j-dev mailing list slf4j-dev@qos.ch http://qos.ch/mailman/listinfo/slf4j-dev
-- Heiko Seeberger Company: weiglewilczek.com Blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net Akka - Simpler Scalability, Fault-Tolerance, Concurrency & Remoting through Actors: akkasource.org
participants (2)
-
Ceki Gülcü
-
Heiko Seeberger