Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • O org.eclipse.dash.handbook
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 155
    • Issues 155
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse ProjectsEclipse Projects
  • Technology
  • Eclipse Dash
  • org.eclipse.dash.handbook
  • Issues
  • #3
Closed
Open
Issue created Jan 08, 2013 by Eclipse Webmaster@webmasterOwner

All Eclipse project Git repositories must include a contribution guide

Submitted by Krum Tsvetkov

Link to original bug (#397644)

Description

Created attachment 225328 draft proposal for the recommendation

There was a proposal on the cross-project-issues list that projects should provide an explicit target definition: http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg08372.html

The proposal was discussed on the AC meeting on 13 Dec 2012: http://wiki.eclipse.org/Architecture_Council/Meetings/December_13_2012#New_Topics

As not all projects are using Tycho as a build technology, the outcome of the discussion was to provide a more general recommendation that projects should provide a "how to contribute" page, and describe that using an explicit target definition is one good option for handling the dependencies.

We also discussed that it could be useful to give some concrete examples of contribution guides.

I tried to write up a draft for such a recommendation. However, I'm not sure where to put it in Wiki, so for now I attach it as plain text here.

What could be a proper place in the Wiki for such a recommendation? I will format it then and put it there, instead of using a txt file :)

What do you think about the attached description? I think it would be nice to have also other technical options described, but my own experience so far is with using Tycho and I couldn't write it.

What about the examples? I just picked a few, but haven't really looked into all projects.

Attachment 225328, "draft proposal for the recommendation":
Recommendation_Target_Platform.txt

Blocking

  • Bug 404585
Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent