Bug 746139 - The trac page for release-notes is wrong
Summary: The trac page for release-notes is wrong
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: release-notes
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: John J. McDonough
QA Contact: Karsten Wade
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-14 03:03 UTC by Horst H. von Brand
Modified: 2013-02-10 19:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-10 19:45:26 UTC


Attachments (Terms of Use)

Description Horst H. von Brand 2011-10-14 03:03:39 UTC
Description of problem:
In the section on "I want to help with the content" it states a git URL for fedora-doc-utils which is wrong. Shouldn't there be a Fedora package with the relevant tools for people who aren't into tool development?


Also, if you aren't a member of the team, the correct URL for the notes themselves replaces 'ssh://<username>@' with 'git://', which is different from what is stated. Shouldn't really derail any somewhat experienced git user, but nevertheless...

Perhaps there should be a contact for trac issues?

Version-Release number of selected component (if applicable):
Good question, that one ;-)
https://fedorahosted.org/release-notes/

How reproducible:
I suspect I'll see the same each time I connect...

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 John J. McDonough 2011-10-24 12:52:29 UTC
I noticed some of those same issues.

Comment 2 Pete Travis 2013-02-10 19:45:26 UTC
I've just removed the 'fedora-doc-utils' reference; I'm not confident we use it any longer, and if we do, the best place for detailed procedural information would be the relevant wiki pages.

The best point of contact for parts of a project that do not have a dedicated bugzilla component would be that project's mailing list. Horst, you are very welcome to contact us at docs.org or in #fedora-docs on freenode. The group would jump at the opportunity to facilitate your contribution.


Note You need to log in before you can comment on or make changes to this bug.