Closed Bug 1242948 Opened 9 years ago Closed 9 years ago

Replace {{Xref_csstime}} occurrences with {{cssxref("<time>")}}

Categories

(Developer Documentation Graveyard :: Macros/Templates, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: teoli, Unassigned, Mentored)

References

Details

(Whiteboard: [good first bug])

We have 42 occurrences of {{xref_csstime}}, a macro we want to delete [1]. This task is about to go on each of these MDN pages, to edit the page and to replace the occurrence of {{xref_csstime}} with {{cssxref("<time>")}}, to save it and to check that the link is working. You need an MDN account and the ability to use a WYSIWYG editor to perform this task. [1] https://developer.mozilla.org/en-US/search?locale=*&kumascript_macros=xref_csstime
Hi Jean, I can solve this bug if you want. Can you assign me to it ?
Hello, I just got my environment set up and am looking for a good first bug (preferably mentored), if this one is still available I would like to contribute if anyone here can assign me to it.
(In reply to Tanner Parker [tparker12] from comment #2) > Hello, I just got my environment set up and am looking for a good first bug > (preferably mentored), if this one is still available I would like to > contribute if anyone here can assign me to it. (Copying mostly the same content from my reply to Tanner's email) This is a documentation bug, not a development bug. So it doesn't need you to setup the development environment. You just need to create an account on MDN (Mozilla Developer Network - developer.mozilla.org) and you can edit the pages containing documentation to fix what's needed for the bug. If you are looking for coding/development kind of bugs/tasks to work on, take a look at www.joshmatthews.net/bugsahoy/ and choose a category other than "MDN / Developer Documentation". But if you are indeed looking for a documentation bug, you should probably pick a different documentation bug from http://www.joshmatthews.net/bugsahoy/?mdn=1 as guillaume already seems to be working on this.
To reduce confusion like this, we should keep the *Assigned To* field up to date.
Flags: needinfo?(saurabh)
(In reply to Saurabh Nair [:jsx] from comment #3) > (In reply to Tanner Parker [tparker12] from comment #2) > > Hello, I just got my environment set up and am looking for a good first bug > > (preferably mentored), if this one is still available I would like to > > contribute if anyone here can assign me to it. > > (Copying mostly the same content from my reply to Tanner's email) > > This is a documentation bug, not a development bug. So it doesn't need you > to setup the development environment. You just need to create an account on > MDN (Mozilla Developer Network - developer.mozilla.org) and you can edit the > pages containing documentation to fix what's needed for the bug. > > If you are looking for coding/development kind of bugs/tasks to work on, > take a look at www.joshmatthews.net/bugsahoy/ and choose a category other > than "MDN / Developer Documentation". > > But if you are indeed looking for a documentation bug, you should probably > pick a different documentation bug from > http://www.joshmatthews.net/bugsahoy/?mdn=1 as guillaume already seems to be > working on this. Thank you for the reply, I ended up working on coding/development bugs as per my open source class. Good day :)
(In reply to rolfedh from comment #4) > To reduce confusion like this, we should keep the *Assigned To* field up to > date. Yep, I agree.
I do agree too, I missed Guillaume message. Guillaume: are you still interested to work on this bug?
Flags: needinfo?(guillaume.heras)
Is the bug fixed ? I have 0 document found on your link : https://developer.mozilla.org/en-US/search?locale=*&kumascript_macros=xref_csstime Else I'm always interested, I just work in parallel on others problems.
Flags: needinfo?(guillaume.heras)
Oh it is. I didn't checked! Thanks all!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
It was a pleasure to help :).
You need to log in before you can comment on or make changes to this bug.