Hi Marketing and Magazine teams,
Since we decided to split Magazine from Marketing, having Magazine ML and IRC Channel separate from Marketing (Marketing meeting for August 30, 2016) we were working really fine. But now we hit a stone, Magazine have no Pagure or trac to follow tickets/issues.
For now, we are working with Marketing Pagure, and we have 3 issues related to the Magazine: 208, 233, and 239.
The idea with this mail is to discuss with both teams if we should split magazine's issues from Marketing Pagure, being Magazine still a subproject of Marketing.
Br,
On 10/11/2016 10:05 AM, Eduard Lucena wrote:
Hi Marketing and Magazine teams,
Since we decided to split Magazine from Marketing, having Magazine ML and IRC Channel separate from Marketing (Marketing meeting for August 30, 2016) we were working really fine. But now we hit a stone, Magazine have no Pagure or trac to follow tickets/issues.
For now, we are working with Marketing Pagure, and we have 3 issues related to the Magazine: 208, 233, and 239.
The idea with this mail is to discuss with both teams if we should split magazine's issues from Marketing Pagure, being Magazine still a subproject of Marketing.
Br,
Hey Eduard, thanks for starting this thread. I'll rehash what I said in the meeting, but I think that a Pagure repository specific to the Fedora Magazine isn't necessary. Even though the Magazine is still a little more split off from Fedora Marketing, I believe that it is still a "sub-sub-project" of Marketing. A lot of interests that Marketing may have now and in the future may be of interest for the Fedora Magazine.
I also think a Trac just for the Magazine won't be heavily used. Anything technical can be filed on the Fedora Infrastructure Pagure, and Magazine editors can take a look on the Fedora Marketing Pagure too (there's a fair bit of overlap).
This is my 2¢ but I'm open to what others think would work best or is least confusing.
On Wed, Oct 12, 2016 at 11:33:32PM -0400, Justin W. Flory wrote:
On 10/11/2016 10:05 AM, Eduard Lucena wrote:
Hi Marketing and Magazine teams,
Since we decided to split Magazine from Marketing, having Magazine ML and IRC Channel separate from Marketing (Marketing meeting for August 30, 2016) we were working really fine. But now we hit a stone, Magazine have no Pagure or trac to follow tickets/issues.
For now, we are working with Marketing Pagure, and we have 3 issues related to the Magazine: 208, 233, and 239.
The idea with this mail is to discuss with both teams if we should split magazine's issues from Marketing Pagure, being Magazine still a subproject of Marketing.
Br,
Hey Eduard, thanks for starting this thread. I'll rehash what I said in the meeting, but I think that a Pagure repository specific to the Fedora Magazine isn't necessary. Even though the Magazine is still a little more split off from Fedora Marketing, I believe that it is still a "sub-sub-project" of Marketing. A lot of interests that Marketing may have now and in the future may be of interest for the Fedora Magazine.
I also think a Trac just for the Magazine won't be heavily used. Anything technical can be filed on the Fedora Infrastructure Pagure, and Magazine editors can take a look on the Fedora Marketing Pagure too (there's a fair bit of overlap).
This is my 2¢ but I'm open to what others think would work best or is least confusing.
I would think we could get by with "magazine" tagged issues for now, given the volume. If that were to change, hopefully that means a good problem to have. ;-)
marketing@lists.fedoraproject.org