|Re: [eclipse.org-architecture-council] Things Committers Should Know, December 2008|
Thanks for your comments Martin. I totally agree with the change in tone.It's an interesting coincidence that I've recently exchanged notes with several committers who needed this information...
Here's the text that I'd like to send: -- Subject: Eclipse Intellectual Property Due DiligenceHello Eclipse Committer. This is a first note in a new series of "Things Committers Should Know". Each month, the Architecture Council  sends out a short note describing some important aspect of life as an Eclipse committer. We hope that these notes are valuable and informative. For more information, please see the "Things Committers Should Know" page. This month, we're going to touch briefly on Intellectual Property (IP) Due Diligence.
As an Eclipse Committer, you certainly know about IP Due diligence. But did you know that the "Eclipse Legal Process" Poster  (the definitive guide to the Eclipse IP Process) has been updated several times in the past year to pick up new special cases? In fact, the document is currently under review for its next iteration (see bug 256789 ). You are also required to move 3rd party dependencies —whether or not they are to be included in your project's CVS/SVN repository or made accessible for download—through the IP Process.
In the coming months, we'll talk more specifically about these important resources. In the meantime, if you have any questions about the IP Due Diligence process, please ask your project leader, your PMC, or one of your project's Architecture Council mentors. http://wiki.eclipse.org/index.php?title=Architecture_Council/Things_Committers_Should_Know
 http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf  https://bugs.eclipse.org/bugs/show_bug.cgi?id=256789 http://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf
--Additional comments welcome. I intend to send this out on behalf of the Architecture Council tomorrow around 12pm et.
Thanks, Wayne Oberhuber, Martin wrote:
Hi Wayne, +1 for the intro, the links and the last paragraph. In the middle, I think I'd prefer to see the wording changed such that the nugget highlights more what's likely unknown. We shouldn't talk about things that we expect committers know already, but highlight what's likely unknown. For instance, like this:As an Eclipse Committer, you certainly know about IP Due diligence. Butdid you know that the IP Process Poster  has been updated several times in the past year to pick up new special cases? And, did you also know that since June 2008 you're also required to push 3rd party dependencies  through the IP Process? <<<<<<<< By focusing more on what's likely unknown, I'd hope that we keep readers interested. I'm afraid that when they get a feeling like "gee I know this already" after the first few words, we might loose some readers. Cheers, -- Martin Oberhuber, Senior Member of Technical Staff, Wind River Target Management Project Lead, DSDP PMC Member http://www.eclipse.org/dsdp/tm-----Original Message-----From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf Of Wayne BeatonSent: Thursday, December 04, 2008 6:43 PM To: eclipse.org-architecture-councilSubject: [eclipse.org-architecture-council] Things Committers Should Know,December 2008Hey folks. I've put together a first entry . Your feedback is invited.I feel a little bit like I'm punting with this first one. The requirement to keep things concise makes this a lot harder than I thought. Still, making sure that people are at least aware of the existence of these two documents is important.I'd like to send this out next week. Thanks, Wayne= http://wiki.eclipse.org/Architecture_Council/Things_Committers_Should_Know/Staging#December_2008 _______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-architect ure-councilIMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal._______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
Back to the top