Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344156 - Tracking of WikiText doc contributions
Summary: Tracking of WikiText doc contributions
Status: RESOLVED WONTFIX
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: IP Log Tool (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Wayne Beaton CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-28 11:58 EDT by John Arthorne CLA
Modified: 2018-03-27 15:56 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2011-04-28 11:58:14 EDT 
A number of projects "crowd source" their documentation use the Eclipse wiki and Mylyn's WikiText. Essentially this allows you to export doc from the wiki and convert it to Eclipse doc format. It then gets consumed in a build and released along with the code in the release distribution. From an IP perspective all contributions to Eclipsepedia are subject to the Eclipse SUA, so I think in general we are covered. However, I don't know of any way to record such wiki-originated contributions in the IP log. Perhaps the IP tooling could help with scraping contributor names from the wiki?
Comment 1 Wayne Beaton CLA 2011-04-28 12:19:59 EDT 
Wikimedia must provide a mechanism for this. I'll look into it.
Comment 2 Eclipse Genie CLA 2015-01-02 06:02:25 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2018-02-24 17:17:31 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Wayne Beaton CLA 2018-03-27 15:56:04 EDT 
WONTFIX.