Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cross-linking issues with forum topics and vice versa #18

Open
aschrijver opened this issue Oct 11, 2018 · 6 comments
Open

Cross-linking issues with forum topics and vice versa #18

aschrijver opened this issue Oct 11, 2018 · 6 comments
Assignees
Labels
project Relates to project structure and documentation

Comments

@aschrijver
Copy link
Contributor

Need to create links to forum topics in the various README's and create forum topics that have a copy of the Proposal issues from Github in them and a link to GH issue.

@aschrijver aschrijver added the project Relates to project structure and documentation label Oct 11, 2018
@aschrijver aschrijver self-assigned this Oct 11, 2018
@ghost
Copy link

ghost commented Oct 11, 2018

and create forum topics that have a copy of the Proposal issues from Github in them and a link to GH issue

Warning regarding posting copies of proposals on the forum: I am not in favor of having two copies of the same document in different places. Not only it adds overhead (which we could do without), but importantly it would incite many members to start commenting on the forum in addition to comments on Github. We need to encourage everyone interested in these projects to come to Github instead.

I'd rather propose we post just a one sentence summary and the link to Github once a proposal is finalized and pushed to the repository.

@aschrijver
Copy link
Contributor Author

aschrijver commented Oct 11, 2018

That is true. I won't maintain the copy on the forum. Instead it has a 'Latest version' link to github. A copy is required for people who are not part of the campaigners team. I want to keep discussions going on in the forum for 2 reasons:

  1. To keep attracting new campaigners/members to the project
  2. Because github should be focused on work, tasks, and doing things. All the general discussion will be very hard to handle otherwise. This is where the forum is better (especially with non-technical people not used to working with issue management on OSS projects)

@ghost
Copy link

ghost commented Oct 11, 2018

@aschrijver, I understand you feel the need to attract as much attention as possible, hence opening up multiple avenues.

But it will be an incredible mess (think of the cross-coordination that would involve) if there were to be two avenues for comments and discussions on the same topics/deliverables.

Sorry, but I have to strongly disagree here. Let us keep all detailed discussions on Github.

@aschrijver
Copy link
Contributor Author

aschrijver commented Oct 11, 2018

I am just saying it is a one-time copy. And one-time creation of a topic per proposal. There is no cross-synchronisation afterwards. These forum topics may be a mess, and they will. A mess you do not want here.

Or are you saying you just want the one Call for Participation topic and nothing more? That will be even messier there, and the forum will forget about this project.

PS. I'm off to bed. 1.18am here.

@ghost
Copy link

ghost commented Oct 11, 2018

What I am proposing:

Let us say we finalize a proposal/issue. There is nothing wrong (on the contrary) with posting an update on the forum, but that update would be as the sample below:

Subject: Reality Shock campaign - new video script ("Dirty Laundry")

The proposed script for this new video, which depicts a man going through the aftermath of a massive data breach, is near completion. To see discussions and give your comments, please go to (Github link to the issue).

@aschrijver
Copy link
Contributor Author

This task is now part of the Aware Prepare: Growth hacking the Awareness Campaigns project campaign.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
project Relates to project structure and documentation
Projects
None yet
Development

No branches or pull requests

1 participant