Steve Eichert: > * How can we be more transparent about what we are working on, and > where we are heading? A blog? A weekly posting? > > I'm not as concerned with the medium of the information (blog, this > mailing list, wiki) as long as the community has access to the > information. A daily or weekly or as often as possible scrum like > status update that the community would be able to see would be cool. > > What did you work on since the last update > What will you be working on until the next scheduled update > What's getting in the way of progress
This is an excellent idea - would folks prefer a Monday or a Friday update? > <warning_thinking_out loud_without_giving_it_much_thought> > Conceptually a git like repo seems like it would offer some > interesting advantages. I'm a git newbie, but from what I've heard > and read it really encourages people to fork projects and play around > with different ideas. Currently, I can't see what anyone else in the > community is working on, let alone the IronRuby team itself. I think > in order to foster a real community around IronRuby we need to not > only make the ironRuby team itself more transparent, but increase the > transparency of the community as a whole. Perhaps IronRuby should > jump on the github bandwagon? :) > </warning_thinking_out_loud_without_giving_it_much_thought> The nice thing about GIT is that you can use they're GIT->SVN bridge and work in a GIT repro on your own box while syncing changes to SVN. So there's nothing stopping you from using GIT today if you want ... Thanks, -John _______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
