Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 498538

Summary:	Migrate CONTRIBUTING file into CONTRIBUTING.md file and merge with contributor guide, migrate adopters guide into README.md.
Product:	[Tools] GEF	Reporter:	Alexander Nyßen <nyssen>
Component:	Misc	Assignee:	Alexander Nyßen <nyssen>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	1.0.0
Target Milestone:	5.0.0 (Oxygen) M2
Hardware:	All
OS:	All
Whiteboard:

Description Alexander Nyßen

2016-07-27 03:12:55 EDT

We should turn our CONTRIBUTING files into a Markdown-formatted ones and merge the contributor guide into them. This way, gef and gef-legacy could have their own contributor guides (we would no longer have to mention both streams in the guide), and it would directly be visible in the GitHub repository.

Comment 1 Alexander Nyßen

2016-07-27 03:14:09 EDT

In addition, the adopters guide could be integrated directly into the README.md file, so adopters can easily find steps to getting started.

Comment 2 Alexander Nyßen

2016-08-06 10:03:12 EDT

Created an initial CONTRIBUTING.md for eclipse/gef. Updated eclipse/gef README.md to point to it instead of the contributor guide.

Comment 3 Alexander Nyßen

2016-08-13 12:20:44 EDT

The contributor guides have been properly migrated for GEF and GEF-Legacy now. The contributor guide in the GEF wiki now refers to both. 

What remains here is to update the README for GEF-Legacy to provide a "getting started" section, so the adopters guide can as well be removed (for GEF this is already the case).

Comment 4 Alexander Nyßen

2016-08-14 07:34:07 EDT

Added a getting started section to the README.md of gef-legacy now as well. I have updated the adopters guide in the GEF wiki to point to the README.md files of gef and gef-legacy.

Resolving as fixed for 5.0.0 M2.