From michelle.olson at sun.com Fri Jun 1 11:18:21 2007 From: michelle.olson at sun.com (Michelle Olson) Date: Fri, 01 Jun 2007 11:18:21 PDT Subject: [content-discuss] Re: need help--opensolaris weekly news Message-ID: <22439930.1180721931883.JavaMail.Twebapp@oss-app1> Hiya Rainer, Thanks for this question, I have one additional volunteer who mailed me offline, so that makes four of us--very cool! More are always welcome. Here's the process as I understand it and an example news report from Glynn below for reference. Process: 1. subscribe to a few lists. (From what I already subscribe to regularly, I know that Rainer is active on sysadmin-discuss, Paul is active on storage, maybe zfs/nfs lists too?, Joythi watches docs-discuss, any others Joythi? I watch ogb-discuss, tools-discuss, website-discuss, osol-announce. Need someone for that Big osol-discuss list.) 2. Set up folders to filter the list mail. (I don't actually do this, but it is what Glynn did to manage this originally. My email sorting/processes stink, so I'm a very bad example, I have one folder, it is called Inbox :) 3. At end of the week, go into the folders and spend a few hours pulling out summaries of discussions, quotes that are interesting, and good tidbits that might have been lost in the slew of mails. 4. After you have a little blurb or two from each folder, map the blurbs to the URLs for the associated threads on opensolaris.org and put them in a new file, then empty the folders of all mail. 5. Put all the little blurbs with URLs to the discussion threads into one mail. 6. Send that one mail to osol-discuss and osol-announce lists for the benefit of community. See below for an example from a while back, looks like Glynn usually cited about 15-20 items in each weekly digest. We can alter this if we want to, we can have one person each week, or we can combine the effort, which might make more sense. So, we'd each contribute blurbs each week from the lists we already watch. See below for example. (I also copy content-discuss here because they used to house the Newsletter, which is no longer being written, so they might want to join this effort instead and possibly host it on their pages, since folks go there for the old newletters already.) Thanks all, much appreciated! -Michelle Hey, Another week goes by, but some more good progress being made. Nice work all! Glynn == > > Derek Cicero announced [1] that build 47 of Solaris Express Community Release > > was now available for download. > > > > 1. http://mail.opensolaris.org/pipermail/opensolaris-announce/2006-September/000252.html > > > > Jim Grisanzio mailed [2] to say that DTrace had won the Wall Street Journal's > > 2006 Technology Innovation Award. Congratulations to Bryan, Mike, and Adam. > > > > 2. http://mail.opensolaris.org/pipermail/opensolaris-announce/2006-September/000253.html > > > > Steve Lau announced [3] that the sources for build 48 of ON were now available, > > along with the usual Mercurial changeset. > > > > 3. http://mail.opensolaris.org/pipermail/opensolaris-announce/2006-September/000259.html > > > > Stephen Hahn mailed [4] the latest meeting notes from the CAB, with discussion > > of the governance/constitution, and some discussion about the need to localize > > certain entry points into opensolaris.org, along with some details of the > > starter kit. > > > > 4. http://mail.opensolaris.org/mailman/private/cab-discuss/2006-September/000636.html > > > > Bonnie Corwin mailed [5] to say that the program roadmap for OpenSolaris has > > been updated. > > > > 5. http://mail.opensolaris.org/pipermail/program-team/2006-September/000319.html > > 6. http://opensolaris.org/os/about/roadmap/ > > > > Dan Price posted [7] details of his changes to webrev, including further visual > > cleanup, improved non-wx operation, getopts command line driven interface, and > > other improvements picked up from the various RFE's logged previously. Dan asked > > if anyone had access to Internet Explorer, or Safari, that he would be grateful > > if it could be tested out on those platforms. > > > > 7. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000854.html > > > > Venky Tv posted [8] a guide for new Mercurial users on the OpenSolaris wiki. > > Feel free to contribute. > > > > 8. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000861.html > > > > On top of Steve's bugzilla installation [9], Keith Wesolowski questioned [10] > > whether this would cause the death of progress being made to open up bugster > > where project teams would favour the current open bugzilla installation. Steve > > argued [11] that that it was definitely meant to be a short term solution, and > > that he did not favour a mass migration of all the current set of bugs, let > > alone figure out any confidentiality issues. Valerie Anne Bubb provided [12] > > a bit of historial content, having been Solaris' representative talking to the > > bugster team previously. Rich Lowe provided [13] some context on the current > > stresses of not having an open bug tracking system. Karyn Ritter assured [14] > > that while progress was slow going, that it was a priority, and that external > > experiences would be an invaluable prod to getting things moving. > > > > 9. http://bugs.grommit.com/ > > 10. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000864.html > > 11. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000867.html > > 12. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000870.html > > 13. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000875.html > > 14. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000877.html > > > > Steve Lau posted [15] a heads up that the current ONNV community has how been > > renamed ON [16]. > > > > 15. http://mail.opensolaris.org/pipermail/website-discuss/2006-September/000897.html > > 16. http://opensolaris.org/os/community/on > > > > Nils Nieuwejaar mailed [17] with a heads up that BrandZ has been integrated into > > mainline Solaris, available in build 49. Congratulations to the BrandZ team. > > > > 17. http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-September/020234.html > > > > Eric Lowe proposed [18] a new virtualization project, to provide DMA memory > > infrastructure, required for developing new high-performance DDI DMA interfaces > > with improved RAS. > > > > 18. http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-September/020259.html > > > > Alan Hargreaves mailed [19] with details of the non-debug bits for build 49. > > > > 19. http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-September/020300.html This message posted from opensolaris.org From Tim.Foster at Sun.COM Fri Jun 1 11:43:59 2007 From: Tim.Foster at Sun.COM (Tim Foster) Date: Fri, 01 Jun 2007 19:43:59 +0100 Subject: [content-discuss] Re: need help--opensolaris weekly news In-Reply-To: <22439930.1180721931883.JavaMail.Twebapp@oss-app1> References: <22439930.1180721931883.JavaMail.Twebapp@oss-app1> Message-ID: <1180723439.107334.225.camel@cranialtrauma> Hi Michelle & all, On Fri, 2007-06-01 at 11:18 -0700, Michelle Olson wrote: > Thanks for this question, I have one additional volunteer who mailed > me offline, so that makes four of us--very cool! More are always > welcome. Here's the process as I understand it and an example news > report from Glynn below for reference. Glynn posted something to the OGB about this (and in my recent May news summary, I was polling for volunteers too[1]) http://mail.opensolaris.org/pipermail/ogb-discuss/2007-May/000507.html When I do the monthly news summaries for the IE-OSUG, I pretty much just wander through mail.opensolaris.org, looking at the monthly archives across as many lists as I can and pick out mails that looks interesting. eg. http://mail.opensolaris.org/pipermail/zfs-discuss/2007-May If there were a weekly category (and "last-weekly", so the switchover to this week's news wouldn't clobber the old stuff) on mail.opensolaris.org, it'd make these a lot easier to put summarise without necessarily having to subscribe to every list - anyone know if it's possible to do that ? I'd be happy to cover zfs-discuss for you if you like? (as well as continuing the monthly (higher-level) summaries for the ie-osug) cheers, tim [1] http://mediacast.sun.com/share/timf/opensolaris-may07-in-review.pdf http://mediacast.sun.com/share/timf/ie-osug-10.mp3 -- Tim Foster, Sun Microsystems Inc, Solaris Engineering Ops http://blogs.sun.com/timf From michelle.olson at sun.com Fri Jun 1 11:52:34 2007 From: michelle.olson at sun.com (michelle olson) Date: Fri, 01 Jun 2007 11:52:34 -0700 Subject: [content-discuss] Re: need help--opensolaris weekly news In-Reply-To: <1180723439.107334.225.camel@cranialtrauma> References: <22439930.1180721931883.JavaMail.Twebapp@oss-app1> <1180723439.107334.225.camel@cranialtrauma> Message-ID: <46606AF2.40306@sun.com> Hi Tim, I didn't know you were doing this for your User Group, very cool. Thanks for volunteering to watch zfs-discuss, that is a huge one! Much appreciated, we now have 5 volunteers, you guys rock! I don't know the answer to your question below, I always just use the jive forums and not mail.opensolaris.org. (I learn something obvious and new each moment of every day on this project!) I copy back docs-discuss in case someone there knows the answer. -Michelle Tim Foster wrote: > Hi Michelle & all, > > On Fri, 2007-06-01 at 11:18 -0700, Michelle Olson wrote: > >> Thanks for this question, I have one additional volunteer who mailed >> me offline, so that makes four of us--very cool! More are always >> welcome. Here's the process as I understand it and an example news >> report from Glynn below for reference. >> > > Glynn posted something to the OGB about this (and in my recent May news > summary, I was polling for volunteers too[1]) > > http://mail.opensolaris.org/pipermail/ogb-discuss/2007-May/000507.html > > When I do the monthly news summaries for the IE-OSUG, I pretty much just > wander through mail.opensolaris.org, looking at the monthly archives > across as many lists as I can and pick out mails that looks interesting. > > eg. http://mail.opensolaris.org/pipermail/zfs-discuss/2007-May > > If there were a weekly category (and "last-weekly", so the switchover to > this week's news wouldn't clobber the old stuff) on > mail.opensolaris.org, it'd make these a lot easier to put summarise > without necessarily having to subscribe to every list - anyone know if > it's possible to do that ? > > I'd be happy to cover zfs-discuss for you if you like? > (as well as continuing the monthly (higher-level) summaries for the > ie-osug) > > cheers, > tim > > > [1] > http://mediacast.sun.com/share/timf/opensolaris-may07-in-review.pdf > http://mediacast.sun.com/share/timf/ie-osug-10.mp3 > > From Bonnie.Corwin at Sun.COM Fri Jun 1 12:20:37 2007 From: Bonnie.Corwin at Sun.COM (Barbara Corwin) Date: Fri, 01 Jun 2007 13:20:37 -0600 Subject: [content-discuss] Re: need help--opensolaris weekly news In-Reply-To: <22439930.1180721931883.JavaMail.Twebapp@oss-app1> References: <22439930.1180721931883.JavaMail.Twebapp@oss-app1> Message-ID: <46607185.8010902@Sun.COM> Just FYI, the newsletter continues to be written. It is here: http://opensolaris.org/os/project/content/newsletter Bonnie Michelle Olson wrote: > Hiya Rainer, > > Thanks for this question, I have one additional volunteer who mailed me offline, so that makes four of us--very cool! More are always welcome. Here's the process as I understand it and an example news report from Glynn below for reference. > > Process: > > 1. subscribe to a few lists. > > (From what I already subscribe to regularly, I know that Rainer is active on sysadmin-discuss, Paul is active on storage, maybe zfs/nfs lists too?, Joythi watches docs-discuss, any others Joythi? I watch ogb-discuss, tools-discuss, website-discuss, osol-announce. Need someone for that Big osol-discuss list.) > > 2. Set up folders to filter the list mail. > > (I don't actually do this, but it is what Glynn did to manage this originally. My email sorting/processes stink, so I'm a very bad example, I have one folder, it is called Inbox :) > > 3. At end of the week, go into the folders and spend a few hours pulling out summaries of discussions, quotes that are interesting, and good tidbits that might have been lost in the slew of mails. > > 4. After you have a little blurb or two from each folder, map the blurbs to the URLs for the associated threads on opensolaris.org and put them in a new file, then empty the folders of all mail. > > 5. Put all the little blurbs with URLs to the discussion threads into one mail. > > 6. Send that one mail to osol-discuss and osol-announce lists for the benefit of community. > > See below for an example from a while back, looks like Glynn usually cited about 15-20 items in each weekly digest. We can alter this if we want to, we can have one person each week, or we can combine the effort, which might make more sense. So, we'd each contribute blurbs each week from the lists we already watch. See below for example. > > (I also copy content-discuss here because they used to house the Newsletter, which is no longer being written, so they might want to join this effort instead and possibly host it on their pages, since folks go there for the old newletters already.) > > Thanks all, much appreciated! > > -Michelle > > > Hey, > > Another week goes by, but some more good progress being made. Nice work all! > > Glynn > > == > > >>>Derek Cicero announced [1] that build 47 of Solaris Express Community Release >>>was now available for download. >>> >>>1. http://mail.opensolaris.org/pipermail/opensolaris-announce/2006-September/000252.html >>> >>>Jim Grisanzio mailed [2] to say that DTrace had won the Wall Street Journal's >>>2006 Technology Innovation Award. Congratulations to Bryan, Mike, and Adam. >>> >>>2. http://mail.opensolaris.org/pipermail/opensolaris-announce/2006-September/000253.html >>> >>>Steve Lau announced [3] that the sources for build 48 of ON were now available, >>>along with the usual Mercurial changeset. >>> >>>3. http://mail.opensolaris.org/pipermail/opensolaris-announce/2006-September/000259.html >>> >>>Stephen Hahn mailed [4] the latest meeting notes from the CAB, with discussion >>>of the governance/constitution, and some discussion about the need to localize >>>certain entry points into opensolaris.org, along with some details of the >>>starter kit. >>> >>>4. http://mail.opensolaris.org/mailman/private/cab-discuss/2006-September/000636.html >>> >>>Bonnie Corwin mailed [5] to say that the program roadmap for OpenSolaris has >>>been updated. >>> >>>5. http://mail.opensolaris.org/pipermail/program-team/2006-September/000319.html >>>6. http://opensolaris.org/os/about/roadmap/ >>> >>>Dan Price posted [7] details of his changes to webrev, including further visual >>>cleanup, improved non-wx operation, getopts command line driven interface, and >>>other improvements picked up from the various RFE's logged previously. Dan asked >>>if anyone had access to Internet Explorer, or Safari, that he would be grateful >>>if it could be tested out on those platforms. >>> >>>7. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000854.html >>> >>>Venky Tv posted [8] a guide for new Mercurial users on the OpenSolaris wiki. >>>Feel free to contribute. >>> >>>8. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000861.html >>> >>>On top of Steve's bugzilla installation [9], Keith Wesolowski questioned [10] >>>whether this would cause the death of progress being made to open up bugster >>>where project teams would favour the current open bugzilla installation. Steve >>>argued [11] that that it was definitely meant to be a short term solution, and >>>that he did not favour a mass migration of all the current set of bugs, let >>>alone figure out any confidentiality issues. Valerie Anne Bubb provided [12] >>>a bit of historial content, having been Solaris' representative talking to the >>>bugster team previously. Rich Lowe provided [13] some context on the current >>>stresses of not having an open bug tracking system. Karyn Ritter assured [14] >>>that while progress was slow going, that it was a priority, and that external >>>experiences would be an invaluable prod to getting things moving. >>> >>>9. http://bugs.grommit.com/ >>>10. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000864.html >>>11. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000867.html >>>12. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000870.html >>>13. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000875.html >>>14. http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000877.html >>> >>>Steve Lau posted [15] a heads up that the current ONNV community has how been >>>renamed ON [16]. >>> >>>15. http://mail.opensolaris.org/pipermail/website-discuss/2006-September/000897.html >>>16. http://opensolaris.org/os/community/on >>> >>>Nils Nieuwejaar mailed [17] with a heads up that BrandZ has been integrated into >>>mainline Solaris, available in build 49. Congratulations to the BrandZ team. >>> >>>17. http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-September/020234.html >>> >>>Eric Lowe proposed [18] a new virtualization project, to provide DMA memory >>>infrastructure, required for developing new high-performance DDI DMA interfaces >>>with improved RAS. >>> >>>18. http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-September/020259.html >>> >>>Alan Hargreaves mailed [19] with details of the non-debug bits for build 49. >>> >>>19. http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-September/020300.html > > > > This message posted from opensolaris.org > _______________________________________________ > content-discuss mailing list > content-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/content-discuss From Jim.Grisanzio at Sun.COM Sun Jun 3 19:34:36 2007 From: Jim.Grisanzio at Sun.COM (Jim Grisanzio) Date: Mon, 04 Jun 2007 11:34:36 +0900 Subject: [content-discuss] Re: need help--opensolaris weekly news In-Reply-To: <46607185.8010902@Sun.COM> References: <22439930.1180721931883.JavaMail.Twebapp@oss-app1> <46607185.8010902@Sun.COM> Message-ID: <46637A3C.4060700@sun.com> Yes, we are still writing the newsletter but we've been low key about it lately. After the OGB approves the Advocacy Community proposal, I'll move the newsletter to that community and delete the Content Project: http://opensolaris.org/jive/thread.jspa?threadID=29342&tstart=0 Jim Barbara Corwin wrote: > Just FYI, the newsletter continues to be written. It is here: > > http://opensolaris.org/os/project/content/newsletter > > Bonnie > > > Michelle Olson wrote: >> Hiya Rainer, >> >> Thanks for this question, I have one additional volunteer who mailed >> me offline, so that makes four of us--very cool! More are always >> welcome. Here's the process as I understand it and an example news >> report from Glynn below for reference. >> >> Process: >> >> 1. subscribe to a few lists. >> >> (From what I already subscribe to regularly, I know that Rainer is >> active on sysadmin-discuss, Paul is active on storage, maybe zfs/nfs >> lists too?, Joythi watches docs-discuss, any others Joythi? I watch >> ogb-discuss, tools-discuss, website-discuss, osol-announce. Need >> someone for that Big osol-discuss list.) >> >> 2. Set up folders to filter the list mail. >> >> (I don't actually do this, but it is what Glynn did to manage this >> originally. My email sorting/processes stink, so I'm a very bad >> example, I have one folder, it is called Inbox :) >> >> 3. At end of the week, go into the folders and spend a few hours >> pulling out summaries of discussions, quotes that are interesting, and >> good tidbits that might have been lost in the slew of mails. >> >> 4. After you have a little blurb or two from each folder, map the >> blurbs to the URLs for the associated threads on opensolaris.org and >> put them in a new file, then empty the folders of all mail. >> >> 5. Put all the little blurbs with URLs to the discussion threads into >> one mail. >> >> 6. Send that one mail to osol-discuss and osol-announce lists for the >> benefit of community. >> >> See below for an example from a while back, looks like Glynn usually >> cited about 15-20 items in each weekly digest. We can alter this if we >> want to, we can have one person each week, or we can combine the >> effort, which might make more sense. So, we'd each contribute blurbs >> each week from the lists we already watch. See below for example. >> (I also copy content-discuss here because they used to house the >> Newsletter, which is no longer being written, so they might want to >> join this effort instead and possibly host it on their pages, since >> folks go there for the old newletters already.) >> >> Thanks all, much appreciated! >> >> -Michelle >> >> >> Hey, >> >> Another week goes by, but some more good progress being made. Nice >> work all! >> >> Glynn >> >> == >> >> >>>> Derek Cicero announced [1] that build 47 of Solaris Express >>>> Community Release >>>> was now available for download. >>>> >>>> 1. >>>> http://mail.opensolaris.org/pipermail/opensolaris-announce/2006-September/000252.html >>>> >>>> >>>> Jim Grisanzio mailed [2] to say that DTrace had won the Wall Street >>>> Journal's >>>> 2006 Technology Innovation Award. Congratulations to Bryan, Mike, >>>> and Adam. >>>> >>>> 2. >>>> http://mail.opensolaris.org/pipermail/opensolaris-announce/2006-September/000253.html >>>> >>>> >>>> Steve Lau announced [3] that the sources for build 48 of ON were now >>>> available, >>>> along with the usual Mercurial changeset. >>>> >>>> 3. >>>> http://mail.opensolaris.org/pipermail/opensolaris-announce/2006-September/000259.html >>>> >>>> >>>> Stephen Hahn mailed [4] the latest meeting notes from the CAB, with >>>> discussion >>>> of the governance/constitution, and some discussion about the need >>>> to localize >>>> certain entry points into opensolaris.org, along with some details >>>> of the >>>> starter kit. >>>> >>>> 4. >>>> http://mail.opensolaris.org/mailman/private/cab-discuss/2006-September/000636.html >>>> >>>> >>>> Bonnie Corwin mailed [5] to say that the program roadmap for >>>> OpenSolaris has >>>> been updated. >>>> 5. >>>> http://mail.opensolaris.org/pipermail/program-team/2006-September/000319.html >>>> >>>> 6. http://opensolaris.org/os/about/roadmap/ >>>> >>>> Dan Price posted [7] details of his changes to webrev, including >>>> further visual >>>> cleanup, improved non-wx operation, getopts command line driven >>>> interface, and >>>> other improvements picked up from the various RFE's logged >>>> previously. Dan asked >>>> if anyone had access to Internet Explorer, or Safari, that he would >>>> be grateful >>>> if it could be tested out on those platforms. >>>> >>>> 7. >>>> http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000854.html >>>> >>>> >>>> Venky Tv posted [8] a guide for new Mercurial users on the >>>> OpenSolaris wiki. >>>> Feel free to contribute. >>>> >>>> 8. >>>> http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000861.html >>>> >>>> >>>> On top of Steve's bugzilla installation [9], Keith Wesolowski >>>> questioned [10] whether this would cause the death of progress being >>>> made to open up bugster where project teams would favour the current >>>> open bugzilla installation. Steve argued [11] that that it was >>>> definitely meant to be a short term solution, and that he did not >>>> favour a mass migration of all the current set of bugs, let alone >>>> figure out any confidentiality issues. Valerie Anne Bubb provided >>>> [12] a bit of historial content, having been Solaris' representative >>>> talking to the bugster team previously. Rich Lowe provided [13] some >>>> context on the current >>>> stresses of not having an open bug tracking system. Karyn Ritter >>>> assured [14] >>>> that while progress was slow going, that it was a priority, and that >>>> external >>>> experiences would be an invaluable prod to getting things moving. >>>> >>>> 9. http://bugs.grommit.com/ >>>> 10. >>>> http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000864.html >>>> >>>> 11. >>>> http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000867.html >>>> >>>> 12. >>>> http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000870.html >>>> >>>> 13. >>>> http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000875.html >>>> >>>> 14. >>>> http://mail.opensolaris.org/pipermail/tools-discuss/2006-September/000877.html >>>> >>>> >>>> Steve Lau posted [15] a heads up that the current ONNV community has >>>> how been >>>> renamed ON [16]. >>>> >>>> 15. >>>> http://mail.opensolaris.org/pipermail/website-discuss/2006-September/000897.html >>>> >>>> 16. http://opensolaris.org/os/community/on >>>> >>>> Nils Nieuwejaar mailed [17] with a heads up that BrandZ has been >>>> integrated into >>>> mainline Solaris, available in build 49. Congratulations to the >>>> BrandZ team. >>>> >>>> 17. >>>> http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-September/020234.html >>>> >>>> >>>> Eric Lowe proposed [18] a new virtualization project, to provide DMA >>>> memory >>>> infrastructure, required for developing new high-performance DDI DMA >>>> interfaces >>>> with improved RAS. >>>> >>>> 18. >>>> http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-September/020259.html >>>> >>>> >>>> Alan Hargreaves mailed [19] with details of the non-debug bits for >>>> build 49. >>>> >>>> 19. >>>> http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-September/020300.html >>>> >> >> >> >> This message posted from opensolaris.org >> _______________________________________________ >> content-discuss mailing list >> content-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/content-discuss > > _______________________________________________ > content-discuss mailing list > content-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/content-discuss From Jim.Grisanzio at Sun.COM Tue Jun 19 18:21:15 2007 From: Jim.Grisanzio at Sun.COM (Jim Grisanzio) Date: Wed, 20 Jun 2007 10:21:15 +0900 Subject: [content-discuss] Re: Re: Status of the Content Project In-Reply-To: <464DF6C5.2050509@rushmores.net> References: <19461425.1179435529454.JavaMail.Twebapp@oss-app1> <464DF6C5.2050509@rushmores.net> Message-ID: <4678810B.9060906@Sun.COM> Hi .... a little update: I migrated the Newsletter content from the Content Project over to the new Advocacy Community Group. All new newsletter content will be posted to the Advocacy CG. I'll ask Derek to put the url re-directs in for that newsletter content when he has a chance, and we'll delete the Content Project when we open the Advocacy CG. Probably in a couple of weeks. Jim -- Jim Grisanzio http://blogs.sun.com/jimgris From Jim.Grisanzio at Sun.COM Thu Jun 21 22:31:49 2007 From: Jim.Grisanzio at Sun.COM (Jim Grisanzio) Date: Fri, 22 Jun 2007 14:31:49 +0900 Subject: [content-discuss] Re: Re: Status of the Content Project In-Reply-To: <4678810B.9060906@Sun.COM> References: <19461425.1179435529454.JavaMail.Twebapp@oss-app1> <464DF6C5.2050509@rushmores.net> <4678810B.9060906@Sun.COM> Message-ID: <467B5EC5.9090209@Sun.COM> Jim Grisanzio wrote: > Hi .... a little update: I migrated the Newsletter content from the > Content Project over to the new Advocacy Community Group. All new > newsletter content will be posted to the Advocacy CG. I'll ask Derek to > put the url re-directs in for that newsletter content when he has a > chance, and we'll delete the Content Project when we open the Advocacy > CG. Probably in a couple of weeks. > > Jim Someone suggested to me another option for the Content Project. Instead of closing it, it's been suggested that perhaps the Content Project can be re-vitalized and re-orged to be a project within the Advocacy Community Group. Or more accurately, the Advocacy CG would sponsor the effort and become associated with. I'm willing to give this a shot, and I can't imagine anyone in the Advocacy CG would have a problem with it. However, it would have to be proposed and approved (casually, of course), and I can't do it alone. I'm happy to contribute to the effort, but I need help. Offers? Thoughts? Good idea? Bad? Jim -- Jim Grisanzio http://blogs.sun.com/jimgris From Michelle.Olson at Sun.COM Fri Jun 22 13:49:25 2007 From: Michelle.Olson at Sun.COM (Michelle.Olson at Sun.COM) Date: Fri, 22 Jun 2007 13:49:25 -0700 Subject: [content-discuss] Re: Re: Status of the Content Project In-Reply-To: <467B5EC5.9090209@Sun.COM> References: <19461425.1179435529454.JavaMail.Twebapp@oss-app1> <464DF6C5.2050509@rushmores.net> <4678810B.9060906@Sun.COM> <467B5EC5.9090209@Sun.COM> Message-ID: <467C35D5.2050604@Sun.COM> Hi Jim, Documentation & L10N communities already endorse the Content Project and we'd like to see it continue forward (obviously). I thought that was clear from the short thread about unhiding the project? Why are you so keen to close this project? It is valid, sponsored, and has active contributors who are also active in the sponsoring communities. We have a few irons in the fire WRT to the VMware article update from Bill and Nacho continues his work to update translated version. I'd rather not see this go into the Advocacy area, when it already has appropriate sponsorship through docs. You are free to drop off as a leader if that suits you. I copy docs alias on this to see if others want to comment either way. Thanks, Michelle Jim Grisanzio wrote: > Jim Grisanzio wrote: > >> Hi .... a little update: I migrated the Newsletter content from the >> Content Project over to the new Advocacy Community Group. All new >> newsletter content will be posted to the Advocacy CG. I'll ask Derek >> to put the url re-directs in for that newsletter content when he has a >> chance, and we'll delete the Content Project when we open the Advocacy >> CG. Probably in a couple of weeks. >> >> Jim > > > > Someone suggested to me another option for the Content Project. > > Instead of closing it, it's been suggested that perhaps the Content > Project can be re-vitalized and re-orged to be a project within the > Advocacy Community Group. Or more accurately, the Advocacy CG would > sponsor the effort and become associated with. I'm willing to give this > a shot, and I can't imagine anyone in the Advocacy CG would have a > problem with it. However, it would have to be proposed and approved > (casually, of course), and I can't do it alone. I'm happy to contribute > to the effort, but I need help. > > Offers? Thoughts? Good idea? Bad? > > Jim