Michelle Olson wrote: > Peter Tribble wrote: >> * OGB 2007/001 Project Instantiation Policy Approved on April >> 25th, 2007 >> >> For as long as we're operating under the current constitution, this >> policy is good. Insofar as there's the potential for major reform to >> simplify the whole process, major effort to revise the policy seems >> unwarranted. (The only things I will note are the naming of a >> specific individual [Eric] as project herald, and the statement on >> 4.1 that there's a project naming policy.) >> > I agree with your comments on this policy above. Eric is no longer > Project Herald (I believe Jim Grisanzio fills this role today). So, > the implementation notes should be updated to reflect the Project > Herald change and we should ask Jim if there is a naming policy > currently in use. >
Yes, I set up projects now. That takes place on project-setup. People post proposals and questions there. Regarding names: In general, I follow Sun`s trademark policy and specifically the posting instructions document for project names: "Solaris and OpenSolaris are trademarks of Sun Microsystems, Inc. that are used to identify Sun products/services. They are used as an adjective, followed by an appropriate noun. It is best/safest to not use these on community and project web pages, particularly in titles." http://opensolaris.org/os/trademark/ http://opensolaris.org/os/projects/posting_instr/ (trademarks section at the top) Inserting a link or short text about naming into project instantiation policy would be good because people usually get to the "posting instructions" document after they get to the project instantiation policy (thanks for pointing that out a couple of months ago, Peter). Overall, since the project instantiation policy is not part of the current constitution, I don`t see why it can`t be replaced easily with Glynn`s project lifecycle policy, which was intended as one of the process documents supporting the new constitution. That would simplify things on the project lifecycle front immediately. But this need not be a distraction with getting the charter/constitution updated and getting the community prepared for a new vote (which is the obvious issue to solve at the moment). We have very few dev project requests now, and I can deal with their issues individually. Also, the largest number of new project requests are coming from the OSUGs, and I`ve been dealing with them in Advocacy since the beginning. For OSUGs, though, we don`t use the project instantiation policy because it`s too complex. Instead, we use an edited version written in a few sentences. Jim -- http://blogs.sun.com/jimgris/
