[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mdt-ocl.dev] Making useful progress
|
Ed,
Thanks for starting this discussion. Here's my $0.02 (if I may):
- I would recommend always having another committer review changes; the EMF and UML2 teams both work this way. Rather than trying to manage several CVS branches, why not attach patches to the Bugzilla record (the way EMF and UML2 do)?
- I would highly recommend exchanging as much communication as possible via this list - that's what it is for, and this is open source after all. Of course, the wiki is another good place to exchange ideas.
- The time for collecting potential features for next year's Helios release is now. Folks tend to work on what benefits their organization the most (and they should have that right) but ultimately what's in the best interest of the component's three communities (vendor/consumer, developer, user) should be your guide.
- Technically, breaking API changes should be avoided, unless there is a compelling reason to do so. Additive changes can be made as long as there is a deprecation/migration plan. Perhaps you could start a wiki page to start gathering input on features and poential API changes for next year...
Cheers,
Kenn
On Wed, Jun 17, 2009 at 2:45 PM, Ed Willink
<ed@xxxxxxxxxxxxx> wrote:
Hi All
Some collaboration ideas
CVS integrity
-------------
When Christian moderated CVS constributions, he was able to ensure
very few accidents as a result of his diligence and knowledge.
The new committers have much less experience, so I suggest that all
enhancements other than simple fixes be performed in CVS branches
and announced as ready 2 weeks prior to a milestone so that at least
one other committer can review them prior to merging into HEAD.
Communication
-------------
I know that Adolfo is keen on IM. I'm not a fan of IM, though maybe
I'm not familiar with a good tool.
I find a two way live text interaction very unsatisfactory. I would expect a 3 or 4
way to be even worse. You gain a little in an ability to correct misconceptions
quickly but lose dreadfully from an ability to express thoughts clearly.
When we have an agenda of topics that need close discussion maybe. I would much
prefer to extend Bugzilla conversations for now.
Plans
-----
I suggest we produce a list of the Bugzillas and see who volunteers
for some, and who can be persuaded to do other important ones.
API changes
-----------
We should try to identify what API changes we are considering as soon
as possible and ensure that they are available for discussion on this
the mdt-ocl.dev list, with some references from the NewsGroup for
anything controversial.
Regards
Ed Willink
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
