#5 Write a beginner's guide to using Trac for Community Blog
Closed: Invalid 4 years ago Opened 5 years ago by jflory7.

As discussed in the [https://meetbot.fedoraproject.org/fedora-meeting-2/2015-11-10/fedora-meeting-2.2015-11-10-17.01.html IRC meeting] today, an introductory post to using Trac is a good idea to helping make onboarding new contributors just a little bit easier. Trac can be a high barrier to entry for many contributors, so breaking it down into less scary parts in an informative article is a good idea.

keekri is leading this task, I am also assisting. Drafting will be done in the Community Blog WordPress - comments and discussion are welcome in this ticket!

Also worth noting is a little more research into seeing what the Fedora Docs Team may have already created to help document this for users. First priority for this is to research what already exists.


Maybe I should start by working on own Trac-fu.

If you need any suggestion, take a peek also [https://fedoraproject.org/wiki/How_to_use_trac here]-
IMO it would be good keep them linked in some way, so people reading would be aware of both existences.

When done, please ping me so I can edit that page linking the CommOps one.

Gabri

Replying to [comment:3 mailga]:

If you need any suggestion, take a peek also [https://fedoraproject.org/wiki/How_to_use_trac here]-
IMO it would be good keep them linked in some way, so people reading would be aware of both existences.

Thanks for this info, Gabri! This is super useful ammo.

When done, please ping me so I can edit that page linking the CommOps one.
Noted!

Brought up in 2015-12-08 meeting; deferred to later in 2016. Not a major priority for the time being but still planned.

Discussed in [https://fedoraproject.org/wiki/Meeting:CommOps_2016-02-02 2016-02-02 meeting].

I am taking on responsibility for this ticket to try to throw something together by the end of the month. It was acknowledged that every sub-group uses Trac a little bit differently, so the focus of this article would be to introduce it from a very basic, low-level perspective, and then maybe link to other team's Tracs as examples of how their workflows differ. It's a flexible idea, and I'll have more to report at the end of the month.

Also, once this is finished, we will need to decide where we want to put it. For now, it's for the Community Blog, but I'd like to put it somewhere a little more noticeable as well. I'm worried that a resource like this might be buried on the CommBlog.

After discussion via e-mail and IRC, I am going to take responsibility for this ticket as well as the Trac Wiki modernization.

In light of the big push for Trac / FedoraHosted to be the new primary method of filing tickets (like we are doing now), I don't think this issue is still relevant. I'm going to close it as wontfix.

@jflory7 changed the status to Invalid

4 years ago

Login to comment on this ticket.

Metadata