« Return to Thread: Introduction
Re: Re: Introduction
by Erik Engbrecht
::
Rate this Message:
I'm not a committer, but I think it works link any other project. Start offering up patches or contributions and Martin and company will decide if they want to accept them and eventually if you should be given commit rights. You probably should both post any contributions to track and send an email to the Scala Internals mailing list.
BTW - I actually think Scalax was/is a good idea, it just may have been too early. The core Scala community of contributors hasn't finished forming yet. There's still alot of core Scala code that I think is essentially unmaintained. It's a big codebase and it really needs a bigger set of maintainers.
--
http://erikengbrecht.blogspot.com/
BTW - I actually think Scalax was/is a good idea, it just may have been too early. The core Scala community of contributors hasn't finished forming yet. There's still alot of core Scala code that I think is essentially unmaintained. It's a big codebase and it really needs a bigger set of maintainers.
On Tue, May 5, 2009 at 10:48 AM, Nils Kilden-Pedersen <nilskp@...> wrote:
I think your last suggestion is fine for a stand-alone project, but less good for general library classes. That sort of stuff is better suited for either the Scala distro itself or a couple larger standalone projects. Otherwise it just gets lost in the forest.On Tue, May 5, 2009 at 9:39 AM, Erik Engbrecht <erik.engbrecht@...> wrote:The original idea behind scalax was that it would be kind of a proving ground for improvements to the Scala standard library, but the community never really developed. It was kind of a response to a constant stream of critisism of the Scala libraries and lots of ideas for enhancements.
I think most people who have projects, or who have experimental forks to Scala have just put them on other project hosting sites like BitBucket and GitHub. Also, the number of Scala commiters has grown substantially since then, so there are more people who can contribute their ideas directly to the main Scala project rather than going through an intermediate step.
My suggestion would be to pick a social code site, put your library there, and then post to the Scala mailing list about it.
BTW, I never considered the Scala library itself, probably because of how Java always worked, i.e. you couldn't really contribute to the JDK. How does that work with Scala? Are there requirements and scope, or can any nitwit, like myself, commit various random code to it?
--
http://erikengbrecht.blogspot.com/
« Return to Thread: Introduction
| Free embeddable forum powered by Nabble | Forum Help |
