John Nilsson <
john@...> writes:
> On Mon, 2007-09-24 at 12:18 +0200, martin odersky wrote:
> > Rather than putting the
> > other style down, it is *much better* to write great
> > examples/turorials/libraries which show how one's favorite style can
> > be used beautifully in Scala.
>
> Why not have community library? A code repository where almost anyone
> will get commit-access. This would be used as a dumping ground for code
> used more or less as a wiki.
I like your ideas about the community contributing code. Certainly
patches are welcome via the issue tracker, and they do go in if they
seem right.
For most community-contributed code, however, I believe that packages
are a betert arrangements. Packages leave the code's author in direct
control o that code's future. Further, they remove EPFL from the loop
for most decisions about propagating the package. The authors can
instead directly post their stuff and try to get people to use them.
For package-based contributions, my best ideas are (1) posting your
project on a site like Google Code or SourceForge, and (2) sharing it
via sbaz. More info is here:
http://scala.sygneca.com/projects/startThat's just my current thinking of course, and I expect the best
mechanisms and culture will need to be felt out over time.
What do you and others think? What can be done to support
non-EPFL folks in sharing Scala code with each other?
-Lex