Removing of hurdles #5
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR is to remove hurdles without sacrificing quality and opportunity 1. I do not see the relevance on requiring a certain timeframe for the PyCon APAC conference to be held. That should be the prerogative of the organizing party and local conditions, and it's up to them to try to fit with the rest of APAC's schedule (or US's PyCon), but should not be a hard requirement. 1. I also do not see the justification of making 5 the minimum number of people in the PyCon APAC team. Steve Holden started PyCon US basically alone. I _do_ understand though that a one person team might be a little unrealistic, so I am suggesting three: 1 chairperson, 1 co-chair to back up the chair person in case she/he is unavailable, and 1 person who handles the cash. All other tasks can basically be juggled between these 3, and they can find help along the way if they need. 1. Food and social events should not be made a requirement, but maybe good-to-haves. I think this should also be a prerogative of the organizers. 1. The rest of the proposal structure which I have proposed to be removed are items which I think will not affect the quality of the conference, but instead put needless hurdles on the organizers. These points will basically put only certain locales into consideration.
| @@ -89,7 +89,7 @@ off by the PAC before they can be put in place. | |||
| 2. The on-site team must be geographically located in a country in the Asia | |||
| Pacific and Australasia region. | |||
|
|
|||
| 3. The on-site team must be willing to actively coordinate with the PAC board | |||
There was a problem hiding this comment.
PAC == PyCon APAC Committee. Changing it to APAC looks wrong. But we might change "PAC board" to "PAC".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to remove hurdles without sacrificing quality and opportunity
All other tasks can basically be juggled between these 3, and they can find help along the way if they need.