[MacPorts] #49742: website update - keywords and cc field clarification
#49742: website update - keywords and cc field clarification ----------------------------+-------------------- Reporter: nhoj.patrick@… | Owner: jmpp@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: website | Version: 2.3.4 Keywords: haspatch | Port: ----------------------------+-------------------- this patch is based upon feedback from raising tickets, to aid others more clearly understand what to put into the keywords field and also what to no put into the cc field. -- Ticket URL: <https://trac.macports.org/ticket/49742> MacPorts <https://www.macports.org/> Ports system for OS X
#49742: guide update - keywords and cc field clarification -----------------------------+---------------------- Reporter: nhoj.patrick@… | Owner: markd@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: Resolution: | Keywords: haspatch Port: | -----------------------------+---------------------- Changes (by ryandesign@…): * owner: jmpp@… => markd@… * version: 2.3.4 => * component: website => guide Comment: Thanks. I don't like that we repeat in the guide a subset of the list of keywords documented in DraftKeywordGuidelines. Either the guide should refer to the list in the Trac wiki, or the list in the Trac wiki should be moved into the guide and the Trac wiki modified to refer to the guide. The list of email addresses one should not Cc should also include one's own email address. -- Ticket URL: <https://trac.macports.org/ticket/49742#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#49742: guide update - keywords and cc field clarification -----------------------------+---------------------- Reporter: nhoj.patrick@… | Owner: markd@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: Resolution: | Keywords: haspatch Port: | -----------------------------+---------------------- Comment (by nhoj.patrick@…): I think this is what I'm trying to help with others that don't use trac daily/weekly. After you referring to DraftKeywordGuildines, I think this is the secret hidden magic foo I've been missing too. I've been raising tickets for a few years but it's the first time it's been mentioned or talked about. If you think about the user journey. I want to raise a defect, okay the obvious link to head to is New Ticket ( https://trac.macports.org/newticket ) This has two references; - https://guide.macports.org/#project.tickets - https://trac.macports.org/wiki/TracTickets I suggest that my keywords part of the patch is changed so that it refer to https://trac.macports.org/wiki/DraftKeywordGuidelines so then what they keywords are close to trac. Regarding the link how should that be done? using the fully qualified url or are their any special tags I should use? -- Ticket URL: <https://trac.macports.org/ticket/49742#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#49742: guide update - keywords and cc field clarification -----------------------------+---------------------- Reporter: nhoj.patrick@… | Owner: markd@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: Resolution: | Keywords: haspatch Port: | -----------------------------+---------------------- Changes (by raimue@…): * cc: raimue@… (added) Comment: If we link to the keywords from the guide, we should drop the "Draft*" prefix from the wiki page. They are widely used as documented now in the tickets, so we should just adopt them as official policy. ''openmaintainer'' and ''nomaintainer'' should not be formatted as mail addresses. Where would users pick this up? If a user adds themselves to CC, do they get multiple mails? If not, there is no harm if users accidentally do this. Fewer instructions are better. -- Ticket URL: <https://trac.macports.org/ticket/49742#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts