Rottenchester wrote: > There are a couple of bugs we're working in sapling that are claimed > to be fixed in the wikis branch. But, as I mentioned this morning, > none of the wikis code has been checked in. It seems like a waste > for us to go out and re-fix those bugs, and it is also a lost > opportunity to start to merge wikis and trunk.
Yes, I wholeheartedly agree. I personally debated even getting involved with sycamore development. I've seen many OS projects that have great promise but just weren't set up in a way that make contributing code easy and welcomed (ie UCSD's Rocks). When the developer community doesn't have access to the mainline code, that throws up a red flag for me. I don't like wasting my personal time for a project that I won't have at least some sense of ownership in. As a problem solver, I like solving new problems not old ones. > Anyway, I'm offering this up to try to start a constructive > conversation, and hope it's taken in that spirit. I also agree. Conversation is a good thing (and there is no ill will in my words). Also, I wouldn't be as active on this list as I am if I thought this project couldn't get past these growing pains. So ya, one more vote for a wikispot dump. Scott _______________________________________________ Sycamore-Dev mailing list [EMAIL PROTECTED] http://www.projectsycamore.org/ https://tools.cernio.com/mailman/listinfo/sycamore-dev
