[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] Things Committers Should Know, December 2008

Thanks for your comments Martin. I've rolled them into the version on the wiki.

Wayne

Oberhuber, Martin wrote:
Hi Wayne,

looks nice!

Couple more ideas:

1. In an effort to reduce the number of hyperlinks, remove
   the link to the AC, leaving only the one to the "Committers
   should know" archive. Its breadcrumb allows navigating up
   to the main AC wiki.

2. Instead of "For more information, ..." it may be better to say
   "These mailings are also archived on the Architecture Council
   Wiki [2]".

3. Replace parentheses which are harder to read by commas:
   ... Poster [3], the definitive guide to the Eclipse IP
   Process,

4. For the bugzilla reference, avoid unnecessary text:
   "In fact, the document is currently under review [4] for
   its next iteration" where [4] refers to the bug.

I was also considering a reference to the "What's new" link / RSS feed, but at the moment I don't actually find this link
very helpful so we may want to defer referencing it to a later
time.


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 Beaton
Sent: Tuesday, December 09, 2008 8:24 PM
To: eclipse.org-architecture-council
Subject: 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 Diligence

Hello Eclipse Committer. This is a first note in a new series of "Things Committers Should Know". Each month, the Architecture Council [1] 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[2]. 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 [3] (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 [4]). You are also required to move 3rd party dependencies [4]-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.

[1] http://wiki.eclipse.org/index.php?title=Architecture_Council
[2] http://wiki.eclipse.org/index.php?title=Architecture_Council/T
hings_Committers_Should_Know
[3] http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf
[4] https://bugs.eclipse.org/bugs/show_bug.cgi?id=256789
[5] http://www.eclipse.org/org/documents/Eclipse_Policy_and_Proced
ure_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. But
did you know that the IP Process Poster [1] 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 [2] 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 Beaton
Sent: Thursday, December 04, 2008 6:43 PM
To: eclipse.org-architecture-council
Subject: [eclipse.org-architecture-council] Things Committers Should Know,December 2008


Hey folks. I've put together a first entry [1]. 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=

[1] 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-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.

_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/eclipse.org-architect
ure-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.
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architect
ure-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.

_______________________________________________
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.