Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-reviews-dev] Project status

Hello Steffen,
We have taken a look at the re-structuring document.

The idea of keeping the reviews sub-project structure flat makes sense and will help facilitate collaboration, specially since we can separate within the same project as Components in Bugzilla as well as in the Git repository

We have the following questions:
  1. There are no R4E committers listed under the SCM project, I think there shall be at least one R4E committer under the SCM project. 
  2. The suggested Git components under Mylyn Reviews don't seem to be under the same project (??)
  3. Is it possible to use shorter names under the Git components e.g.
org.eclipse.mylyn.reviews/framework
org.eclipse.mylyn.reviews/tbr
org.eclipse.mylyn.reviews/r4e
org.eclipse.mylyn.reviews/gerrit

Best Regards
/Alvaro for R4E Team


On Thu, Sep 23, 2010 at 2:56 PM, Steffen Pingel <steffen.pingel@xxxxxxxxxxx> wrote:
Thanks for the update, Mario. It's unfortunate that the ESE talks got rejected. I'll be attending the conference either way and would be happy to meet up if anyone else is going, too.

I didn't hear anyone from the Reviews project respond to the restructuring discussion on today's call. I basically suggested that instead of creating sub-sub-project for R4E and Gerrit to proceed with a single Mylyn Reviews project that holds all components. Everyone involved gets commit rights and social conventions are used to limit commits to certain parts rather than Unix permissions.

My experience is that particularly in the early stages of development features tend to require changes in the reference implementation as well as the framework and often overlap between references implementations. Not having commit rights on all components can hamper development speed and it's often better to revert a change than be blocked on an review or merging of a patch. It also encourages contributions to the framework and avoid code duplication.

I'd be curious to know what your thoughts are about this proposal: http://wiki.eclipse.org/Mylyn/Restructuring#Reviews_.28Incubation.29 ? I am in favor of keeping the structure as simple as possible which always leaves the option to split out sub-sub-projects later on if needed.

Steffen



On Thu, Sep 23, 2010 at 9:55 AM, Mario Bernhart <mario.bernhart@xxxxxxxxxxxxxxxxx> wrote:
> Hi all,
>
> I want to give you a short overview of the project status:
>
> - Our talk at ESE was bounced. Steffen informed me that "there is no love
> for Mylyn" and all Mylyn related talks were rejected.
> https://www.eclipsecon.org/submissions/ese2010/view_talk.php?id=1728
>
> - Alvaro made some progress on the model
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=324327
>
> - Steffen extracted a set of classes that could be reused from the Atlassion
> Connector for the inline commenting feature
> http://github.com/spingel/mylyn-reviews
>
> - Steffen filed a CQ for the Gerrit Connector
> https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4453
>
> - I started the Gerrit Connector proposal
> http://wiki.eclipse.org/Reviews/GerritConnectorProposalDraft
>
> - Stefan (not Steffen :) shared his implementation of the changeset
> detection feature
> http://github.com/sreiterer/mylyn-reviews-scm-integration
>
> I would propose those dates for an online followup to the Vancouver meeting:
> http://www.doodle.com/8gwnhb3qwf373xs4
>
> Please discuss the next actions via the mailing list.
>
> Mario
>
>
> _______________________________________________
> mylyn-reviews-dev mailing list
> mylyn-reviews-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-reviews-dev
>



--
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com


_______________________________________________
mylyn-reviews-dev mailing list
mylyn-reviews-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylyn-reviews-dev



Back to the top