On Mon, Apr 4, 2016 at 9:18 AM, James Bishop <james@xxxxxxxxxxxxxx> wrote: > On Mon, 2016-04-04 at 00:42 -0400, Justin W. Flory wrote: >> On 04/03/2016 10:59 AM, Sylvia Sánchez wrote: >> > >> > Hi Justin! >> > Your link doesn't exist or has no text... Is it right? >> > >> > >> > Cheers! >> > >> Yes, nothing is there yet, but the info we are looking at drafting up >> is >> intended to go there. >> >> -- >> Cheers, >> Justin W. Flory >> jflory7@xxxxxxxxx >> >> -- >> marketing mailing list >> marketing@xxxxxxxxxxxxxxxxxxxxxxx >> http://lists.fedoraproject.org/admin/lists/marketing@lists.fedoraproj >> ect.org > > Hi Justin, > > Thanks for getting back to me yet. The big thing I was wondering about > was what was already done, since I saw a few names already attached to > the ticket. I was also concerned about stepping on toes due to going > ahead and doing stuff without checking in first. This is a totally normal thing to wonder about, and I have an answer for you: Just Do It. Do the things. Your are implicitly powered, as a member of the Fedora community, to dive in an contribute. You don't need my permission, or the marketing team's, or anyone else's. Most of us would rather celebrate progress than have you block on process. In the event that you do make a mistake, the wiki is revision controlled, and we can revert it if we need to, or migrate your work to a different place. > The one question that I had was where I should put my work. Does it go > on the TRAC, or the wiiki? Think of the wiki as the "whiteboard" or "working document," and the Trac as the place where we track the task at hand. There can be information sharing and flow between them, but generally, Trac is the place where we update everyone with links and progress, and the wiki is where we collaboratively edit the content. Hope This Helps, --RemyD. -- Remy DeCausemaker Fedora Community Lead & Council <decause@xxxxxxxxxx> https://whatcanidoforfedora.org -- marketing mailing list marketing@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/marketing@xxxxxxxxxxxxxxxxxxxxxxx