[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [eclipse.org-architecture-council] Things Committers Should Know, December 2008
- From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
- Date: Thu, 4 Dec 2008 19:22:12 +0100
- Delivered-to: firstname.lastname@example.org
- Thread-index: AclWOC2606qgcDdYSy+v4hZMfS/u6wABH86w
- Thread-topic: [eclipse.org-architecture-council] Things Committers Should Know, December 2008
+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  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.
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
> -----Original Message-----
> From: 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 . 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.
> eclipse.org-architecture-council mailing list
> 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.