-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For #6 in particular we should have consensus on framework as a starting point. SpringMVC seems like the right choice.
Marlon On 3/25/11 11:07 AM, Scott Wilson wrote: > > On 25 Mar 2011, at 14:48, Franklin, Matthew B. wrote: >> It looks like accounts for us new committers are being created. As we >> prepare to commit the donated code bases, I thought it would be good to >> lay out some of the next steps. The last few weeks seem to have been busy >> for everyone, and we haven't had many discussions regarding what we need >> to do to get Rave moving forward. The following is a list of things I >> think we need to accomplish in the near term. The list is by no means >> comprehensive and there is probably a better place for it to live, but it >> is intended to spark discussion. > > Looks like a good start - thanks for starting the ball rolling! > >> 1. Commit donated code bases >> 2. Finish public website on CMS (think Ross started this?) >> 3. Lay out wiki structure and port relevant portions to Apache wiki (think >> Ate started this?) >> 4. Discuss working agreements for coding practices, quality, unit testing, >> coverage, CI, sandbox environments, etc (Some of this is probably standard >> Apache practice) > > I don't think there is such a thing as a standard Apache coding practice :-) > >> 5. Analyze initial feature list from proposal and review donated feature >> sets >> 6. Discuss high level architecture and agree on basic design >> 7. Agree on process for "cherry picking" features and integrating them >> into the Rave code base > > Well, we can pick things we want to work on and mail the list to say we're > doing it, but beyond that I don't think we can have that much of a process - > anyone can implement any features they want and submit patches for them, its > up to committers whether to commit them. > >> 8. Commit initial project structure and configure CI >> 9. Begin work on features >> >> This list is high-level, but I think it is a good starting place. Time to >> get this project moving forward! > > +1 > >> >> -Matt >> > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNjLDpAAoJEEfVXEODPFIDN+QH/2CXMQGCgDOGo0Lblblbz+Xc XTgQBo/AbXn+qrlhkTiV6OEWwpjaFO/orj0XBIEPKaPvStpSWEaM3yiWvCF3nYCU zvEwADE58H156Xk1323FpnudVkVEfwsQWtxqX9/7yNoV4ndxyWnIl+BeRl5LvSCY QjJt3oqWEcWBtzlF+QnmHbyS5Vz72FV76GK+5hr5S937/quLA86fZOzYtBQ+nhiB fk9yT4TZF3IhMjs2jOGUcn6s0ekq2YRwSO70XTz9xIW5p9fIoZwWyCNJkIP8E0hK GRuY0cjmublbh2B3DKkuV0v6f/O3yQmApyrB/g7v8WSK4W1ykHfujXQAAiNGdqs= =XNoC -----END PGP SIGNATURE-----
